Péter Szilágyi
Péter Szilágyi
@holiman OP is talking about the snapshot flush threshold, not the trie of. I'm a bit reluctant to touch that part since we want to merge snapshots and pathdb, so...
This PR seems simple and good, just maybe not needed (making the surrounding code harder to understand). My 2c, lets leave it open until the root cause for the sync...
The reason we haven't added a reputation system or an algorithmic disconnect is because they are too easy to game. Since Geth's code is public, it's trivial to see what...
Engine API spec says GetPayloadV3 can only be called during Cancun :) > Client software MUST return -38005: Unsupported fork error if the timestamp of the built payload does not...
Guess this is not needed any more with the supply delta on master now.
Closing this issue. Unsure where we are on this, but it's not something we're actively trying to address so cleanup time.
This is IMHO working as intended? Pebble can do concurrent compaction, and during initial sync, we're inserting data at an insane rate that the database needs to compact. Why would...
Hmm, after initial sync, there are still some background tasks running (tx indexing / unindexing, snapshot regeneration), which can do a lot of database load. It should subside in a...
We think this is natural that pebble will compact until sync is done (and maybe a bit after). If it doesn't settle down ever we can take a look, but...
We'd need to investigate a bit how to expose metadata in Prometheus and InfluxDB. I'm all for surfacing these infos, just have no idea yet what the standard way is....