Hive Multisig is live!

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