Our great sponsors
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
And ETH today is just still so damn undervalued, on just about every single metric you can possibly measure. Whether you're looking at the annual revenue and the price-to-sales ratio, the exchange reserves, the burn rate, the number of active addresses, the amount of ETH staked in the beacon chain, the transaction counts, including L2s (h/t u/mister_eth), the amount still locked in DeFi, the widespread adoption of ENS, the earth-shattering explosion of NFTs into the mainstream culture, and on and on.
New WIP specs for Danksharding: https://github.com/ethereum/consensus-specs/blob/c6b5e28bb10c228da88822aba522a4e23f7d3f58/specs/sharding/beacon-chain.md
And ETH today is just still so damn undervalued, on just about every single metric you can possibly measure. Whether you're looking at the annual revenue and the price-to-sales ratio, the exchange reserves, the burn rate, the number of active addresses, the amount of ETH staked in the beacon chain, the transaction counts, including L2s (h/t u/mister_eth), the amount still locked in DeFi, the widespread adoption of ENS, the earth-shattering explosion of NFTs into the mainstream culture, and on and on.
And that's without even touching upon the fact that the market hasn't truly started to price in The Merge aka The Cliffening/Triple Halvening (h/t /u/insidethesimulation) or any of the other hugely consequential and beneficial improvements on the Ethereum protocol development roadmap.
After the merge, when it's time for a beacon client to produce a block, it will ask its execution client to build a block with certain characteristics. The communication between the two clients is defined by the Engine API. With this, the beacon client will notify the execution client that a certain execution layer payload was accepted by the beacon chain forkchoice rule via engine_forkchoiceUpdateV1, and it will include an additional parameter to the call PayloadAttributesV1 which will alert the execution client that it is about to propose a block and needs an execution payload to be built. In that extra parameter is a field suggestedFeeRecipient. This will be an execution layer address which will receive the priority fees from the block. The reason it is "suggested" is that it leaves open a design space for proposer-builder separation where it is not known who will actually construct the block that the execution client responds with.