
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

## Description

In remote monitoring, [Lighthouse Advanced Metrics](https://lighthouse-book.sigmaprime.io/advanced_metrics.html?highlight=monitor#remote-monitoring) reports disk stats, such as `disk_node_bytes_free`, for the disk mounted at `/`. However, this may not correspond to the disk holding the actual beacon chain data.

## Version

Using the 6.0.0 executable from the release.

## Present Behavior

Currently, remote monitoring always reports the disk space for the root (`/`) mount point.  

Relevant code reference: https://github.com/sigp/lighthouse/blob/c042dc14d74352512b7632e0ee6ec07f1aa26b3a/common/eth2/src/lighthouse.rs#L183

## Expected Behavior

Remote monitoring should report the disk space for the `datadir` (or the default directory) instead of the root mount point. This is important as users may mount a separate drive specifically for beacon chain data.

## Steps to Resolve

1. Set up Lighthouse with remote monitoring enabled.
2. Configure `datadir` to point to a mount point on a second drive intended for storing beacon chain data.
3. Observe the reported disk stats to see if it's for the `datadir` mount point or `/`.  


good first issue

low-hanging-fruit

lighthouse

Rust

Update Remote Monitoring to Report Disk Usage for Datadir Mount Point

Following are the tests that are relatively easy to convert while also allowing to convert a large number of files from the tests repo in one go:

#### Random tests
[stRandom](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stRandom)
[stRandom2](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stRandom2)
In random tests need to look at the vm trace. Really are triggered like 5-6 cases of vm exceptions
I think it is enough to create minimum set of instructions that trigger the same vm exception. 1 per test.
Many tests just repeat itself. 

#### Zero knowledge 
[stZeroKnowledge](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stZeroKnowledge)
[stZeroKnowledge2](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stZeroKnowledge2)
Most tests from this folders are really just vectors for the precompiles. It is a base template with many parametrisation vectors.

#### Precompiled contracts
[stPreCompiledContracts1](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stPreCompiledContracts1)
[stPreCompiledContracts2](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stPreCompiledContracts2)
This are basically vectors to test the precompiles. should be easy to convert. 


#### Quadratic complexity folder
[stQuadraticComplexityTest](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stQuadraticComplexityTest)
This must be not really quadratic complexity but the stress tests that call something many times. Easy to convert.

#### Storage overwrite combinations
[stSStoreTest](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stSStoreTest)
This tests mainly verify the gas usage of storage touch situations   x to 0, 0 to x, x to x, 0 to 0  and so on. 
And refunds to when we x to 0, or 0 to x to 0.
This can be extended to also verify tstore in the same manner. 

#### TimeConsuming tests
[stTimeConsuming](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stTimeConsuming)
Need to revisit this test logic, but as far as I remember that are basically also storage overwrite/refund combinations. 
It is one template with many-many-many vector combinations. can really shrink down in python in code. 

#### stWalletTest
[stWalletTest](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stWalletTest)
This are legacy tests. those are actually ever first DAO tests if I am not mistaken. this does not test much of evm, but a smart contract. we can decide if we want to drop it or keep it. can be just converted as is. but sometimes I saw this tests breaking with the protocol development, so maybe they have something. 

#### Call Combinations Interuptions
[stCallCodes](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stCallCodes)
[stCallDelegateCodesCallCodeHomestead](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stCallDelegateCodesCallCodeHomestead)
[stCallDelegateCodesHomestead](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stCallDelegateCodesHomestead)

Here all tests are basically the same template. we take [calltype] -> C1 -> [calltype2] -> C2 -> [calltype3] -> C3
where calltype are all possible call opcodes. and C1, C2, C3 contracts are recording the context opcodes results like origin, selfbalance, address and so on.  then at some point can happen a revert by  REVERT, OOG,  and this revert can happen at C1 or C2 or C3   so really here are just 

for all calltypes
for all oogtypes
for all oogposition
[calltype] -> C1 -> [calltype2] -> C2 -> [calltype3] -> C3

the type of call changes the result of context opcodes. and reverts are removing the subcall changes. so it creates interesting situations where we can see what are the values of context opcodes, which contract they are recorded to and was it really reverted when OOG* happened. 

#### Gas Prices
[stEIP150singleCodeGasPrices](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stEIP150singleCodeGasPrices)
Here I have some ideas. this a basic test to measure gas price of some atomic evm operations. what we really need is to have a gas schedule map in python defined for each fork. and then we test on each fork that that schedule is really what external evm charges. 

by schedule I mean.  intrinsic transaction gas, intrinsic call operation gas,  storage access gas, hot address / call address call, base opcode gas price (I think already covered but without the schedule), memory expansion gas price formulas and so on. so here a little more work. 

A Python framework and collection of test cases to generate test vectors for Ethereum execution clients

execution-spec-tests

Python

Easy to convert test from ethereum/tests 

Currently the `misc/MMU_SUCCESS_BIT` may carry both “success" or "exception" information, yet it's called a `SUCCESS_BIT`. This involves changing the corresponding `mmu.SUCCESS_BIT` column to `mmu.MESSAGE_BIT`, too. As well as some of the neighbouring documentation.

cleaning

Specification of the constraint system underlying Linea's zk-EVM.

linea-specification

Rename the `misc/MMU_SUCCESS_BIT` to `misc/MMU_MESSAGE_BIT`

Source: https://github.com/ethereum-lists/chains

Existing Code: https://github.com/ethereum-optimism/op-analytics/blob/main/other_chains_tracking/get_ethereum_chain_list.ipynb

This could be a good starting set for EVM chain metadata (should not have Bitcoin, Solana, etc)

This can be an input to #890 

Onchain Data, Utilities, References, and other Analytics on Optimism

op-analytics

Jupyter Notebook

Read from ethereum-lists/chains

Legacy OVM1 data (before the current OP Mainnet Chain) is necessary for usage and economics. Legacy aggregate data from Dune lives in 

`oplabs-tools-data.api_table_uploads.dune_ovm1_daily_data`

Migrate OVM1 Data to New Schema / Folder

Migrate L2Beat data pre-API update - I believe this goes farther back in history?

Data lives in: 
- `oplabs-tools-data.api_table_uploads.daily_l2beat_aoc_by_token`
- `oplabs-tools-data.api_table_uploads.daily_l2beat_l2_activity`

Migrate Legacy L2Beat Data to new Schema/Folder

Requirement on having ETH transfers for L1 and L2s.

Existing Notebook: https://github.com/ethereum-optimism/op-analytics/blob/main/op_collective_economics/opcollective_feesplit/op_collective_revenue.ipynb

Existing Dune Query: https://dune.com/queries/3046107

**Ideal set-up is we:**
1. Have a list of all OP Collective Receiver Addresses
2. Track all transfers to and from those addresses, regardless of counterparty
3. Build a list of all known Superchain member sender addresses, and tag transactions accordingly.
4. Build a processes with Partnerships/Finance to ensure that we are as up to date as possible, leading up to revshare contract enshrinement (which we then integrate to)

**Address lists**
The known list exists in the Dune query (originally planned to do this in the GH repo lists, so you'll see some existing files, but we never used them and they fell out of date).

**Data Schema**
Transfers are infrequent and require audit-ability. So we should preserve all transaction & transfer level data, which we then build our aggregations on top of.

**Other Considerations**
Some transfers will come from a generic RaaS address, and not be clearly attributable by Superchain member. We should have some method for (later on) manually attributing / splitting a transfer by the appropriate Superchain member (i.e. RaaS A sends 1 ETH, we need to split 0.3 for Chain B's revshare, and 0.7 for Chain C's revshare.

Migrate OP Collective Revenue Transactions

### Describe the feature

In #36 we introduced zktrie and included the specification https://github.com/scroll-tech/reth/blob/feat/scroll-bmpt/crates/scroll/trie/assets/zktrie.md. The specification is outdated and does not include mention of domain separation for node hashing. We should update it to include this.

The constants for domain seperation in node hashing can be found here:
https://github.com/scroll-tech/reth/blob/c960cb7b482b1ff46567b663b6ab3d2c35ed4aeb/crates/scroll/trie/src/lib.rs#L16-L29

We should also update the part which suggests that the keys are truncated to 248 bits. This is not the case, all 254 bits (bn254 field size) are used in the key space.

### Additional context

_No response_

documentation

help wanted

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

reth

Update `zktrie` Specification 

https://blockscout.slack.com/archives/C059WER5EB1/p1709774370457039


searching for `.eth` of `eth` is super long. most probably because database of `graph-node` contains too many records for `eth` domain. 

possible solutions:

* ignore searching for TLD
* if problem in graph node records, add job that will remove useless records

blockscout-rs

bens: domains lookup for TLD domains is very long

### Description

The function [`answer_request `](https://github.com/paritytech/polkadot-sdk/blob/41a5d8ec5f3d3d0ff82899be66113b223395ade5/polkadot/node/network/statement-distribution/src/v2/mod.rs#L3245-L3246) should handle  [`AttestedCandidateRequest`](https://github.com/paritytech/polkadot-sdk/blob/82117ad53fc68e8097183e759926b62265ffff0a/polkadot/node/network/protocol/src/request_response/v2.rs#L32) and respond the peer who send it, also should check if the peer is allowed to request the candidate (i.e. they're in the cluster or we've sent them a manifest), should responde with [`AttestedCandidateResponse`](https://github.com/paritytech/polkadot-sdk/blob/82117ad53fc68e8097183e759926b62265ffff0a/polkadot/node/network/protocol/src/request_response/v2.rs#L47)

🕸️ Go Implementation of the Polkadot Host

gossamer

feat(statement-distribution): Implement `answer_request`

Similar to the `TestMessage` helper class, it might be worth having one for coins as well. 

We could have a static many function which could generate multiple coins.

```ts
const coins: Coin[] = TestCoin.many({
  owner: '0x09c0b2d1a486c439a87bcba6b46a7a1a23f3897cc83a94521a96da5c23bc58db'
}, 4);
```

feat

fuels-ts

TypeScript

Add `TestCoin` helper class

Add a section within developers that explains how to disable authentication for the json rpc.
Very useful during local development.

Also add a section on
- how generate the authentication token,
- important fields 
- and format to use when sending the request to the client.

This doesn't currently exist, the only reference to "authentication" is in the engine section of the doc's page which is less than sufficient.

enhancement

docs

JavaScript

Add Instructions on how to use and turn off authentication for json rpc.

This is a top-level issue for tracking the manual porting of ethereum/tests test cases to execution-spec-tests:

> **Contributions to manually port individual test cases are very welcome!**

**If you're already familiar with ethereum/tests and execution-spec-tests, jump to the issue tracker below!**

#### Background
[ethereum/tests](https://github.com/ethereum/tests) was the repository used to define EVM test cases from [Frontier](https://ethereum.org/en/history/#frontier) up to and including [The Merge](https://ethereum.org/en/history/#paris). The test cases are defined as YAML (and sometimes JSON) files in the [./src/ sub-directory](https://github.com/ethereum/tests/tree/develop/src) and the JSON "test fixtures" (fully-populated tests that can be executed against clients) are generated using [ethereum/retesteth](https://github.com/ethereum/retesteth). These JSON artifacts are regenerated when required and added to the repository, for example, in the [./GeneralStateTests/ sub-directory](https://github.com/ethereum/tests/tree/develop/GeneralStateTests).

From [Shanghai](https://ethereum.org/en/history/#shapella) on, new test cases (in particular for new features included in hard-forks) have been defined in Python in this repository (execution-spec-tests). The existing test cases are still important to execute against clients, however, and porting ethereum/tests to execution-spec-tests ensures that the test cases can be continually maintained and filled (generated) for newer forks. It also has the advantage that client teams will only need to obtain test fixture releases from one source.

#### Automated Port to Python
Although there will be an effort to automate ("transpile") the remaining test cases from YAML (respectively JSON) to Python; contributions to manually port individual test cases can be very beneficial and are welcome! 

The benefits of manual porting are:
1. Reduce the number of test cases by combing multiple YAML (resp. JSON) test cases in one Python test function (via parametrization).
2. Potentially improve coverage by parametrizing the Python version.
3. Code/docstrings are likely higher quality than an automated conversion.
4. The test can be better [organized within the `./tests` folder](https://ethereum.github.io/execution-spec-tests/main/writing_tests/adding_a_new_test/) in execution-spec-tests by the fork and the EIP in which the functionality was introduced.

#### Process
1. Pick a single or a set of YAML test cases in ethereum/tests to port and create an issue in this repository - optional, but definitely recommended if porting tests from the tracker below to avoid duplicate work.
2. Create a PR with the ported tests:
    a. Add the list of ported YAML files to [converted-ethereum-tests.txt](https://github.com/ethereum/execution-spec-tests/blob/1b30c336eae6b0746ea4db441ac74406f2fb2322/converted-ethereum-tests.txt).
    b. If the tests can't currently be filled, please explain the issue (feel free to also [open a Discussion](https://github.com/ethereum/execution-spec-tests/discussions/new?category=general)).

#### Help with ethereum/tests

The test formats are described in the [ethereum/tests online docs](https://ethereum-tests.readthedocs.io/en/latest/blockchain-ref.html). Note that state filler test cases in YAML can be parametrized, see the [docs here](https://ethereum-tests.readthedocs.io/en/latest/test_filler/state_filler.html#the-indexes).

#### Hints to Get Started with ethereum/execution-spec-tests

0. Start here: [Getting Started → Installation](https://ethereum.github.io/execution-spec-tests/main/getting_started/installation/).
1. Use `uv run et make test` to create a template test module (currently a WIP in #950).
2. Where to put the test? See how tests are organized in [Writing Tests → Adding a New Test](https://ethereum.github.io/execution-spec-tests/main/writing_tests/adding_a_new_test/).
3. State vs Blockchain test? If in doubt try to write a state test, see [Writing Tests → Types of Tests → Deciding on a Test Type](https://ethereum.github.io/execution-spec-tests/main/writing_tests/types_of_tests/#deciding-on-a-test-type).
4. Tests are filled via EELS by default (no further installation necessary; it's a Python dependency and got installed in Step 0), see [Filling  → Getting Started](https://ethereum.github.io/execution-spec-tests/main/filling_tests/getting_started/).
5. Parametrizing test functions is encouraged, see [Writing Tests → Writing a New Test → Parametrizing Tests](https://ethereum.github.io/execution-spec-tests/main/writing_tests/writing_a_new_test/#parametrizing-tests).
6. The Opcode mini-lang defined in this repository is the preferred way to define bytecode in tests (if feasible). For a very simple example, see [`test_chainid()`](https://github.com/ethereum/execution-spec-tests/blob/85393456e75f5f3b476cb5e61c35d48172f9d543/tests/istanbul/eip1344_chainid/test_chainid.py#L28) - there are other examples in the tests.

Feel free to reach out for help or guidance in the Ethereum R&D discord or via DM; see [Getting Help](https://ethereum.github.io/execution-spec-tests/main/getting_started/getting_help/) in the docs.

```[tasklist]
### Test Cases
- [ ] Add test cases for any single opcode (porting an entire test case from ethereum/tests can be overwhelming; instead add your own test cases for a single opcode from https://www.evm.codes/).
- [x] [src/GeneralStateTestsFiller/VMTests/vmTests](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/VMTests/vmTests) - swapFiller.yml - WIP: ethereum/execution-spec-tests#1012
- [x] [src/GeneralStateTestsFiller/VMTests/vmTests](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/VMTests/vmTests) - dupFiller.yml.
- [x] [src/GeneralStateTestsFiller/VMTests/vmTests](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/VMTests/vmTests) - pushFiller.yml - WIP: ethereum/execution-spec-tests#974
- [ ] [src/GeneralStateTestsFiller/VMTests/vmTests](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/VMTests/vmTests) (Note: DUP already ported).
- [ ] [src/GeneralStateTestsFiller/stLogTests/](https://github.com/ethereum/tests/tree/4f65a0a7cbecf4442415c226c65e089acaaf6a8b/src/GeneralStateTestsFiller/stLogTests).
- [ ] [src/GeneralStateTestsFiller/stRandom](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stRandom) and [src/GeneralStateTestsFiller/stRandom2](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stRandom2) (see #1016 for details)
- [ ] [src/GeneralStateTestsFiller/stZeroKnowledge](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stZeroKnowledge) and [src/GeneralStateTestsFiller/stZeroKnowledge2](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stZeroKnowledge2) (see #1016 for details)
- [ ] [src/GeneralStateTestsFiller/stPreCompiledContracts1](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stPreCompiledContracts1) and [src/GeneralStateTestsFiller/stPreCompiledContracts2](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stPreCompiledContracts2) (see #1016 for details)
- [ ] [src/GeneralStateTestsFiller/stQuadraticComplexityTest](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stQuadraticComplexityTest) (see #1016 for details)
- [ ] [src/GeneralStateTestsFiller/stSStoreTest](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stSStoreTest) (see #1016 for details)
- [ ] [src/GeneralStateTestsFiller/stTimeConsuming](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stTimeConsuming) (see #1016 for details)
- [ ] [src/GeneralStateTestsFiller/stWalletTest](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stWalletTest) (see #1016 for details)
- [ ] [src/GeneralStateTestsFiller/stCallCodes](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stCallCodes), [src/GeneralStateTestsFiller/stCallDelegateCodesCallCodeHomestead](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stCallDelegateCodesCallCodeHomestead) and [src/GeneralStateTestsFiller/stCallDelegateCodesHomestead](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stCallDelegateCodesHomestead) (see #1016 for details)
- [ ] [src/GeneralStateTestsFiller/stEIP150singleCodeGasPrices](https://github.com/ethereum/tests/tree/develop/src/GeneralStateTestsFiller/stEIP150singleCodeGasPrices) (see #1016 for details)
```

#### Some Examples of Ported Tests

| ethereum/tests | ethereum/execution-spec-tests|
|---------------------|------------------------------------------|
| [src/GeneralStateTestsFiller/VMTests/vmTests/dupFiller.yml](https://github.com/ethereum/tests/blob/4f65a0a7cbecf4442415c226c65e089acaaf6a8b/src/GeneralStateTestsFiller/VMTests/vmTests/dupFiller.yml) | [tests/frontier/opcodes/test_dup.py](https://github.com/ethereum/execution-spec-tests/blob/1b30c336eae6b0746ea4db441ac74406f2fb2322/tests/frontier/opcodes/test_dup.py) |
| [GeneralStateTests/stCreate2/call_outsize_then_create2_successful_then_returndatasize.json](https://github.com/ethereum/tests/blob/4f65a0a7cbecf4442415c226c65e089acaaf6a8b/src/GeneralStateTestsFiller/stCreate2/call_outsize_then_create2_successful_then_returndatasizeFiller.json), [GeneralStateTests/stCreate2/call_then_create2_successful_then_returndatasize.json](https://github.com/ethereum/tests/blob/4f65a0a7cbecf4442415c226c65e089acaaf6a8b/src/GeneralStateTestsFiller/stCreate2/call_then_create2_successful_then_returndatasizeFiller.json)| [tests/constantinople/eip1014_create2/test_create_returndata.py](https://github.com/ethereum/execution-spec-tests/blob/1b30c336eae6b0746ea4db441ac74406f2fb2322/tests/constantinople/eip1014_create2/test_create_returndata.py) |

scope:tests

type:feat

port

tracker

tracker(static tests): port ethereum/tests test cases

If chains are in the superchain-registry:

1. Read their available metadata from there (i.e. L1 contracts), rather than maintaining our own.
2. Calculate a field for OP Governed chains `ProxyAdminOwner = "0x5a0Aae59D09fccBdDb6C6CcEB07B7279367C3d2A"`

Eventually, only include chains in dashboards if they appear in the registry, to incentivize listings and remove the manual effort of managing multiple registries.

Links
- [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry)
- [OP Analytics Manual Metadata](https://github.com/ethereum-optimism/op-analytics/blob/main/op_chains_tracking/inputs/chain_metadata_raw.csv)

Ideally we also have some indication of when the registry changed, so we can mark when some configurations changed (i.e. when chains become "op governed")

Read Chain Metadata from Superchain Registry

### Which components does the task require to be changed? (think hard pls)

sncast

### Description

The default value needs to be updated [here](https://github.com/foundry-rs/starknet-foundry/blob/master/crates/sncast/src/helpers/configuration.rs#L37) to avoid problems with deserialization (currently it is deserialized to `None`) 

sncast

Blazing fast toolkit for developing Starknet contracts.

starknet-foundry

Add `block_explorer` field to `ShowConfigResponse`

RiscV uses relative addressing for branches like `BLTU`.  That means to get the absolute target address of a branch, you need to add the relative target address specified in the instruction to the address of the instruction itself.

That's a `u32` addition, ie we need to handle wrap-around.

Luckily, all the relevant information is known statically, so we can handle this computation at 'setup' time instead of at runtime, saving us a few `u32` range checks.

This might be a good first issue for newcomers.  Have a look at the structure `InsnRecord` and perhaps go from there.  Also consider implementing the same feature in the emulator to keep the two parts of the system in sync.

If you are in the swing of things, you can look into doing the same change for unconditional jump.

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

ceno

Convert branch instruction to use absolute addressing

Related: https://github.com/semaphore-protocol/semaphore/issues/318

documentation  📖

A zero-knowledge protocol for anonymous interactions.

semaphore

Add documentation to explain how to terminate the `bn128` curve

Create the `total_votable_supply` table following the schema in the [Governance Schema Document](https://docs.google.com/document/d/1G479lQS5q25TJCsGraRoO5NC8Jttu0R9_cRSAYPxY9A/edit?usp=sharing)
- Calculate and record the total votable supply daily.
- Calculate the `circulating_supply_share` as `(total_votable_supply / total_circulating_supply) * 100`.

Implement Total Votable Supply Table

### Related Component

compiler

### Problem

As the title states, hex literals have their optional suffix counted as part of their digits. This causes the following error, and related errors for types aside from b256:

```
  --> /Users/camden/Source/charcoal/out/ds_auth/src/main.sw:69:75
   |
67 |     } else if src == storage.owner.read() {
68 |         return true;
69 |     } else if storage.authority.read() == Identity::Address(Address::from(0x0000000000000000000000000000000000000000000000000000000000000000b256)) {
   |                                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ hex literals must have 1..16 or 64 digits
70 |         return false;
71 |     } else {
```

If we count the zeroes, logically we can deduce that there is in fact exactly 64 digits in the following:
```
0x0000000000000000000000000000000000000000000000000000000000000000b256
```

But there is no attempt made to strip the `b256` before counting.

### Steps

1. Create a sway project.
2. Create a b256 variable using the `0x0000000000000000000000000000000000000000000000000000000000000000b256` constant.
3. Run `forc build`

### Possible Solution(s)

Maybe strip the suffix before this point:
https://github.com/FuelLabs/sway/blob/73e1a7a80301d341864ea75de4124bf98d52a3ce/sway-core/src/transform/to_parsed_lang/convert_parse_tree.rs#L3388-L3402

### Notes

Should be an easy fix, but it should be done ASAP.

### Installed components

```console
camden@Camdens-MacBook-Air sway % fuelup check
latest - Up to date
fuelup - Up to date
camden@Camdens-MacBook-Air sway % fuelup show
Default host: aarch64-apple-darwin
fuelup home: /Users/camden/.fuelup

Installed toolchains
--------------------
latest-aarch64-apple-darwin (default)

active toolchain
----------------
latest-aarch64-apple-darwin (default)
  forc : 0.66.4
    - forc-client
      - forc-deploy : 0.66.4
      - forc-run : 0.66.4
    - forc-crypto : 0.66.4
    - forc-debug : 0.66.4
    - forc-doc : 0.66.4
    - forc-fmt : 0.66.4
    - forc-lsp : 0.66.4
    - forc-tx : 0.66.4
    - forc-wallet : 0.11.1
  fuel-core : 0.40.0
  fuel-core-keygen : 0.40.0

fuels versions
--------------
forc : 0.66.9
forc-wallet : 0.66.9
```


compiler: frontend

team:compiler

ODHack12

🌴 Empowering everyone to build reliable and efficient smart contracts.

sway

Sway hex literals have their suffix counted as digits

As per the discussion here: https://discord.com/channels/905194001349627914/1306104244486668369/1306929797296816200, Firefly-cli currently hard code the starting block of the Firefly batch pin contract event to `0` to ensure no events could be missed. But this is impractical when using multi-party mode with a public chain: https://github.com/hyperledger/firefly-cli/blob/14e7721bf8cca1fc6b2b217d00a5d79926a17af2/internal/stacks/stack_manager.go#L988

## Workaround

The currently workaround is to update the firefly_core yaml generated manually to start indexing the events from a desired block number. (hint: `newest` can be used if you don't care about missing events which breaks integrity of indexed data)

An enhancement would be making the FirstEvent configurable



Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity