Private transactions for your Safe, now in early access for professional teams

Professional teams can now test private balances, transfers, and transaction queues on their Safe with Bermuda, a compliant privacy solution funded by Gnosis. Help decide what comes next, and make your workflow the standard.

Public blockchains make financial activity independently verifiable. It is one of their most important properties and a foundational reason organizations use Safe.

For many teams, that transparency is exactly what they want. It supports accountability, governance, and independent verification of how assets are controlled.

But not every workflow has the same requirements. Payroll, treasury execution, counterparties, and pending DeFi transactions can contain information an organization may not want to disclose publicly.

For Safe, privacy is an additional capability users should be able to choose when a workflow requires it.

If confidentiality is becoming relevant to how your organization operates onchain, apply to become a Safe Privacy Design Partner.

The question we have been exploring is whether teams can retain the self-custody, verifiability, and organizational controls they already rely on with Safe, while adding confidentiality where a particular workflow requires it.

Privacy without giving up control

Privacy for an organization is different from privacy for an individual wallet.

Professional teams still need multiple signers, asynchronous approvals, recovery, policies, transaction verification, and security controls. Adding confidentiality should not mean abandoning those properties.

Privacy redistributes trust assumptions rather than removing them. Different approaches introduce different dependencies and trade-offs. Safe's role is to ensure that adding privacy does not compromise the user's self-custody or control.

This reflects a broader Cypherprise principle: professional-grade capabilities should strengthen what organizations can do without creating a new custodian or dependency they cannot replace or exit.

Over the past year, Safe has explored different approaches to privacy alongside teams across the Ethereum ecosystem, including Railgun and Kohaku.

Cheshire, an internal Safe privacy research project, explored how threshold cryptography and MPC could allow multiple participants to control private assets without reducing organizational control to a single privacy key. Nicolas Consigny and Vitalik Buterin later featured a demo of Cheshire in the Ethereum Foundation talk "Kohaku: Reclaiming the Original Vision" at EthCC[9]. Cheshire's source code is available on GitHub.

One principle has remained consistent: confidentiality should not require giving up control.

From research to beta testing with Bermuda

We are now working with Bermuda to bring that principle to enterprise users.

Bermuda has focused on combining shielded transactions with multi-party account control and has increasingly shaped its product and roadmap around the requirements of Safe users.

Private balances, transfers, transaction queues, and DeFi calls are already built in. Share your requirements for threshold configuration, recovery, and organizational policies, and help make them the standard.

The focus on policies and recovery is an important reason we are working together.

Bermuda and Safe are exploring how confidentiality can extend the account model and controls users already understand. Bermuda has also built a solution for issuers and is developing approaches to screening and policy enforcement for private transactions, another area we want to evaluate carefully with professional users.

Bermuda and Safe are inviting enterprise users to become design partners. Design partners can use Bermuda with their Safes on testnet and help shape the workflows before release. 

Now entering real-world testing

The Bermuda integration is currently in beta.

Safe is validating the complete end-to-end experience, and there are important questions to work through across security, audits, UX, recovery, policy compatibility, compliance requirements, and the additional infrastructure private transactions introduce.

That validation is the purpose of this next phase.

We also expect privacy for smart accounts to evolve across different technical approaches. Private payments, confidential balances, transaction queues, and private DeFi activity may not ultimately require the same solution.

As we evaluate Bermuda and other approaches, confidentiality alone is not enough. We also want to understand whether users can verify what matters, recover without introducing a new custodian, replace infrastructure dependencies, and exit with their assets under their own control.

Our work with Bermuda gives us a concrete implementation through which to start testing these questions with the organizations that actually face them.

Help us shape what comes next

The hardest questions are:

• Where does confidentiality create meaningful value?

• What should remain public?

• Where do we need independent verification?

• Who inside an organization needs visibility?

• Which existing controls need to carry across? 

To help answer those questions, we are opening a Safe Privacy Design Partner Program.

Selected teams will work directly with Safe and Bermuda to test privacy workflows against real organizational requirements, from treasury operations and payments to transaction preparation and other sensitive onchain activity. Design partners can also share their requirements for threshold configuration, recovery, and organizational policies before release.

Design partners’ feedback will help inform what Safe should build, integrate, or support next.

Privacy and Safe Pro

This work also reflects a broader principle behind Safe Pro.

As organizations operate more complex workflows onchain, we want to give them more choice and stronger controls without taking away the security, self-custody, or familiar workflows they already have with Safe.

For some professional workflows, greater control over information disclosure may become a requirement.

Qualified Safe Pro customers and other professional teams may therefore participate as design partners, test beta implementations, and work with Safe and partners such as Bermuda on future requirements.

If your organization is exploring confidentiality onchain, apply to become a Safe Privacy Design Partner.

Safe Labs

2 October 2026

Copy link