HyperCore and HyperEVM Transfer and Action Ordering
Summary
This technical note explains when assets and actions move between HyperCore and HyperEVM. Transfers from HyperCore to HyperEVM wait in the Layer 1 queue until the next HyperEVM block. Transfers in the reverse direction are processed in the same Layer 1 block as the HyperEVM block, after that block has been built.
It also sets out the order of operations within a block: the Layer 1 block is built first, then the EVM block, followed by EVM-to-Core transfers and CoreWriter actions. A key operational constraint is that the account submitting a CoreWriter action must already exist on HyperCore before EVM block construction. A transfer intended to initialize that account in the same block will not satisfy the requirement, and the action will be rejected. The note offers timing and sequencing details rather than trading performance evidence; it is relevant to implementing transactions and execution logic on the platform.
Key ideas
- HyperCore-to-HyperEVM transfers wait until the next HyperEVM block.
- HyperEVM-to-HyperCore transfers occur in the same Layer 1 block, after the EVM block is built.
- CoreWriter actions are processed after EVM-to-Core transfers.
- An account must already exist on HyperCore before the EVM block is built for its CoreWriter action to be accepted.
- A same-block transfer cannot initialize an account in time for a CoreWriter action.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.