There are three properties an implementation might attempt to hold, detailed below. With Opaque Handoffs, they form a trilema (pick two of three) and trivially allow for E-Order. With Transparent Handoffs, you can get all three, but lose E-order. E-order can be re-established with the WormholeOp.
Handoffs have a register side (OCapN: bootstrap method "deposit-gift") and a two-message redeem side (OCapN: record "desc:handoff-give" and bootstrap method "withdraw-gift").
For Opaque Handoffs, the Receiver and the Exporter cannot see what Reference is being handed off from the redeem side alone. Therefore, Handoff cannot resolve until after the register and redeem messages have been seen by the exporter.