# 5.3 Value Accrual Loop: Dual-Token Flywheel

The core innovation is that a single API revenue event simultaneously increases both $QBT scarcity and $qYield yield.

Both effects are deterministic, on-chain, and proportional to usage.

#### Forward Flywheel

1. API demand increases (organic growth or B2B contract execution)
2. More $QBT fee transactions processed through the fee router
3. 15% of fees burned → circulating $QBT supply decreases
4. Reduced supply + increased demand → upward price pressure on $QBT
5. Higher $QBT value → increased operator collateral value → improved overcollateralization → enhanced Vault credit quality
6. Increased net Vault yield → accelerated $qYield buyback-and-burn → $qYield price appreciation
7. Higher $qYield yield attracts new deposits → Vault TVL growth
8. Larger TVL enables more operator loans → more nodes → greater API capacity → returns to Step 1

#### Reverse Spiral: Honest Risk Assessment

**Critical Disclosure:** The same flywheel that amplifies growth may reverse under adverse conditions. Transparent analysis of downside scenarios is essential for informed capital allocation.

*Figure 5.B — Reverse Spiral Phases and Protocol Circuit Breakers*

<table data-header-hidden><thead><tr><th width="71.6666259765625"></th><th width="197.11114501953125"></th><th width="242.888916015625"></th><th></th></tr></thead><tbody><tr><td>Phase</td><td>Negative Trigger</td><td>Cascade Effect</td><td>Protocol Circuit Breaker</td></tr><tr><td>1</td><td>API demand stagnation/decline</td><td>Reduced burn rate; price pressure reverses</td><td>Bootstrap fund subsidy auto-activation</td></tr><tr><td>2</td><td>Sharp $QBT price decline</td><td>Operator collateral falls below LTV threshold</td><td>Dynamic LTV adjustment via governance</td></tr><tr><td>3</td><td>Rising operator defaults</td><td>Insurance fund absorbs losses; eventual depletion</td><td>Automatic lending freeze at threshold</td></tr><tr><td>4</td><td>Vault yield floor breached</td><td>Accelerated withdrawals; TVL decline</td><td>Withdrawal queues + minimum APY support</td></tr><tr><td>5</td><td>Significant TVL decline</td><td>Reduced operator lending; scaling halts</td><td>B2B minimum volume guarantees triggered</td></tr><tr><td>6</td><td>Node count stagnation/decline</td><td>API capacity constraints; SLA degradation</td><td>Existing nodes continue servicing reduced demand</td></tr></tbody></table>

#### Minimum Viable Network (MVN) Threshold

Transitioning from subsidized to organic yield is a critical milestone in protocol maturity.

*Figure 5.C — MVN Quantitative Thresholds*

<table data-header-hidden><thead><tr><th width="150.33331298828125">Text</th><th width="143.3333740234375"></th><th></th></tr></thead><tbody><tr><td>Metric</td><td>MVN Threshold</td><td>Rationale</td></tr><tr><td>Active Nodes</td><td>500</td><td>Sufficient throughput for regional B2B SLA fulfillment</td></tr><tr><td>Monthly API Calls</td><td>10M</td><td>Revenue generation exceeds bootstrap fund burn rate</td></tr><tr><td>Vault TVL</td><td>$25M</td><td>Capital base sufficient for 500-node lending at 150% LTV</td></tr><tr><td>B2B Contract Revenue</td><td>$100K/month</td><td>Baseline recurring revenue for yield floor coverage</td></tr><tr><td>Organic Yield</td><td>≥6% APY</td><td>Competitive with alternative DeFi yield sources</td></tr></tbody></table>

If MVN is not achieved, the bootstrap fund subsidizes yield at 8% minimum APY for 18 months.

Failure to reach MVN within 18 months triggers governance actions, including yield adjustment, fund extension, or structured wind-down. This sunset mechanism prevents indefinite subsidy dependence.


---

# 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://railquant.gitbook.io/quantarail/5.3-value-accrual-loop-dual-token-flywheel.md?ask=<question>
```

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.