Hive Multisig is finally live at this address! If you don't know what Hive Multisig is, I encourage you to read this article.
/!\ Do not play with the Update Account section and update your weights and thresholds if you don't know what you are doing ;)
Hive Multisig in action
Using this dApp you can update your account keys, initiate multisig transactions, and receive multisig transactions initiated by another user.
In the video below, I am connecting on two different accounts (@stoodkev and @lecaillon), knowing that @lecaillon account has a threshold of 2 on its active key, and that @stoodkev has authority over it with a weight of 1. This means that @lecaillon needs to sign and also obtain @stoodkev signature to perform an active authority operation (here a transfer)
This is how it goes:
- Both accounts login to the service (you can see two signatures for each because we register both the posting and active key).
- @lecaillon initiates a transfer
- @lecaillon signs the transfer
- @lecaillon encodes the operation for other potential signers
- As a potential signer, @stoodkev immediately receives the signature request
- @stoodkev decodes the signature request
- @stoodkev agrees with the transfer and thus, signs it
- The backend acknowledges that there are enough signatures and notify @stoodkev that he can broadcast the transfer
- The transfer is broadcasted successfully
Repositories
Of course, all this work is opensource and can be found on our Github:
Going further
We now have a workable Beta but there is still much that can be done to make this better. In the coming month we will focus on :
- SDK Documentation: So that dApps can easily use the SDK to perform multisig requests
- Gathering user feedback and making the necessary changes
More long-term goals include :
- Decentralizing the multisig backend
- Providing multisig bots, to give more granularity to Hive keys (more on that later)
- DevOps work to get a more robust architecture
