fix(reku): autocc fromBlock starts from latest+1 rather than latest in realtime mode

Author: nom4dv3

packages/reku/README.md

@@ -18,7 +18,7 @@
 
 ### AutoCrossCheck
 Conceptually it supports 'catchup', 'realtime', 'mix' modes, controled by `fromBlock` and `toBlock`;
-- realtime mode: run over the latest block data; enter when `fromBlock` and `toBlock` are NOT present; starts from `latestblocknum` and never ends, always waits until `latestblocknum >= lastcheckpoint + batchBlocksCount`;
+- realtime mode: run over the latest block data; enter when `fromBlock` and `toBlock` are NOT present; starts from `latestblocknum+1` and never ends, always waits until `latestblocknum >= lastcheckpoint + batchBlocksCount`;
 - catchup mode: run over historical block data; enter when `fromBlock` and `toBlock` is present; starts from `fromBlock` and ends at `toBlock`;
 - mix mode: start in catchup mode and transit to realtime mode; enter when `fromBlock` is present and `toBlock` is NOT; auto-transit when `lastcheckpoint > latestblocknum - batchBlocksCount`;
 

packages/reku/event/crosschecker/autochecker.ts

@@ -54,7 +54,7 @@ export class AutoCrossChecker extends BaseCrossChecker {
     // TODO: use blockNumber for performance
     const latestblocknum = await retryOnNull(async () => await this.provider.provider?.getBlockNumber())
     const {
-      fromBlock = latestblocknum,
+      fromBlock = latestblocknum + 1,
       batchBlocksCount = 10,
       pollingInterval = 1000,
       blockInterval = ETH_BLOCK_INTERVAL,