getting started

This guide explains the basic Snow-Fall workflow for Cosmos multisigs.

Before you begin

Make sure you have:

  • a supported Cosmos wallet installed, such as Keplr;
  • access to the Cosmos account that will act as one of the multisig signers;
  • the correct chain selected;
  • the signer addresses and public keys of all multisig members;
  • a clear agreement with the team on the multisig threshold, such as 2-of-3 or 3-of-5.
  • Snow-Fall is non-custodial. Your wallet keeps your keys. The dashboard coordinates the operation.

    Step 1: Sign in with your wallet

    Open the dashboard and connect your Cosmos wallet from the Cosmos workspace.

    Your wallet will ask you to sign a login message. This proves that you control the wallet address. It does not move funds and does not give Snow-Fall access to your private keys.

    Step 2: Create or import a multisig

    Create a new multisig when you are starting from scratch.

    Import an existing multisig when the address already exists and you want to manage it from Snow-Fall.

    For both flows, review the chain, threshold, signers, signer public keys, and final multisig address before using it.

    Step 3: Create a transaction

    Choose the multisig, select the action, and fill in the required fields.

    Common Cosmos actions include:

  • send funds;
  • delegate stake;
  • undelegate stake;
  • redelegate stake;
  • withdraw rewards;
  • governance vote.
  • A transaction starts as a draft. Once it is ready, Snow-Fall shows a human-readable review screen.

    Step 4: Review before signing

    Every signer should review:

  • chain name and chain ID;
  • multisig address;
  • signer address;
  • recipient or validator address;
  • amount and denom;
  • fee and gas;
  • memo;
  • payload hash.
  • The payload hash is a fingerprint of the transaction that helps detect changes. After the first signature, the payload is locked.

    Step 5: Collect signatures

    Each signer opens the transaction and signs with their wallet.

    The signature progress card shows who signed, who is still pending, and whether the threshold has been reached.

    Step 6: Finalize

    When enough valid signatures are collected, the transaction can be finalized.

    Finalization creates the signed transaction bytes. It does not necessarily mean the transaction has been sent to the network yet.

    Step 7: Broadcast

    Broadcasting submits the finalized transaction to the selected Cosmos chain.

    Snow-Fall requires a final confirmation before broadcast. After success, the dashboard stores the transaction hash.

    Step 8: Verify the result

    Check the transaction status in Snow-Fall. When available, also verify the transaction in a block explorer.

    First operation recommendation

    For a new multisig, start with a small test transaction before using larger amounts or validator operations.