Every action you take here is a real Cookie Chain transaction: a SPL Memo instruction signed by your wallet and confirmed on-chain, with live feedback at every step. No custom program, no token transfers, nothing leaves your wallet except the transaction fee (paid in COOK). Feed and dashboard are read directly from the Cookie Chain RPC.
Nightly is required by the Cookie Chain brief and is detected first;
other standard SVM wallets (Phantom-style window.solana) work too.
Point the wallet's custom network at https://rpc.cookiescan.io
(see the README).
not connected
Connected address:
Balance: COOK (read-only RPC; if it shows 0 you have no gas for fees — see the bridge at hyperlane.cookiescan.io)
This deployment's demo transactions are gated on a pending sponsor COOK gas drip (there is no faucet; the only $0 route is a sponsor drip). Until it lands, the Sign & send button stays disabled for this deployment's operator demo wallet only, and this banner stays up. Everything else — wallet connect, address display, transaction construction, free RPC simulation, confirmation handling, feed and dashboard — is live and real. Sending with your own funded wallet is unaffected by the gate and works normally right now.
On-chain memo payload (spl-memo program
):
Live from the Cookie Chain RPC: memo transactions matching the
cookiejar:v1 schema, from the tracked jar wallets below plus your
connected wallet. refresh ·
tracked list: participants.json
Tracked wallets live in participants.json next to this
page (a static file, so anyone can open a PR to add their jar). Your connected
wallet's recent activity is always included automatically.
Cookies baked per hour, last 24 hours (single series; block time from RPC).
https://rpc.cookiescan.io · explorer cookiescan.io (the app checks this and warns on a wrong network) — deployed and executable on Cookie Chain, so no custom program and no deploy cost.cookiejar:v1|<kind>|<note>, kind ∈ {bake, taste, tip}.tools/verify_tx.py.