Skip to main content

Nested Safe's

Using as a Safe as a signer for another Safe

Tobias Schubotz avatar
Written by Tobias Schubotz
Updated over a month ago

What are Nested Safes?

Nested Safes allow you to use one Safe as a signer for another Safe. This creates a hierarchical security structure where child Safes inherit the security properties of their parent Safe.

Example of a nested safe setup;

2 Owners. One owner signs using an EOA (Metamask) while the other owner uses another safe. The threshold for this safe is 2 implying that both owners must sign the transaction in order for it to be successful.

The transactions are executed in a tree structure.

  1. The transaction is proposed in the original Safe

  2. The transaction is broadcasted and then pops up in the queue on the nested or signer safe

    • Each signatory of that Safe must then sign the transaction, these could also be other Safe's. You could potentially have chains of nested Safe's

  3. Finally, transaction is then executed on the original Safe

Key Benefits

  • Enhanced Security: Create multiple security layers for your most valuable assets

  • Organizational Structure: Mirror your organizational hierarchy on-chain

Creating a Nested Safe

  1. Access your Safe{Wallet}
    ​

  2. Set up a new Nested Safe

    • Click "+ Add Nested Safe" located on the main Dashboard screen

    • Name your Nested Safe (e.g., "Delighted Nested Safe")

    • Select assets to fund it with

    • Click "Next"

  3. Confirm the creation

    • Review transaction details

    • Approve the transaction

Managing Nested Safes

  • View all Nested Safes via the Nested Safes interface, you can see this in the setup section on the wallet.

  • Add multiple Nested Safes to create complex hierarchies

  • Rename existing Nested Safes for better organization

Transaction Flow with Nested Safes

  1. Transaction Proposal: A transaction is proposed in the parent Safe

  2. Child Safe Notification: The transaction appears in the queue of the child/signer Safe

  3. Multi-level Signing: Owners of the child Safe must sign according to its threshold

  4. Execution: Once threshold requirements are met at all levels, the transaction executes on the parent Safe

πŸ’‘ Child-Safe's also function as de facto proposers

Child Safe owners can propose transactions directly to their Parent Safe using pre-validated signatures, enabling immediate processing in nested configurations.

Best Practices

  • Start with simple hierarchies before creating complex structures

  • Use clear naming conventions for easy identification

  • Consider threshold requirements carefully at each level

  • Regularly audit your Nested Safe structure

FAQ

Can Nested Safes have their own Nested Safes? Yes, you can create multiple levels of nested hierarchies.

What happens if a parent Safe is compromised? Child Safes could potentially be affected, so secure your parent Safe appropriately.

Did this answer your question?