troubleshooting

This guide helps users understand common issues and what to do next.

Wallet not detected

Check that:

  • your wallet extension is installed;
  • the browser profile is correct;
  • the wallet is unlocked;
  • the page has been refreshed after installing the wallet;
  • the wallet supports the selected chain.
  • Wrong chain selected

    Make sure the transaction chain matches the multisig chain.

    If the chain is wrong, do not sign. Create a new transaction on the correct chain.

    Missing public key

    Some multisig flows need signer public keys to derive or finalize the multisig transaction.

    Ask the signer to connect their wallet and provide the expected public key through the supported flow.

    Signer is not a multisig member

    This means the connected signer does not match the multisig member list.

    Check:

  • signer address;
  • public key;
  • chain prefix;
  • imported multisig member data.
  • Payload hash mismatch

    Snow-Fall rejects signatures when the submitted payload hash does not match the stored transaction payload.

    This protects against transaction changes. Refresh the page and verify the transaction. If the issue continues, recreate the transaction.

    Duplicate signature rejected

    A signer can only sign the same payload once.

    If the signer already signed, wait for the remaining members.

    Threshold not reached

    The transaction needs more signer weight before it can be finalized.

    Check the signature progress card to see who is still pending.

    Cannot finalize

    Common causes:

  • not enough signatures;
  • transaction is in the wrong status;
  • member public keys are missing;
  • multisig keyset does not match the multisig address.
  • Review the error message and signer list.

    No RPC configured

    Broadcast and account data lookup require a working RPC endpoint for the selected chain.

    Go to chain settings and review RPC configuration.

    Account number or sequence could not be resolved

    Cosmos account number and sequence are part of the signed payload.

    Snow-Fall blocks transaction creation when this data cannot be resolved, unless a development-only fallback is enabled. Configure a working RPC endpoint or try again later.

    Stale sequence

    A sequence can become stale when another transaction from the same multisig is broadcast before the current one.

    Create a new transaction draft and collect signatures again.

    Broadcast failed

    Check:

  • RPC endpoint status;
  • fees;
  • account sequence;
  • chain ID;
  • transaction status;
  • raw error details in the advanced section.
  • Do not keep retrying without understanding the error.

    Active transaction already exists

    Snow-Fall may block new drafts when another active transaction exists for the same multisig.

    Finalize, broadcast, cancel, or resolve the active transaction first.