Just a few weeks ago, we were 50x slower than the top Ethereum clients. Now, we're third in these benchmarks, closing in on second place. We just started focusing on performance related work. We're merging performance related PRs daily and steadily stabilizing Ethrex. We expect significantly better numbers soon.
I think the strategy of keeping the codebase simple and clean will start showing major advantages from now on when doing performance and maintenance related work.
All benchmarks will be released with code so anyone can reproduce the results. We're also starting to create testnets using Ethrex for different products.
If you want to support us an independent @ethereum team, please star the repo, it really helps more people discover what we're building.
Things are moving: Ethrex now runs as an L1 @ethereum execution client (with the Lambda EVM), a ZK + TEE L2 client, and supports both based and centralized modes. Based mode still WIP. We’re building a lightweight DB to go beyond a gigagas and parallelizing everything. Consensus client next? All in <100k LOC.
Some teams raised 9 figures to do less and said we couldn’t deliver. We always deliver. Rogue is next.
We couldn't have done anything of the things we did in ethereum without the support and help of @StarkWareLtd @ethereumfndn @0xPolygon. We also learnt a lot from @Consensys.
Our @class_lambda client Ethrex now runs as an L1 @ethereum execution client (with the Lambda EVM), a ZK + TEE L2 client, and supports both based and centralized modes.
Based mode still WIP. We’re building a lightweight DB to go beyond a gigagas and parallelizing everything.
Consensus client next? All in <100k LOC.
Some teams raised 9 figures to do less and said we couldn’t deliver. We always deliver.
Our @class_lambda client Ethrex now runs as an L1 @ethereum execution client (with the Lambda EVM), a ZK + TEE L2 client, and supports both based and centralized modes.
Based mode still WIP. We’re building a lightweight DB to go beyond a gigagas and parallelizing everything.
Consensus client next? All in <100k LOC.
Some teams raised 9 figures and said we couldn’t deliver. We always deliver.
Our @class_lambda client Ethrex now runs as an L1 @ethereum execution client (Lambda EVM), a ZK + TEE L2 client, and supports both based and centralized modes.
Based mode still WIP. We’re building a lightweight DB to go beyond a gigagas and parallelizing everything.
Consensus client next? All in <100k LOC.
Some teams raised 9 figures and said we couldn’t deliver. We always deliver.
We're writing a small article for our @class_lambda blog about SNARK verification in Bitcoin.
Apart from the BitVM and ColliderVM papers and the criticism from @rot13maxi and @AlpenLabs posts, which other articles or posts should we read or reference? Thanks!