Threshold authorization without threshold signatures. The signature-agile architecture works unchanged with ECDSA (FIPS 186-5), ML-DSA (FIPS 204), or SLH-DSA (FIPS 205), giving custody providers a practical migration path without depending on a yet-to-be-standardized lattice-based threshold signature scheme.
Complete the workflow in order. All data required for this demo stays in this browser.
Load the operator identity used to administer or approve this vault. For the demo, you can generate a new identity here. Secret key material never leaves this browser.
The hosted demo uses the default secure coordination service and Pluto RPC. Override these values only when running the stack locally.
Vault infrastructure
Deploy a dedicated custody vault and fund it with 10 test ETX for the end-to-end authorization demo.
The current operator will become the vault administrator when the custody policy is registered.
Add every authorized approver, including this operator when applicable, and choose how many approvals are required to release assets.
Approver onboarding
Each approver completes these steps in their own browser using their assigned operator identity.
Enter the activation ID provided by the vault administrator. Your locally generated approval material is encrypted for the other approvers and remains recoverable in this browser.
Generate this approver’s protected authorization material and securely coordinate it with the rest of the approval group. No manual key exchange is required.
Verify the protected material received from the other approvers and commit this operator’s authority to the group. The administrator can activate the policy after all approvers finish.
Admin action — the vault administrator runs this after every approver has completed secure activation. Activation records the governance policy on-chain and makes the vault transaction-ready.
Transaction control
Approvers submit authorization shares. When the policy threshold is met the vault is authorized on-chain.
Confirm the vault, destination, and amount before submitting your approval. This action is signed by the loaded operator identity.
Each authorization slot can be used once. Move to the next available slot for a new withdrawal.