Skip to content

Porting splitting GW CTM deployer into the zksync-os compatible branch#1974

Merged
StanislavBreadless merged 58 commits intodraft-v31-with-zksync-osfrom
sb/split-gw-ctm-deployer-with-zksync-os
Jan 26, 2026
Merged

Porting splitting GW CTM deployer into the zksync-os compatible branch#1974
StanislavBreadless merged 58 commits intodraft-v31-with-zksync-osfrom
sb/split-gw-ctm-deployer-with-zksync-os

Conversation

@StanislavBreadless
Copy link
Collaborator

What ❔

ports draft-v31 changes + the ones inside #1964

Why ❔

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.

@StanislavBreadless StanislavBreadless marked this pull request as ready for review January 19, 2026 15:34
@StanislavBreadless StanislavBreadless changed the title Sb/split gw ctm deployer with zksync os Porting splitting GW CTM deployer into the zksync-os compatible branch Jan 19, 2026
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e39b707942

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +94 to +97
try zkChain.getChainTypeManager() returns (address result) {
chainCTM = result;
} catch {
continue;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Remove try-catch around getChainTypeManager

l1-contracts/AGENTS.md explicitly forbids try-catch, and this new try zkChain.getChainTypeManager() path swallows reverts and silently skips a chain when the call fails (e.g., misconfigured or uninitialized chain), returning address(0) later. That hides real errors in deploy/introspection workflows that are supposed to fail fast and makes it easy to ship with incorrect address resolution.

Useful? React with 👍 / 👎.

Comment on lines +135 to +136
// Call getName() on the facet
(bool success, bytes memory data) = facetAddr.staticcall(abi.encodeWithSignature("getName()"));

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid staticcall for facet name discovery

l1-contracts/AGENTS.md also forbids staticcall; the new facet-name probe uses staticcall and masks failures by just skipping facets when the call fails, which can leave adminFacet/mailboxFacet/etc. unset without surfacing an error. This violates the repo’s fail-fast rule and can mislead scripts that rely on complete facet discovery.

Useful? React with 👍 / 👎.

@StanislavBreadless
Copy link
Collaborator Author

lints dont pass because of zksync os related changes.

I will merge the PR to only include the correct hashes

@StanislavBreadless StanislavBreadless merged commit 138d2a0 into draft-v31-with-zksync-os Jan 26, 2026
16 of 22 checks passed
@StanislavBreadless StanislavBreadless deleted the sb/split-gw-ctm-deployer-with-zksync-os branch January 26, 2026 10:26
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