Please support parity_listStorageKeys

[ytrezq]

Rationale

This api still OpenEthereum only, allows to list all storage/blockchain on past blocks and is required to build a token rich list on past blocks as well required by many security analysis tools.

Implementation

No idea on how to implement it though it looks like https://github.com/ledgerwatch/erigon failed to find a way to implement it without breaking database compatibility and thus is unwilling to implement it. Please notice OpenEthereum required the database to be fatdb enabled in addition to tracing enabled (full archive node instead of just archive node).

[AusIV]

@philip-morlier - I believe we could massage debug_storageRangeAt into this syntax. I'm not sure we could match the sort order parity used, but we should be able to get the result set.

[philip-morlier]

@AusIV @ytrezq I have added this into our internal development cycle and will begin investigating in the near future. @ytrezq do you have access to a fully synced OpenEthereum archive node?

[ytrezq]

@philip-morlier sorry for the delay. I was looking for someone who could fix openethereum/openethereum@98873fc? I mean openethereum code has it s difficulty bomb which was planned in June not delayed.

Because of this, I crashed the RocksDb Index/MANIFEST file. The data inside sst files itself is Ok. The underlying problem is the Facebook tool used to rebuild Manifest comes from the ldb erra and doesn’t support multiple columns. I ve no idea on how to repair this.

Though there are examples on https://openethereum.github.io/JSONRPC-parity-module#parity_liststoragekeys.