Vultisig
Website
  • Overview
  • Vultisig Vault User Actions
    • Creating a Vault
    • Managing your Vault
      • Vault Details
      • Vault Backups
      • Vault Rename
      • Vault Reshare
      • Vault QR
      • Vault Upgrade
    • Keysign
      • How Keysigning works
      • Signing a Transaction
  • Vultisig Infrastructure
    • Overview
    • Vultiserver
      • How does a Fast Vault work?
      • Transaction Policies
      • Why is it safe?
  • Relay Server
  • Vultisig Ecosystem
    • Vultisig Extension
      • How to use Vultisig Extension
    • Web App
  • Marketplace
  • Vultisig SDK
  • Threshold Signature Scheme
    • Threshold Signature Schemes used by Vultisig
      • How GG20 works
      • How DKLS23 works
    • TSS Actions
    • Difference to Multi-Signatures
    • Difference to Passkeys
    • Emergency Recovery
  • VULTISIG Token
    • The $VULT token
    • Launch of $VULT
    • $VULT Staking
    • Airdrop
      • Airdrop V2
  • Other
    • Vultisig Bot
    • Security
    • Frequently Asked Questions
    • Privacy
    • License
    • Terms
  • Developer Docs
    • Infrastructure Overview
    • Vultisig SDK
      • How to use it
  • Marketplace
    • Plugins
    • Ai Agents
Powered by GitBook
On this page
  • Set Up
  • 2-of-2 Fast Vault
  • Vault Share storage
  • Transaction Signing

Was this helpful?

Edit on GitHub
  1. Vultisig Infrastructure
  2. Vultiserver

How does a Fast Vault work?

PreviousVultiserverNextTransaction Policies

Last updated 3 months ago

Was this helpful?

Set Up

2-of-2 Fast Vault

In this setup, the Vault is created together with a user's device and the Vultisigner server. The user registers a keygen request with the Vultisigner server, which creates a new Vault that records the connection to the user's device. A keygen ceremony is then executed, which creates the Vault shares on the user's device and on the Vultisigner server. \

Vault Share storage

The Vultisigner's Vault Shares are stored on a dedicated Vultisigner server, which contains the Vault Shares along with configured instructions for signing transactions.\

For security reasons, the Vultisigner's Vault share is password encrypted and the user must provide an email address to which the Vault share will be sent during setup, for backup and independent access.

Transaction Signing

When a user wishes to sign a transaction, the request is sent to the Vultisigner server. The appropriate Vultisigner Vault will verify that the configured transaction policies are met before participating in the Keysign process. If they are met, the Vultisigner joins the Keysign ceremony and the transaction is broadcasted to the blockchain.

In case the Vultisigner server is offline and unable to sign, the user needs to import the Vultisigner share received via email into another device and sign like a normal Keysign.

Vultisigner Flowchart