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. If you don't know what multisig is or why making it easy to use is valuable to our ecosystem, please read the proposal.
Backend
Last month, we forecasted that we'll finish the first version of our multisig backend within one month, and I'm happy to announce that I synced with our team yesterday and they delivered in time.
Our backend is now available to authenticate users based on a signed message, pass along transactions to be signed to the corresponding users, determine who should broadcast the operation, and notify users of the success or failure of the operation.
SDK (Software Development Kit)
For Hive Multisig to be useful, we need dApps and wallets to be able to implement it easily. For this, our next step is to develop an SDK that will handle interactions between the dApps and our backend, and add an extra layer of security by verifying the identity of the transaction initiator.
Once the SDK is ready, we'll integrate it into our own multisig front-end to be able to perform more real-situation tests and also work on providing documentation for other dApps to integrate it seamlessly.
I'm really excited to see this work coming alive, and will post again as soon as we have new updates!