See also:
Safe{Core} Protocol is an open, modular framework to make smart accounts secure, portable, and composable.
The goal is to create a comprehensive system, designed to enhance the safety and flexibility of user interactions within the smart account ecosystem. The protocol provides a common framework for building additional tools, encourages the composition of various modules, and supports different types of smart accounts. In order to achieve interoperability and security, the protocol enforces a set of rules within the smart account ecosystem.
The architecture of the Safe{Core} Protocol is composed of several integral components, each carrying its unique responsibilities. The protocol is designed to distinctly separate these elements by defining explicit interfaces, thus allowing independent expansion and iteration of each part. This modularity ensures the sustainable growth and evolution of the smart account ecosystem.
At the heart of the protocol is the Manager, ensuring adherence to the prescribed rules set by the Registry. The Manager serves as an intermediary layer coordinating communication and interactions between Accounts and Modules.
Accounts are smart-contract based user accounts (or “smart accounts”). The Safe{Core} Protocol is account-agnostic, meaning that it is not tied to a specific account implementation.
Modules extend the functionality of Accounts in different ways. Initial modules are plugins, hooks, function handlers and signature validators, but additional modules can be added to the Safe{Core} Protocol at a later point.
The Registry plays a critical role in maintaining and enforcing standards and security guarantees. Only the Modules that adhere to these guidelines will be recognized and managed by the Manager.
To provide a coherent context to the various parts and their interactions, the provision of Metadata is crucial. This information allows developers to append additional context to interactions, enhancing user understanding and interaction transparency.