> For the complete documentation index, see [llms.txt](https://docs.vapinetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapinetwork.ai/stake/contracts.md).

# Staking contracts

Stake is coming soon; its contracts hold active stake, check reviewer eligibility, and provide historical stake checkpoints.

{% hint style="info" %}
Stake is coming soon. This page describes how it works at launch.
{% endhint %}

These contracts hold active stake, read stake for eligibility, and supply the historical data used by the Compute distribution. The roles below follow the staking architecture.

## Contracts and roles

| Contract or module       | Role                                                                                                                                                              |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `VapiStaking`            | Accepts vAPI stake, writes timestamp checkpoints, handles unstake requests, and handles withdrawals. It does not decide reviewer eligibility or dispute payments. |
| `ThresholdReviewersGate` | Reads active stake for reviewer eligibility. It does not move vAPI or register reviewers.                                                                         |
| `ReviewerRegistryV2`     | Manages reviewer seats, verification, and escrow caps. It does not hold stake or cast panel votes.                                                                |
| `DisputeResolverV2`      | Selects panels, handles voting, and pays voters. It does not hold escrow principal.                                                                               |
| `EscrowV1`               | Holds USDC principal and dispute deposits and settles them atomically. It does not send dispute fees to a treasury.                                               |
| Compute control plane    | Reads historical stake for the daily Compute allowance. It does not move vAPI.                                                                                    |

## Fixed parameters

| Parameter                      | Value                                          |
| ------------------------------ | ---------------------------------------------- |
| Unstake cooldown               | `604800` seconds, or 7 days                    |
| Initial reviewer threshold     | `100,000 vAPI`                                 |
| Threshold bounds               | `10,000` to `1,000,000 vAPI`                   |
| Threshold change timelock      | 7 days                                         |
| Compute snapshot and execution | `00:00:00 UTC` and from `00:10 UTC` by default |

## vAPI token on Base

The vAPI token on Base is:

`0x1eA8deB921AA6015f4938010C848140b98108Dd2`

[View the token on BaseScan](https://basescan.org/token/0x1eA8deB921AA6015f4938010C848140b98108Dd2).

Checked on 2026-10-02.


---

# 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.vapinetwork.ai/stake/contracts.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.