Sergey

@ljoss17 here you go, let me know if you need more. ``` 2024-07-01T11:54:03.805896Z INFO ThreadId(01) using default configuration from '/home/monitoring/.hermes/config.toml' 2024-07-01T11:54:03.806405Z INFO ThreadId(01) running Hermes v1.10.0+fc998de4 2024-07-01T11:54:03.807674Z INFO ThreadId(01) rest:...

@ljoss17 can packets clearing interfere with Hermes functioning properly? (my thought was they might submit transaction and mess with account sequence, but not sure if if it's the case or...

@ljoss17 one more thing I just discovered: so I used the same config as above, with trace logging, but without clear_on_start (but with clear_interval), and it seems to also not...

@ljoss17 just to clarify: my biggest concern here is not the packets being not relayed correctly (this is likely either the node being misconfigured, or blocks being pruned), but rather...

@ljoss17 okay so, the `excluded_sequences` config part did the trick apparently, therefore I confirm it's working with it.

@romac I'm all in for making a PR on that, but I am not sure about how to implement it in the best way. Are there any similar places which...

@romac any idea on what I can take as a reference to do this (this as in properly refactoring it, as otherwise it won't compile) properly? My Rust knowledge is...

I love how Nomic did it: when there's a new upgrade coming, validators are preparing a new binary, which signals its readiness for a new upgrade, and once +2/3 of...