Chain-Specific Info

This step-by-step guide is designed to help you seamlessly onboard to Console, explaining both Safe creation and import flows. A video tutorial is also available below.


Console is a self-custodial product with a security-first design.

Based on Safe, we leverage the gold standard of multi-sig security and have built additional access control, automation, and execution functionalities on it. Console is not an isolated or closed environment. You can connect to any dApp on Ethereum and Arbitrum via Wallet Connect to perform any transaction you wish, as you would normally do from your wallet.

Console's onboarding process is designed for ease and efficiency, taking only moments to complete. Users initiate by linking a wallet, such as Metamask, choosing to either establish a new Console with a Safe setup or import an existing one. A single transaction will set up the new Safe or verify the imported one, establishing Safe owners as Console owners. The Main Safe, central to the Console environment, governs all administrative actions with its on-chain signature threshold.

After onboarding, users gain full access to the Console Account, ready to perform standard operations, interact with dApps, and expand functionality through Sub-Accounts. These Sub-Accounts are separate Safes owned by the Main Safe, tailored by Owners with specific Operators and Policies to enhance control and precision. Owners have the flexibility to manage any Sub-Account, while Operators are confined to their assigned areas, all accounts are owned by under the Main Safe for streamlined administrative oversight.

Onboarding Tutorial

Once you will get approved to access Console, you will be able to log in on Ethereum or Arbitrum, and you will be asked to sign in to your wallet (all of the multi-sig signers will have to do so).

Step 1: Connect Your Wallet and confirm ownership

Begin by connecting your Ethereum EOA wallet using supported interfaces like Rabby, MetaMask, WalletConnect, or others.

  • Please connect the wallet you want as a Console owner. You can always change the created/imported Safe ownership configuration with an admin transaction.

  • You will be asked to sign a message with your wallet to confirm your ownership of it.

Step 2: Name your Console

Here you can give a name to your Console. This will be private and visible to you and your team members. You can change this name at any time from the Console settings. Once onboarded, you will be able to create SubAccounts and name them separately for their purpose.

Additionally, you can create multiple Consoles with fully separate owners, accounts and history.

Step 3: Choose Your Onboarding Path

  • Decide whether to create a new Safe or import an existing one.

  • Creating a new Safe is ideal for new users, while importing is suited for users with an existing Safe setup.

The owners of the created/imported Safe will be the owners of the Console. For example, if a Safe is imported with a signature threshold of 4/7, the 7 owners will be the Console owners, and the 4/7 threshold (signature from the Main Safe) will be required for all administrative operations, such as setting up SubAccounts, controlling accesses, policies and members. A Console can host several Sub-Accounts, which can be configured according to the actions and tasks required to carry out. This allows teams to create and join multiple consoles, improving delegation, control, and team collaboration.

For Safe Creation Flow

Step 4: Create Your Safe

  • Follow the prompts to configure your new Safe, including naming your Safe and setting up the ownership structure and signature threshold.

  • Your Safe is the Main Account and owner of your Console, governing the subsequent admin setup and operations across your Console.

If you create a new Safe, you will then be able to set the owners and the execution threshold in advance. Bear in mind: this Safe will control all of the Sub-Accounts in the Console environment.

Step 5: Finalise Safe Creation

  • Review the transaction details for creating your Safe.

  • Sign the transaction using your connected wallet. This step incurs a gas fee for deploying the Safe smart contract on the blockchain.

This Safe is solely owned by the owners you added and is a default Safe with no customisation added. This Safe is yours to keep and use forever, and fully accessible at any time through the independent Safe UI and contracts.

Step 6: Access Console Dashboard

  • Once your Safe is created, you'll be redirected to the Console dashboard.

  • Explore Console features, create Sub-Accounts, set policies, and start managing your DeFi operations.

For Safe Import Flow

Step 4: Import Your Safe

Console will auto-detect the Safes your connected EOA wallet is an owner of

  • Select the Safe you would like to import

Step 5: Verify Ownership

Sign Verification Transaction

  • Sign a verification transaction to confirm your ownership of the Safe and its association with your Console.

  • This step requires meeting the signature threshold of the Safe being imported. If the Safe has a multi-sig threshold (e.g 3/5), the other owners will also have to be ready to sign an import transaction to prove the Safe’s ownership

Step 6: Explore Console

  • With your Safe imported, you're all set to utilise Console.

  • Start by exploring available features, creating Sub-Accounts, and customising permissions for your team and operations.

Step 7: Customise Your Console

  • Post-onboarding, enhance your Console organisation by creating Sub-Accounts.

  • Assign specific functions and names to each Sub-Account to reflect their roles within your organisation.

This guide aims to provide a clear path to onboard to Console, whether you're setting up a new Safe or bringing an existing one into the Console ecosystem.

For further assistance, feel free to check out the rest of the Console documentation, and reach out to the team through the live chat bubble on the bottom left of the Brahma website, or in the Console dashboard once onboarding is completed.

Last updated