> For the complete documentation index, see [llms.txt](https://docs.stakingrewards.com/staking-data/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakingrewards.com/staking-data/methodologies/polkadot-pattern-substrate-srb/zkverify-srb.md).

# zkVerify SRB

VFYSRB is a benchmark representing the annualized staking rate for the VFY token.

VFYSRB is calculated and published by Staking Rewards via the [zkVerify Profile](https://www.stakingrewards.com/asset/zkverify) and [Data API](https://www.stakingrewards.com/data-api).

> **TL;DR:** zkVerify staking rewards use the Substrate era-based reward model: era validator rewards annualized over 365 days divided by total staked VFY tokens. Validator-level rates are adjusted by commission in the Nominated Proof of Stake system.

### VFY Staking Rewards Rate: VFYSRB

$$
VFYSRB = evr \* t\_y / st
$$

<table><thead><tr><th width="145">Formula Key</th><th width="169">Metric Name</th><th>Description</th></tr></thead><tbody><tr><td>evr</td><td>Era Validator Reward</td><td>The total reward distributed to all validators for the previous era, sourced directly from on-chain storage.</td></tr><tr><td>st</td><td>Staked Tokens</td><td>The total staked VFY in the active era, sourced from on-chain era total stake.</td></tr><tr><td><span class="math">t_y</span></td><td>Year Constant</td><td>1460 eras — used to annualize the per-era reward (6-hour eras, same as Kusama).</td></tr></tbody></table>

* VFYSRB is non-compounded, excluding returns from reinvestment of rewards.
* The reward rate is derived from actual on-chain era rewards, not from an inflation model estimate.
* Both claimed and unclaimed rewards are included.

#### Slashing

* VFYSRB does not factor in the possibility of slashing occurrences.
* zkVerify implements Substrate's standard slashing mechanism. Validators can be slashed for equivocation or prolonged unresponsiveness.

***

### VFY Validator Staking Rewards Rate: VFYSRB(v)

Staking Rewards calculates the VFYSRB for each validator based on their individual era points (performance) and commission rate.

$$
VFYSRB(v) = (vep / tep \* tvr) / t\_m \* t\_y / vst
$$

<table><thead><tr><th width="149">Formula key</th><th width="216">Metric Name</th><th>Description</th></tr></thead><tbody><tr><td><span class="math">vep</span></td><td>Validator Era Points</td><td>Validator era points accumulated in the observation period.</td></tr><tr><td>tep</td><td>Total Era Points</td><td>Total era points for all validators in the observation period.</td></tr><tr><td>tvr</td><td>Total Validator Rewards</td><td>All rewards distributed to all validators in the observation period.</td></tr><tr><td>vst</td><td>Validator Staked Tokens</td><td>Validator staked tokens, self-staked and nominated.</td></tr><tr><td><span class="math">t_y</span></td><td>Year Constant</td><td>365d</td></tr><tr><td><span class="math">t_m</span></td><td>Month Constant</td><td>30d</td></tr></tbody></table>

***

#### Observation Period:

1. The VFYSRB is determined based on the latest completed era at the evaluation point.
2. This data is then annualized for a comprehensive year-long projection.

#### Calculation

The calculation happens every 6 hours and is immediately published via [Data API](https://www.stakingrewards.com/data-api).

#### Limitations

1. VFYSRB employs a 365-day convention for annualizing era reward data. This convention remains consistent and does not accommodate adjustments for leap years.

***

### VFY Real Reward Rate: VFYSRB^R

The real reward rate calculates the reward rate adjusted for inflation in the network.

$$
VFYSRB^R = 1+VFYSRB/(1+ir)-1
$$

<table><thead><tr><th width="147">Formula key</th><th width="148">Metric name</th><th>Description</th></tr></thead><tbody><tr><td>ir</td><td>Inflation Rate</td><td>Fixed at 2.5% annually, as defined in the zkVerify runtime configuration.</td></tr></tbody></table>

**Inflation Rate Behavior**

* zkVerify uses a fixed 2.5% annual inflation rate. All inflation is distributed to validators and nominators — there is no system fee or treasury allocation. 70% of transaction fees are burned, with the remaining 30% going to the block author.

***

### Other zkVerify metrics calculated by Staking Rewards:

<table><thead><tr><th width="212.99999999999994">Metric</th><th>Description</th></tr></thead><tbody><tr><td>Delegated Tokens</td><td>The number of VFY tokens nominated to validators.</td></tr><tr><td>Self Staked Tokens</td><td>The number of VFY tokens staked by validators directly.</td></tr><tr><td>Staking Wallets</td><td>Total number of nominators on-chain.</td></tr></tbody></table>

***

Data Sources:

* zkVerify Substrate RPC (on-chain staking pallet queries via py-substrate-interface)
* CoinGecko for price and circulating supply

***

#### References:

* [zkVerify Documentation](https://docs.zkverify.io/)
* [zkVerify Staking FAQ](https://docs.zkverify.io/node-operators/nominators/nominatorsFAQs)
* [zkVerify Token](https://zkverify.io/token)

***

:books: [Learn more about VFY Staking](https://www.stakingrewards.com/asset/zkverify)

:bar\_chart: [Calculate your VFY Staking Rewards](https://www.stakingrewards.com/calculator?asset=zkverify)

:gear: [Access historic zkVerify Staking Data via API](https://www.stakingrewards.com/data-api)

```
Last updated on 03/13/2026
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.stakingrewards.com/staking-data/methodologies/polkadot-pattern-substrate-srb/zkverify-srb.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.