51 Commits

Author	SHA1	Message	Date
Sasha	7cfc36207e	Merge branch 'weboko/waku-send-api' of github.com:waku-org/specs into weboko/waku-send-api	2025-10-08 23:50:05 +02:00
Sasha	79a96a6acf	address review	2025-10-08 23:49:54 +02:00
Sasha	8387ada41c	address comment	2025-10-08 23:43:38 +02:00
Sasha	a25e3b9d3a	Update standards/application/waku-api.md ... Co-authored-by: Ivan FB <128452529+Ivansete-status@users.noreply.github.com>	2025-10-08 15:07:06 +02:00
Sasha	55dfcf950a	add Send API	2025-10-07 00:42:32 +02:00
fryorcraken	e42629eb9c	Rename Waku API's "Waku Config" to "Protocols" Config ... Make it clearer that with this config, we are configuring the Waku protocols, in contrast to other parameters which are more executable related. Related to https://github.com/waku-org/nwaku/issues/3493	2025-10-01 22:21:46 +10:00
fryorcraken	5cd0080f32	remove message confirmation	2025-09-29 21:15:32 +10:00
fryorcraken	6a421f5955	change "sovereign" to "core"	2025-09-26 23:05:58 +10:00
fryorcraken	b9454e3d97	change "relay" to "sovereign"	2025-09-26 16:08:15 +10:00
fryorcraken	7748d6a9ba	add metadata	2025-09-26 16:05:24 +10:00
fryorcraken	214ee738ea	note on errors	2025-09-26 16:00:59 +10:00
fryorcraken	34b94435d5	raw spec	2025-09-26 15:56:10 +10:00
fryorcraken	09e3ade109	clarify scope	2025-09-26 15:53:59 +10:00
fryorcraken	82181bf2c1	fix inconsistencies	2025-09-26 15:47:47 +10:00
fryorcraken	0c64eaac58	integrate feedback	2025-09-26 11:39:49 +10:00
fryorcraken	ad4fb96e7d	prefer entry_nodes	2025-09-26 11:32:23 +10:00
fryorcraken	388c25714f	add toc	2025-09-25 14:03:10 +10:00
fryorcraken	616306e378	Mention trait approach for ETH RPC ... After feedback from @osmaczko	2025-09-25 13:53:04 +10:00
fryorcraken	9d5191f75f	static store default value	2025-09-25 13:50:15 +10:00
fryorcraken	fa5bf8cc4c	finish sentence	2025-09-25 13:48:40 +10:00
fryorcraken	4ab882189d	change address to ipv4 ... So a different fields can be provided for ipv6 when supported	2025-09-25 13:46:35 +10:00
fryorcraken	036fe615ed	change to seed nodes	2025-09-25 13:45:21 +10:00
fryorcraken	6de55db122	change confirmation to store/filter	2025-09-25 13:42:28 +10:00
fryorcraken	a0700f0730	results may return void	2025-09-25 13:35:05 +10:00
fryorcraken	5bb37c24dc	update networking section	2025-09-15 15:31:50 +10:00
fryorcraken	f834dc4346	by default no static store nodes are passed	2025-09-12 17:40:23 +10:00
fryorcraken	40450003ac	use "waku config"	2025-09-12 13:40:54 +10:00
fryorcraken	6c01164f92	only auto sharding, remove mix up on option	2025-09-11 15:51:13 +10:00
fryorcraken	0004fff780	if a default is possible it means values are optional	2025-09-10 15:33:44 +10:00
fryorcraken	a3c37c1be1	if a default is possible it means values are optional	2025-09-10 15:32:06 +10:00
fryorcraken	cf84d3d4a3	Move eth rpc endpoints to top	2025-09-10 14:19:52 +10:00
fryorcraken	f68707ea86	default network message validation	2025-09-10 14:15:23 +10:00
fryorcraken	b2b81b4c2c	remove multiaddr type	2025-09-10 14:02:35 +10:00
fryorcraken	f1225e1cca	Add web3 RPC API URLs	2025-09-09 19:55:56 +10:00
fryorcraken	1ec75279d5	rename function to createNode	2025-09-09 14:49:12 +10:00
fryorcraken	872115a9c0	Apply suggestion from @chaitanyaprem ... Co-authored-by: Prem Chaitanya Prathi <chaitanyaprem@gmail.com>	2025-09-09 13:24:26 +10:00
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