Sign in with a Casa Estates ID

The CEID

A Casa Estates ID is a player account, public like a Farcaster id. A player may never show you an address: a game without a blockchain, or one that only needs an address months later for a reward drop, works the same.

Flow

1. Your server makes a nonceRandom, single use, short-lived, bound to the session that will receive the token.
2. The page askssignIn({ nonce }). Casa Tookan shows a sheet with your name, icon and domain. The first time, it creates the player’s CEID — nothing to fill in.
3. The player approvesThe CEID key signs around your nonce in Casa Tookan’s native signer. Their recovery phrase never leaves it.
4. Casa Tookan’s server issues the tokenIt checks the signature and the device, adds the facts and signs a JWT for your origin (aud).
5. Your server verifies itAgainst the published keys (JWKS), without calling Casa Tookan. Then you read the shared addresses on-chain yourself — never trust a wallet about what a player owns.
6. Later, ask for addressesrequestAddresses({ nonce, chains, reason }) when you need them: a drop, an inventory. A new token carries them.

Manifest

Declare it in /.well-known/casatookan.json. The identity field, reserved until now, takes this shape; the capability identity.ceid replaces the reserved identity.estate.

{
  "version": "1",
  "app": {
    "name": "Orb Quest",
    "capabilities": { "required": ["identity.ceid"] },
    "identity": {
      "reason": "Your CEID keeps your progress across devices.",
      "addresses": [
        { "chain": "bip122:000000000019d6689c085ae165831e93", "max": 2, "reason": "Activate the orbs you hold on Counterparty" },
        { "chain": "eip155:1", "max": 1, "reason": "Your Ethereum cards" }
      ]
    }
  }
}

In the page

Available inside the Casa Tookan browser when the manifest declares identity.ceid. Calls reject with an error whose code says why:

const { nonce } = await fetch('/auth/nonce').then((r) => r.json());

// account only: no address leaves the wallet
const { token } = await window.casaTookan.ceid.signIn({ nonce });
await fetch('/auth/casa', { method: 'POST', body: token });

// months later, for the drop
const { nonce: n2 } = await fetch('/auth/nonce').then((r) => r.json());
const { token: withAddresses } = await window.casaTookan.ceid.requestAddresses({
  nonce: n2,
  chains: [{ chain: 'bip122:000000000019d6689c085ae165831e93', max: 1 }],
  reason: 'Where should we send your reward?',
});

The token

A JWT (ES256) signed by Casa Tookan’s server, valid 24 hours. Ask for a new one after that — no sheet if nothing changed.

{
  "iss": "https://ctserver.everdreamsoft.com",
  "aud": "https://orbquest.game",
  "sub": "ceid:48213907",
  "env": "production",
  "ceid": 48213907,
  "username": "CasaTookanUser#48213907",
  "usernameDefault": true,
  "addresses": [
    { "chain": "bip122:000000000019d6689c085ae165831e93", "address": "1Abc…k9Z", "since": "2026-03-02" }
  ],
  "facts": {
    "deviceAttested": true,
    "deviceUnique": true,
    "transfers": 0,
    "ceidAge": 214,
    "farcaster": { "fid": 4242 }
  },
  "nonce": "…", "iat": 1791878400, "exp": 1791964800
}

Verify it on your server

Never in the page alone: a token checked only in the browser can be forged by the player.

1. SignatureAgainst the keys at https://ctserver.everdreamsoft.com/.well-known/jwks.json (cache them, follow kid). They sign production tokens only: a development token fails there by itself.
2. Audience and issueraud is exactly your origin, iss is Casa Tookan’s server.
3. NonceThe one you issued for this session, unused. Burn it.
4. Timeexp not passed (allow a minute of clock skew).

import { createRemoteJWKSet, jwtVerify } from 'jose';

const JWKS = createRemoteJWKSet(new URL('https://ctserver.everdreamsoft.com/.well-known/jwks.json'));

export async function verifyCasaToken(token, expectedNonce) {
  const { payload } = await jwtVerify(token, JWKS, {
    issuer: 'https://ctserver.everdreamsoft.com',
    audience: 'https://orbquest.game',
    clockTolerance: 60,
  });
  if (payload.nonce !== expectedNonce) throw new Error('nonce');
  return payload; // key the player on payload.ceid
}

Development builds

Test with Casa Tookan Dev. Its CEIDs live apart from production ones and are signed by a development key published at https://ctserver.everdreamsoft.com/.well-known/jwks-dev.json. Point your staging server there and check env === "development"; your production server keeps the production keys and never sees test accounts. TestFlight builds of the main app attest as production: don’t test with them.

Multiple accounts

Sharing addresses per app doesn’t stop one person from playing as many — that isn’t its job. Each attack has its own answer.

Rules players live by

Privacy

Try it in the playground

The developer playground mini app has a CEID tab that plays every scenario above — first sign-in, play without addresses, the drop, refusals, expired, replayed and foreign tokens, a rename, a new phrase, the anti-Sybil threshold — next to tabs for the environment, the manifest, the providers and deep links. Open /playground/ in Casa Tookan: it signs in against this server (a development build gets env: "development" tokens). In a plain browser it plays against a mock wallet and a mock issuer, under their own issuer and key, so a mock token never passes for Casa Tookan's.