Crypto wallet security, layer by layer.
Den is a wallet platform for organizations that need shared approvals and transaction controls. The signing client, Guardian service, and onchain smart contracts independently check the selected policy and approvals before standard execution.
Multisig approvals, with transaction policies
Require multiple people to approve a payment, then limit which recipients, tokens, amounts, and contract calls the selected policy allows.
Three independent security checks
Your signing client, the Guardian, and onchain smart contracts each validate the selected policy and required approvals before standard execution.
Your keys. Shared control.
Your members hold the keys that authorize transactions. The Guardian co-signs standard transactions, but its signature alone cannot authorize a transfer.
Security you can verify
Review the open-source contracts and independent Certora and yAudit reports. Verify the onchain controls protecting your digital assets.
See how a payment passes every security layer
Start by creating a transaction within policy. Requests outside the selected policy are blocked before approvals; valid payments continue through member signatures, Guardian checks, and onchain execution.
Create a transaction within policy
Crypto wallet security and custody FAQs
How does Den differ from a multisig wallet?
A multisig wallet requires a threshold of signatures. Den supports multi-party approvals and adds configurable rules for recipients, tokens, spending, and contract interactions. The signing client, Guardian, and smart contracts independently validate the selected policy. Smart contract multisigs such as Safe can also add controls through modules and guards.
Who controls the assets in a Den wallet?
Your organization’s members hold the signing keys that authorize transactions. In the standard flow, Den’s Guardian also co-signs after validating the policy and approvals. You can operate your own Guardian through a self-hosted deployment.
Can the Guardian move funds on its own?
A Guardian signature alone cannot authorize a standard transfer. The contracts also require member signatures and compliance with the selected transaction policy.
What happens if a server is compromised?
The onchain contracts still verify the selected policy and required signatures. Bypassing a server-side check does not remove those contract-level requirements. The signing client also checks the policy independently before signing.
How are changes to members and policies approved?
Changes to members, groups, and policies require the organization’s separate admin approval threshold. Payment approval permissions do not automatically grant permission to change those controls.
What if Den becomes permanently unavailable?
Den’s disaster recovery mechanism lets you recover your funds if Den becomes permanently unavailable. Recovery uses separately configured addresses and timelocks. The Transaction Recovery path bypasses the normal policy engine.
Explore related capabilities
Technical documentation
Move onchain with confidence.
Explore enterprise crypto wallets with programmable policies, mobile approvals, and onchain enforcement.