15 Commits

Author	SHA1	Message	Date
fryorcraken	bebbe8b284	Add message validation	2025-08-06 16:15:40 +10:00
fryorcraken	6a37950c66	user snake case for field names	2025-08-05 15:28:46 +10:00
fryorcraken	1e312bc2c3	update sharding defaults from previous discussions	2025-08-05 15:27:48 +10:00
fryorcraken	e92d2f8d8e	Change init to create ... As it is commonly used across both js-waku and nwaku code bases.	2025-08-05 15:16:00 +10:00
fryorcraken	6289f91f8f	wip	2025-07-21 22:07:14 +10:00
fryorcraken	4ca0e08038	rework structure, include feedback	2025-06-30 15:25:12 +10:00
fryorcraken	b20f5fd179	rename RFC	2025-06-30 14:39:30 +10:00
fryorcraken	2096211872	remove extra	2025-06-30 14:28:00 +10:00
fryorcraken	73354fd683	Only specify nim and TS naming convention ... Reducing the scope, we can review Rust, Golang and C in a separate PR.	2025-06-30 14:26:25 +10:00
fryorcraken	25984c0b14	Remove shard relay subscription for init config ... Being able to set what shard to subscribe too when initialising a Waku node is a biased towards service nodes. Indeed, subscribing to shard should be done with the `subscribe` API (yet to be defined). Which can be used with a content topic, and pubsub topic (only if static sharding). A service node such as the `wakunode2` binary can still accept "shards to subscribe to" via CLI, but this is unrelated to the Waku node conf, and the `wakunode2` software should simply call `subscribe` when ready.	2025-06-30 14:22:49 +10:00
fryorcraken	95ebcd9ea0	Reducing prescription re language mapping	2025-06-24 13:03:22 +10:00
fryorcraken	d5c688a327	set default value	2025-06-24 12:43:11 +10:00
fryorcraken	adaba5428b	typos and types	2025-06-24 12:23:12 +10:00
fryorcraken	e013c15848	add language translation	2025-06-18 16:34:21 +10:00
fryorcraken	93bd790c25	Propose custom IDL for Waku API definition	2025-06-18 10:13:03 +10:00