Wagmi is quickly rising to be the #1 Web3 frontend library. The Wagmi CLI allows blazing-fast iteration on full-stack hackathon projects w/ its Foundry integration.
We want to get replace primitive-types in all our Rust code with @recmo's Ruint. The biggest blocker here is replacing ethabi's internal types with Ruint.
No big expectations here. Would like to see things like AMM/Lending/NFT/... styleless React components which abstract away common on-chain operations.
I don't think any of the existing Etherscan-esque buttons w/ inputboxes cut it, need to be opinionated
Implementation of MEV Share
This was proposed recently, it is feasible but not for newbies (+ maybe some FB ppl on it alrd), come find me to route to the rihgt ppl / spec out together if you're interested
Excited to be open-sourcing Reth, an Ethereum execution layer in @rustlang 🦀
Reth is a new Apache/MIT-licensed full-node implementation of Ethereum by @paradigm and the community, focused on contributor-friendliness, modularity, and performance.
1. Building a performant node for power users 2. Contributing to Ethereum’s stability by improving client diversity 3. Giving back to Ethereum by contributing to the roadmap
We are building Reth to accommodate a broad user base, including stakers, hobbyists, RPC node operators, bridges, MEV searchers, and even L2s (e.g., Optimism/Arbitrum) or other Ethereum-adjacent projects (e.g., Polygon, BSC, Avalanche, Fantom etc.).
.@paradigm is building Reth, a Rust Ethereum Execution Layer.
Reth is not a fork or a rewrite of any other client implementation.
It is a new Apache/MIT-licensed full node implementation of Ethereum focused on contributor friendliness, modularity, and performance. 1/8
Reth does not include code from any existing client but stands on the shoulders of giants including Geth, Erigon and Akula.
We sponsored the project in the interest of client diversity, so we are sorry to see any other project ceasing development. It is a loss for the space. 2/8
A core goal of Reth is modularity and open-source friendliness.
Every component is built to be used as a library: well-tested, heavily documented and benchmarked.
We envision that developers will import the node's crates, mix and match, and innovate on top of them. 3/8
This time, @a_kirillo and @jneu_net and I teamed up to see if we can bring Narwhal & Bullshark, a novel mempool & consensus algorithm, to the Cosmos ecosystem 🧵 1/18
As more and more blockchain systems get deployed to production, two problems are frequently encountered:
1. Achieving consensus with high throughput and low latency paradigm.xyz/2022/07/consen… (cc @LefKok) 2. Building a distributed application on top of that consensus
Cosmos uses Tendermint (TM), a high-performance BFT consensus algorithm, and the Cosmos SDK, a toolkit which enables developers to launch their own chain on TM.
@brockjelmore@joshie_sh Scripting & Deployments are critical for making Foundry more than just a testing framework, and expanding on ChainOps.
Following our Solidity-centric philosophy, we introduce a new set of cheatcodes (`broadcast`), which make any calls affected by them to be posted onchain.
@brockjelmore@joshie_sh The above script is simple. It'll generate two calls, the `Contract` deployment tx, and the call to `test()`.
You can take this file and insert it into your own tx management system. Or, you can add `--broadcast`, and Forge will broadcast it for you (right pic has receipts!).
tl;dr: 1. proposer boost (was created to counteract balancing attacks (arxiv.org/abs/2203.01315, eprint.iacr.org/2021/1413.pdf) on Ethereum PoS 2. only some nodes had upgraded 3. reorg caused due to boost applied by some but not all nodes 4. not an issue as all nodes eventually upgrade
Separately, as this came up, PoS Ethereum has finality that is not like Tendermint's single-slot finality. This exists for a good reason, and there's work on single slot finality