The surface
| Component | Status |
|---|---|
pallet-identity-ssi — did:emp documents, account mapping, revocation | Live; one DID registered (14 Sep 2026) |
| KryptoOS issuer / verifier / resolver | Circuit verified against a real chain; not publicly deployed |
pallet-compliance, pallet-sanctions — credential-gated transfers | Wired; unexercised |
pallet-account-abstraction — session keys, N-of-M, recovery guardians | Wired; session-key call adapted in Eoonia |
pallet-pqc-keys — ML-DSA (FIPS 204) verification in the runtime, per-account levels, sealed accounts | Live; CheckPqcPolicy in every transaction |
pallet-privacy, ZK verifier pallets | Wired; the earlier ZK module that leaked the secret was deleted |
Ideas from the plan
- Verifiable credentials with on-chain revocation: issue off chain, anchor the hash, revoke on chain, verify against
Revoked. - An identity wallet with N-of-M multisig and a recovery guardian, on account abstraction.
- A PQC demonstration: register an ML-DSA key, seal the account, show a classical signature rejected and a post-quantum one accepted.
What a team should know
- The DID prefix is
did:emp:(the pallet's). Five incompatible formats circulated in 2026; use the pallet's. - The pallet's storage is
Dids,AccountToDid,Revoked— nothing else. Older SDK code referenced storage items that do not exist. - Test decoders against a node, not against the library's source: the ecosystem's own audit got a field name wrong for eleven days by reading polkadot-js instead of the chain.
- Consensus is classical. A sealed account protects against key theft, not against block forgery. Say so in your demo; it is the honest claim and judges know the difference.
Why this track matters most
Half the runtime takes identity as input: fee discounts for verified humans, credentialed paymaster sponsorship, compliance on regulated assets, device attestation. All of it waits on more than one DID. A team that registers the second, third and hundredth did:emp — and finds what breaks — moves the whole ecosystem.
The winners this page listed
Were another hackathon's. This track's first winner will have done something the ecosystem has not yet: made identity on EmpoorioChain plural.
Based on TESTNET_HACKATHON_PLAN.md (Track 3), the KryptoOS Phase 3 verification and POST_CUANTICO_HASTA_DONDE_LLEGA.md.