# Role-based Incentives $VELOCITY clearly separates responsibilities among participants. This separation reduces systemic risk and aligns incentives with contribution. #### Issuers Issuers are entities such as universities, employers, governments and platforms that **issue digital credentials (**such as ID, degree, skill, license, employment experience.) They: * do **not** stake tokens * do **not** operate nodes * Pay gas fees for writing credential metadata to the ledger. This includes initial Credential registration and Credential revocation (status updates) * are rewarded **only when** their credentials are **verified** Issuers monetize **credential usefulness**. They are compensated on a per-verification basis: credentials that are trusted and relied upon generate recurring revenue; unused credentials do not. #### Oracle Node Operators Node operators maintain the oracle infrastructure and form the **verification layer of the network**. They: * stake $VLCT (self-stake + delegated stake) * participate in verification pipelines * process proof and response flows * earn rewards from fees and emissions * may be slashed for misbehavior Node operators secure verification. They do **not** issue credentials. #### Delegators / Stakers Delegators secure the network **economically** by delegating $VLCT to node operators. They: * back well-behaving nodes * earn a **yield** on staked tokens * are compensated from: * emissions (initial bootstrap phase) * verification fees (long-term steady state) Delegators/Stakers do not need to operate infrastructure. They provide economic security. #### Relying Parties Relying parties are consumers of verifications: * enterprises * platforms * financial institutions * applications and protocols They submit verification requests and pay Trust Ledger Call fees in $VLCT.\ They are the primary **demand engine** of the token economy. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://velocity-network.gitbook.io/velocity-network/usdvlct-tokenomics/editor.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.