Nim backports 1.6 git log --oneline --pretty="format:%m https://github.com/nim-lang/Nim/commit/%H %s" --left-right --cherry-pick devel...origin/version-1-6 [ ] - https://github.com/nim-lang/Nim/commit/16f42084d32144d5afb2a5cc3a5a833e5295a8bc fixes #20900; Calling template through from generic function across module fails to build (#21649) [ ] - https://github.com/nim-lang/Nim/commit/be06446ffecd7665651a25d6b07fade5cc019296 fix #15691 (#21623) [ ] - https://github.com/nim-lang/Nim/commit/5e016e4466151ddb86a72a46cc2bbf83dfd6dfe3 fixes #21638; fromJson should support empty objects (#21641) [ ] - https://github.com/nim-lang/Nim/commit/686c75cef032481630e27dad3731df98e067b75e for loop expression can now have generated iterator's called (#21627) [ ] - https://github.com/nim-lang/Nim/commit/a37a83cbff89867be9cbc5ba2f50c37e99efe0f1 fixes #21617; createTypeBoundOps with PContext in order to instantiate generics (#21619) [ ] - https://github.com/nim-lang/Nim/commit/814d3e6818b6c4ed976818ecf525a599502e080e fix #19430 (#21603) [ ] - https://github.com/nim-lang/Nim/commit/c06623bf8ccfccf4788e9f4d2f044ab1bde6fe46 Fix segfault caused by ensuring valueless statics are not evaluated (#21577)

WIP implementation https://github.com/status-im/nimbus-eth2/pull/4550 What this solves The maximum block size is 1.8 MB - depending on who you ask, the blob adds another 128-1024kb on top of that. Data takes time to stream: 1mb on 10mbit = 1 s of streaming - we maintain a gossip mesh of ~8 peers, meaning that if we do nothing else, we need to both send and receive 8x the block+blob amount under time pressure, which is a lot to ask. Core to the problem is that the block processing can be done independently of the blob - the situation is similar to how the execution processing can be done independently of the consensus processing. Practically, it means that we can process the block, start gossiping it then process the blob, parallelizing utilization of both block and blob.