Skip to content

draft: disable portal canonical-factory check (zone-009 Moderato regenesis)#708

Draft
Zygimantass wants to merge 1 commit into
mainfrom
disable-portal-factory-check
Draft

draft: disable portal canonical-factory check (zone-009 Moderato regenesis)#708
Zygimantass wants to merge 1 commit into
mainfrom
disable-portal-factory-check

Conversation

@Zygimantass

Copy link
Copy Markdown
Member

DO NOT MERGE as-is.

The TIP-1091 protocol-managed ZoneFactory (0x5aF2...0000) does not exist on Moderato (no genesis alloc, no node precompile), so since #625 ZonePortal.initialize reverts NotFactory for any freshly deployed factory — zone creation is currently impossible on Moderato.

This draft comments out the msg.sender check so a fresh ZoneFactory can deploy + initialize portals there. Used only to build a one-off tempo-zone-xtask / tempo-zone image pair for the zone-009 regenesis (its portal predates the processWithdrawal ABI change, wedging withdrawals — see the Withdrawal processing cycle failed loop in the sequencer logs).

Once an L1 exposes the canonical factory (genesis-installed or via hardfork), zone regenesis goes through the normal path and this branch is obsolete.

…esis

The TIP-1091 protocol-managed ZoneFactory (0x5aF2...0000) does not exist on
Moderato (or any live chain) yet, so ZonePortal.initialize can never succeed
there: the factory that deploys the portal is not at the canonical address and
initialize reverts NotFactory.

This draft disables the msg.sender check so a freshly deployed ZoneFactory can
create and initialize portals on Moderato, unblocking the zone-009 regenesis
(withdrawals are stuck on a portal that predates the processWithdrawal ABI
change). Not intended to merge as-is.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant