[Draft/Discussion][OBRA] Cross-Chain Signers Synchronization for Multi-sig Wallets

Proposals Phase 1: Draft
1
  1. Initiative title: [Draft/Discussion] [OBRA] Cross-Chain Signers Synchronization for Multi-sig Wallets - Vadim Makovsky

  1. Abstract:
    This proposal introduces a new approach to creating and managing multi-sig wallets across different Layer 2 (L2) networks, enhancing the user experience. When the configuration of the master wallet on the Ethereum blockchain is changed, the corresponding changes of the owners set are automatically across all dependent wallets on the L2 networks. The update process requires a valid zk-proof to confirm the new signers.

    The final solution will include a ready-to-use safe module, along with full-cycle integration into the proving protocol, covering proof building and verification.

  1. Aligned strategy: Wildcard strategy
  1. Funding request: 35000 USDC.
  1. If applicable, upfront funding: No
  1. Relation to budget: Total budget 35%, Remaining Budget 15%

  1. Metrics and KPIs:

    We are working on Dune visualization and are going to add it in this section before the start of voting for the proposal

  • Number of manual transactions changing the Owners set on follower networks

  • Number of Successful Account Synchronizations

  • User satisfaction rating

  • Security incidents reported

  1. Initiative description:

    This proposal aims to enhance the user experience in managing cross-chain multi-sig accounts. Currently, when users want to change a signer in such a wallet, they must manually create, sign, and approve the same transaction across all blockchains or rollups where the wallet exists. This process requires the presence and action of all signers throughout and incurs gas fees on each blockchain or rollup.

    This initiative proposes using a zero-knowledge proof approach to propagate updated signers across all protocols with a single action.

    Effects and Impact Analysis

    Pros:

    • Provides a reliable synchronization method that improves user experience.

    • Reduces the risk of human error.

    • Advances in the development of omni-chain architecture.

    • Requires less or the same amount of gas.

    Cons:

    • Requires an additional module.

    Implementation

    In the context of the interchain sync, there is a master chain (the preferable options are the Gnosis Chain and the Ethereum Mainnet) and several follower chains (such as Arbitrum, Polygon, and others).

    The trustless sync mechanism will consist of several parts:

    • The off-chain indexer of the master chain

    • The off-chain zk-proving part (includes the multi-sig verification circuit)

    • The endpoints on the follower chains

    Integration with the Safe contracts

    The integration with the Safe contracts will be done through a Safe module that will manage the zk-proof verification and trigger Safe’s OwnerManager to apply the verified changes in the multi-sig configuration.

  2. Current status: We are going to use funding to create a service.

  1. Risks:

  • The Modules allowed to modify Owners set have the highest access level to the Safe account, so a proper audit is crucial.

  • Implementation complexities due to the different configurations of the Safes.

  1. Timeline and milestones:

    Phase I. Proving in testnets

    • 7 weeks: Design and implementation of the threshold multi-sig verification circuit

    • 4 weeks: Implementation of indexers and provers. Provers management CLI development.

    • 2 weeks: Deployment of testnet follower chains verifiers. Integration of verifiers with the testnet Safe contracts.

    Phase II. Distributed proving in testnets

    :compass: We are working on Dune visualization and are going to add it in this section before the start of voting for the proposal

    • 3 weeks: Implementation of intermediate verification strategies and fault-tolerance algorithms of proof aggregation.

  • Separate module

    • 4 weeks: UI for the module.

  • A Zodiac module

    • 2 weeks: integration with the Zodiac library

  • A Safe module

    • 2 weeks: integration with the Safe Modules repository

    Phase III. Distributed proving in mainnet

    The timelines of this phase will depend significantly on the security audit, so for now, we will only describe the intermediate steps.

    TBD (est. 5 weeks): Deployment of the mainnet follower chains verifiers and integration of the verifiers with the mainnet Safe contracts.

  1. Initiative lead: Individual, Vadim Makovsky
  1. Team:

Vadim Makovsky - project manager, ex CEO p2p.org, early lido.fi contributor ( vadim.makovsky@gmail.com, telegram: vadimicus, x: vadimicus)

Nikita Kaskov - technical lead, ex CTO Fair Math, ex Head of cryptography nil.foundation ( mail.nikita.kaskov@gmail.com, telegram: nkaskov )

Mikhail Voronov - research lead, head of Research fluence.network (michail.vms@gmail.com, x: vms11

Alexander Cherenkov - RnD engineer , ex zk research nil.foundation

  1. Additional support/resources: media promotion, when the work is done
  1. Implementation dependencies: No
1 Like
2

Hey @vadimicus, as I mentioned on Discord, this is an OBRA proposal, and the DAO has temporarily paused accepting OBRA proposals for this sprint.

2 Likes
3

Hi @amanwithwings,

Thanks for your response!

I just have a small question for clarification. Will my proposal still be reviewed during the Community call, even if it doesn’t require upfront funding as it stands?

4

It will not be considered in this sprint, as it requests funding to execute.