[Discussion] Use Ethereum Distribution System to distribute Safe wallets

Authors: peersky.eth ( tim@peeramid.xyz )

Created: 2024-10-31

Abstract

This proposal suggests integrating the Ethereum Distribution System (EDS) developed by Peeramid Labs with the Gnosis Safe wallet to streamline and enhance the distribution of assets within the Safe DAO.

The EDS, written predominantly in Solidity is designed to automate and secure the distribution of Ethereum-based assets & infrastructure. By leveraging EDS, Safe DAO can achieve a more efficient, transparent, and secure method for distributing tokens and managing multi-signature wallets, ultimately enhancing the overall governance and operational efficiency of the DAO.

This proposal addresses multiple ORBA goals such as Safe token utility & Foster module ecosystem

Proposal types

State which proposal type this proposal belongs to.
SEP: Constitutional Proposals
SEP: Governance Proposals
Other SEPs

Proposal details

Purpose and Background

The purpose of this proposal is to integrate the Gnosis Safe wallet distribution within Ethereum Distribution System (EDS) developed by Peeramid Labs and enhance the smart wallet source code distribution mechanism managed by Safe DAO.
The EDS, predominantly written in Solidity, offers a secure and automated method to distribute Ethereum-based assets, aligning with Safe DAO’s goals of transparency, efficiency, and security in managing multi-signature wallets. This integration aims to streamline asset management, reduce manual intervention, and leverage the robust functionalities provided by EDS for improved governance and operational efficiency.

Integrating with EDS provisions new novel ways of interacting, writing and securing software. Users of EDS distributions may incorporate it in their own distributions, allowing to bypass needs to issue token allowances and permits for contracts operating within a trusted ecosystem or instance.

One Year Support:

  • Peeramid Labs will establish dedicated support line to gather Gnosis Developer community feedback and assist on any technical questions
  • Developer tooling: to ease the creation and distribution of new EDS versions, modules and guards.
  • Upon initial release Peeramid Labs will take on duty to create a governance proposals for new safe versions addition to repository and provide technical support.
  • Educational sessions: Peeramid Labs will host at least 5 educational workshops (online or in person) where will be explained new mechanics developer can embed in their applications, as well as elaborate documentation needed for developers to build and migrate their existing solutions for Safes using EDS

Effects and Impact Analysis

Pros:

  • ORBA [Safe DAO token utility]: Distributor model in EDS provisions ability to charge accounts for runtime security on subscription base while keeping security oracle choice up to a user, fostering decentralized security oracle market

  • OBRA [Foster module ecosystem]: Safe DAO provisions success for it’s product and enables ecosystem level integration capabilities:

    • developers may re-use DAO distributed packages to create own versions (e.g. additional modules & guards)
    • DAO may list such additional packages in own repositor(y/ies)
    • Other projects may easily incorporate Safe Wallets in own Distributions
  • Efficiency: Safe DAO can focus on distributing best smart account, without need to design the distribution pipeline

  • Security: The EDS model provisions ability for Safe distributions to be wrapped by ERC7746 as middleware, making a runtime checks to the distributors, who may act as security oracles, and may disable specific vulnerable instances or require version upgrades

  • Transparency: Provides a clear and auditable record of distributions, improving transparency and accountability within the DAO.

  • Operational Overhead: Reduces the operational burden on DAO members by automating routine tasks.

  • Scalability: Facilitates easier scaling of asset distribution as the DAO grows, without a corresponding increase in manual workload.

  • Semantic versioning: Safe accounts may reuse build-in semantic versioning system, e.g. to embed EIP712 signatures

Cons:

  • Complexity: Initial setup and integration may be complex and require domain expertise.

Risks:

Technical Risks: Potential bugs or vulnerabilities in the EDS or integration process. New solution, needs to be heavily battle tested.
Operational Risks: Mismanagement or misconfiguration could lead to distribution errors.

Alternative Solutions

Currently there is no global united distribution system on-chain.

Alternative for SAFE DAO is to use own distribution system & factories that is not the main objective of SAFE and it leads to reduced efficiency and fragmentation.

Implementation

Setting up a Distributor Contract: A distributor contract managed by Safe DAO will be established to handle asset distributions.
Integration with Safe Multisig Contracts: The integration will be done using ERC7746, allowing “safe guards” extensions to hook back to DAO managed distributor contract to ensure secure and compliant operations of multisig contracts.

Own implementation possible
Own implementation but with funding (how much % to implementation)
Request for technical support through Safe matter experts:

  • Who is needed?
  • Did you reach out?
  • Is there a roadmap?

Open Questions

Should EDS development be managed as a DAO itself?
Currently, EDS does not support major version upgrade migration scripts. Would this feature be desired?

Funding Request

  • Auditing EDS: (TBD, may be joint ecosystem effort)
  • Implementing Guard Plugin & initial distribution: $10,000
  • Setting up EDS Repository for Safe DAO: $1,000
  • Implementing Additional Features:

Total Funding requested: $41,000 USD (TBD)

One year support

About Peeramid Labs

Our mission is to accelerate coordination of decentralized communities, we build social coordination tooling & infrastructure, part of which is EDS.

You can read more about us at https://peeramid.xyz

Copyright

Copyright and related rights waived via CC0.

1 Like

Hey @peersky, thank you for the proposal! Noting that the funding ask might benefit from clarification — could you add something along the lines of a ‘total funding request’ to summarize the total amount requested?

2 Likes

cheers!

and input of old gnosis json key wayback 2016