finalize and broadcast

Finalization and broadcast are two different steps.

Finalization creates the signed transaction bytes after enough signatures are collected. Broadcast sends the finalized transaction to the Cosmos network.

When a transaction can be finalized

A transaction can be finalized when the signature threshold is reached.

For example:

  • in a 2-of-3 multisig, any two valid signatures are enough;
  • in a 3-of-5 multisig, any three valid signatures are enough.
  • Snow-Fall shows the signature progress and status.

    Finalization checklist

    Before finalizing, verify:

  • the transaction status is ready to finalize;
  • the expected signers have signed;
  • the payload hash is still the expected one;
  • the transaction details are still correct.
  • Finalization does not require a seed phrase or private key.

    Broadcast checklist

    Before broadcasting, verify:

  • the chain is correct;
  • the RPC endpoint is available;
  • the signed transaction was finalized successfully;
  • the account sequence has not become stale;
  • the team is ready to send the transaction on-chain.
  • Snow-Fall requires explicit confirmation before broadcast.

    After broadcast

    If the broadcast succeeds, Snow-Fall records the transaction hash.

    Use the dashboard history or a block explorer to verify the result.

    If broadcast fails

    Broadcast can fail for several reasons:

  • RPC endpoint unavailable;
  • account sequence changed;
  • insufficient fees;
  • chain rejected the transaction;
  • transaction expired or became stale;
  • wrong chain configuration.
  • If the account sequence changed, create a new transaction draft and collect signatures again. Existing signatures usually cannot be reused for a changed sequence.

    Safety note

    Do not repeatedly broadcast without understanding the error. Review the failure message, chain configuration, and RPC status first.