I noticed Dash's announcement from yesterday and then the Inleo AMA which was titled "Dash Launch Party!" and definitely wanted to dedicate some time to it today.
But plans don't always come out the way we want and I had a very busy day outside the online space.
I watched / listened to the AMA in a few breaks and I am still not even half way through.
But I was reminded during the AMA of the new signup / login method to Inleo (and indirectly, Hive) using a Keystore file, which is quite a common wallet used especially by long time users in crypto in various blockchains.
How does this work?
Effectively, Inleo creates a new full Hive account with the master password set to the seed phrase of the Keystore file. This is how the two are linked and how the keystore file and password can be used to log into the account AND sign other transactions without asking for permission at every transaction being broadcast (that's how keystore wallets work). Practically, any private key may be used on accounts logged in with keystore, at least in Inleo, since the seed of Keystore can derive any private key. But that won't work on other Hive apps, which don't have direct integration with Keystore.
That greatly simplifies the interaction with Hive (via Inleo) for someone who is not used to the 4 private keys system, but at a loss of a tiered security system provided by the multiple private keys.
For other apps, you'd need to use a classic method of broadcasting transactions like Hive Keychain, after adding the account with the private keys you want to it.
My Test
I created a new alt account (@gadrian-leo) via Inleo, using my Keystore file to test the new system. The onboarding process worked flawlessly for me, and they have improved it a lot, in a multi-step process where you set up some profile info and pick a few communities you are interested in. I assume a similar process is used if someone joins via a different route than Keystore. I also made my first (and only, for far) thread from the new account:
Note that I hadn't added my corresponding Hive account to Hive Keychain at that time, and the transaction went through based on my login via Keystore. There was no confirmation, I just hit "Thread" and it was sent and soon after received a reply too.
For posting and voting, I believe that's the best way to do it. In fact, we often allow (or not?) Keychain to send transactions requiring the private posting key without asking for permission every time. I still have my concerns about the "no confirmation needed" way of working with Keystore, in case of more sensitive transactions, like on Hive are the ones that require the active key, or even the owner key.
Dash
I don't have a Dash account, but I'm thinking to create one and maybe link it to the same keystore file. Basically, I want to see the Inleo skin for Dash. It shouldn't be too difficult, but everything takes time...
Last words
Seems like all parties involved, Inleo, Hive, and Dash, are doing well lately, price-wise. Looks like the markets agree...
Posted Using InLeo Alpha
