Repository navigation
Conversation
Closes #328 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
Deploying website with
|
| Latest commit: |
4cfc3d7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://aaa28fd9.website-70y.pages.dev |
| Branch Preview URL: | https://claude-node-bonding-fees-doc.website-70y.pages.dev |
|
Closing unmerged. The source ADR ( |
Summary
docs/protocol/network.mdx(NAT traversal) said relays are funded "from the protocol treasury or from node bonding fees". No bonding or registration fee exists anywhere in the protocol: the ADRs (decdn/decdn/adr) define no such fee — the capacity bond is locked and returned on unbonding, and the only fee flows are theFeeRoutersettlement splits (ADR 026). The protocol treasury is a defined, funded entity (15% DAO allocation + the 10% FeeRouter treasury share), so the sentence now names it alone.Picked over "the treasury share of settlement fees" because that would understate the treasury's funding sources (the DAO allocation also feeds it).
Note: the phrase originated in
decdn/decdn/adr/architecture.md("funded from protocol treasury or node staking fees"), which still carries the same undefined fee — fixing that at the source is a follow-up in that repo.Closes #328
🤖 Generated with Claude Code