Wallet
Pipoke is a social app and a wallet, both at once. The wallet panel shows your POKE balance, your OCT balance, the coins you launched and own, your live positions and P/L, your engagement claim status, your session key state, your faucet eligibility, and a quick send. There is no separate wallet app to switch into.
Pipoke runs on Octra Devnet today. Any fee, price, or limit referred to here is a contract setting chosen for testing. Every one is owner-settable, and mainnet values will be different. These docs describe how the mechanics work, not what the numbers are.
#What the wallet panel shows
| Section | Source |
|---|---|
POKE balance |
POKEToken.balance_of(wallet) |
OCT balance |
Octra node octra_balance RPC |
| Positions | Per-coin BondingCurveToken.balance_of(wallet) |
| P/L | Computed from buy/sell history on each coin |
| Engagement claim | Pending Merkle proof from EngagementVault |
| Session key state | Live status from SessionRegistry |
| Faucet eligibility | Cooldown timers from POKEFaucet and OCTFaucet |
The wallet panel is read-only on the chain side. Sending, swapping, and claiming are signed transactions like any other.
#Send and receive
send is a standard OCS-01 transfer for POKE or a coin. OCT send is a standard Octra transfer. Receiving needs no action on your end beyond having a wallet that holds the asset.
For someone to send you POKE, your wallet has to have been previously seen by POKEToken at least once. A first-time recipient sees their first inbound POKE after the sender pays a one-time POKE activation fee, which is the OCS-01 standard's anti-spam pattern.
#Swap
In-Pipoke swaps go through BondingCurveToken:
| Direction | Method | When |
|---|---|---|
| Coin (pre-grad) | buy / sell |
While the coin is still on the curve. |
| Coin (post-grad) | swap_oct_for_token / swap_token_for_oct |
After graduation. |
There is no POKE ↔ OCT AMM yet. Pipoke V1 does not ship a built-in POKE/OCT swap UI; this is on the roadmap.
#Claim
The wallet panel surfaces the claim paths:
| Claim | Where it goes |
|---|---|
| Engagement | EngagementVault.claim_with_proof_dN |
| Creator alloc | BondingCurveToken.claim_creator_alloc (after your coin graduates) |
| Faucet | POKEFaucet.claim and OCTFaucet.claim |
All three are session-keyed by default, so they go through silently.
#Today's wallet stack
Pipoke connects through the 0xio Octra wallet, a browser extension. The wallet exposes the window.octra provider, which the Pipoke app talks to. The 0xio extension handles signing for the initial connect and for anything outside the session-key scope.
#In-app embedded wallet (roadmap)
The Pipoke roadmap includes an embedded in-app wallet so the 0xio extension is no longer required for casual users. The embedded wallet will keep the seed in a browser secure-storage layer and expose the same window.octra-style provider locally. See roadmap.