... #HiveDapps
... #HiveDapps
There is a way.
You create an account with a posting key with a weight of 40, and for each new user you have a private key and a public key created. This account will have a weight of 1. Then, when the user logs in with your API, they will see the public key and the original account name will be hidden. The user then logs in as if using their own public and private keys. For content, you only return the content that was signed with the user's public key. And for publishing, they will end up sending a multisign request with their key, and the main account will arrive at your server. If it's new content, it's accepted; if it's for editing, there will be a check to see if it was signed with their key.
This is interesting.
Thank you for sharing this.
How long has this technology been on Hive?
Which one? MultiSig? Create new public and private keys to add? Always
How many Private/Public Keys can be created per account?
40, I think, and if you want you can remove or swap any of them at any time, https://multisig.hive-keychain.com
Has anyone implemented this yet?
No one.
To complement this, you can also use Hive Keychain (you need to enable multisig in its settings, and use the real username) to make this multisig request, and the requests appear on https://multisig.hive-keychain.com/#/signRequest
Whats the best way to integrate LITE accounts into dBuzz?
And have other frontends done it?
How long have LITE accounts been available?
Thank you.
Whats the best way to integrate LITE accounts into dBuzz?
That will be for your development team to figure out. I cannot offer any guidance on that
And have other frontends done it?
Peakd and Keychain have integrated VSC so far
How long have LITE accounts been available?
About the last 6 months
