-
Notifications
You must be signed in to change notification settings - Fork 292
bug: read only finalised LogMessageToL2
events
#1521
Comments
@apoorvsadana Picking this up |
Sure, assgined |
Yes, right now Madara starts processing immediately as it receives events. Confirmed by checking code and logging L1 current block number and block number at which event was dispatched, both are same - meaning waiting for block confirmations are not in place. Approach we could take is - instead of streaming events, we can watch for new blocks. On every new block production we can iterate through events of @apoorvsadana what do you think? |
Similar to |
As discussed with @apoorvsadana , its better to rely on rpc to tell us finalized blocks to be 100% deterministic and efficient. Will come back to this once we migrate to alloy |
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
still blocked |
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
repository archived in favor of https://github.com/madara-alliance/madara |
Currently, if I understand it correctly, Madara reads events instantly from the L1 even if they arne't finalised. First, we need to confirm this is the case. If it yes, we need to change this so that only finalised events are read.
The text was updated successfully, but these errors were encountered: