scaffold-eth VS consensus-specs

If you want to learn to develop apps for the EVM (Thats Ethereum, Polygon, xDai, Aurora and many others) then you should read through the code in the various branches of https://github.com/austintgriffith/scaffold-eth for really good full-stack examples

git clone [https://github.com/austintgriffith/scaffold-eth.git](https://github.com/austintgriffith/scaffold-eth.git) challenge-2-token-vendor cd challenge-2-token-vendor git checkout challenge-2-token-vendor yarn install

In this blog post, I’m going to cover the first scaffold-eth speed run project: creating a Staking dApp. If you want to know more about scaffold-eth and my current journey in the web3 world you should read my previous article: My journey in Web3 development: scaffold-eth.

https://github.com/austintgriffith/scaffold-eth is a great ethereum boilerplate project that uses yarn workspaces in a monorepo, its a pretty standard practice that I've seen in the NFT/blockchain dev space.

I'm a fullstack JS developper, i've working and looking heavily into building on ethereum, so this is my first dive into the space. I would love some feeback from more senior devs on this, on the React and Dapp part. It is heavily based on scaffold-eth (and some Uniswap-interface code reading) so I'd recommend starting there if you're starting out rather than my starter, the docs and content there are first class. The stack is just the stack i am used to working with: Tailwind UI, Typescript and Redux Toolkit, and more. I'll be adding more examples other than the Greeter soon. Also i am for hire if you're looking for junior Dapp devs :) Thank your for your time !

I think its 1 million: https://github.com/ethereum/consensus-specs/issues/2137

how "radically decentralized" the development of the Ethereum core is. In the past half a decade only 133 devs have contributed to Ethereum source code. 2 devs have written 25% of the code. The first 10 developers have written 70% of the Ethereum code. Consensus specifications the ones that all the clients implement. Half are Consensys employees https://github.com/ethereum/consensus-specs

I think this will be defined here: https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/fork-choice.md

Clients dependent on Consensys core and ETH management repo. A client is just the implementation directed by Consensys written in a different language. Fact is about 10 developers are the only reason those clients will update with staking. https://github.com/ethereum/consensus-specs

Exits are processed at 7 per epoch (currently). There is no queue for withdrawals. See https://github.com/ethereum/consensus-specs/pull/3068

https://github.com/ethereum/consensus-specs/blob/dev/specs/p...

For that, we have to take the vanilla deposit contract from the consensus specs: deposit_contract.sol, get the Solidity compiler version 0.6.11, compile the binary of the runtime part, and create an empty deposit tree.

The PoS consensus specification