Asigna
WebStacksClarity
  • Introduction
    • About Asigna
    • Supported Wallets
    • Supported Networks
    • Verification Tool
    • Source Code
    • Official Links
  • Bitcoin multisig
    • Technical Specifications
    • Quickstart
      • Connecting to Asigna
      • Setting up your Vault
      • Managing your Vault
        • Permissions
        • Sub-Accounts
        • Settings
      • Vault Balance
        • Runes
        • BRC-20s
        • Ordinals
        • Rare Sats
      • Embedded Apps
      • UTXO Management
      • Batch Transactions
    • Recovery
      • Software Wallet Setup in Sparrow
      • Ledger Setup in Sparrow
      • Ledger Setup in Caravan
  • Stacks multisig
    • Native Stacks approach
    • Quickstart
      • Connecting to Asigna
      • Setting up your Vault
      • Managing your Vault
        • Permissions
        • Sub-Accounts
        • Settings
      • Vault Balance
        • SIP-10s
        • NFTs
        • STX20
      • Nonce, queue and conflict transactions
      • Interacting with Apps
  • EVM MULTISIG
    • About
    • Networks and Contracts
    • Quickstart
      • Connect to Asigna
      • Setup Multisig
      • Funding Multisig
      • Batched transactions
      • dApps
  • FRACTAL MULTISIG
    • Technical specifications
  • Developers
    • Integrate Asigna Multisig into your App
      • Stacks
      • Bitcoin
      • EVM
    • Multisig SDK
      • Bitcoin SDK
      • Stacks SDK
      • EVM SDK
  • Appendix
    • Contact us
    • Asigna Audits
    • Privacy Policy
    • Terms of Use
Powered by GitBook
On this page
  1. Introduction

Verification Tool

Asigna Vault Verification

PreviousSupported NetworksNextSource Code

Last updated 2 months ago

The Verification Tool is an open-source utility designed to ensure that a multisig address consists solely of designated owners and remains free from unauthorized internal or external keys that could enable access without owner consent.

This tool was developed based on audit reports to further enhance Asigna’s reliability and facilitate the generation of secure multisig addresses.

Its implementation allows for the secure restoration and usage of your multisig outside of the Asigna app, even in the unlikely event that the Asigna website becomes unavailable. The open-source code for this functionality can be found here.

Address Construction Logic

  • Bitcoin Taproot

Asigna Vault addresses leverage the Taproot Bitcoin Upgrade, enhancing efficiency and privacy. Every Taproot address requires an internal public key to be passed as a single spender, which does not naturally align with a multisig setup.

To overcome this, Asigna employs MuSig public key aggregation, combining all owners' public keys into a single aggregated key. This effectively creates an "everyone agrees" branch, ensuring that multisig owners face no additional risks while benefiting from Taproot Upgrade optimizations.

  • Bitcoin WSH

Asigna Witness Script Hash addresses are designed for maximum compatibility across Bitcoin wallets, including hardware, desktop, and browser extension wallets.

This is achieved through a standard sorted WSH multisig script, ensuring broad usability while maintaining Bitcoin’s native security and flexibility.

  • Stacks

The Stacks blockchain features built-in multisig functionality, allowing for native multisig address creation. Asigna utilizes this native approach, ensuring that its multisig implementation inherits the full security guarantees of the Stacks blockchain without additional dependencies.

How it works?

Each ready-to-use Asigna Vault is automatically labeled with a Verified icon in the Vault preview and sidebar menu, ensuring users can quickly identify authenticated vaults.

To personally verify your Vault address, navigate to the Vault page and click the Verified icon on the sidebar menu of the selected Vault.

You will be redirected to the Verification Tool page, where the tool will automatically populate the confirmation threshold and owners' public keys fields, as you have been forwarded from the Asigna app.

The tool then generates the expected address based on the acquired threshold and public keys and compares it with the actual address of your Vault.

If the addresses match, the verification is considered successful.