When Is a Treasury Transfer Final?

A treasury transfer is final only when it has the required approvals and the receiving chain shows the agreed settlement status. A written rule should say who can approve a payment, what counts as settled, and who checks the result. This keeps a signed transaction from being mistaken for a completed transfer.

Start by separating approval from settlement. A multisignature wallet, which needs several people to approve a transaction, controls whether it can be sent. The blockchain controls when it is settled. For transfers between chains, those are separate steps too: a relay bridge passes information or assets between chains, and its process may add its own waiting period. For that specific process, see how a relay bridge handles cross-chain swaps.

What should a treasury finality rule include?

A useful rule names the transfer type, the evidence required, and the person responsible for checking it. Set rules for ordinary payments, large payments, and cross-chain transfers separately if their risks or timelines differ.

Write down these points for each type:

• Approval: who must sign, and whether a second person must check the recipient and amount.
• Settlement evidence: what chain status or transaction record counts as complete.
• Waiting period: whether the team waits for a defined status, a set number of confirmations, or both.
• Exception handling: who can pause or review a transfer if the chain or bridge is delayed.

Keep the rule specific enough that a different team member can follow it. For example, “wait until the transaction is finalized on the destination chain, then record the transaction ID” is clearer than “wait until it looks safe.”

Should a treasury wait for confirmations or finality?

Use the receiving chain’s own settlement signal where one exists, and define a confirmation rule where it does not. A confirmation means another block has been added after the transaction; it can increase confidence, but the meaning varies by chain.

Ethereum.org’s proof-of-stake documentation describes finality as a checkpoint process: validators representing at least two-thirds of staked ETH agree on checkpoint pairs. That is different from simply seeing a transaction in a recent block. A treasury policy can require both an on-chain status and a human check of the recipient, amount, and network before funds are treated as available.

How should cross-chain transfers be treated?

Count a cross-chain transfer as complete only after the destination chain reflects the expected asset or action. A transaction on the source chain shows that one leg began; it does not, by itself, prove the destination leg finished.

Record the source transaction ID, destination transaction ID when available, asset, amount, and the person who confirmed receipt. If the bridge reports a delay or failure, pause any dependent payment until someone checks the destination state. Avoid one universal waiting period: chains and bridge designs differ, so use the settlement evidence that matches the route.

The practical rule is simple: approval authorizes a transfer, but settlement evidence closes it. Define both in advance, and make the evidence easy to find in the treasury record.