Scorbajio

> I am not sure what to make of the karma browser test failures. It seems to be complaining about a dist file. @acolytec3 are these karma errors a known...

> Great work! I have some questions. Do you also have an URL to this compact encoding somewhere? Thanks! I wasn't able to find much on compact encoding. There is...

> Hmm OK now I get > > ``` > not ok 1 Error: invalid keys order > --- > operator: error > stack: |- > Error: invalid keys order...

> Yes, I'll take care of that. Picking this PR back up.

#1893

When calling `getAccountRange`, the `proof` and `accounts` arrays contain data elements that look like this: ``` { account: { hash: , body: [ , , Uint8Array(0) [], Uint8Array(0) [] ]...

Now that there is reference data for `getAccountRange`, next steps are to figure out how to divide the fetching process into smaller tasks, if necessary. When fetching accounts, we need...

@g11tech I wasn't able to get `forceSnapSync` option to work. I would set it like this: ``` DEBUG=devp2p:* npm run client:start:dev2 -- --forceSnapSync=true ... ``` I ended up hardcoding it...

#2070 is being continued at #2107.

Closing this and continuing on https://github.com/ethereumjs/ethereumjs-monorepo/issues/2874.