telosnetwork / telos-consensus-client

Consensus client for TelosEVM
Apache License 2.0
2 stars 0 forks source link

Once caught up and not syncing, use batch size of 1 #33

Closed poplexity closed 4 weeks ago

poplexity commented 2 months ago

If batch size is a large number (i.e. 500) then when we are done syncing and caught up to head, we wait to send batches of 500 blocks to reth. This gives a poor user experience when users need to wait longer than necessary for their receipt to be available from RPC.

We should track when we are caught up and just send every block once we are, either batch size of 1 or just don't use batches at all. (maybe send_batch function can check if it's size of 1 and not send batch if so)