Decentralized deployment

[maikReal]

What to do?

• [ ] @maxaleks Deploy our current UI on IPFS and create several mirrors. For this purpose, we can use dappling.network. Also, we can also leave the Netlify mirror as well
• All mirrors shouldn't be connected to the app.zkbob.com subdomain
• UPD 18.10: We need to leave the app.zkbob.com deployment as it is right now
• @maxaleks After deploying the UI, pls, attach all mirrors to this issue. So, final result is: link to IPFS deployment and 2 raw links for mirrors
• We can take a look at how TC made this
• [ ] @maxaleks Fix all issues that can be caused by deploying on IPFS. From the latest deployment (https://zkbob-ui.dappling.eth.limo/) that @r0wdy1 made, we got the following list of issues:
• Issue with Sentry
• No access to downloading parameters. For now, we have access only to the zkbob.com domain and localhost
• Wallet connect doesn't work
• [ ] Add licenses for all necessary repos, including UI repo @r0wdy1
• [ ] Add the guide "How to deploy zkBob UI on IPFS?" to the zkBob UI repo @r0wdy1 We can also add small instruction how to launch the app locally

[maikReal]

UPD 11.10: Not relevant @r0wdy1 Will start researching the first stage, but he will need the help of @maxaleks

• we need to change routers on the UI

[maikReal]

UPD 18.10:

Regarding the decentralization protocol, we’ve opted to maintain the current state of the app located at app.zkbob.com. Concurrently, we are actively developing the IPFS version and other mirrored deployments. To highlight these decentralization options, we plan to add additional buttons on our website. While these alternatives may not perform as well as our primary deployment on app.zkbob.com, it’s a conscious choice. Users interested in decentralized apps should be aware of the necessary trade-offs.

Addressing the question of updating all instances with each release, the affirmative stands true for now, given our infrequent releases. Once changes related to the Tron deployment are completed, we can promptly launch all mirrors.

So, for now, we still need at least:

• IPFS deployment
• eth.limo deployment (via dappling.network)
• Cloudflare IPFS deployment (using the cl-ipfs domain that we also can get through dappling.network)

Concerning the parameter downloading issue:

• For app.zkbob.com, the current setup remains unchanged.
• For other instances, we can either retain the Cloudflare method (as we use it for app.zkbob.com right now) or explore Arweave, contingent on cost-effectiveness and minimal resource investment for enabling parameter downloads through this platform.

cc @maxaleks @r0wdy1 @akolotov