Demos · DEMO-MINT
Available for evaluationMinting walkthrough
How ENI6MA Foundry manufactures a cohort of per-identity binaries. Screenshots are placeholders until capture from DEMO-MINT completes.
1. Choose variant & cohort size
Select a circuit variant (standard, hardened, or hybrid) and how many identities the cohort should contain. Foundry treats this as a manufacturing job, not a user signup form.
Screenshot pending
Foundry job form: variant + cohort size
2. Embed policy & entropy
Each binary is compiled with its own config, entropy, and policy. Identity travels with the artifact; there is no vault of transferable secrets to export afterward.
Screenshot pending
Mint progress: embedding entropy per identity
3. Emit cohort zip + manifests
The appliance produces a cohort package: binaries, manifests (hash, size, timestamps), and handles ready for registry activation.
Screenshot pending
Cohort zip contents listing
4. Activate in Control
Upload manifests to ENI6MA Control. Activation is a registry state change; revocation later is the same kind of one-shot state change in reverse.
Screenshot pending
Control registry: cohort activated
After mint: enforce
Minted circuits only matter once a Gate enforces them. The gate order below is the same curriculum as DEMO-HACK.
Gate order after activation
- 01
Request hash
Recompute digests; reject on mismatch
- 02
Endpoint
endpoint_id matches server constant
- 03
Policy
policy_hash from server POLICY_STRING
- 04
Anchor
Circuit handle active in registry
- 05
Freshness
tau within the call window
- 06
Burn nonce
Spend before twin validation
- 07
Validate
Twin proof check (local or registry)
- 08
Serve
Application policy, then resource