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
For someone lacking full context and understanding of the ZK stack, what was the rationale for #398 and why is it no longer needed to listen for L2->L1 events? I suspect this has to do with EIP-4844 but I cannot deduce anything with confidence after looking at the source code around the watcher and finalizer module, and how it affects the condition(s) in which the service triggers the onchain tx.
Any response or pointers would be much appreciated, thanks in advance 🙏
(edit: did not intend to add the bug label and I cannot remove it.)
The text was updated successfully, but these errors were encountered:
Hello,
For someone lacking full context and understanding of the ZK stack, what was the rationale for #398 and why is it no longer needed to listen for L2->L1 events? I suspect this has to do with EIP-4844 but I cannot deduce anything with confidence after looking at the source code around the
watcher
andfinalizer
module, and how it affects the condition(s) in which the service triggers the onchain tx.Any response or pointers would be much appreciated, thanks in advance 🙏
(edit: did not intend to add the bug label and I cannot remove it.)
The text was updated successfully, but these errors were encountered: