An asset can be usable inside a rollup before a withdrawal makes it available on Ethereum Mainnet. Treasury planning needs the exit process, rather than only the speed of an internal transaction.
The documented exit has a dispute window
Ethereum’s optimistic-rollup documentation explains that withdrawals to Mainnet involve a challenge period and later completion on L1. It also describes liquidity-provider routes that can pay a user earlier for a fee. The applicable steps and timing must be checked for the specific rollup and bridge; the documentation is not a service guarantee for every implementation. Ethereum documentation — Optimistic rollups
Trace where the funds are usable at each stage
Suppose a business holds an invented 100,000 token units on an optimistic rollup and needs to pay a supplier on Mainnet tomorrow. A fast transfer within the rollup would not itself put those units on the supplier’s required network.
The business might start a native withdrawal, but its supplier deadline must be compared with every remaining exit step. A request recorded on L2, a proof submitted on L1 and a completed Mainnet transfer are different operational states. Marking them all “sent” hides the point at which the supplier can actually use the funds.
Alternatively, imagine a liquidity route offering 99,700 units on Mainnet in exchange for the 100,000-unit claim. The nominal difference is 300 units before separate costs. That quote changes both timing and the route’s dependencies. It is not simply the same withdrawal delivered sooner without consequence.
The comparison also needs asset identity. A token carrying the same symbol on two networks may have a different contract or claim structure. A supplier’s ability to accept it must be established before equating the two balances.
This is a cash-availability problem even when the underlying asset price does not change. An accounting total across networks can remain constant while spendable funds on the required network are insufficient. Price exposure, bridge exposure and payment timing deserve separate entries in the review.
Define completion in the destination network
Verify the native withdrawal sequence, current challenge rules, completion transaction and destination asset. For an alternative route, examine the fee, available size, contract permissions and consequences if the provider does not complete its part.
Reconcile the destination balance before recording the payment obligation as funded. The relevant treasury metric is usable liquidity where it is needed, by the required time. An L2 confirmation alone does not establish that outcome.