Den is a crypto wallet policy engine for teams and developers. Set who can initiate and approve transactions, which assets and contract actions are allowed, and how much a permitted operation can move through the dashboard or API.
Bring approvals, permissions, and spending boundaries into the same workflow. Explore each capability, then try the controls for yourself.
Require approvals from a specific person or a group, with the threshold that fits the operation. A vendor-payment policy can require 2 of 5 members, while another policy governs routine transfers with its own approval requirements.
Define which accounts a policy covers and which people or groups can initiate transactions. Your Operations team can prepare a payment while the Administrator group provides the required approvals. Organize treasury, operating, and customer accounts around their own workflows.
Use token and destination conditions to describe the transfers a policy permits. Limit a vendor-payment flow to USDC and approved recipients, or give another account a different set of permissions. The selected policy determines which requests qualify.
Set a token-transfer amount limit for each transfer or across a configured time interval. Track usage per initiator, source account, or destination, or combine usage across them. Choose the interval and its start time to define when the spending allowance resets.
A contract permission can be more precise than access to an entire application. Scope a policy to a contract address, permitted functions, and argument conditions. For example, allow a supply action in a lending contract while keeping a withdrawal outside that policy.
Use the API and TypeScript SDK to initiate transactions under your organization’s policies. An automatic-approval policy can handle a permitted routine flow without manual member approvals, while a policy for another operation can require a group to sign.
Policy changes follow a proposal workflow. Review the intended changes and collect the required administrative approvals before they take effect. The authority to change a policy is distinct from the members allowed to approve transactions under it.
A policy engine applies the transaction rules you configure: which accounts and initiators can use a policy, what transfers or contract calls it permits, and which approvals are required. Den validates the selected policy in the signing client, Guardian service, and onchain smart contracts during standard execution.
Require approvals from a specific person or a group, with the threshold that fits the operation. A vendor-payment policy can require 2 of 5 members, while another policy governs routine transfers with its own approval requirements.
Define which accounts a policy covers and which people or groups can initiate transactions. Your Operations team can prepare a payment while the Administrator group provides the required approvals. Organize treasury, operating, and customer accounts around their own workflows.
Use token and destination conditions to describe the transfers a policy permits. Limit a vendor-payment flow to USDC and approved recipients, or give another account a different set of permissions. The selected policy determines which requests qualify.
Set a token-transfer amount limit for each transfer or across a configured time interval. Track usage per initiator, source account, or destination, or combine usage across them. Choose the interval and its start time to define when the spending allowance resets.
A contract permission can be more precise than access to an entire application. Scope a policy to a contract address, permitted functions, and argument conditions. For example, allow a supply action in a lending contract while keeping a withdrawal outside that policy.
Use the API and TypeScript SDK to initiate transactions under your organization’s policies. An automatic-approval policy can handle a permitted routine flow without manual member approvals, while a policy for another operation can require a group to sign.
Policy changes follow a proposal workflow. Review the intended changes and collect the required administrative approvals before they take effect. The authority to change a policy is distinct from the members allowed to approve transactions under it.
An approval threshold is one part of a Den policy. You can require 2 of 5 members of a group and also constrain the transaction’s asset, destination, amount, or contract call. Different policies can give different operations their own permissions and approval requirements.
Yes. An automatic-approval policy can permit a defined flow without manual member approvals. The transaction must still meet that policy’s conditions and authorization requirements. Programmatic API members can initiate permitted operations through the API and TypeScript SDK.
Token-transfer conditions can specify the token, allowed destinations, and amount threshold. An amount limit applies to a selected token. Usage limits can cap the total transferred during a configured interval, with scopes such as an initiator, source account, destination, or combined usage.
Yes. Contract-interaction conditions can specify the destination contract, permitted functions, and argument values. This lets you define the operation a policy authorizes rather than granting unrestricted access to every action in an application.
Policy changes follow the organization’s administrative permissions and proposal workflow. Proposed changes are reviewed and collect their required approvals before taking effect. Approving a transaction under a policy does not by itself grant permission to change that policy.
To Approved vendor
assetamountTo Service provider
assetamountTo Operating wallet
spenderamountExplore enterprise crypto wallets with programmable policies, mobile approvals, and onchain enforcement.