Verification tool
The Verification Tool is an open-source utility designed to ensure that a multisig address is solely composed of designated owners and is free from any unauthorized internal or external keys that might permit access without the consent of the owners.
This verification tool was specifically tailored in accordance with audit reports to enhance Asigna reliability and allow the generation of secure multisig addresses.
What is more, the implementation of this verification tool creates the possibility to securely restore and use your multisig outside of the Asigna app (in case of the unlikely scenario, when Asigna website goes down). The open-source code for this case can be found here.
Address construction logic:
Bitcoin Taproot Asigna Safe addresses utilize the Taproot Bitcoin Upgrade. Every Taproot address necessitates an internal public key to be passed as a single spender, which doesn't align well with a multisig solution. To circumvent this, we employ MuSafe public key generation derived from all owners' public keys. This effectively creates an 'everyone agrees' branch, introducing no additional risks for multisig owners.
Bitcoin WSH Asigna WSH scripts are created for a more general use case which can be used with almost any bitcoin wallet, including hardware, desktop, and extensions. It is done through a standard sorted wsh multisig script.
Stacks Stacks blockchain has a built-in multisig feature, allowing to create a different address type for the multisig use case. Asigna uses native approach, ensuring the security is as good as the Stacks blockchain itself.
How it works?
Each ready-to-use Asigna Safe is automatically marked with "Verified" icon on the Safe preview and dashboard.
To personally verify your Safe address, go to the Safe page and click on "Verified" icon on the dashboard of the selected Safe.
You will be forwarded on the Verification tool page. The tool will automatically fill the confirmation threshold and owners' public keys fields, as you've been redirected from the Asigna app. Then the tool generates the expected address according to the acquired threshold and public keys. Finally, the tool matches the expected address with the actual address of your Safe.
In case of a match, the verification is considered successful.
Last updated