Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

retrieve chain's L1 contract addresses onchain #14757

Open
bitwiseguy opened this issue Mar 10, 2025 · 1 comment
Open

retrieve chain's L1 contract addresses onchain #14757

bitwiseguy opened this issue Mar 10, 2025 · 1 comment
Assignees
Labels
A-op-chain-ops Area: op-chain-ops

Comments

@bitwiseguy
Copy link
Contributor

We should be able to retrieve all of a chain's L1 contract addresses as long as we know the following two addresses:

  • L1StandardBridge
  • SystemConfig

We need to write a tool that will retrieve all other contact addresses via onchain queries.

References

@bitwiseguy bitwiseguy added the M-needs-triage Meta: this issue needs to be labelled label Mar 10, 2025
@bitwiseguy bitwiseguy moved this to Todo in OP Chain Ops Mar 10, 2025
@bitwiseguy bitwiseguy self-assigned this Mar 10, 2025
@bitwiseguy bitwiseguy moved this from Todo to In Progress in OP Chain Ops Mar 10, 2025
@bitwiseguy bitwiseguy added A-op-chain-ops Area: op-chain-ops and removed M-needs-triage Meta: this issue needs to be labelled labels Mar 10, 2025
@bentrnr21
Copy link

Hi, I came across this issue and wanted to share some potential solutions that might help.

It seems like the setL1BlockValuesInterop function does not currently include the operator fee parameters. Here are some possible steps to address this issue:

1.	Check the existing function implementation – It would be useful to inspect how setL1BlockValuesInterop is currently handling L1 block values and determine where the operator fee should be added.
2.	Verify recent changes – If this issue appeared recently, it might be worth checking recent commits to see if any modifications accidentally removed or altered the operator fee handling.
3.	Update function parameters – If the function needs to include additional parameters for operator fees, modifying the function signature and updating its logic accordingly could be a solution.
4.	Test the changes – Adding unit tests to ensure that the new operator fee logic is correctly applied would help validate the fix.
5.	Check related functions – If setL1BlockValuesInterop relies on other functions, they might also need adjustments to correctly pass and process the operator fee parameters.

Would be great to hear any insights from the team on whether this approach makes sense. Looking forward to updates!

Best regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-op-chain-ops Area: op-chain-ops
Projects
Status: In Progress
Development

No branches or pull requests

2 participants