I've recently been immersed in 
The DropChain integration will make it possible for people to use standard social logins to hold and use Rstory. The service essentially sets up managed web wallets for every user, abstracting the crypto away for users that aren't into it. DropChain will also make credit card sales of Rstory tokens possible. This is huge, because my next best option for credit card sales was a sketchy exchange that wanted $1250 to enable token sales.
My tentative plan is to mint 1M Rstory tokens on DropChain, under the symbol RSTY. Then I'll integrate RSTY with the website, which should be straightforward. The DropChain API is clear and simple. I doubt I'll have to write more than a dozen lines of code for the integration.
Making RSTY compatible with the total project will be slightly trickier. My first step will probably be to build a bridge between RSTY and RSTORY on EOS. Since DropChain is based on Algorand, its transactions can include a transaction1_note. And EOS transactions can include memos. This makes it possible for a sender on one blockchain to include in a memo or note the address of their wallet on the other blockchain.
Using this feature, I'll make an app that facilitates 1:1 swaps of RSTY and RSTORY. Right now, I'm looking at doing it in Flask, Docker-izing, and hosting it on Google Cloud Run. The user would go to the page, send their transaction to the bridge wallet, the app would capture the memo/note receiving address and token quantity from the blockchain, then it would send the correct number of tokens from the other bridge wallet to the specified receiving address.
This isn't something I've done before, but I've got a good sense about how it could all work. The part I'm getting hung up on is key security. The app will need the private keys of the bridge wallets to sign transactions. I can keep the keys hidden in an environment variable, but Google recommends instead using their secrets tool, which is super complicated. Docker has a secrets feature, but I'm not fully clear on how secure that is. Right now I'm looking at storing encrypted keys in one file and having a standalone decryption script access them. How would you secure your keys in a Docker-ized Flask app?
The path forward for upgrading rstory.io is a little more uncertain. My friend is making a Svelte version of the site, but it's not yet clear that this can run on my pure client side situation. I welcome the opportunity to learn the new tools and can see the potential with Svelte. Yet I'm also determined to make pages and apps that can be replicated by Rstory community members and run entirely on IPFS. Hopefully Svelte can work in this environment.
Once RSTY is integrated with rstory.io and I've got a bridge app working, my next step is to add TUDE on ETH to the bridge. This is slightly trickier than DropChain and EOS because there are nontrivial transaction fees to worry about. I want all fees to be paid by the user, but that sets up a situation where a user would be sending tiny amounts of ETH to the bridge wallet and the cost of that alone in fees might amount to a couple of bucks.
Read Free Mind Gazette on Substack
Read my novels:
See my NFTs:
