Your Cometa positions, on-chain.
See what you have staked, claim rewards, withdraw when you want to. Everything happens directly between your wallet and the Cometa contracts on Algorand.
Connect
Choose the wallet that holds your Cometa positions.
Look up an address without connecting
Positions
No Cometa positions on this address.
If you staked from a different account, try connecting that one.
Reading on-chain state.
Is this safe to use?
The page is static and open source. It never sees your seed phrase. Every transaction is built locally, simulated against Algorand first so failures show up as a message instead of a wallet prompt, and then handed to your wallet to review before you sign.
The App ID on each position matches the contracts Cometa deployed. You can verify any of them on allo.info before signing.
Why might a withdraw fail?
Usually a contract lock period that has not elapsed yet, or not quite enough ALGO to cover the inner-transaction fee bump (about 0.004 ALGO). When the page can simulate your call ahead of time it shows the on-chain reason before your wallet pops; on the first withdraw against a new asset it submits an opt-in first and the simulate step is skipped, so a wallet rejection is the first signal there.
Why am I asked to confirm more than once on a withdraw?
The Cometa contracts only accept one application call per group, so claim and unstake go in separately. You sign everything in one wallet prompt; the page then submits each step on its own and waits for confirmation between them. ASA opt-ins ride in front when the receiving account needs them.
Who built this?
CorvidLabs and friends in the Algorand community. The code is open at github.com/CorvidLabs/open-cometa. Issues and PRs welcome.