Proof of control of a self-hosted wallet
Send a counterparty a link. They sign a challenge with any wallet, a hardware device, or a pasted signature. You get a verifiable certificate that the key was controlled — anchored on-chain. No screenshots, no Satoshi test.
Built for FATF R16 / EU TFR / MiCA. The signer never needs an account.
Three steps. The counterparty does one of them, and needs no account to do it.
Pick a chain, add your reference, get a link (or QR) to send however you like.
The counterparty signs plain text with any wallet. Never a transaction, never a seed phrase.
Verified on the right chain, certified, and anchored on-chain to fix the time it existed.
The signature is verified, hashed into a certificate, folded into a merkle root, and anchored — first on Polygon, then Bitcoin.
This is part of the product, not the fine print. We are precise about the claim.
The full statement, the per-chain cryptography and how to verify it yourself are on the proof semantics page.
Several regimes require verifying control of a self-hosted wallet by technical means — not a screenshot.
The “travel rule” expects obliged entities to verify control of self-hosted wallets by technical means.
Regulation (EU) 2023/1113 requires verifying that a self-hosted wallet is controlled by the customer.
Self-hosted-wallet checks under MiCA need a repeatable, evidenced method — not a screenshot.
Message signing on every major chain. Hardware and offline signing via paste — no wallet integration required.
EIP-191 signatures verify on any EVM network out of the box — this is a curated set, not a limit.