Ömer Faruk Irmak 6cdcff6275 fix: reuse timestamp for blocks failing CCC (#1031) ... we assume that same height wont trigger multiple reorgs to be able to put an upper bound on the reorg depth. We rely on the fact that AsyncChecker executes transactions one-by-one and tells worker the safe set of transactions to include in the replacement block that wont trigger another error on the same block. If worker changes the timestamp and that causes significant changes to the execution flow of included transactions; we might have a height where multiple reorgs happen.		2024-09-10 14:59:42 +03:00
..
stress	feat: Sync and relay L1 messages (#350)	2023-06-07 07:24:19 -07:00
miner.go	feat: implement and integrate counter-based CCC (#982)	2024-09-04 13:33:51 +03:00
miner_test.go	feat: implement and integrate counter-based CCC (#982)	2024-09-04 13:33:51 +03:00
scroll_worker.go	fix: reuse timestamp for blocks failing CCC (#1031)	2024-09-10 14:59:42 +03:00
scroll_worker_test.go	feat: implement and integrate counter-based CCC (#982)	2024-09-04 13:33:51 +03:00