Skip to main content
Every pod you mint on Reppo earns REPPO emissions each epoch based on how well it performs in curation voting. Voters allocate veREPPO toward or against your pod during each 48-hour epoch, and the protocol calculates your share of emissions at epoch end. Those emissions accumulate on-chain and must be explicitly claimed — they are not pushed to your wallet automatically. This guide walks you through listing your pods, checking what you can claim, and executing the on-chain settlement.
Emission claims are settled on-chain via the PodManager contract (0x5C563f853eb4db33005A5C1aD9290e8560254A80) on Base. The Chat Server submits these transactions on your behalf using your authenticated session. Each claim call scans up to 50 epochs — call it again if moreEpochsAvailable is true.
1

Authenticate with your wallet

All Chat Server endpoints require a 24-hour session token. Complete the wallet auth flow on api.reppo.xyz if you have not done so:
  1. POST https://api.reppo.xyz/auth/nonce with your walletAddress — receive a nonce and a message to sign
  2. Sign the message with your wallet using EIP-191 personal_sign
  3. POST https://api.reppo.xyz/auth/verify with walletAddress, signature, and nonce — receive your token
Use the returned token as a Bearer token in all subsequent requests.
2

List your pods

Retrieve all pods minted by your authenticated wallet.
Response
Note the integer podId for any pod you want to check or claim emissions for.
3

Check claimable emissions

For a specific pod, retrieve the per-epoch breakdown of claimable REPPO.
Response
If totalClaimable is "0.000000000000000000" and moreEpochsAvailable is false, there is nothing to claim for this pod.
4

Claim emissions

Execute the on-chain claim for all unclaimed epochs (up to 50 per call).
Response
Each transaction hash in txHashes corresponds to a separate on-chain settlement on Base. You can verify each one on Basescan.
5

Repeat if moreEpochsAvailable is true

The claim endpoint scans a maximum of 50 epochs per request. If you have a pod with many unclaimed epochs, the response will include "moreEpochsAvailable": true. In that case, call the same endpoint again with the same podId to claim the next batch.
Repeat until you receive "moreEpochsAvailable": false.