-
-
reth
Modular, contributor-friendly and blazing-fast implementation of the Ethereum protocol, in Rust
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Back in November, Artem Vorotnikov (Akula developer) made this tweet:
It wasn't explicitly mentioned as the reason, but I'm fairly certain it's associated with Paradigm's new client, Reth. This controversy raised some concerns for me. What is the team's opinion on the ability for large companies to "buy a seat at the table" by either building their own client or purchasing an existing client (for example, Offchain Labs recent acquisition of Prysmatic Labs)? Is this good to bad for the ecosystem? If bad, is there anything we can do to disincentivize this?
EIP-1559 was a surprise to me in a good way. We had spent so much time imagining what it would look like, probably expecting it to be a bit rough around the edges at first. The adoption numbers at the beginning were not high (still lots of type 0/1 transactions) but the basefee was working like a charm. Props to watchtheburn.com and perema's fee feed, which I used to track the early deployment!
EIP-1559 was a surprise to me in a good way. We had spent so much time imagining what it would look like, probably expecting it to be a bit rough around the edges at first. The adoption numbers at the beginning were not high (still lots of type 0/1 transactions) but the basefee was working like a charm. Props to watchtheburn.com and perema's fee feed, which I used to track the early deployment!
I would definitely love for there to be more work on ZK programming languages. Exposing the internals more to help people do this was one of my motivations for attempting the task of making my own PLONK implementation. We need more tools to help people write circuits, and verify circuits; we should get to the point where verifying a verification key can be done eg. on etherscan as easily as verifying solidity code can be today.
Consensus Layer Withdrawal Protection
One totally different route we could take is eventually moving away from the EVM to some ZK-friendly EVM like Cairo. Existing EVM code would be replaced with execution of an EVM interpreter written in Cairo. This is all fairly long-term speculation at this point though.