
Ethereum represents the gateway to a worldwide, decentralized computing paradigm. This platform enables you to run decentralized applications (DApps) and smart contracts that have no central points of failure or control, integrate with a payment network, and operate on an open blockchain. With this practical guide, Andreas M. Antonopoulos and Gavin Wood provide everything you need to know about building smart contracts and DApps on Ethereum and other virtual-machine blockchains.

Discover why IBM, Microsoft, NASDAQ, and hundreds of other organizations are experimenting with Ethereum. This essential guide shows you how to develop the skills necessary to be an innovator in this growing and exciting new industry.

A guide to the operation and use of Ethereum and other EVM-compatible blockchains.

Mastering Ethereum


The story of the idealists, technologists, and opportunists fighting to bring cryptocurrency to the masses.

In their short history, Bitcoin and other cryptocurrencies have gone through booms, busts, and internecine wars, recently reaching a market valuation of more than $2 trillion. The central promise of crypto endures—vast fortunes made from decentralized networks not controlled by any single entity and not yet regulated by many governments.

The recent growth of crypto would have been all but impossible if not for a brilliant young man named Vitalik Buterin and his creation: Ethereum. In this book, Laura Shin takes readers inside the founding of this novel cryptocurrency network, which enabled users to launch their own new coins, thus creating a new crypto fever. She introduces readers to larger-than-life characters like Buterin, the Web3 wunderkind; his short-lived CEO, Charles Hoskinson; and Joe Lubin, a former Goldman Sachs VP who became one of crypto’s most well-known billionaires. Sparks fly as these outsized personalities fight for their piece of a seemingly limitless new business opportunity.

This fascinating book shows the crypto market for what it really is: a deeply personal struggle to influence the coming revolution in money, culture, and power.

Idealism, Greed, Lies, and the Making of the First Big Cryptocurrency Craze

The Cryptopians


Tokens - often referred to as cryptocurrencies - can represent anything from an asset to an access right, such as gold, diamonds, a fraction of a Picasso painting or an entry ticket to a concert. Tokens could also be used to reward social media contributions, incentivize the reduction of CO2 emissions, or even ones attention for watching an ad. While it has become easy to create a token, which is collectively managed by a public Web3 infrastructure like a blockchain network, the understanding of how to apply these tokens is still vague.

The industry keeps referring to “Blockchain” as different from “Bitcoin,” creating an artificial divide that is often misleading. There seems to be too little understanding about the fact that Bitcoin is a blockchain network, which is (a) globally managed by people who mostly do not know each other, and (b) enabled by the consensus protocol that (c) incentivizes all network actors for their contributions with a native token. The governance rules are tied to the minting of a native blockchain token. The Bitcoin token can, therefore, be seen as the currency of a distributed Internet tribe, called the Bitcoin network, where network actors are rewarded with Bitcoins, just as the Ether is the currency of the distributed Internet tribe Ethereum network, or Sia is the native currency of the Sia network. The Bitcoin network and other distributed ledgers all represent a collectively maintained public infrastructure and are the backbone of the next generation Internet, what the crypto community refers to as the Web3.

This book attempts to summarize existing knowledge about blockchain networks and other distributed ledgers as the backbone of the Web3, and contextualize the socio-economic implications of the Web3 applications such as smart contracts, tokens, and DAOs to the concepts of money, economics, governance and decentralized finance (DeFi).

Token Economy


Learn to Code Blockchain DApps By Building Simple Games

CryptoZombies is an interactive school that teaches you all things technical about blockchains. Learn to make smart contracts in Solidity or Libra by making your own crypto-collectibles game.

#1 Solidity Tutorial & Ethereum Blockchain Programming Course

CryptoZombies


Node Guardians is a gamified educational platform that creates lore-rich programming challenges for experienced Solidity, Huff, Cairo and Noir developers. Think of it as a skill-based RPG where developers can become familiar with specific stack components and a place where they can showcase their abilities. 

### Skills Upgrade

We have created a series of coding challenges called “quests” to engage smart contract developers, providing them with the knowledge to build safe and gas efficient applications. In addition to practical skills, we also provide theoretical knowledge about crypto history, technology and economics through building a library of articles that break down complex concepts of distributed systems & decentralized finance.


### Public Good

