Den Documentation
  • What is Den?
    • Den
    • Safe Contracts
    • Supported Chains
    • Security Practices
  • Set up Den
    • Sign In With Ethereum
    • Using Existing Safes
    • Creating and Managing Safes
  • Creating Transactions
    • Getting Started
    • Send Tokens
    • Connect to Dapps
    • Custom Transaction Builder
    • Upload a JSON file
    • Adding Descriptions
    • Simulations
    • Batching
  • Signing and Executing
    • Overview
    • Edit Descriptions
    • Decoded Data
    • Smart Contract Search
    • Simulation
  • Pay Gas from Safe
    • Overview
    • How it Works
    • FAQ
  • Payment Requests
    • Overview
    • Send the Request Form
    • Request a Payment
    • See Requests you've sent
    • Approve and Pay Requests
  • Organizations
    • Overview
  • Notifications
    • Overview
    • Set a Reminder Frequency
    • Discord
    • Telegram
    • Slack
    • SMS
    • Bot Commands
  • Links
    • Book a Demo
    • Support
    • Feature Requests
Powered by GitBook
On this page
  1. What is Den?

Security Practices

How we make sure your team stays secure

PreviousSupported ChainsNextSign In With Ethereum

Last updated 2 years ago

Den is an interface on top of the Safe Contracts. These contracts have been well tested and audited. You can find the audits .

Safe is the most popular mechanism for teams to store assets on-chain and is trusted by DAOs, DeFi Protocols, Investment Firms, and other security conscious organizations. Over $39B is stored in Safe contracts, representing about 5% of all cryptocurrencies.

Due to the security mechanisms implemented in the Safe contracts, Den is not able to modify the Safe Contracts or any transactions that a user has signed or executed.

Den’s interface and bot software are well-tested and subject to stringent review before deployment. Address labels and transaction description messages are only visible to other owners of the Safe, who’ve proven their ownership by producing a verifiable compliant cryptographic hash. That data is stored on servers managed by the Den team, which is inaccessible to all but permissioned Den engineering team members that have been 2 factor authenticated, so that information stays private.

here
EIP-4361