light-client
light-client copied to clipboard
raiden-network
Deploy dApp on IPFS
Description
Acceptance criteria
Tasks
- [ ]
Story Points
Why do this?
We want to ensure the dApp is always accessible in a decetralized way.
Yesterday I have met @RachBLondon from 3Box. They have been developing a wrapper to easily use IPFS. MetaMask is also using it to enable the user to backup their data. Maybe an option here or for #152
@christianbrb I was thinking for a while if we could possibly leverage IPFS for the backup/restore of the user data.
Thank you for the links, I will have a look.
I think at some point I was looking into deploying to IPFS and it didn't seem like much work to actually integrate the deployment in our CI workflow.
How to automatically deploy it on IPFS: https://medium.com/coinmonks/automated-deploy-to-ipfs-and-ens-12bae2f40302?
I would say that using the ENS part is probably not feasible since automating this requires to pass the private key controlling the domain to the CI server configuration. I don't think we want to do that.
As an alternative, from a quick read, I can see that there is ipns and DNSLink. So we could use something like that for people to always find the latest deployment of the light client dApp
I am not sure if this is possible yet but I am just noting it as a point to research. We should look if it is possible to use ENS through IPNS so that we don't have to update ENS everytime a deployment happens.
Afaik, https://mesa.eth.link/ and http://openswap.eth.link/ do it this way, maybe this could serve as an example. For mesa we can ask gnosis/the dxdao guys how they did it, if more information is needed.
