Implement IPFS back-end

[kwingram25]

Contracts/code bundles currently stored in browser storage should be stored in a IPFS-based file system or database store - possibly Orbit-DB

• Requires addition of user credentials
• New design spec(s)?

[kwingram25]

After research, decided to implement in AvionDB - built on Orbit, familiar Mongo-like API

@erler we will need to add a user login somewhere in the design, although not pressing at the moment. Or go with some other way to sync across devices - docs include samples for using a QR code, for example

[erler]

Cool. If we can have a web3 login where users can simply login with the Polkadot Extension that'd be ideal. Though we need to think about how different addresses on different networks relate to a single (or several?) user ID(s) then I guess.

[kwingram25]

Anyone can upload or deploy with any of their existing accounts, though, so linking it to one maybe isn't the best choice. Anyway, I don't think there is anything sensitive to hide behind the login, it's just retrieving publicly available things on the chain that you want to see on another device

[kwingram25]

Some issues with AvionDB as well - looking into using Textile which has handy user identity flow and could be integrated into Polkadot extensions: https://docs.textile.io/#threaddb

[Textras]

@kwingram25 what issues/roadblocks did you experience with AvionDB? How has Textile been in comparison? Thanks!