You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
We should be able to retrieve all of a chain's L1 contract addresses as long as we know the following two addresses:
We need to write a tool that will retrieve all other contact addresses via onchain queries.
References
The text was updated successfully, but these errors were encountered: