v7 Breaking Release Planning

[holgerd77]

Follow-up on #1717
Branch: master develop-v7 

Next breaking release round for the monorepo libraries, major features: Buffer -> Uint8Array transition, ESM/CJS builds, permanent statemanager (account/storage) and trie (nodes) caches, EVM/VM/StateManager EEI and state access refactoring with cleaner API, EIP-4844 in beta (?), internally refactored trie library (needs confirmation), VM/Blockchain Level dependency removal, lighter VM/Blockchain packages (genesis states removal), Shanghai default HF

• May/June: First round of Beta releases
• July: Final Releases

TODO

• ESM round 2: src root path adoptions (browser compatibility), also see Monorepo: Switch to hybrid ESM/CJS Build #2685, open for grasps
• EVM/EEI/StateManager rework part 2, in progress EVM, remove EEI: cleanup statemanager #2702, @jochem-brouwer
• VM/Blockchain: removal of genesis states, lighter packages, @g11tech
• rustbn.js library release, Remove rustbnHotFix from package.json @holgerd77 @acolytec3
• Replace c-kzg with typescript-kzg library if feasible (would be really good!), @acolytec3 Proof of concept typescript kzg integration #2725
• Trie library refactoring, performance tests, sync tests, Trie: Internal Refactoring #2662, @ScottyPoi, everyone
• Update ethersStateManager to use ethers v6, Make ethersStateManager more awesome #2720, @acolytec3
• Optional but nice: continue with Optimism Bedrock work Improved Optimism Bedrock Compatibility #2713, check breaking change needs, @holgerd77
• Remove deprecated Rinkeby, Ropsten networks (please only do after Optimism PR Improved Optimism Bedrock Compatibility #2713 merged)
• Integrate @ethereumjs/wallet library, @holgerd77, everyone
• General consistency round, "hidden" deprecations (like block: swap withdrawal/opts in constructor #2715), everyone

Decisions

• PoW Deprecation? Yes/no? In what form?, everyone

[jochem-brouwer]

I was planning to ship #2000 this month, but it would make sense if we remove the warm/touched addresses/accounts in EEI first, so will start with that.

[acolytec3]

I was planning to ship #2000 this month, but it would make sense if we remove the warm/touched addresses/accounts in EEI first, so will start with that.

No strong opinion about warmed/touched accounts but that minimal EEI would be a big win for devs. It still takes a fair bit of boilerplate to get a standalone EVM instantiated (unintuitively requires you to import the VM so you can get the EEI.

[jochem-brouwer]

My EVM/VM points regarding the touched/warm accounts is in #2604

[holgerd77]

Closed by #2945