Investigate decentralized standard to exchange signatures and transactions

[rmeissner]

Part 1: Define the problem

What problem are you trying to solve?

Currently the best way to exchange signatures and transactions is to rely on our centralized infrastructure. It would be good to support a more decentralized approach.

To what strategic goals does it contribute

Decentralization

What is your hypothesis?

If we provide a more decentralized solution it will allow more ecosystem contributors to build integrations on top of the Safe and provide additional services and fallbacks.

What value does this bring to our customer and/or our mission? What is the goal?

More custom solutions for specialized user flows and more stability due to more decentralized alternatives.

This also is important for one of our primary goals: Decentralization

How do we measure it?

Data exchanged via p2p logic.

Links:

• https://docs.google.com/document/d/1qRE5L9GEvN9dTKGLfMNSQvG3fN4k9rP5n1KncH9jEgI/edit
• https://gitcoin.co/issue/status-im/js-waku/586/100028462

Part 2: Shaping the problem

Problem Owner

// To define

Non Goal(s)

• The current services should not be adjusted

Envisioned or preferred Solution

Solution 1

Define Waku messaging protocol

Overview Waku defines a decentralized (p2p) communication layer that can be used to exchange information. Based on this a protocol should be defined that allow exchanging and verifying information related to Safe indexing.

To verify the solution some testing script should be developed. In a next step these could be converted into a micro-service that can propose information to our centralized service architecture.

Check existing prototype: https://github.com/Soptq/gnosis-safe-waku

Rough Scoping & Timeline

1 month should be enough for developing a MVP.

Risk(s), Key Trade Offs & Decisions

• Creating our own implementation. TradeOffs: A lot of time, resources and expertise is required for that, also legal implications. Advantages: full control of the service, even taking comercially advantages like charging fees if we want.

Related topics

• Refactor the service infrastructure to be a combination of micro services (e.g. extract notification service from transaction service)
• Allow external transaction services to be connected to our infrastructure setup

Open Questions

[DmitryBespalov]

If possible and looks like in scope, I'd vote for researching if this can be used as a general means for a data sync between applications/interfaces. Not just signatures and transactions, but an alternative to a centralized cloud database

[fryorcraken]

If possible and looks like in scope, I'd vote for researching if this can be used as a general means for a data sync between applications/interfaces. Not just signatures and transactions, but an alternative to a centralized cloud database

Hi, Waku dev here.

Yes, this should be possible. Do note that we are targeting 30 days message retention capability in the fleet.