Locking REPPO for veREPPO
- Your tokens are illiquid until the lock expires — you cannot withdraw early
- You can reallocate how your veREPPO is distributed across datanets each epoch
- A larger lock and a longer duration both increase your voting power per token
Splitting your REPPO across multiple wallets does not increase your total voting power. The stake-weighted model is designed so that Sybil strategies are economically self-defeating.
Epochs
An epoch is the fundamental time unit of the Reppo protocol — a 48-hour window during which all curation and reward activity takes place:- Publishers submit pods to datanets
- Voters allocate veREPPO across datanets and specific pods
- Voting power decays linearly from the start of the epoch to the end
- Rewards accrue based on vote tallies and fee accumulation
Who earns emissions
REPPO emissions flow to three groups each epoch based on their contribution to the network:Performance Pool distribution
The Performance Pool accumulates from creation fees (50%), publishing fees (10%), and access fees (10%). It distributes every third epoch:- 80% to REPPO stakers
- 20% to datanet owners
Datanets that generate more activity, attract more staked capital, and produce higher fee revenue receive a proportionally larger share of each distribution.
How staking rewards are calculated
Staking is a datanet-level reward mechanism. It is separate from locking REPPO for veREPPO and separate from publishing, and it is designed to reward long-term REPPO holders and high-quality datanet operators. To reduce short-term gaming, datanet scores use 3-epoch smoothing:- 50% from the last epoch
- 30% from epoch -2
- 20% from epoch -3
Amplifi staking
In addition to curation staking, Reppo supports Amplifi staking — a separate staking program with its own reward structure. To record an Amplifi stake:amount, subnetId, and txHash. Amplifi stakes are scoped to a specific datanet and operate independently of your veREPPO lock.
Claiming pod emissions
For pods minted on-chain, you claim emissions through the Chat Server API athttps://api.reppo.xyz. Claims execute as on-chain transactions via the PodManager contract on Base.
1
Request a nonce
2
Verify your signature
3
Call the emissions endpoints
Include
Authorization: Bearer <session-token> on calls to GET /pods/{podId}/emissions and POST /pods/{podId}/emissions/claim.