amirylm

`go test -benchmem -cpu 1 -benchtime 5s -bench=. ./automation/benchmark/...` ``` pkg: github.com/bloxapp/ssv/automation/benchmark cpu: Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz pubsub_router_signing 106813 57358 ns/op 3840 B/op 46 allocs/op pubsub_router_verification 100000000 65.92...

https://github.com/bloxapp/ssv/pull/644 was merged You can continue once `stage` is aligned with `stage-v1` or `main`

`84faed4aa33046f79449353386c72b9a93ef409bf6cc6773e411f7917f94fb125735f580a1505b83fced30eb5aeb7e3b` was added to stage at 4/10 11:32

Fixed in https://github.com/bloxapp/ssv/commit/f86fc9f11c3c2d0eb2375165742ed2312c5315d8

Let's also add versions for the protocols: - `/sync/highest_decided/0.0.1` - `/sync/decided_by_range/0.0.1` - `/sync/last_change_round/0.0.1`

The idea of additional commit just for the coverage is something we need to change. @lior-blox I think it's time to start using codecov.io or some other service..

On hold, to be continued in future versions

We can expect the CPU to be increased, but it should be in a managed way where we control how much resources are allocated for this process.

@ferglor There are 2 tables that gets queried: 1. evm logs (log poller) where we call `poller.IndexedLogs` of `DedupKeyAdded` event with the given workIDs (should be indexed). called from `scanner.go`...