# Den Get your multisig transactions built, signed, and executed fast ### What is Den? Den provides a self-custodial, multi-signature wallet for onchain organizations. Teams, including both DAOs and traditional organizations, use Den for managing protocols, interacting with DeFi, onchain operations, and more. Den is built on top of the Safe Contracts (formerly Gnosis Safe). Safe is the most trusted asset storage mechanism onchain, accounting for over 5% of all cryptocurrency stored. Signing in to Den will automatically fetch your existing Safes. Den does not modify your Safe or add additional contracts. ### What problems does Den solve? Signers on multisigs face a number of challenges. These can result in exposing your team to vulnerabilities, wasting hours of time, or dedicating precious engineering resources towards operations. The major problems Den solves today are: * Coordinating - Some teams spend days getting everyone to sign multisig transactions. From needing a hardware wallet that is far away to people forgetting to sign, it can be incredibly challenging to get your transactions executed. * Understanding - Onchain transactions are becoming more complex and challenging to read. Complex parameters, numbers divided by 10^18, and a lack of context make it a challenge to be confident that you're doing the right thing. * Creating - Creating new transactions is a risky, slow, anxiety-inducing process. Some teams dedicate engineering resources to building custom interfaces and scripts to create transactions. Additionally, most dapps are not designed for multisigs which leads to unusable experiences. How does Den solves these problems? #### Solution 1: Coordinating Den offers Discord, Telegram and SMS bots that send notifications to your team on a recurring basis until your transactions are executed. The bots are also capable of tagging signers who have not yet signed a transaction, generating stats to see who are the least active signers, and more. #### Solution 2: Understanding Den's transaction page makes understanding transactions easy by parsing even the most complex transactions, allowing signers to simulate transactions to see their outcomes (powered by Tenderly), and enabling signers to add descriptions to transactions so you can share more information. #### Solution 3: Creating Den's transaction creation flow makes it easy to create any type of transaction, whether these are token transfers, dapp interactions, or custom contract calls. Transactions can be created in batch so there are fewer transactions for your team to sign. Lastly, Den allows you to simulate as you create which allows for easy iteration and provides confidence that your transactions will succeed. # Safe Contracts The most trusted platform to manage digital assets Den is built on the Safe Contracts with no additional smart contract code. ### Safe Contracts Safe is a self-custodial, multi-signature wallet. A multi-signature wallet require multiple parties using individual wallets to sign a transaction before it is executed. The rules of execution are defined in an `n-of-m schema`, where `n` is the minimum number of signers needed for a transaction to execute and `m` is the total number of signers on a wallet. For example, on a `2-of-3` multi-signature wallet there are 3 total signers on the wallet, but only 2 of them need to provide signatures for a transaction to execute. Safe is deployed on Ethereum and a several other EVM (Ethereum Virtual Machine) Chains. It currently stores over 5% of all cryptocurrency. You can find more usage data for Safe here (data only covers Ethereum Mainnet): ### SafeDAO and Governance Delegation The Safe Contracts and infrastructure are stewarded by the SafeDAO, a decentralized autonomous organization consisting of contributors across the Safe ecosystem. Den actively votes in SafeDAO governance proposals as a delegate. If you hold $SAFE tokens, you can delegate your votes to Den on [Snapshot](https://snapshot.org/#/delegate/safe.eth) to either * jgov.onchainden.eth * igov.onchainden.eth Den's voting decisions are shared publicly on [Twitter](https://twitter.com/search?q=from%3A%40onchainden%20SEP\&src=typed_query\&f=top). # Supported Chains Where can you use Den to manage your Safe multi-signature wallet? Den supports the official Safe multi-signature wallet deployments on the following chains: * Ethereum * Polygon * Optimism * Arbitrum * Base * Berachain * Gnosis Chain * Avalanche * BNB Chain * Zora * Corn * Blast * World Chain We add new chains based on customer feedback. Please contact our team if you'd like to see support for additional chains. # Security Practices How we make sure your team stays secure Den is an interface on top of the Safe Contracts. These contracts have been well tested and audited. You can find the audits [here](https://github.com/safe-global/safe-contracts). 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 [EIP-4361](https://eips.ethereum.org/EIPS/eip-4361) 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. # Sign In With Ethereum A modern sign in experience for an onchain world The first step to using Den is signing in. Instead of web2 authentication, Den uses Sign In With Ethereum. In the Sign In With Ethereum model, Den provides a message for you to sign with your wallet. By signing this message, Den is able to verify that you are the true owner of the wallet. Signing this message does not enable any assets to be transferred or otherwise affected. An example message is shown below. You can read more about Sign In With Ethereum [here](https://login.xyz/). ![](https://731861436-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPw0mN04sXbA90tnBcjau%2Fuploads%2FOW0PGnRaDlPGFH1XLfgb%2FScreen%20Shot%202023-01-07%20at%209.29.52%20PM.png?alt=media\&token=4cbf3154-fcf3-41dd-bc01-2eafbd8301be) # Using Existing Safes Den automatically fetches any existing Safes After you sign in, Den automatically fetches any existing Safes where you are a signer across all supported networks.
# Creating and Managing Safes Den lets you create new Safes, modify Safe owners, and update the threshold Den provides full ability to create new Safes and manage existing ones. ### Create a New Safe You can create a new safe from your Safe List page by clicking the `Create Safe` button.
### Manage Safe Owners Safe owners can be added, or removed on the owners page. To get to this page, select the Safe you'd like to modify and click the button with the group of people.
Here you can add and remove owners, as well as change the minimum number of signers required for a transaction to execute. # Getting Started Easily send tokens, interact with dapps, and build custom transactions For any type of transactions you'd like to create, click the `Create Transaction` button in the top right corner.
You'll need to be signed in to create a transaction if you aren't already. Next, select the Safe you'd like to create a transaction for.
From here you'll be presented with three options * Send Tokens * Use WalletConnect * Build it myself We'll dive into the details of each of these options over the next few pages, as well as some of the other ways Den makes creating transactions fast and easy. # Send Tokens Den makes it easy to transfer ERC20 tokens Den automatically fetches the tokens in your Safe for you to select which one to send. Then, just specify the amount and recipient.
The token transfer page allows you to transfer one or many tokens to as many recipients as you'd like. Click `Add Token Transfer` to add an additional transfer. # Connect to Dapps Connect to dapps through Den using WalletConnect Den allows you to connect to dapps using your safe. Once you've selected `Use WalletConnect`, go to the dapp you want to use in a new tab and locate the WalletConnect link. This is typically found by clicking `Connect Wallet` on the dapp then selecting `WalletConnect`. To get the WalletConnect link click `Copy to clipboard`.
After you paste this link into Den, you'll be connected to the dapp. Once the dapp prompts you to sign a transaction, don't forget to come back to Den to finish creating it. # Custom Transaction Builder Directly interact with any contract address with the Transaction Builder Some teams like to directly interact with smart contracts and Den's transaction builder makes it easy with a Custom Transaction Builder, no matter how complicated your inputs are. This is accessible when you select the `Build it myself` option. Paste in the address of the contract you'd like to interact with. Den will automatically retrieve the contract's ABI, and will even fetch ABIs for the proxy contract's implementations.
# Upload a JSON file Upload a JSON file specifying transaction data You can upload a JSON file with transaction data to use that transaction in Den. Many teams generate these files using scripts so they can run complex testing and analysis, or import them from other tools. These JSONs can include a single transaction, or a list of many transactions. To upload a JSON, select the "Use a smart contract" when choosing how you want to create your transaction. Then click "Upload JSON".
Den accepts two formats for JSON uploads: * Transactions with `to`, `value`, and `data` fields * Transactions with the function name and parameters specified, based on the Safe UI transaction builder's import / export format Example for the first format: {% code title="Approve 0 WETH" %} ```json { "chainId": "1", "transactions": [ { "to": "0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2", "value": "0", "data": "0x095ea7b300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" } ] } ``` {% endcode %} # Adding Descriptions Den lets you add descriptions to explain transactions At the end of creating a new transaction, Den allows you to add a description. This description is only shared with other owners of the Safe who have signed in with Den, as well as verified notification channels.
# Simulations Simulate transactions as you create Den lets you simulate transactions as you create them, so you can easily iterate to the desired outcome. Simulations show you if a transaction succeeds, how state changes, and what event logs are emitted. To simulate while creating a transaction, click `Simulate Transaction` in the sidebar on the right side of the page.
# Batching Take several actions within one transactions Den allows you to take multiple actions within one transaction. You can add additional transactions to a batch by clicking the `Add transaction` button in the sidebar on the right side.
# Overview The Transaction Page Den's transaction page makes it easy to understand what's happening in your transactions so you can sign and execute in confidence. You can reach this page by selecting a transaction from your Safe page, or by clicking on the link sent in your Den notifications. You can sign, or execute, at any time by clicking the green button on the bottom right corner of the screen. You can reject by clicking the red button on the bottom left.
# Edit Descriptions Den lets you add descriptions to explain transactions Den allows you to add description to your transactions, so you can provide greater clarity on transactions for your team. This description is only shared with other owners of the Safe who have signed in with Den, as well as verified notification channels. Descriptions can be edited from the transaction page by clicking `Edit Description`.
# Decoded Data Den provides simplicity, and handles complexity Den provides easy to understand views for common transaction types. For example, token transfers are displayed as:
Den decodes even the most complex transactions to make them easily human-readable. Parameters have a number of improvements to make them human readable, such as * Numbers can be adjusted based on their decimals * Addresses are labeled so you're not squinting at hex values * Any parameter can be clicked to see where it appears in the underlying smart contract code The below example is an OpenSea Seaport contract call, and can be interacted with [here](https://app.onchainden.com/safes/test/transactions/0x0196ef56a4f4fab14cf38dcbc6021d1b0e397541c50f3f5cea063a684015fb2c).
# Smart Contract Search Find relevant locations in smart contracts Not sure what's happening in a smart contract call? Den lets you click on function names, parameter names, and struct attributes to search where they are in the code so you know exactly how they're used. For example, click here to search the struct parameter `Consideration Amount`.
# Simulation Simulate transactions before you execute Den lets you simulate transactions, so you can be confident in the outcome before you execute. Simulations show you if a transaction succeeds, how state changes, and what event logs are emitted.
# Overview Historically, the last signer to sign a transaction for a Safe multisig has needed to pay the gas for that transaction to be executed. Den let's you pay gas from your Safe directly, instead of paying gas from your personal signing wallet.\ \ By paying gas from your safe directly, you no longer need to: 1. Keep track of gas reimbursements 2. Create extra transactions to reimburse signers for gas. Each of which: 1. Requires collecting signatures 2. Cost gas that needs to be reimbursed again
# How it Works > 📢 Paying gas from your Safe is a native functionality of the Gnosis Safe contracts. For more information, check out [the contracts](https://github.com/safe-global/safe-contracts/blob/main/contracts/Safe.sol) or reach out to our team. ### Requirements 1. Transactions with Safe gas payments must be created in Den. See the FAQ to learn how to make any transaction pay gas from your Safe. 2. Your Safe must have enough native tokens (e.g. ETH on Ethereum Mainnet, MATIC on Polygon, etc) to pay the gas fee. ### How it Works When a transaction is created in Den, it is configured by default so the Safe pays the cost of gas to any executing wallet. After you click execute on Den, a relayer executes the transaction on your behalf and is reimbursed by the Safe automatically. You can choose to override this relayer, and execute with your own wallet. In that case, your wallet is reimbursed instead. If you end up executing this transaction elsewhere, the wallet that executes will be reimbursed instead. # FAQ
What are the security implications of paying gas from a Safe? Paying gas from your Safe is a native functionality of the audited Safe contract. No new smart contract code is used for this feature.\ \ When you create a transaction in Den, the maximum amount is included in the signature itself. The Safe contract enforces that it can not be exceeded. You will see the maximum gas fee, alongside an estimate, when you create and execute transactions in Den.
Will this be more expensive than manually reimbursing signers? It depends, but is likely to save your team money overall. Each individual transaction will be slightly more expensive to send the gas payment alongside the transaction. However, this feature will remove the need to do independent reimbursement transactions, which are more expensive because they include the added gas cost from validating that an additional set of Safe signatures are correct.
Do signers still have to pay gas? Signers will only pay gas if they select “Execute (Pay gas myself with auto-reimbursement)” when executing the transaction, or if the transaction was not created with the ability to pay gas from the Safe.
How can I turn an existing transaction into a gas reimbursed transaction? Navigate to the transaction, click the “Reuse This Transaction” button ![](https://731861436-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPw0mN04sXbA90tnBcjau%2Fuploads%2F2XWVI1Xkpc9j87niNo1e%2Fimage.png?alt=media\&token=32e7a0a3-f24f-4f86-81b3-61eeb932cc4b) 🚨 The nonce will not match. If you wish to replace the non-reimbursed transaction, be sure to edit the nonce before submitting ![](https://731861436-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPw0mN04sXbA90tnBcjau%2Fuploads%2F3LB3miWgxO1YSg9bSpZb%2Fimage.png?alt=media\&token=792b6f75-b738-44fe-a03d-96deabc9ef28) Note: you will have to recollect signatures for this newly created transaction
How do I know if a transaction has gas fees paid by the Safe or not? Look out for the following alerts: ![](https://731861436-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPw0mN04sXbA90tnBcjau%2Fuploads%2FAIpoLw5hX6uH6XH2ZX1r%2Fimage.png?alt=media\&token=76e24118-214f-44de-8d73-558927cc50c0) ![](https://731861436-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPw0mN04sXbA90tnBcjau%2Fuploads%2FF0a5tTxFrQKA2AEmSXAM%2Fimage.png?alt=media\&token=5d2b0972-c048-4817-bbe7-7d1d071b5aa1) Every transaction will have one of these on the page, depending on if it was created with gas paid from the Safe or not.
Does the Safe have to pay gas in native tokens? This first version of gas paid from Safe only supports native token payments. If you want to pay gas in other tokens, let our team know.
What are the maximum possible and estimated gas fees? The maximum possible gas fee is the most your Safe can possibly pay for this transaction. It is encoded in the transaction signatures and enforced by the Safe contract. The estimated gas fees are what you can expect to pay for the transaction if you execute right now. We use a Tenderly simulation and current network fees to calculate this estimate.
# Overview Managing and creating Payment Requests Payment Requests allow team members, vendors, contractors, and others to request payments from your Safe. Teams use payment requests for many types of payments, such as accepting invoices, managing reimbursements, running payroll and more. Payment Requests can be created by anyone with the [payment request form](/payment-requests/send-the-request-form). Signers and editors in your [organization](/organizations/overview) are able to reject or approve requests. Signers can pay approved requests by [creating a transaction](/payment-requests/approve-and-pay-requests). Payment Requests include: * Payment details (token, amount, recipient) * Descriptions * File Uploads
# Send the Request Form Send a link that can be used to request a payment Signers and [editors in your organization](/organizations/overview) can share a link allowing anyone to request a payment from your Safe. This link can be re-used and does not expire. Start by clicking "Payment Requests" in the header.
Then select "Share Payment Request Form".
Finally select which Safe's request form you'd like to share and click the link to copy it to your clipboard.
# Request a Payment Request a payment from the Safe Fill out the Safe's payment request form to request a payment. There are two ways you can get to this form: 1. If you're a Safe signer or organization member, you can click Payment Requests -> Request a Payment
2. Otherwise, a Safe signer or [organization editor](/organizations/overview) can send you a link to the form. Once you have the form, fill in the payment details.
Next, add a description and upload any relevant files. You can also add a bookkeeping category and workstreams for requests to Safes that are in [Organizations](/organizations/overview).
Finally, review the request to confirm it's correct before submitting it to the Safe.
# See Requests you've sent See all the requests you've sent Tracking your requests is important to ensure you are properly paid. To see a list of all the payments requests where your address is the recipient, click the Payment Requests button in the navigation bar. Then, select "Requests sent".
Here, you’ll see a table with * The requests you’ve made * The statuses of those requests * The onchain transactions they’re associated with if they’ve been queued for payment or already paid
# Approve and Pay Requests Approve, reject, and pay the requests users have sent to a Safe Signers and [editors in your organization](/organizations/overview) can approve and reject requests. Signers can create a transaction to pay approved requests. Requests to Safes in [organizations](/organizations/overview) also include a category and workstreams, which will automatically sync to your bookkeeping so you don't need to worry about categorizing them after the payment is sent. To see requests across your Safes, click "Payment Requests" then "Requests received".
Select the requests you'd like to approve or reject. Once you've made your selection, click the approve or reject button to update these requests.
Requests are paid by creating a transaction. Only approved requests can be used to create a transaction. Select the approved requests you'd like to pay, then click the create transaction button to create a transaction that includes these requests.
# Overview Manage Safes in an organization, perform bookkeeping, and get financial insights Organizations, as well as bookkeeping and financial insights, are part of Den's upcoming premium tier. These feature are currently available in limited early access. [**Book a demo here**](https://calendly.com/onchainden/demo) to learn more and see if you qualify for early access. The premium tier provide an organization where you can: * Group together related Safes. * Give non-signers permission to see and edit offchain data such as payment requests, address book labels, and transaction descriptions. Transparent organizations can make this information public. * Complete end-to-end bookkeeping for your Safes and any other addresses such as wallets and contracts. * Export data and sync categorized bookkeeping data to Quickbooks as journal entries. Xero and Netsuite coming soon. * Access dynamic financial insights charts and reports. [Book a demo now to learn more.](https://calendly.com/onchainden/demo) # Overview Understanding and Configuring Den's Notifications Den's Discord, Telegram, Slack and SMS bots send notifications to your team on a recurring basis until your transactions are executed. Notifications are sent when a transactions is created, executed, or rejected. Reminder notifications are sent at a pre-defined frequency for transactions that have not been executed within that time frame. These notifications help your team coordinate effectively to execute transactions fast. DAOs also use notifications for greater community transparency into multisig operations. You can configure notifications by going to a Safe's Notification page. To get here, select your Safe and click the bell icon.
# Set a Reminder Frequency Reminders are sent on a recurring basis until the transaction is executed If a transaction isn't signed after a certain period of time, Den will send a reminder notification so your team doesn't forget to sign it. These reminder notifications are sent on a recurring basis until the transaction is executed. For example, if you set your reminder frequency to `24 hours` then your team will receive a reminder notification every day until the transaction is executed. The reminder frequency can be changed on the notifications page by selecting a new value in the reminder frequency dropdown.
# Discord Setting up Discord Notifications Discord notifications can be set up by following the instructions on the Safe's notification page. Instructions differ based on whether or not you are an admin for the Discord server. An admin is required to add the bot to your server. Once the bot is added, anyone can set it up. Some teams with complicated Discord permissions may run into trouble setting up the Bot. If this happens to you, contact the Den team for support using the link in the sidebar to the left. To see the instructions for setting up Discord, click `Add The Den Bot`.
# Telegram Setting up Telegram Notifications Telegram notifications can be set up by following the instructions on the Safe's notification page. To see the instructions for setting up Telegram, click `Add The Den Bot`.
# Slack Setting up Slack notifications Slack notifications can be set up by following the instructions on the Safe's notification page. You will be directed to Slack, where you will install Den's Slack Application into your workspace. If you are using a private channel, you must first invite the bot to the channel. To see the instructions for setting up Slack, click `Add the Den Bot`.
# SMS Setting up SMS Notifications SMS notifications can be set up by inputting your phone number next to your address on the Safe's notification page. You can only set up notifications for your own phone number for privacy purposes. You're able to see if other team members have added their phone numbers as indicated by `(***) ***-***`, but won't have access to their information. SMS is currently supported for the following regions: US, Canada, Bahamas, Ireland, Belgium, Germany, Portugal, and UK. Interested in an unsupported region? Contact the Den team using the Feature Requests link in the sidebar to the left.
# Bot Commands What you can do with Den's Discord and Telegram Bots Den's Discord and Telegram bots support a number of commands to help your team move fast, such as tagging team members who have not yet signed, temporarily silence notifications, generate stats on signer activities, and more. {% hint style="info" %} For a full list of commands, run the `/help` command in Discord or Telegram {% endhint %}