Escrow Channel Withdrawal Flow
Escrow withdrawals are the protocol path for moving value from a user's home-channel balance to a non-home chain. The mechanism can be supported by Nitrolite, but docs.yellow.org does not yet document escrow withdrawals as a builder-facing workflow.
:::caution Not documented as an app workflow yet Escrow operation mechanics are intentionally deferred until the Nitronode automation and product surface are ready for public builder docs. Use the home-channel withdrawal and app-session lifecycle docs for the current v1 builder path. :::
What is stable
The conceptual model is still useful when reading protocol material:
- A user's home ledger remains the canonical balance for an asset.
- A withdrawal to a non-home chain needs an escrow path because the target chain cannot directly verify the home chain's latest channel state.
- Nitronode coordinates signed off-chain state updates and on-chain settlement paths.
- Applications should not ask users to run escrow withdrawal state construction manually.
Protocol reference
Protocol-level operation names and invariants live in Cross-chain and Assets. This Learn page intentionally avoids escrow state construction steps until the public Nitronode workflow is documented.
Current builder guidance
For applications today:
- Use home-channel withdrawal for same-chain exits.
- Use app-session withdrawal to return app-session funds to the user's home channel.
- Treat escrow withdrawal automation as a future product path until the public Nitronode workflow is documented.