One portable asset, issued jointly by independent domains. It carries its issuers, their signatures and the rules for moving it, and finds the services that can authorize a transfer through each issuer's own domain.
Checking this domain…
Test identities, not wallets. Owners are test keys generated in this tab with Web Crypto (ECDSA P-256) and kept only in this tab's session storage. They disappear when the tab closes and cannot be recovered; use "Export identities" if you want to bring them back. Nothing here is a durable production wallet, and the server never sees a private key.
| Name | Key id | Owns |
|---|
You get a private test session. Create a test certificate owned by Alice, then ask each issuing domain to approve its issuance. Each domain fetches the same definition from the registry, checks it against its own pinned roster, keys, policies and limits, and signs with its own key. No wallet and no administrator token.
This is an approving domain. Assets are created on ; when asked, this domain fetches the definition from there, validates it under its own rules and signs. Paste an asset id or an exported asset below to see this domain's own independent verification.
The exported file contains the asset id, issuer identities and keys, the complete roster, the issuance signatures, the signed issuance and transfer policies, discovery references and capabilities, the ownership authority and the signed ownership history. It is verified here with Web Crypto. A file on its own can prove who issued the asset and how it has changed hands, but not what is current: only the registry can say that.
| Issuer | Discovery | Services |
|---|
Server-side events as they happened, including every rejected attempt and every request one domain made to another.
What this proves, and what it does not. Each issuing domain signs only after validating the asset itself under its own pinned configuration, and the registry executes only a transfer the current owner signed and a satisfied approval certificate. This is not atomic settlement across independent ledgers and not Byzantine fault tolerant consensus: one designated state authority holds ownership state and could withhold or roll back history, which a fresh signed state attestation and the signed history make detectable but not impossible.
Forged signatures, tampered metadata, duplicate approvals, replays, stale state, competing transfers, unavailable peers, restarts and service relocation are exercised by test/manual-multi-issuer-php.js, not by controls here. Public sessions are limited, rate-limited and expire.