ApeChain
Arbitrum Stylus verifier
Not asked yetPlate XXI
Check a post-quantum signature on-chain.
Replay a signature AWS KMS made for a live treasury, or make a key here and sign with it, and ask the deployed verifiers whether the signature holds: the Stylus program on ApeChain and the Solidity verifier on Arbitrum One. It needs no wallet: the check is a read-only call, the same one a Qanary account makes before it lets the post-quantum key act.
Replay a signature from AWS KMS
A live treasury (0xA3d2…EbEe) keeps its root key in an AWS KMS HSM. Its first operation on Arbitrum One carried an ML-DSA-44 signature by that key over the operation’s hash. This reads the signature from that transaction and asks both verifiers about the same key, hash and signature: the Stylus program on ApeChain and the Solidity verifier on Arbitrum One.
- Key pointer
- 0xdb5C…9B5C
- Signed hash
- 0x70bd…a364
Arbitrum One
Solidity verifier
Not asked yetOr sign in this page
A fresh key is generated in your browser from 32 random bytes and thrown away when you leave. The message is hashed with keccak-256; the verifier receives the 32-byte hash, as an account would.
Key format: inline scheme id ‖ public key, 0x02 for ML-DSA-44, 0x03 for ML-DSA-65, 0x04 for Falcon-512. Accounts store the same bytes once in the key store and pass a 20-byte pointer instead.