We planned to add several new networks/chains to the Gnosis Safe however when adding BSC/Polygon/Arbitrum support we noticed that there are several issues such as unreliable nodes which leads to overhead in managing the required backend services.
Problem details
We believe in a "multi-chain future" and planned to add support to many new networks to the Safe.
We added support to BSC, Polygon. Arbitrum support is in progress.
We worked on a unified interface to manage multiple networks via 1 interface.
We built the "unified client gateway"
Still, we encountered many issues that slowed us down:
Unreliable nodes that posed challenges to indexing
Increased user requests
EVM issues with beta-projects (cf. the issue we encountered with Arbitrum)
Essentially we had to fix a lot and could not handle adding more networks just yet.
Some future network integrations even require adapting the contract code.
Solution ideas
Make it easier to self-host the Safe infrastructure
Improve documentation.
Build an Safe L2 interface which only works with events, i.e. which only requires an RPC endpoint and which does not require our full-fledged backend.
Explore integration of non-Gnosis hosted networks in the UI (While making it clear in the UI)
Fix performance bottlenecks on our side as much as possible.
Problem summary
We planned to add several new networks/chains to the Gnosis Safe however when adding BSC/Polygon/Arbitrum support we noticed that there are several issues such as unreliable nodes which leads to overhead in managing the required backend services.
Problem details
Solution ideas