Build a Casa Tookan app.

At a glance

The manifest

Casa Tookan reads the Wallet App Manifest, an open format any wallet can read: the W3C Web App Manifest your site most likely already has, plus one wallet member holding only what the standard has no member for.

{
  "name": "Orb Quest",
  "short_name": "Orbs",
  "description": "A card game played with your Counterparty assets.",
  "start_url": "/play",
  "scope": "/",
  "background_color": "#101820",
  "categories": ["games", "trading-cards", "counterparty"],
  "icons": [{ "src": "/icon-1024.png", "sizes": "1024x1024", "type": "image/png" }],
  "screenshots": [{ "src": "/shots/duel.png", "sizes": "1284x2778", "form_factor": "narrow" }],
  "wallet": {
    "version": "1",
    "subtitle": "Duel with your orbs",
    "heroImageUrl": "/hero-1200x630.png",
    "splashImageUrl": "/splash-200.png",
    "chains": { "required": ["bip122:000000000019d6689c085ae165831e93"], "optional": ["eip155:8453"] },
    "capabilities": {
      "required": ["provider.counterparty", "wallet.ready"],
      "optional": ["casatookan:identity.ceid"]
    },
    "extensions": {
      "casatookan": { "identity": { "level": 1, "reason": "One player per device" } }
    }
  }}

W3C standard in blue, unchanged · Added highlighted: the whole extension.

Where Casa Tookan finds it

1. https://<your-domain>/.well-known/wallet-app.json: the same JSON, served on its own;
2. else the <link rel="manifest"> in the <head> of your home page (https://<your-domain>/). Keep it in the served HTML; do not add it by script.

The first one with a wallet member is used whole: the two are not merged. Relative URLs resolve against the URL the manifest was fetched from.

W3C standard Members reused as is

Added The wallet member

Every field is read leniently: one that fails its check is ignored, the rest still applies.

Casa Tookan only extensions.casatookan

identity sets what your app may ask of the player’s Casa Estates ID: level (0–3), a reason, and addresses, the most addresses per CAIP-2 chain it will ever ask for ([{ "chain": "…", "max": 1–5, "reason": "…" }]). See CEID.

association

Proof that the domain belongs to you, signed by any blockchain account:

"association": {
  "account": "eip155:1:0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266",
  "payload": "eyJkb21haW4iOiJvcmJxdWVzdC5nYW1lIn0",
  "type": "eip191",
  "signature": "0x…"
}

• account: a CAIP-10 account;
• payload: base64url JSON { "domain": "your-domain", "issuedAt": "…" };
• type: the signature type (eip191 for EVM, bip322-simple for Bitcoin);
• signature: the signature of the message defined in the specification.

Stored by Casa Tookan, not verified yet. It will be required for anything scoped to your domain.

Images

The same sizes as Farcaster mini apps: one set of files serves both. The icon sits on light and dark backgrounds and in round masks: give it an opaque background of its own, and keep the art within the central 80 %. No SVG: many native image views can’t draw it. Without a banner, Browse falls back to your Farcaster manifest’s images (3:2 ones are cropped to 1.91:1), then to your icon over a blurred copy of itself.

Chains

CAIP-2 ids. Anything else is ignored.

Capabilities

The provider.* capabilities and wallet.ready come from the specification’s open registry: names any wallet hosting apps can offer as they are. What only Casa Tookan offers carries its casatookan: prefix; other wallets ignore it. Former names are still honoured: casatookan.ready (now wallet.ready), identity.ceid and identity.estate (now prefixed).

A required chain or capability Casa Tookan lacks shows the user a dismissible notice. Your app still opens. Optional ones are informative.

In the page

Injected before your own scripts. Signing goes through the standard providers above: there is no Casa Tookan-specific signing API.

window.wallet = {
  ready(),        // hide the splash screen (the neutral name)
};

window.casaTookan = {   // Casa Tookan’s own
  isCasaTookan: true,
  version: '1',
  ready(),        // the same, by its former name
  ceid,           // Casa Estates ID sign-in
};

if (window.casaTookan?.isCasaTookan) {
  // running inside Casa Tookan: ceid is there
}

Call window.wallet?.ready() and your app works in any wallet that offers it; test for Casa Tookan only for what is its own. A window.wallet your own scripts define is left alone.

window.addEventListener('load', () => {
  renderFirstScreen();
  window.wallet?.ready();
});

How Casa Tookan reads it

Farcaster mini apps

Casa Tookan also reads /.well-known/farcaster.json and hosts mini apps built on @farcaster/miniapp-sdk when the active casa owns a Farcaster account: context, Sign In With Farcaster, the wallet, haptics. Serve both manifests and they are merged field by field, the Wallet App Manifest first. You only need a Wallet App Manifest to override what differs in Casa Tookan, or to declare Bitcoin and Counterparty. A domain declared by farcaster.json alone is the app only at its homeUrl and below.

Not supported: adding the mini app and its notifications (no notification server), posting casts (handed to farcaster.xyz).

Playground

Edit a manifest and see, as you type, what Casa Tookan makes of it: the checks the app applies, your icon at every size, and the screens your users will see. It starts with a real one, the Dev Playground’s, live at ctserver.everdreamsoft.com/.well-known/wallet-app.json. Change its name, banner or colour, load your own domain, or paste your manifest. For the full specification checks, use the specification’s validator.

The Dev Playground serves icon-1024.png (1024 × 1024), hero-1200x630.jpg and splash-200.png (200 × 200): one set of files for the address bar, Browse, the app page and the splash. Open it in Casa Tookan from ctserver.everdreamsoft.com/playground.