About BA | Signet
Last updated 30 September 2026
BA | Signet proves that a counterparty controls a blockchain address. They sign a short message with the wallet that holds it; you get a certificate that anyone can verify.
Rules such as FATF Recommendation 16, the EU Transfer of Funds Regulation and MiCA ask firms to establish who controls a self-hosted wallet. A screenshot or a declaration proves little, and a test payment costs money and moves funds. A signature over a message that names the address, the chain and a one-time code proves control of the key, and moves nothing.
What it does
You create a request and send the link to your counterparty. They open it, sign the message in their own wallet, with a hardware device, or by pasting a signature, and we verify it against the address on the right chain. No account, no transaction, no gas for them.
If you choose, a hash of the certificate is anchored on Polygon and, through OpenTimestamps, on Bitcoin. That fixes the time the certificate existed by, and the open-source verifier checks all of it without trusting us.
What we are honest about
A certificate proves that the holder of the key signed that message. It does not prove who the signer is, that nobody else holds the key, or that they were not coerced. Binding a certificate to a person is your KYC, not ours.
Who makes it
Signet is built by Aletheia Tech Ltd, the team behind BlockchainAnalysis.io. It shares its anchoring infrastructure with BA | Stamp (blockchain timestamping) and BA | Scribe (document signing).