[Discussion] Introduction to GuardianSafe: Advanced Security Guard for Safe Wallets Built on Bloxchain Protocol

Overview

GuardianSafe is a security extension guard module designed to enhance the multisig security of Safe wallets. Developed by our research team at ParticleCS, It is built upon our Bloxchain Protocol and our State Abstraction technology. This protocol provides a foundational multi-phase, role-based security architecture that underpins GuardianSafe’s enhanced security features.


Motivation and Context

Recent discussions within the Safe community have highlighted critical areas for improvement in Safe wallet security, notably:

  • The risks associated with the unrestricted DELEGATECALL operation

  • The need for configurable time-lock mechanisms for transaction approval

  • Supporting meta-transactions for gas-efficient and delegated transaction management

  • Enhancing multi-factor verification with role-based access control (RBAC)

GuardianSafe is designed to address these concerns by providing a modular security guard that integrates directly with Safe wallets via the ITransactionGuard interface, enforcing rigorous security policies before transaction execution.


Key Functionalities

  1. DELEGATECALL Protection
    By default, GuardianSafe blocks all DELEGATECALL operations, preventing unauthorized external code execution which could compromise wallet security. Owners may selectively enable DELEGATECALL with enforced delays to mitigate risk.

  2. Multi-Phase Time-Locked Workflows
    Transactions proceed through distinct phases, requiring an initial request and a mandatory time delay before final approval and execution. This approach introduces a temporal security layer permitting external monitoring and intervention.

  3. Meta-Transaction Support
    GuardianSafe facilitates gasless transaction approvals and cancellations through meta-transactions, enabling the broadcaster role to submit signed transactions under controlled conditions.

  4. Role-Based Access Control
    The module implements granular RBAC separating transaction creation, broadcast, and emergency recovery duties into discrete roles with clearly defined permissions, reducing attack surfaces associated with key compromise.

  5. Transaction Guard Enforcement
    Acting as a Safe wallet guard, GuardianSafe validates all transactions, ensuring they adhere to configured security policies, including preventing unauthorized guard modifications.


Community Alignment

GuardianSafe synthesizes and extends multiple community-led initiatives:

These integrations ensure GuardianSafe reflects current best practices and addresses evolving security threat models.


Availability

GuardianSafe is currently available for experimental deployment in our sandbox environment:
**https://sandblox.app/contracts/guardian-safe

more information can be found on our official repo:**

The module is open for community testing, feedback, and collaboration.
under open-source license MPL-2.0


Conclusion

GuardianSafe represents a methodical and technically rigorous security enhancement for Safe multisig wallets, leveraging foundational innovations in the Bloxchain Protocol and State Abstraction. It provides a multi-layered, auditable security solution addressing key vectors of risk identified by the Safe community.

We invite discussion, review, and collaboration to further refine and integrate GuardianSafe into the broader Safe ecosystem.


Particle Crypto Security Team

I have not looked at the details but on the surface it looks nice. Is there a plan to have it autided and moved out of experimental status? If yes, what is the timeline?

[Disclaimer - my original account, JaCoderX had been flagged by AI on a different post, so will use this temporary account just for this topic until it is resolved with Safe]

short answer - yes, we plan to audit around Q1 2026

longer answer - the GuardianSafe security extension is being built on top of our development and security framework called Bloxchain Protocol, which by itself is a library of contracts.
being safe users ourself we decide to build the GuardianSafe as our first real world use case of the framework. so audits are our main focus but the whole protocol need to be audited before we can officially audit the guard

GuardianSafe is still in development, so any idea the community have could be implemented as part of the guard.

also the team here at safe is working on it own technologies like the policy engine guard framework posted just yesterday. So maybe more synergies can be created by the two frameworks

anyway our goal is to audit in Q1 2026, but we are flexible to adjust to the evolving space needs

1 Like