https://github.com/5afe/safe-core-protocol-specs
Safe{Core} Protocol is an open, modular framework to make smart accounts secure, portable, and composable.
https://github.com/5afe/safe-core-protocol-specs
Last synced: 8 months ago
JSON representation
Safe{Core} Protocol is an open, modular framework to make smart accounts secure, portable, and composable.
- Host: GitHub
- URL: https://github.com/5afe/safe-core-protocol-specs
- Owner: 5afe
- License: gpl-3.0
- Created: 2023-05-17T09:55:52.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2024-02-14T08:30:52.000Z (over 2 years ago)
- Last Synced: 2025-03-30T08:32:57.768Z (about 1 year ago)
- Homepage:
- Size: 1.11 MB
- Stars: 68
- Watchers: 13
- Forks: 13
- Open Issues: 14
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
**:warning: This repository is not actively developed at the moment. :warning:**
# Safe{Core} Protocol Specification
See also:
- [Protocol Whitepaper](./whitepaper.pdf)
- [Protocol Implementation](https://github.com/5afe/safe-core-protocol)
- [Protocol Demo Application](https://github.com/5afe/safe-core-protocol-demo/)
## Motivation
Safe{Core} Protocol is an open, modular framework to make smart accounts secure, portable, and composable.
## Objectives
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.
[Read more on "Objectives" ->](./objective/README.md)
## Architecture
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.
### Manager
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`.
[Read more on "Manager" ->](./manager/README.md)
### Accounts
`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.
[Read more on "Accounts" ->](./accounts/README.md)
### Modules
`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.
[Read more on "Modules" ->](./modules/README.md)
### Registry
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`.
[Read more on "Registry" ->](./registry/README.md)
### Metadata
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.
[Read more on "Metadata" ->](./metadata/README.md)