beacon-APIs
execution-apis
beacon-APIs | execution-apis | |
---|---|---|
3 | 11 | |
311 | 883 | |
3.5% | 2.9% | |
8.3 | 7.6 | |
15 days ago | 8 days ago | |
HTML | Io | |
Creative Commons Zero v1.0 Universal | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
beacon-APIs
-
Daily General Discussion - June 1, 2023
The clients are already built to conform to the execution API spec and beacon API spec, so building tools to interact with them is already client-agnostic to a great degree. If I add a custom ETH mainnet endpoint to Metamask, it doesn't care what client is providing the endpoint - only that it conforms to the spec.
-
Daily General Discussion - July 22, 2022
Our light client API endpoints have now been aligned to the spec discussed at Devconnect in Amsterdam. To see the updated endpoints, refer to the discussion here: https://github.com/ethereum/beacon-APIs/pull/181
- How ETH 2.0 will help with scaling
execution-apis
-
Latest Developments in Ethereum: Successful Deployment of Dencun Goerli Shadow Fork, Execution API Updates, Verkle Proof Precompile Proposal, and Upcoming ACD Calls
Devs agreed to make minor changes to execution api specifications so that users can retrieve blob gas price data. https://github.com/ethereum/execution-apis/pull/486
-
Vault - Level 08
With this knowledge we only need to figure out how to read the value from the deployed contract. There is a JSON-RPC API implemented in each Ethereum node in order for applications to interact with Ethereum, more about the API can be found here. Thankfully we have access to the web3js library on the web application which enables us to use this API.
-
Daily General Discussion - June 1, 2023
The clients are already built to conform to the execution API spec and beacon API spec, so building tools to interact with them is already client-agnostic to a great degree. If I add a custom ETH mainnet endpoint to Metamask, it doesn't care what client is providing the endpoint - only that it conforms to the spec.
-
Proposed block but not with MEV
The problem isn't about the execution client being able to see the reward value, it can. The problem is that it has no way of reporting it and so neither validator nor mev software can make any comparisons and "pick the bigger local block". This is still an open issue https://github.com/ethereum/execution-apis/issues/307
-
Has anyone ever gotten a MEV reward less than the tip you gave the MEV relay?
Correct, this would require a spec change. That discussion is here: https://github.com/ethereum/execution-apis/issues/307
-
Shared Execution Clients
Is this the API?
- How to make an API Query the Blockchain
-
EIP-1559 interaction with Proof of Stake
People who are smarter than me read the specs and dumbed it down for me lol. In this case it's all about the engine API for CL<->EL interop
-
Daily General Discussion - January 10, 2022
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.
-
Planning to set up staking
Infura will probably not offer the Engine API required after the merge. See https://community.infura.io/t/infura-post-merge-from-a-staker-perspective/3889/6
What are some alternatives?
spdx-spec - The SPDX specification in MarkDown and HTML formats.
eth2-ubuntu - Configuration of an Ubuntu 20.04 LTS server for use as an Eth2 staking system, including setup of monitoring dashboard.
pm - Project Management: Meeting notes and agenda items
consensus-specs - Ethereum Proof-of-Stake Consensus Specifications
node-red-contrib-alexa-remote-cakebaked - Forked for me and the community to keep dependencies up to date :)
go-ethereum - Go implementation of the Ethereum protocol
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
ethmerge.com-content - Markdown formatted content for the ethmerge.com website.
GazeRecorder - GazeRecorder | Behavior Analytics Made Easy | Website Eye-Tracking Heatmaps
besu - An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
PNG-spec - Maintenance of the PNG specification
crypto-fees - Website for comparing total daily fees of various blockchain protocols.