You are viewing a single comment's thread from:
RE: Call for more tools on the testnet!
I'm not really familiar with what all of that stuff is. Can you please provide some more context?
I'm not really familiar with what all of that stuff is. Can you please provide some more context?
Sure. Using a QR code you can attach a steem post to anything in reality. https://twitter.com/dluxxr/status/1050905950373072896
Here is a video on a business card, but could just as easily be on a paper menu or a information label in an art gallery. QR code to voting or steem/sbd transfer in a matter of seconds.
The VR portion at cheerful suggestion allows you to build VR experiences. Say like a classroom or an art gallery... all monetized and secured by steem data... stored on IPFS
video walkthrough VR platform and VR creation
How are the keys for the transaction signing handled?
Also, do you actually have an instance that is connected to the testnet version of the blockchain?
We rely on steemconnect.
The VR and AR dApps loading in to the browser this way are sandboxed in an iFrame with window messaging to their container... which has the steem connect token in a cookie. We can also store a users memo key. In short these dApps only know a users steem name... and if they want to make any changes other than vote they should be prompted for permission... users can also be asked if the XR app should have access to encrypt or decrypt using your memo key.
In short, these are steem aware applications that don't actually have any access to user keys. The test environments have some console feedback to show proper window messaging happened.
I've built in a lot of functionality that hasn't been used yet. As such things like commenting and custom_json would require a test net... I'm short on funding and necessity right now. Maybe even a lack of need?
Well, if you are using SteemConnect, then afaik your "test" environments would all still be pointing to the mainnet. Additional changes are needed in SC for it to support testnet connectivity. Once those are done, you would need to make changes to your app to use that testnet version as well.
While it would undoubtedly be preferable to have the environments totally separate, SC doesn't really need to be tested by every app as long as the HF doesn't make changes to the SC api itself necessary. It helps in testing SC, but if one or two big apps which use all the api calls work with it the rest also will.
Well part of it is just to get more users to actually use the testnet. It would be nice if whatever apps they are used to using could be used there.