c801a11190
* Fix name after API change
why:
Slipped through (debugging mode)
* Fine tuning error counters
why:
Previous operating mode was quite blunt and considered some unnecessary
condition. Error handling was invoked and the peer zombified where one
could have continued working with that peer.
* Provide `kvt` table API bypassing `FC`
details:
Not a full bypass yet
why:
As discussed on Discord:
Ideally, those would pass through fc as well, as thin wrappers around
the db calls, for now - later, we probably see some policy involved
here and at that point, fc will be responsible for arbitrage between
sources (ie if a rpc source sends the block the syncer is syncing
while the syncer is working, fc is there to referee

* Apply `kvt` API from `FC` to beacon sync
* No need to use extra table for persistent header cache state record
why:
Slot zero can do. This allows deleting that table wholesale when needed
once thatfeature is available.
* Logger updates
details:
+ Lifting main header/block op logs from `trace` to `debug`
+ Set metrics update before nano-sleep (for task switch)
|
||
|---|---|---|
| .. | ||
| chain | ||
| executor | ||
| pow | ||
| tx_pool | ||
| block_import.nim | ||
| casper.nim | ||
| chain.nim | ||
| dao.nim | ||
| eip4844.nim | ||
| eip6110.nim | ||
| eip7702.nim | ||
| executor.nim | ||
| gaslimit.nim | ||
| tx_pool.nim | ||
| validate.nim | ||
| withdrawals.nim | ||