Settings
Broadcast propagation
NIP-QW14. Relay is node-to-node: each message type propagates hop by hop under its own policy — how far it travels, how old and how large it may be, how wide each hop fans it out, the minimum folded hop-score to keep relaying, and how long a hop's signed score is reused before it is recomputed. These are the stock defaults a node ships; a relaying node edits its own copy in its client config.
| type | hops | max age | max size | fan-out | score floor | hop-rating TTL | rate/day |
|---|---|---|---|---|---|---|---|
| proposalProposal — an open job call | 3 | 7 d | 8 KiB | 3 | 1.0 | 3 d | 50 |
| demandDemand — work wanted | 4 | 14 d | 4 KiB | 3 | 0.9 | 3 d | 20 |
| profileProfile push | 3 | 30 d | 16 KiB | 2 | 1.0 | 7 d | 5 |
| newsNews | 6 | 30 d | 32 KiB | 4 | 0.8 | 7 d | 10 |
| reviewReview | 4 | 90 d | 8 KiB | 3 | 1.1 | 3 d | 20 |
The coordination server at /api/broadcast is a fan-out-0 rendezvous — it holds valid envelopes and hop-ratings for nodes that were offline when a broadcast passed, and makes no relay decision of its own.