Keith Ingram
Keith Ingram
Happy to go along with whatever is in ink! and it seems more accurate to what is actually being done in each step
Seems like a good way to go for us as well
After research, decided to implement in [AvionDB](https://github.com/dappkit/aviondb) - built on Orbit, familiar Mongo-like API @erler we will need to add a user login somewhere in the design, although not pressing...
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...
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](docs)
Still need to investigate if it is possible to get the return value from a sent tx - when I first implemented the old contracts app it was not.
@erler any specs for this at the moment? I went through the old one and couldn't find any. Would be best to have on the Call page probably