Hello XLayer team,
As the project has officially announced the migration from zkEVM to the OP Stack, I would like to request clarification on how existing on-chain data will be handled. Since the two architectures differ significantly in terms of state commitment, node implementation, and state tree structure (and are therefore not directly compatible), we would like to understand the migration mechanism in advance to prepare our applications accordingly.
How will user assets (ETH / ERC-20 / NFT) be preserved on the new OP-based chain?
Will you perform a full state snapshot of the zkEVM chain and load it into the OP chain genesis?
Or will migration rely on a bridge-based mechanism, requiring users to initiate asset transfers manually?
How will existing smart contracts and their storage be migrated?
Will contract bytecode and storage be automatically imported into the OP chain?
Or will ecosystem projects need to redeploy contracts and manually re-initialize state?
Clarifying the migration approach will help ecosystem developers prepare for compatibility and ensure a smooth transition when the upgrade happens.
Thank you.
Hello XLayer team,
As the project has officially announced the migration from zkEVM to the OP Stack, I would like to request clarification on how existing on-chain data will be handled. Since the two architectures differ significantly in terms of state commitment, node implementation, and state tree structure (and are therefore not directly compatible), we would like to understand the migration mechanism in advance to prepare our applications accordingly.
How will user assets (ETH / ERC-20 / NFT) be preserved on the new OP-based chain?
Will you perform a full state snapshot of the zkEVM chain and load it into the OP chain genesis?
Or will migration rely on a bridge-based mechanism, requiring users to initiate asset transfers manually?
How will existing smart contracts and their storage be migrated?
Will contract bytecode and storage be automatically imported into the OP chain?
Or will ecosystem projects need to redeploy contracts and manually re-initialize state?
Clarifying the migration approach will help ecosystem developers prepare for compatibility and ensure a smooth transition when the upgrade happens.
Thank you.