Guillaume Ballet comments

Results 119 comments of


                                            Guillaume Ballet

core: store the chunked code directly in the database

This PR is on hold. More performance has been squeezed out by refactoring the code to ensure that tree keys for chunks are not computed more than once, and the...

rework of extcopy, storing the offsets alongside the code

note to self: this PR has to be merged before production, as not having it represents a potential DoS vector because the code will be re-chunkified each time a code-related...

rework of extcopy, storing the offsets alongside the code

Revisiting this issue 2 years later, some comments: * It is indeed a potential DOS vector if the code size limit is increased, as one could inexpensively call `EXTCODECOPY` multiple...

Verkle trie fuzzer

@jwasinger do you think this PR could be salvaged with the new version of the tree? Otherwise, I'll close it.

Offline cache for github worker

@karalabe @parithosh had something in the pipe to solve this. Not sure what the current state is. Basically, the cache is big because it's never cleared. It should be cleared...

Offline cache for github worker

also FYI it _is_ a local cache, it's just that copying it takes forever

debug_traceCall returning inaccurate gasUsed when both blockOverrides and stateOverrides are used

@Bitwise0x any update on this? We need your input, and will close this issue otherwise. To be clear, your last response does not help us, we would like to know...

Error IDs should only be four bytes long

No PR created, and we can not see any way out of this, closing. Feel free to open that PR if you think you have a workable fix.

transaction indexing is in progress

No response, and it seems there's no issue since you can retrieve the receipt.

shower thought: store the top of the tree as a single node

another idea is to store it with compressed points, as these points can be serialized/deserialized together, thus amortizing the cost.