Emission claims are settled on-chain via the
PodManager contract (0xcfF0511089D0Fbe92E1788E4aFFF3E7930b3D47c) 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.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:POST https://api.reppo.xyz/auth/noncewith yourwalletAddress— receive anonceand amessageto sign- Sign the message with your wallet using EIP-191
personal_sign POST https://api.reppo.xyz/auth/verifywithwalletAddress,signature, andnonce— receive yourtoken
token as a Bearer token in all subsequent requests.List your pods
Retrieve all pods minted by your authenticated wallet.ResponseNote the integer
podId for any pod you want to check or claim emissions for.Check claimable emissions
For a specific pod, retrieve the per-epoch breakdown of claimable REPPO.Response
If
| Field | Description |
|---|---|
podId | On-chain token ID |
currentEpoch | The current protocol epoch |
totalClaimable | Total unclaimed REPPO (decimal string) |
epochs | Per-epoch breakdown with claim status |
moreEpochsAvailable | true if more than 50 unclaimed epochs exist |
totalClaimable is "0.000000000000000000" and moreEpochsAvailable is false, there is nothing to claim for this pod.Claim emissions
Execute the on-chain claim for all unclaimed epochs (up to 50 per call).Response
Each transaction hash in
| Field | Description |
|---|---|
claimed | true if at least one epoch was claimed |
totalClaimed | Total REPPO sent to your wallet (decimal string) |
txHashes | One transaction hash per claimed epoch |
moreEpochsAvailable | true if additional unclaimed epochs remain |
txHashes corresponds to a separate on-chain settlement on Base. You can verify each one on Basescan.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 Repeat until you receive
"moreEpochsAvailable": true. In that case, call the same endpoint again with the same podId to claim the next batch."moreEpochsAvailable": false.