DFNS Concordium Activation Assistant
DFNS can create a Concordium wallet, but the wallet only becomes operational after its public key is tied to a Concordium ID credential and activated on-chain. This page documents and prototypes the missing guided activation layer.
No DFNS secrets in public helperConcordium ID App approval requiredSelf-hosted runner for full activation
What the assistant does
- Starts from an inactive DFNS Concordium wallet public key.
- Uses Concordium ID App / WalletConnect to create the credential deployment payload.
- Returns the payload needed for DFNS activation.
- Self-hosted mode can call DFNS, poll status, and write a redacted receipt.
Boundary
The public helper must not receive DFNS API tokens, service-account private keys, seed phrases, raw identity credentials, or legal-name/DOB attributes.
The credential deployment payload is treated as transient activation material.
Activation payload helper
This browser-side helper validates inputs and formats an activation package. The actual WalletConnect/ID App request is implemented in the self-hosted runner first, then this page is wired to the same tested module.
Showing
- Status JSON: /api/dfns-concordium-activation/status
- Sample receipt: redacted sample receipt
- Docs: management note, user guide, operator guide, architecture, troubleshooting.
Mainnet-first validation
Use a fresh inactive Concordium Mainnet DFNS wallet for the first public proof, with production DFNS credentials kept inside the self-hosted runner. Confirm whether DFNS activation accepts {expiry,unsignedCdiStr} only or the full serialized credential object including randomness.