Skip to content

Conversation

@xenoliss
Copy link
Contributor

Update the script written in #306 to work with our recent tooling.

@linear
Copy link

linear bot commented Nov 21, 2025

CHAIN-548 Update SmartEscrow contract to use aliased L1 addresses

@cb-heimdall
Copy link
Collaborator

cb-heimdall commented Nov 21, 2025

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/2
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 2
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 2
2
1 if commit is unverified 0
Sum 2

@@ -0,0 +1,11 @@
OP_COMMIT=d09c836f818c73ae139f60b717654c4e53712743
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there any reason that this OP commit is different from the 594bc933a38425f745b46399a3619bcdeb74965d that we've been using?

Copy link
Contributor Author

@xenoliss xenoliss Nov 24, 2025

Choose a reason for hiding this comment

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

I used the commit associated with u17 (op-contracts/v5.0.0-rc.2 if I'm not mistaken)

Choose a reason for hiding this comment

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

Nice

Copy link
Contributor

@jackchuma jackchuma left a comment

Choose a reason for hiding this comment

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

This looks good to me - I think we just need to confirm if the l1 safe address is what we want to own it now that we have the security council involved

bun run scripts/genValidationFile.ts --rpc-url $(RPC_URL) \
--ledger-id $(LEDGER_ACCOUNT) \
--workdir .. --forge-cmd 'forge script --rpc-url $(RPC_URL) \
$(SCRIPT_NAME) --sig "sign(address[])" "[$(CB_SIGNER_SAFE_ADDR)]" --sender 0x6CD3850756b7894774Ab715D136F9dD02837De50' --out ../validations/cb-signer.json;
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we name the output file coinbase-signer.json ? It'll help with readability in the signer tool

bun run scripts/genValidationFile.ts --rpc-url $(RPC_URL) \
--ledger-id $(LEDGER_ACCOUNT) \
--workdir .. --forge-cmd 'forge script --rpc-url $(RPC_URL) \
$(SCRIPT_NAME) --sig "sign(address[])" "[$(OP_SIGNER_SAFE_ADDR)]" --sender 0x4d494C5F61b60752D3A10062276a0eFC22596151' --out ../validations/op-signer.json;
Copy link
Contributor

Choose a reason for hiding this comment

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

and can the op file name be optimism-signer.json ?

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.

6 participants