Check a signature yourself.
This page runs the same function the back room's door runs - one verifier, one algorithm, no second copy. Paste an address, the exact message, and the signature. Nothing here logs anybody in, spends a nonce, or writes anything down.
What a valid answer means
The key behind that address signed that text, character for character. It does not mean the address holds anything, and it never means a transaction was authorised - a message signature cannot move a coin or an inscription. That is the whole reason the back room asks for one.
Taproot only
This accepts BIP-322 signatures from bc1p addresses and nothing else. A legacy signature against a taproot address is refused rather than waved through, here and at the door.
The verifier is the door
api/lib/bip322.php. This page and the sign-in call the same function with the same arguments. If this page is wrong about a signature, the door is wrong in exactly the same way - which is the point of publishing it.
Four signatures that must fail. A green row here means the verifier has changed and something is wrong.
- refuseda signature that is not base64
- refusedan empty signature
- refuseda legacy address, which this verifier must refuse outright
- refused64 zero bytes as the witness