Node Guardians is a public good for developers and will always remain so. 
In addition to supporting the growth of cool ecosystems, we plan to make the platform sustainable by managing [infrastructure](https://infra.nodeguardians.io/) across various networks.

Rewarding non-contributing operators wastes funds, we prefer community-building and education.


Node Guardians is a gamified educational platform that creates lore-rich programming challenges for experienced Solidity, Cairo, Huff and Noir developers.

Node Guardians


Speed Run Ethereum aims to provide a structured learning path for onboarding developers to Ethereum.

Ethereum Dev Speed Run with a framework for submitting challenges, get feedback from ethereum builders, and in the process unlocking new challenges and proof of completion.

Speedrun Ethereum

Teaching the next generation of smart contract developers and auditors. Learn from industry-leading experts how to build the next generation of web3 applications and level up your career.


Level up your web3 career through industry leading comprehensive courses

Cyfrin Updraft


This is an initiative for the early solidity developers by those who were early developers sometime.

In this approach, we are looking to categorize the smart contract according to the difficulty level in multiple standards. For now, we are keeping the standard 0 to 5(can be discussed).

This initiative needs great support from Blockchain enthusiast, developer and researchers to build this school in a way which can attract learners and provide them ease for development.

First place for early developers to learn Solidity 

solidity-school


## Introductory Modules

- What is a SNARK?
- Building a SNARK (part 1)
- Building a SNARK (part 2)

## Whiteboard Sessions with ZK Projects​

- SNARKs vs. STARKS with Brendan and Bobbin
- PLONK and Custom Gates with Adrian Hamelink
- Lookup Arguments for Performance Optimisation with Mary Maller
- Zero Knowledge Virtual Machine (zkVM) with grjte
- Achieving Decentralised Private Computation with Pratyush Mishra
- Introduction to zkRollups with Barry Whitehat
- zkEVM with Jordi Baylina
- ZK Swaps with Henry de Valence
- zkID with Oleksandr Brezhniev
- Fast Recursion with Plonky2 with William Borgeaud

ZK Whiteboard Sessions is an educational series on all things zero knowledge

ZK Whiteboard Sessions


## What is a smart contract?

Smart contracts are the backbone of decentralized applications (DApps) and Web3. A smart contract is a simple program that lives on a blockchain network (such as Ethereum). They're actually not that smart. And nothing like a (legal) contract. They’re more like an executable piece of code that requires input or an trigger from an external source. They can validate those input conditions and if correct, execute their own logic to update the state on a blockchain.

## Benefits

They often serve the following purposes:
- Store and maintain data
- Manage relationships with users, or other contracts

Benefits of smart contracts are
- Immutable - once deployed none can change them
- Composable - they’re public and anyone can interact with them, or build on top of them. Much like public APIs

## Resources

The following resources have been the most popular resources on the site for a long time. These are all highly recommend to start learning about Solidity


### 1. Official Solidity website
The most obvious resources is ofcourse the official website and documentation of the Solidity team itself. The Solidity team covers all the core concepts and fundamentals of Solidity and smart contracts in general. Highly recommended

https://soliditylang.org/


### 2. Solidity by Example
The second one on the list is Solidity by Example. A great collection of more practical examples, incl. source code and supporting videos.

https://solidity-by-example.org/


### 3. CryptoZombies 
CryptoZombies is an interactive school that teaches you all things technical about blockchains. A fun and interactive way to write smart contracts in Solidity by making your own crypto-collectibles game.

https://cryptozombies.io/


### 4. Speedrun Ethereum

Speedrun Ethereum helps you get to the next level. It teaches you how to build on Ethereum; the superpowers and the gotchas while you build up your Web3 portfolio. If you like this, also make sure to check out the other work of the amazing [Austin Griffith](https://twitter.com/austingriffith) such as [ETH-build](https://eth.build/) and [Scaffold-eth](https://scaffoldeth.io/).

https://speedrunethereum.com/


### 5. Smart Contract Best Practices 

Smart contracts are complex instruments that have the authority to allocate high-value resources between complex systems. Often working autonomously. With huge financial loss at risk. This makes them critical components in these systems. Development of such components requires thoughtful design, solid engineering practices, rigorous testing and a strong security mindset. This document provides a baseline knowledge of security considerations.

https://consensys.github.io/smart-contract-best-practices/


## Other resources

If you'd like to read more, make sure to checkout all the other [Solidity](/tags/smart%20contracts) resources on the site.

Solidity is a programming language designed for developing smart contracts that run on Ethereum. It's the most in demand skill in the Web3 space. These are the best resources to help you learn more about it.

Best resources to learn Solidity


Navigating conversations and understanding key concepts in web3 sometimes requires its own terminology. In this regard, web3 is not just a technological shift, but also a cultural one.

This guide will provide you with the **most essential terms** to decode the language and become a web3 citizen. It is tailored to provide you with clear and concise definitions for the unique terms that define this industry.

Dive in, discover, and enhance your fluency in the unique lexicon of the web3 industry. (-:

If you want to contribute to the glossary, [have a look on Github](https://github.com/wslyvh/useWeb3/tree/main).

## Glossary a-z

- **Airdrop**  
  Distribution of free tokens, usually to promote a product or incentivise early users

- **Altcoin**  
  Alternative coin, any cryptocurrency other than Bitcoin

- **AMM**  
  Automated Market Maker, popular mechanism among decentralized exchanges (DEXes) involving liquidity pools instead of an orderbook-based system

- **Anon**  
  Anonymous, entity that wishes to remain anonymous or pseudonymous

- **Beacon Chain**  
  Ethereum’s proof-of-stake (PoS) consensus layer

- **Bridge**  
  Service that transfers tokens between multiple blockchains (cross-chain)

- **BUIDL**  
  Term to describe the web3 building ethos, even despite a bear market, inspired by HODL

- **CeFi**  
  Centralized finance, the “traditional” finance sector, in contrast to DeFi (decentralized finance)

- **CEX**  
  Centralized Exchange, app for swapping tokens run by a company, often used for fiat exchange; in contrast to DEX (Decentralized Exchange)

- **Cypherpunks**  
  Cypher + punks, movement originating in the early 90s, emphasizing the need for privacy in the digital age, enforced by cryptography

- **DAO**  
  Decentralized Autonomous Organization, blockchain-based organizations that are owned and governed by their members via tokens

- **DApp**  
  Decentralized Application, blockchain-based services that use smart contracts in their backend and thus have a distributed nature, without the need for intermediaries

- **DeFi**  
  Decentralized Finance, general term for decentralized services in the financial sector, that are permissionless and globally available, e.g., DEXes (decentralized exchanges) or lending protocols

- **Degen**  
  Degenerate, term for a person that is deeply involved in crypto or a specific sector, e.g., DeFi Degens

- **DEX**  
  Decentralized Exchange, blockchain-based app for swapping tokens that use smart contracts to be permissionless

- **Diamond Hands**  
  Holding a digital asset through very volatile times

- **DYOR**  
  Do Your Own Research, principle of self-verification instead of trusting others

- **EIP**  
  Ethereum Improvement Proposal, a process to describe standards for the Ethereum platform

- **ERC**  
  Ethereum Request for Comments, form of EIP to specify application layer standards; the most popular ones are ERC20 for fungible tokens and ERC721 for non-fungible tokens

- **EVM**  
  Ethereum Virtual Machine, the environment in which all Ethereum accounts and smart contracts live, the EVM defines the rules for computing a new valid state from block to block

- **Exchange**  
  An application that allows users to buy and sell crypto assets

- **Exit Scam**  
  Scenario in which a project or a part of a team steals the investors’ money and leaves

- **Explorer**  
  Webpage that displays information about the transaction history of a blockchain

- **Faucet**  
  Service that dispenses free tokens, usually for test networks

- **Flippening**  
  Term to describe a pivotal change in price or perception, e.g., when the market cap of a token exceeds the one of another token

- **FOMO**  
  Fear Of Missing Out, term to describe the feeling of not being included in something, e.g., a crypto investment or news

- **Fork**  
  Split of a blockchain or project due to technical issues or a dispute

- **FUD**  
  Fear, Uncertainty and Doubt, the opposite of FOMO

- **Gas**  
  Term for the fee that Ethereum transactions cost; it is used to reward validators and prevents malicious use of the blockchain

- **Genesis Block**  
  The first block recorded in a blockchain

- **Gm**  
  Good morning, form of greetings in crypto communities; due to the global nature of web3 it can be used at any time of the day

- **Hash**  
  Function that can be used to map data of arbitrary size to fixed-size values, e.g., for encryption, cryptographic hash functions are used in many parts of the web3 industry

- **HODL**  
  A frequent term referring to a strict buy-and-hold strategy, became famous after a misspelling in the bitcointalk forum in 2013

- **ICO**  
  Initial coin offering, the process of selling tokens when launching a new crypto project, inspired by the initial public offering (IPO) for stocks.

- **JOMO**  
  Joy Of Missing Out, converting FOMO into a positive feeling

- **KYC**  
  Know Your Customer, a process to verify the identity of customers; often used by centralized exchanges or entities

- **Layer 1**  
  Base blockchain architecture that serves as the foundation for other layers, also called mainnet, e.g., Ethereum

- **Layer 2**  
  Built on top of layer 1, usually for scaling purposes, e.g., Optimism

- **Minting**  
  Process of creating new token(s)

- **Mixer**  
  Decentralized Application that “mixes” tokens to cover their transaction history, used for private transactions

- **NFT**  
  Non-Fungible Token, a type of token that is not interchangeable or divisible, in contrast to fungible tokens; often used for digital collectibles

- **Node**  
  An instance holding a copy of the blockchain, it is connected to other nodes, synchronizing the blockchain and thus forming the network

- **OG**  
  Original Gangster, a person who was very early involved in crypto or a specific project

- **Oracle**  
  Data bridge to bring real-world information onto the blockchain

- **P2P**  
  Peer-to-peer, referring to a transaction between two people without other (central) parties involved

- **Rollups**  
  Popular type of layer 2, scaling solution that uses transaction bundling (“rolling up”) transactions before publishing them to the main chain

- **Rug Pull**  
  Scenario in which a team abandons a project and/or removes its liquidity, similar to exit scams

- **SBTs**  
  Soul-Bound-token, type of NFT that is non-transferrable

- **Smart contract**  
  Programs that run on the blockchain that follow the "if this then that" logic, they execute themselves when certain conditions are met

- **Snapshot**  
  Record of a blockchain at a particular block height, also the name of a popular DAO voting tool

- **Solidity**  
  Smart Contract Programming Language, created for the Ethereum blockchain but popular for other chains as well

- **Stablecoin**  
  A cryptocurrency that is pegged to another asset, mostly USD

- **Staking**  
  Process of locking tokens to contribute to validation in a proof of stake blockchain

- **Token**  
  Representation of a digital asset on a blockchain

- **TVL**  
  Total Value Locked, equivalent of USD locked in a blockchain or protocol, often used as an indicator in DeFi, e.g. in lending protocols

- **Validator**  
  Virtual entity participating in the consensus of a proof of stake blockchain, they participate in producing blocks and validating transactions

- **WAGMI**  
  Acronym for “We're All Gonna Make It”, expression used to show an optimistic attitude about the future of web3

- **Whale**  
  An entity holding a large amount of cryptocurrency, sometimes even a significant part of a project

- **Whitepaper**  
  Document that is released with new crypto projects to explain the details of the project.

- **ZKP**  
  Zero-Knowledge-Proof, cryptographic mechanism to verify an information without revealing it, often used for scaling solutions of privacy applications


The glossary provides you with definitions for the most important terms to navigate the web3 landscape.

Crypto glossary – important terms to navigate web3


This handbook is for people who are interested in exploring the vision behind “Web3”, and who wish to acquire in-demand skills that are essential to realizing that vision.  

A Handbook for Smart Contract Development

Learn Solidity


Create Eth App supports multiple frontend frameworks. It comes with a host of decentralized finance templates pre-filled with contract ABIs, addresses and subgraphs. Everything you need to build a modern Ethereum-powered single-page app.

- Learning how to write Ethereum-powered apps in a comfortable and feature-rich development environment.
- Starting new Ethereum-powered single-page React applications without wasting time on copy-pasting boilerplates
- Creating examples with React for your Ethereum-related libraries and components.

Create Ethereum-powered apps with one command

Create Eth App


**Features**
- Next.js
- Ethereum
- Typescript
- Chakra UI
- Wagmi
- Connectkit
- Ethers.js

An open-source Next.js + Ethereum starter kit to quickly ship Web3 Apps

Nexth Starter kit


Everything you need to build on Ethereum!

Quickly experiment with Solidity using a frontend that adapts to your smart contract

Forkable Ethereum dev stack focused on fast product iterations

Scaffold-ETH


Becoming a blockchain engineer is the most fun, rewarding, and exhilarating choice I’ve and my colleagues have ever made. And we’ve already blazed the trail for you to get started! In this article, we will show you exactly how to learn to become a blockchain engineer, from beginner to professional.

Spoiler alert, here is the exact blueprint we are going to cover to get you to a successful blockchain engineer:

1. Understand why you should become a blockchain engineer
2. Take a Blockchain Course
3. Join a Hackathon, the Community, & Build
4. Start your own protocol, Take a job, Freelance & Contribute

If you make it this far, you’ve done it! Although, I’ll add a bonus step 5 that we will talk about soon.

5. You’ve made it! Keep learning!

That’s it! These are the exact steps you need to take to become a blockchain engineer!

Become a blockchain, solidity, and smart contract engineer by following these steps

Become a Blockchain Engineer


Odds are you’ve heard about the Ethereum blockchain, whether or not you know what it is. It’s been in the news a lot lately, including the cover of some major magazines, but reading those articles can be like gibberish if you don’t have a foundation for what exactly Ethereum is. So what is it? In essence, a public database that keeps a permanent record of digital transactions. Importantly, this database doesn’t require any central authority to maintain and secure it. Instead it operates as a “trustless” transactional system — a framework in which individuals can make peer-to-peer transactions without needing to trust a third party OR one another.

Still confused? That’s where this post comes in. My aim is to explain how Ethereum functions at a technical level, without complex math or scary-looking formulas. Even if you’re not a programmer, I hope you’ll walk away with at least better grasp of the tech. If some parts are too technical and difficult to grok, that’s totally fine! There’s really no need to understand every little detail. I recommend just focusing on understanding things at a broad level.

Many of the topics covered in this post are a breakdown of the concepts discussed in the yellow paper. I’ve added my own explanations and diagrams to make understanding Ethereum easier. Those brave enough to take on the technical challenge can also read the Ethereum yellow paper.

Many of the topics covered in this post are a breakdown of the concepts discussed in the yellow paper. I’ve added my own explanations and diagrams to make it easier.

How does Ethereum work, anyway?


I recently joined Edge & Node as a Developer Relations Engineer and have been diving deeper into smart contract development with Ethereum. I have settled upon what I think is the best stack for building full stack dApps with Solidity:

▶︎ Client Framework - React
▶︎ Ethereum development environment - Hardhat
▶︎ Ethereum Web Client Library - Ethers.js
▶︎ API layer - The Graph Protocol

Building Full Stack dApps with React, Ethers.js, Solidity, and Hardhat

The Complete Guide to Full Stack Ethereum Development


Educational sandbox for building on web3. Visually understand how Ethereum works by doing.

ETH.Build


https://www.youtube.com/watch?v=gyMwXuJrbJQ

This course will give you a full introduction into all of the core concepts in blockchain, smart contracts, solidity, NFTs/ERC721s, ERC20s, Coding Decentralized Finance (DeFi), javascript and solidity, Chainlink, Ethereum, upgradable smart contracts, and full stack blockchain development.   

Some of the technologies covered are:
- The Graph
- Chainlink
- Metamask
- Alchemy
- Remix
- Hardhat
- Solidity
- Openzeppelin
- Trail of Bits
- Ganache
- Ethers
- Etherscan
- Coinmarketcap
- Aave
- IPFS
- Fleek.hq
- Filecoin
- NextJS
- Moralis
- Web3uikit
- Opensea
- Pinata
- Nft.storage

 And more!

Follow along with the videos and you'll be a blockchain wizard in no time!  💻 The repository with helpful links to all code, resources, and support forums is located here: https://github.com/smartcontractkit/full-blockchain-solidity-course-js.

This course will give you a full introduction into all of the core concepts related to blockchain, smart contracts, Solidity, ERC20s, full-stack Web3 dapps, decentralized finance (DeFi), JavaScript, TypeScript, Chainlink, Ethereum, upgradable smart contracts, DAOs, the graph, moralis, aave, IPFS, and more. Follow along with the videos and you'll be a blockchain wizard in no time!

Learn Blockchain, Solidity, and Full Stack Web3 Development with JavaScript – 32-Hour Course


Learning Solidity with a collection of YouTube videos and example code.

Learning Solidity


Here we collect and discuss the best DeFi & Blockchain researches and tools 

DeFi Developer roadmap


ETH Gas Tracker helps you discover how gas works, why it matters and help you set optimal gas fees to use the Ethereum network more efficiently. Get real-time gas prices, historical data, and average fees to time your transactions and save money. Ethereum Gas Tracker is the best way to track gas prices and provides an API for developers to integrate gas data into their applications.

Monitor and track the Ethereum, and L2 gas prices to reduce transaction fees and save money

ETH Gas Tracker


This document provides a baseline knowledge of security considerations for intermediate Solidity programmers. It is maintained by ConsenSys Diligence, with contributions from our friends in the broader Ethereum community.

A guide to Ethereum smart contract security best practices

Smart Contract Best Practices

Sometimes CLI Options tests have a [failure](https://github.com/hyperledger/besu/actions/runs/18488059153/job/52675394377?pr=9303) that looks like

```
NetworkingOptionsTest > getCLIOptions_default() FAILED
    java.lang.AssertionError at AbstractCLIOptionsTest.java:76
```

Downloading the test report, the full error is:


```
java.lang.AssertionError: 
Expecting empty but was: "Invalid metadata file /home/runner/work/besu/besu/app/build/data/VERSION_METADATA.json
```

I guess it's a concurrency issue with multiple tests reading/writing the same version metadata file



good first issue

flake

test

An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu

besu

Java

flaky test: CLI Options test

#### Expected behaviour
`eth_simulateV1` should be exposed via `ethclient`


#### Steps to reproduce the behaviour
use `github.com/ethereum/go-ethereum/ethclient` in your golang project and try to call `eth_simulateV1` or `Simulate`. there no related method available in ethclient that calls it.

#### Notes
`eth_simulateV1` is a relatively [new method](https://github.com/ethereum/execution-apis/pull/484). `ethclient` just needs to be updated to support and expose it.

type:bug

help wanted

Go implementation of the Ethereum protocol

go-ethereum

eth_simulateV1 missing from ethclient

It appears that there are still some differences when you run `make reftests` on the same commit but different systems. This is almost certainly related to randomness somewhere. It appears to exist in these different areas:

* `ssz_generic/progressive_containers/invalid/*modded*`
* `sanity/blocks/pyspec_tests/mix_blob_tx_and_non_blob_tx`
* `operations/proposer_slashing/pyspec_tests/builder_payment_deletion_current_epoch`
* `operations/proposer_slashing/pyspec_tests/builder_payment_deletion_previous_epoch`
* `operations/proposer_slashing/pyspec_tests/builder_payment_deletion_too_late`

<img width="1861" height="1027" alt="Image" src="https://github.com/user-attachments/assets/cc69ebaa-1300-4b31-903c-7af51fc516ad" />

<img width="1861" height="1027" alt="Image" src="https://github.com/user-attachments/assets/7ef3c5b6-fe22-49fe-a52c-b775e7e50538" />

<img width="1861" height="1027" alt="Image" src="https://github.com/user-attachments/assets/93c8fb1d-14a7-4de5-bece-ba4a0d70d11a" />

Ethereum Proof-of-Stake Consensus Specifications

consensus-specs

Python

Make reftest generation reproducible

I've just noticed that there are not updated containers for many of the lightclient upgrades.

For example, `LightClientUpdate`:

https://github.com/search?q=repo%3Aethereum%2Fconsensus-specs+%22class+LightClientUpdate%22&type=code

There's only one of these defined, but the header field technically changes in each upgrade:

https://github.com/search?q=repo%3Aethereum%2Fconsensus-specs+%22def+upgrade_lc_update_to_%22&type=code 

We should define updated containers for these type of situations.

For example, we would define a new `Modified LightClientUpdate` section here:

https://github.com/ethereum/consensus-specs/blob/master/specs/capella/light-client/sync-protocol.md#containers

It would look like:

### Modified `LightClientUpdate`

```python
class LightClientUpdate(Container):
    # [Modified in Capella]
    attested_header: LightClientHeader
    next_sync_committee: SyncCommittee
    next_sync_committee_branch: NextSyncCommitteeBranch
    # [Modified in Capella]
    finalized_header: LightClientHeader
    finality_branch: FinalityBranch
    sync_aggregate: SyncAggregate
    signature_slot: Slot
```

This is a bit explicit, but I'd rather be explicit than confusing.

lightclients

Missing updated containers in lightclient specs

### Description
On Windows (64-bit), any call into the secp256k1 native library via besu-native fails with java.lang.UnsatisfiedLinkError. This is because the required secp256k1.dll is not available, and the README currently lists Windows build instructions as TBD.

This means that on Windows machines, no method in LibSecp256k1 can be invoked successfully.

### Example Failure
```
LibSecp256k1.secp256k1_ec_pubkey_parse(
    CONTEXT,
    pubKey,
    pubKeyBytes,
    pubKeyBytes.length
);
```

**Produces**
```
java.lang.UnsatisfiedLinkError: 
  'int org.hyperledger.besu.nativelib.secp256k1.LibSecp256k1.secp256k1_ec_pubkey_parse(
       com.sun.jna.ptr.PointerByReference, 
       org.hyperledger.besu.nativelib.secp256k1.LibSecp256k1$secp256k1_pubkey, 
       byte[], 
       long
   )'
    at org.hyperledger.besu.nativelib.secp256k1.LibSecp256k1.secp256k1_ec_pubkey_parse(Native Method)
```

### Expected Behavior
Windows (x64) users should be able to load and call secp256k1 native methods just like Linux/macOS users.
Either prebuilt binaries (.dll) should be published alongside Linux builds, or clear instructions provided for building on Windows.

### Actual Behavior
All calls into LibSecp256k1 fail with UnsatisfiedLinkError on Windows because no native library is present.

### Environment
- OS: Windows 10 / Windows 11 (64-bit)
- Java: 21.0.7 (also reproducible on other versions)
- besu-native version: latest

### Additional Context
The [README](https://github.com/hyperledger/besu-native) documents Linux build steps, but for Windows simply states TBD.
Without Windows support, any Java project that depends on besu-native cannot function on Windows.

### Suggested Next Steps
- Provide build instructions or CI workflows to compile secp256k1.dll for Windows.
- Publish Windows native artifacts alongside Linux/macOS.
- Update the README to explicitly state supported platforms and how to build for Windows.


besu-native

Windows support missing for secp256k1 (UnsatisfiedLinkError on all native calls)

I haven't seen these messages before.

<img width="1212" height="318" alt="Image" src="https://github.com/user-attachments/assets/d78133d8-fbfd-4947-a198-095cb45d45a0" />

This is probably associated with `uv` changes or the reftest summary PR.

Fix error messages when ctrl-C'ing out of make reftests

Rust full node implementation of the Fuel v2 protocol.

fuel-core

Rust

Make backup tool part of the `fuel-core` binary

When sending a transaction with EIP-7702 `authorizationList`, Besu fails
to estimate gas if the `gas` parameter is not explicitly provided.

If `gas` is set manually, the transaction executes successfully.
If `gas` is omitted, Besu calls `eth_estimateGas` internally and returns
an error:Error message:Invalid parameters were provided to the RPC method.Double check you have provided the correct parameters.

This suggests that `eth_estimateGas` does not yet fully support the new
EIP-7702 transaction format with `authorizationList`.

eth_estimateGas fails with EIP-7702 (authorizationList) transactions

When running `make test` I get the following warnings:


```
tests/core/pyspec/eth2spec/test/altair/light_client/test_data_collection.py::test_light_client_data_collection
  /Users/jtraglia/Projects/leo/consensus-specs/venv/lib/python3.13/site-packages/_pytest/python.py:161: PytestReturnNotNoneWarning: Test functions should return None, but tests/core/pyspec/eth2spec/test/altair/light_client/test_data_collection.py::test_light_client_data_collection returned <class 'generator'>.
  Did you mean to use `assert` instead of `return`?
  See https://docs.pytest.org/en/stable/how-to/assert.html#return-not-none for more information.
    warnings.warn(

tests/core/pyspec/eth2spec/test/altair/light_client/test_sync.py::test_light_client_sync
  /Users/jtraglia/Projects/leo/consensus-specs/venv/lib/python3.13/site-packages/_pytest/python.py:161: PytestReturnNotNoneWarning: Test functions should return None, but tests/core/pyspec/eth2spec/test/altair/light_client/test_sync.py::test_light_client_sync returned <class 'generator'>.
  Did you mean to use `assert` instead of `return`?
  See https://docs.pytest.org/en/stable/how-to/assert.html#return-not-none for more information.
    warnings.warn(

tests/core/pyspec/eth2spec/test/altair/light_client/test_sync.py::test_supply_sync_committee_from_past_update
  /Users/jtraglia/Projects/leo/consensus-specs/venv/lib/python3.13/site-packages/_pytest/python.py:161: PytestReturnNotNoneWarning: Test functions should return None, but tests/core/pyspec/eth2spec/test/altair/light_client/test_sync.py::test_supply_sync_committee_from_past_update returned <class 'generator'>.
  Did you mean to use `assert` instead of `return`?
  See https://docs.pytest.org/en/stable/how-to/assert.html#return-not-none for more information.
    warnings.warn(

tests/core/pyspec/eth2spec/test/altair/light_client/test_sync.py::test_advance_finality_without_sync_committee
  /Users/jtraglia/Projects/leo/consensus-specs/venv/lib/python3.13/site-packages/_pytest/python.py:161: PytestReturnNotNoneWarning: Test functions should return None, but tests/core/pyspec/eth2spec/test/altair/light_client/test_sync.py::test_advance_finality_without_sync_committee returned <class 'generator'>.
  Did you mean to use `assert` instead of `return`?
  See https://docs.pytest.org/en/stable/how-to/assert.html#return-not-none for more information.
    warnings.warn(

tests/core/pyspec/eth2spec/test/altair/light_client/test_sync.py::test_light_client_sync_no_force_update
  /Users/jtraglia/Projects/leo/consensus-specs/venv/lib/python3.13/site-packages/_pytest/python.py:161: PytestReturnNotNoneWarning: Test functions should return None, but tests/core/pyspec/eth2spec/test/altair/light_client/test_sync.py::test_light_client_sync_no_force_update returned <class 'generator'>.
  Did you mean to use `assert` instead of `return`?
  See https://docs.pytest.org/en/stable/how-to/assert.html#return-not-none for more information.
    warnings.warn(

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
```

We should fix these so there are no warnings.

Warnings when running tests

### Describe the feature

We currently compute the compressions ratio even for L1 messages, which isn't used since L1 fees aren't paid on L1 messages. Skip the calculation for L1 messages, similar to what is done for the encoding:
- https://github.com/scroll-tech/reth/blob/b2377df23567e57f1068911d947d2ca0f9c34252/crates/scroll/alloy/evm/src/tx/mod.rs#L164
- https://github.com/scroll-tech/reth/blob/b2377df23567e57f1068911d947d2ca0f9c34252/crates/scroll/alloy/evm/src/tx/mod.rs#L273


### Additional context

_No response_

Modular, contributor-friendly and blazing-fast implementation of the Ethereum protocol, in Rust

reth

Skip compressions for L1 messages

Consider the deeply nested expressions that might be used in precompiled circuits, we should adjust the stack size. For example, I adjust it to 32M when running weierstrass addition in the rust code. However, I haven't find a good way to adjust the stack size in `benches/`. I tried:
- `RUST_MIN_STACK=... cargo bench -p ceno_zkvm --bench weierstrass_add`
- `RUSTFLAGS="-C link-args=-Wl,-z,stack-size=33554432" cargo bench --bench weierstrass_add`

Neither of them works.

Now I temporarily remove `criterion_main!` and use a self-defined main function to resolve the issue, while waiting for a better way to do it.

For more details, see the following:
#1072 

Accelerated Zero-knowledge Virtual Machine by Non-uniform Prover Based on GKR Protocol

ceno

Not able to change stack size in `cargo bench`.

Add state overrides to AbstractTraceCall 

- similar to eth_call

snack

Add state overrides to AbstractTraceCall

## Description

We had an insecure HTTP dependency creep into our Cargo.toml, fixed by:

- https://github.com/sigp/lighthouse/pull/8094

It would be good to run a tool on CI to detect these, as suggested by @hopinheimer.


dependencies

lighthouse

Ensure HTTPS links in Cargo.toml

Why is there no IPC support for Lighthouse? I think it is a typical case where a node runner has execution and consensus clients on the same machine. In addition, OP Stack needs to connect to l1 execution and beacon nodes. These can also be run on the same machine, especially given the powerful hardware you have these days.

IPC outperforms http/ws:
- low CPU overhead
- no memory copy
- low latency per call

enhancement

optimization

HTTP-API

IPC support for the beacon API

Currently a lot of the meta information of the tests vectors is contains in its directory structure.

From: https://github.com/ethereum/consensus-specs/blob/master/tests/formats/README.md?plain=1#L123-L126

```
File path structure:
tests/<config name>/<fork or phase name>/<test runner name>/<test handler name>/<test suite name>/<test case>/<output part>
```

This information comes from this class: https://github.com/ethereum/consensus-specs/blob/master/tests/infra/manifest.py

This is not convenient for  refactorings and for example if you want to distribute just one test vector, instead of all of them.

Modify the ad-hoc framework so this information appears additionally in a `manifest.yml` in every test vector.

testing

Manifest file for tests vectors

### Overview

Hello developers.

I'm running a separate Pectra PoS testnet chain for API testing. During testing, I observed discrepancies in the JSON-RPC responses from execution clients—geth, besu, nethermind, reth and erigon. Specifically, when calling `eth_getBlockReceipts` with invalid request, Besu returns an `Block not found` error with code `-32000`, while the other four clients respond with `null` as defined in the [exec-api spec](https://ethereum.github.io/execution-apis/api-documentation/).

```
# besu
{"error": {"code": -32000, "message": "Block not found"}, "id": 1, "jsonrpc": "2.0"}
# geth
{"id": 1, "jsonrpc": "2.0", "result": null}
# nethermind
{"id": 1, "jsonrpc": "2.0", "result": null}
# reth
{"id": 1, "jsonrpc": "2.0", "result": null}
# erigon
{"id": 1, "jsonrpc": "2.0", "result": null}
```

Spec definiton of the response:
```
"oneOf": [
	{
		"title": "Not Found (null)",
		"type": "null"
	},
	{
		"title": "Receipts information",
		"type": "array",
	...
```
Thanks for your attention!

### Steps to Reproduce

Call the `eth_getBlockReceipts` with invalid block number:

```shell
curl POST http://127.0.0.1:10652 \
   -H "Content-Type: application/json" \
   -d '
{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "eth_getBlockReceipts",
  "params": [
    "0x1014083b159295235b6b84814f860e91d2a5105bf11c60f97ae8fb2b00cb7ff9"
  ]
}'
```

**Expected behavior:** Return `null` for not found.

**Actual behavior:** Return error.

**Frequency:** 100%

### Logs

```
# besu
{"error": {"code": -32000, "message": "Block not found"}, "id": 1, "jsonrpc": "2.0"}
# geth
{"id": 1, "jsonrpc": "2.0", "result": null}
# nethermind
{"id": 1, "jsonrpc": "2.0", "result": null}
# reth
{"id": 1, "jsonrpc": "2.0", "result": null}
# erigon
{"id": 1, "jsonrpc": "2.0", "result": null}
```

### Versions (Add all that apply)
* OS Name & Version: Ubuntu-20.04

Client versions

- besu/v25.8.0/linux-x86_64/openjdk-java-21
- Geth/v1.16.3-stable-d818a9af/linux-amd64/go1.24.6
- Nethermind/v1.33.1+cda59e5b/linux-x64/dotnet9.0.8
- reth/v1.7.0-9d56da5/x86_64-unknown-linux-gnu
- erigon/3.1.0/linux-amd64/go1.24.7

with 

- Prysm/v6.0.4 (linux amd64)


Inconsistent response of  JSON-RPC `eth_getBlockReceipts`

Go set TLS 1.2 as the default for clients in 1.18 and servers in 1.22:

- https://tip.golang.org/doc/go1.18#tls10
- https://tip.golang.org/doc/go1.22#minor_library_changes

I believe CodeQL has a mechanism for checking a project's minimum supported Go version. So this query should only fire for project's that support Go < 1.22 or 1.18 depending on the code used (i.e. client vs. server).

This would make a good first issue for someone 👍 

CodeQL queries developed by Trail of Bits

codeql-queries

CodeQL

MissingMinVersionTLS inaccurate for newer Go versions

Implement a transaction selection time of high scored transactions 

Current behaviour

```
Produced #23,192,821 / 300 tx / 0 om / 29,481,838 (1.5%) gas / (0xb9dbf8b76bec7e7f780559df0abe419df36f4726a50f61a4970745f1af466834) in 1.569s / Timing(started at 2025-09-
11T09:58:35.158638058Z, protocolWait=0ms, duplicateWorldState=31ms, preTxsSelection=3ms, txsSelection=1373ms, 
blockAssembled=31ms, importingBlock=129ms, notifyListeners=0ms, log=0ms)
```

Expected behaviour
```
Produced #23,192,821 / 300 tx / 0 om / 29,481,838 (1.5%) gas / 
(0xb9dbf8b76bec7e7f780559df0abe419df36f4726a50f61a4970745f1af466834) in 1.569s / Timing(started at 
2025-09-
11T09:58:35.158638058Z, protocolWait=0ms, duplicateWorldState=31ms, preTxsSelection=3ms, 
txsSelection=1373ms, txsSelectionHighScore=950ms, 
blockAssembled=31ms, importingBlock=129ms, notifyListeners=0ms, log=0ms)
```

This helps to investigate the transaction selection time one there is a timeout to understand what time the transactions that were included in the block took in terms of selection time, example :

```

Produced #23,354,394 / 70 tx / 0 om / 2,785,671 (0.1%) gas / 
(0x051f72e4bff0c012e2c03fc9fcf4d476a3775689ce1329647439e26ec17280d6) in 2.014s / Timing(started at 
2025-09-15T09:13:46.954264875Z, protocolWait=46ms, duplicateWorldState=0ms, preTxsSelection=2ms, 
txsSelection=1923ms, blockAssembled=15ms, importingBlock=26ms, notifyListeners=0ms, log=0ms) 
```
I this case, there was a timeout but we don't know the real time it tool to select the 70 transactions
```
Transaction ... is processing for 1704ms, giving it 316ms grace time
```

Implement tx selection time of High scored txs

# Rationale

It is possible to fetch a single storage slot of a contract using `debug_getStorageAt` method. Anyone doing local simulations will need to call this method over and over and concur the overhead of repeated calls.

The idea is to implement a new method, perhaps `batchGetStorageAt` which fetches multiple slots of the same contract or even `batchGetStorage` which can receive a mapping of contract addresses to slot keys and returns the relevant storages of those accounts.

# Implementation

Do you have ideas regarding the implementation of this feature? Yes
Are you willing to implement this feature?

type:feature

Batch getStorageAt RPC method

We added the feature to disable the tests for the new MetaTxV0 preset, since the syscall is not compatible yet with the coverage tool. The feature should be removed, and the tests should be re-enabled for coverage when the cairo-coverage tool gets updated.


OpenZeppelin Contracts written in Cairo for Starknet, a decentralized ZK Rollup

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity