If you run recurring DAO grants and recipients need funds on different networks, route each payout to the chain and token they can use, then reconcile the received amount against the approved grant. A cross-chain transfer adds a bridge route and a second network’s settlement to an ordinary treasury payment, so plan for both before signing.
Prepare the payout list before moving funds
Start with the approved grant amounts, each recipient’s destination network, and the token they have agreed to receive. Keep this list tied to the governance proposal or payment record; it gives your signers a clear source of truth when several transactions happen in one payout cycle.
For every recipient, confirm the chain and full address through a trusted channel. EVM addresses can look identical across Ethereum and Base, but the same address on the wrong chain may not reach the intended account or may be unusable there. Ask recipients to confirm the exact token too: a bridged version of a stablecoin may have a different contract address from the token your treasury holds.
Choose a source asset that can reach the destinations you need. If the treasury holds a different token, converting it may add another swap and another price movement to account for. Leave enough of the source chain’s native token for gas; the treasury needs it to submit the transaction even when the grant itself is paid in a stablecoin.
Compare the delivered amount, time, and route
A cross-chain route can lock tokens on one chain and release or mint a representation on another, or use liquidity on both chains to pay the recipient directly. A routing service can compare available bridges and decentralized exchanges (DEXs), which swap tokens on-chain, but the cheapest route is not always the one that best fits a grant deadline or risk policy.
Compare the amount the recipient is expected to receive, the source-chain gas, the route’s estimated completion time, and the bridge design involved. A quote can include a token conversion as well as the bridge transfer, so check that the final asset matches the recipient’s agreed token rather than comparing only the amount leaving the treasury. Network congestion and available liquidity can change both cost and timing.
For example, suppose a DAO approves 6,000 USDC: 2,500 for a contributor on Base, 2,000 for a contributor on Ethereum, and 1,500 for another contributor on Base. If the treasury holds the full amount on Ethereum, the first and third payments need cross-chain routes while the second can remain a same-chain transfer. Treat any displayed output as an estimate until settlement; record the actual received amount and account for the difference from the grant allocation.
Execute each grant as a separate, checkable payment
For a recurring payout, handle each recipient as its own line item. That makes it easier to trace a failed or delayed route and prevents a problem with one destination from obscuring the status of the other grants.
- Match the recipient: copy the destination address, network, token, and approved amount into the payout record.
- Set the destination: identify the chain and token the recipient is due to receive, including the correct token representation.
- Compare routes: review estimated net output, gas, timing, and route details against the DAO’s treasury policy.
- Check treasury balances: confirm the grant asset and enough native gas are available on the source chain.
- Have authorized signers review: compare the transaction details with the approved payout before the multisig signs.
- Reconcile settlement: record the source transaction and confirm the recipient received the intended asset on the destination chain.
For the example, send the two Base allocations as separate cross-chain payments and pay the Ethereum recipient from the treasury on Ethereum. If a Base route estimates 2,496 USDC for a 2,500 USDC allocation, decide before signing whether the DAO covers that shortfall or the grant should be adjusted; don’t silently reduce the recipient’s award. The figures are illustrative, and actual output depends on the route and network conditions.
One real edge case is a destination transfer that settles after a governance deadline or recipient’s planned use of funds. A fast route can help, but route timing is an estimate: send deadline-sensitive grants early enough to resolve a delay, and confirm receipt on the destination chain before marking them complete. Keep the source and destination transaction references together so another treasury operator can audit the payout.
Make recurring payouts easier to audit
For frequent grant rounds, reuse a payout sheet with columns for proposal, recipient, chain, token contract, approved amount, expected output, source transaction, and settlement status. This catches a wrong-chain address or an unexplained output difference before it becomes a treasury reconciliation problem.
Bungee is a cross-chain bridge aggregator built by Socket that finds routes across bridges and DEXs for transfers between EVM networks and layer 2 chains. bungeebridge.co is the service for comparing and handling those cross-chain routes.
Use the same review rule each round: compare the recipient’s net amount, route timing, and treasury policy before choosing a route, then verify settlement before closing the grant record. For moving funds to recipients on different chains, Bungee Bridge is a way to handle the routing step; a practical final tip is to save the quoted route details beside the actual transaction records for later reconciliation.