IN DEVELOPMENT · EXPERIMENTAL — SHAKE256 hashing + SLH-DSA / ML-KEM demo. Not verifiable by standard Gen6 RealSeal apps. PQC keys are generated in-browser.

Gen6 RealSeal Notary PQC · DEV

SHAKE256 notarization, SLH-DSA signatures, and ML-KEM encryption — client-side. Files/messages never leave this browser.

Experimental PQC toolkit. Hashing is SHAKE256 (not Blake2b-256), so on-chain records are not verifiable by standard Gen6 RealSeal apps — use the Verify tab. Post-quantum keys (SLH-DSA, ML-KEM) are generated in this browser, held in memory only, and never uploaded or auto-saved. Export to keep them; if lost they are unrecoverable; if leaked, others can sign/decrypt as you. They are separate from your on-chain account key.
Connection, project & hash settings

Defaults: wss://gen6.app:443/node, project 886, SS58 355. On-chain writes (hash / signature anchor) need the pallet's dataHash to accept these byte lengths.

Notarize
Verify
Sign · SLH-DSA
Encrypt · ML-KEM

1Connect wallet

Signing is delegated to your wallet extension. This page never sees your seed or account private key.

2Select & hash file (100% local)

3Review & seal on-chain

Call
dataRegistry.storeData(projectId, dataHash)
projectId
dataHash
Connect wallet, hash a file, connect chain.

Activity log