docs(glossary): migrate remaining 'staking' terms to 'bonding'

[yigitdot]

Problem

The glossary table in docs/overview/glossary.mdx still uses the old staking terminology. The rest of the docs and site copy were migrated from "staking" to "bonding" in #145, but this glossary table was missed.

Fix

In the glossary table, update the technical protocol references:

• stake → bond
• staked → bonded
• staking → bonding

Concretely, five cells change:

Term	Current	Updated
Client	"No stake, no gossip publish."	"No bond, no gossip publish."
Node	"A staked QUIC endpoint…"	"A bonded QUIC endpoint…"
Peer mesh	"The flat set of all staked nodes."	"The flat set of all bonded nodes."
Stake (term name)	Stake	Bond
TOKEN	"The deCDN staking token…"	"The deCDN bonding token…"

Preserve "stake" only where it is idiomatic (e.g. "having a stake", "skin in the game") rather than a technical protocol verb/noun. The glossary contains no idiomatic uses, so every occurrence in this table should change.

Corrected table

| Term                   | Definition                                                                                                                                                                        |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Blob**               | A content-addressed byte sequence. Every blob is identified by its hash; clients verify received bytes against the known hash.                                                    |
| **Channel (payment)**  | On-chain escrow between client and node that backs off-chain vouchers. Opens with a deposit; settles with the latest voucher.                                                     |
| **Client**             | A lightweight QUIC endpoint that streams content and pays per MB. No bond, no gossip publish.                                                                                     |
| **DHT**                | Kademlia-subset content discovery. Nodes self-publish records when caching a blob.                                                                                                |
| **Gossip**             | Epidemic broadcast over topic channels for node metadata and rate updates.                                                                                                        |
| **Hash sequence**      | An ordered collection of blob hashes (a directory or manifest equivalent).                                                                                                        |
| **Node**               | A bonded QUIC endpoint that caches and delivers blobs. Some are origin-backed; others are pure caches.                                                                            |
| **Origin-backed node** | A node configured with an S3-compatible store, NFS mount, or local disk — the canonical source for specific blobs. Never experiences a true cache miss.                           |
| **Origin backend**     | The opaque storage behind an origin-backed node (S3, R2, B2, MinIO, NFS, local disk). Never exposed to the network.                                                               |
| **Peer mesh**          | The flat set of all bonded nodes. Discovery via gossip; content location via DHT.                                                                                                 |
| **Probe**              | Parallel latency + availability check that runs before any delivery commitment.                                                                                                   |
| **Selection score**    | A combined ranking over advertised price, observed latency, and reputation. Lower is better.                                                                                      |
| **Bond**               | TOKEN locked on-chain by a node to join the mesh — a capacity bond that scales with declared bandwidth. Returned on deregistration after an unbonding period.                     |
| **TOKEN**              | The deCDN bonding token: locked as a node's capacity bond and burned by the buyback sink. Not used for payments; governance weight comes from delivered bytes, not TOKEN balance. |
| **USDC**               | The payment currency for all delivery. Fixed at deployment; channels deposit, voucher, and settle in USDC.                                                                        |
| **Voucher**            | A signed off-chain payment message. The primary payment instrument between client and node.                                                                                       |

---

Originally flagged by @gemini-code-assist[bot] in #145 (comment)

[github-actions]

🎯 Agentic Issue Triage

This is a documentation task to align the glossary with the protocol's renamed terminology: stake/staking → bond/bonding.

The proposed glossary table in the issue body already reflects the target state — the task is to find any remaining occurrences of the old terminology in the docs and update them.

📋 Sub-tasks checklist

• Search content/ and docs/ for occurrences of stake, staked, staking used as technical protocol terms (not idiomatic expressions like "having a stake")
• Update glossary entries to use bond, bonded, bonding per the table in the issue body
• Preserve idiomatic uses of "stake" (e.g. "skin-in-the-game", "having a stake in") — do not rename those
• Verify the updated glossary table renders correctly
• Check TOKEN definition: ensure "bonding token" language is consistent throughout

🔍 Debugging / search strategy

Run a quick ripgrep sweep to find candidates:

# Find protocol-term uses of stake/staking in docs
rg -i '\bstake[sd]?\b|\bstaking\b' content/ docs/ --glob '*.mdx' --glob '*.md'

Then review each hit to distinguish technical uses (rename) from idiomatic uses (keep).

i️ Context

• Originally surfaced by @gemini-code-assist[bot] in PR docs: sync protocol docs to canonical decdn/decdn state #145 review (discussion_r3328864546)
• The glossary table in the issue body already shows the desired end-state — use it as the reference
• Only docs/ content is relevant here (Mintlify source at docs.decdn.org); the main website (app/, components/, content/blog/) likely does not contain this glossary

Generated by Agentic Triage for issue #146 · ● 1.3M · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@c7d030cd6d4607b90d9ac3ffc8b24aff4f251632