Casa Tookan

Documentation

How the Casa Tookan wallet keeps its keys and talks to sites and apps.

dApp connections & deep links The signer sheet, which casa signs, the connection index, and the casatookan:// links (browse, web3 login, callbacks and signature formats). Key storage Where recovery phrases and private keys live, who can unlock them, and how the native signer uses them — custody, the two DEK wraps, migrations, threat model. Build a Casa Tookan app The casatookan.json manifest: name, icon, banner and splash screen, required chains and capabilities, window.casaTookan — with a validator. Sign in with a Casa Estates ID Draft. One account per player (CEID), the addresses they choose to show you, a 24-hour token to verify on your server, and facts against multiple accounts. Sell for Tookans Preview. Your server signs offers, players pay from their CEID’s Tookans, receipts signed by Casa Tookan reach your callback — 15 % commission, 90 days held, refunds. Test your app on the web devapp.casatookan.com opens your app in a browser like the phone does: the bridge script, a manifest served with CORS, framing and session cookies — and what stays phone-only. Deep link tester Open it on a phone with Casa installed: builds every link, returns with Casa’s answer and verifies the signature.