fryorcraken d05209e837

Proposed different format to express message events ...

Changes:

- `eventType` field is part of the event data, which does not really match how it's done in JS
- `eventType` has a `default` value. Does not really make sense as it's not something the API consumer can pass/change
- `addEventListener` is defined, but this is JS specific, the API should define concepts in a generic manner so it can easily be applied across languages.
- name`EventEmitter` is very generic, but this is an event emitter for messages only
- new `properties` field was introduced, but it is unclear where these properties belong to, we have been using `fields` so far. This should be a field on `WakuNode`

2025-10-28 14:18:13 +11:00

..

dandelion.md

Update dandelion.md

2024-07-09 04:34:01 -04:00

device-pairing.md

Update device-pairing.md

2025-05-22 09:10:25 -04:00

noise-sessions.md

Update noise-sessions.md

2024-07-09 06:03:39 -04:00

noise.md

Update noise.md

2024-07-09 06:17:34 -04:00

p2p-reliability.md

docs: clarify that losses are possible message losses (#59)

2025-03-26 12:34:56 +00:00

rln-keystore.md

Update rln-keystore.md

2025-07-30 21:23:33 -04:00

tor-push.md

Update tor-push.md

2024-07-09 06:26:27 -04:00

waku-api.md

Proposed different format to express message events

2025-10-28 14:18:13 +11:00