Karim Taam

currently @thomas-quadratic is working on that

@jframe could you check the block pruning modification we are doing in this PR to be sure it's correct. normally we did tests but I prefer to have your feedback

Can you keep your node db to help us débug ? Are you sure to use the latest version of BESU for step 4? Since the start of the sync...

I do not know if you have a way to share your database in order to save us 3 weeks of sync to return to this block. We can discuss...

working on that currently thanks to the database shared

yes feel free to do it 👍 most important is here - Write historical block history https://github.com/hyperledger/besu/blob/verkle/ethereum/core/src/main/java/org/hyperledger/besu/ethereum/mainnet/HistoricalBlockHashProcessor.java - Allow to add exception in order to write empty account in the...

I think the second proposition (cache) seems to be interesting. Having all of the validation result in cache can simplify the code (we just have to modify the validator and...

Just a question. A peer that is useless for the worldstate part may not be for the blockchain part. Is there not a risk of losing valid nodes for a...

testing currently the PR with my snapsync boost feature

Could you try to upgrade to the version 23.10.3 ?