acolytec3

@gabrocheleau could we skip the failing tests for now and then continue work for the kaustinen7 changes (notably the fix I have for the `encodeBasicData` function) in the statefulVerkleStateManager branch?

The full rpc spec is [here](https://playground.open-rpc.org/?schemaUrl=https://raw.githubusercontent.com/ethereum/portal-network-specs/assembled-spec/jsonrpc/openrpc.json&uiSchema%5BappBar%5D%5Bui:splitView%5D=false&uiSchema%5BappBar%5D%5Bui:input%5D=false&uiSchema%5BappBar%5D%5Bui:examplesDropdown%5D=false) I don't think we need to implement all of them but maybe like `addENR` would be helpful.

My initial instinct is a clean package without all the dross of our CLI tooling that's built so specifically to be hive compliant. The core `portalnetwork` module works pretty cleanly...

Are we properly acknowledging the FIN in all scenarios or is there still some edge case where we are closing a socket before the FIN is sent?

Shouldn't we also do this check in common on start up?

Sad I couldn't finish this one.

A few comments for posterity/discussion: 1) The main use of the `AsyncEventEmitter` class is for pausing bytecode execution to be able to evaluate the state of the EVM at that...

No doubt related to all the `common` refactor stuff we've done lately.

@roninjin10 question for you on tree-shaking. I've been doing some experiments with export maps that specifically define all of the entry points for a given module (specifically with `statemanager` as...

> Gave it a look and the reason tree shaking isn’t working in state manager package is this part of package.json > > "type": "commonjs", > > Change this to...