As you may know, thanks to the support of the DHF, I've hired a team to work on making multisig actually usable on Hive. Here's the original proposal.
Our dApp is almost ready and includes everything you'll need to initiate a multisig transaction.
Here you can check which keys can be used for signing on a particular account. Obviously, this displays the public keys ;p
After logging in, you can add/remove/update keys, and set up their weight and threshold to get ready for using multisig. The account update is signed using Keychain, unless you need to update the owner authority, in which case you will need to use the key directly (since we don't keep the owner key on Keychain).
This is the page on which you can create a multisig transaction and sign it, before passing it along to the other signers.
This part still needs a few fixes but it will be ready soon. It already handles creating the transaction and signing it, and soon, we will add the automatic detection of other signers, and the transmission through our backend.
We are also making good progress on the backend side. Messages are passed between users using socket.io, and necessary data is stored in MariaDB. Note that the content of the transactions is entirely encrypted.
Ultimately, if identified as online by the backend, each potential signer will receive a request to sign the transaction. When the necessary threshold is attained, the last one to sign will be requested to broadcast the operation, and others will be notified.
We still have work to do on this side but we believe we're going in the right direction.
Once the front end is ready, we will work on building an SDK and corresponding documentation, in order for other developers to be able to implement multisig easily.
Happy to get any feedback from you guys!
Support Hive Multisig Development by voting for this proposal on Hive Keychain, PeakD, on HiveSigner, or from Hive Keychain's governance page.
