
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

              Wouldn't it make sense to be able to have on the same row a WCP and a EUC call ? It would save up to three rows (nb of EUC calls), and won't make the MXP wider as the computation perspective is not the widest one.

_Originally posted by @letypequividelespoubelles in https://github.com/Consensys/linea-specification/pull/103#discussion_r2012426035_
            

good first issue

London to Prague

performance

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

linea-specification

Have both `WCP_XXX` and `EUC_XXX` columns in the `MXP/computation` perspective

### What feature should we add?

EIP-7702 is working well with manual transaction signing via ethereum/eth-account#316. There are undoubtedly better ways to interact and build 7702 transactions than currently exist within web3.py. Today we must do something like:

(untested, pseudocode-ish)
```py
# get the contract of interest, as an example
contract = w3.eth.contract(address=contract_address, abi=contract_abi)

acct = Account.from_key(my_key)
signed_auth = acct.sign_authorization({
    "address": contract.address,
    "nonce": w3.eth.get_transaction_count(acct) + 1,
    "chainId": w3.eth.chain_id,
})

# extract the data for the desired contract interaction
contract_call = contract.functions.myFunction(arg1, arg2).build_transaction()

tx = {
    "to": acct.address,
    ...
    "authorizationList": [signed_auth],
    "data": contract_call["data"],
}
signed_tx = acct.sign_transaction(tx)

w3.eth.send_raw_transaction(signed_tx.raw_transaction)
```

The goal would be to improve the DevEx to build and send a 7702 transaction. I believe this likely has to exist at the *web3.py*, not the *eth-account* level, as we should have access to the web3 object to facilitate `eth_chainId`, `eth_getTransactionCount` (nonce), `eth_estimateGas` calls, contract call data collection, etc.

---

Loosely, if I have a known contract and ABI, I'd like to be able to say take this account, authorize this account to behave like that contract, and build my transaction with this auth inside the "authorlzationList" while making the first call to function A on the contract. It may also be better to have a builder where there can be many iterations of this to build a single transaction with many such auths.

Enhancement

Help Wanted

A python interface for interacting with the Ethereum blockchain and ecosystem.

web3.py

Python

What DevEx improvements can we add for 7702 transaction interactions?

Would be good if Grafana shows by default:

- multiaddr node listens on
- ENR of node
- ENRTree used for bootstrap if any

Deployment docker-compose files to deploy an nwaku node

nwaku-compose

Shell

Show more connection details in Grafana

There are some pieces that we still need to document (testing API) and there are some pieces that have changed (how coverage is tracked).

documentation

help wanted

Parallelized, coverage-guided, mutational Solidity smart contract fuzzing, powered by go-ethereum

medusa

Do a general refresh/revamp of `mdbook`

## Overview

In the majority of our logging we have been lazy and done string interpolation. 
This has meaningful meaningful performance overheads, especially for whenever it is used during hot loops or heavy work loads - trace logging in world state comes to mind. 

We need to migrate to %s etc interpolation (for verbose and lower) such that we only pay for it whenever that log level is enabled. 

Modules check list provided below
- [ ] accounts  
- [ ] archiver  
- [ ] aztec  
- [ ] aztec-faucet  
- [ ] aztec-node  
- [ ] aztec.js  
- [ ] bb-prover  
- [ ] blob-lib  
- [ ] blob-sink  
- [ ] bot  
- [ ] builder  
- [ ] constants    
- [ ] entrypoints  
- [ ] epoch-cache  
- [ ] ethereum  
- [ ] foundation  
- [ ] ivc-integration  
- [ ] key-store  
- [ ] kv-store  
- [ ] l1-artifacts  
- [ ] merkle-tree  
- [ ] native  
- [ ] node_modules  
- [ ] noir-bb-bench  
- [ ] noir-contracts.js  
- [ ] noir-protocol-circuits-types  
- [ ] p2p  
- [ ] p2p-bootstrap  
- [ ] protocol-contracts  
- [ ] prover-client  
- [ ] prover-node  
- [ ] pxe  
- [ ] scripts  
- [ ] sequencer-client  
- [ ] simulator  
- [ ] stdlib  
- [ ] telemetry-client  
- [ ] txe  
- [ ] update-snapshots.sh  
- [ ] validator-client  
- [ ] watch.sh  
- [ ] world-state  

C-node

aztec-packages

logging: migrate to pino substitution instead of string interpolation

Base has changed how they print simulation links:

![Image](https://github.com/user-attachments/assets/1406a592-390d-4d8b-8cc8-a6a300eef879)

![Image](https://github.com/user-attachments/assets/87e2fc10-a3f6-4c6f-bc63-85599e6cdc87)

The instructions in [NESTED.md](https://github.com/ethereum-optimism/superchain-ops/blob/c6a65044b3931e6a18b6616f6863e3d61494746b/NESTED.md?plain=1#L74) and [SINGLE.md](https://github.com/ethereum-optimism/superchain-ops/blob/c6a65044b3931e6a18b6616f6863e3d61494746b/SINGLE.md?plain=1#L57) need to be updated to accomodate this change.

superchain-ops allows builders to create and execute tasks on EVM chains. 

superchain-ops

Solidity

Change NESTED.md and SINGLE.md to reflect two-step simulation link

We need an end-to-end integration test for the paymaster, which covers the following:

- Checks all endpoints for desired results from the paymaster
- Does a complete end-to-end gas sponsored transfer

Overall, this needs to be a test that we can put in our [tests](https://github.com/FuelLabs/fuel-station/tree/main/tests) folder, and once it runs successfully, we know that everything is working correctly with the paymaster.


We plan to remove client.test.ts and server.test.ts as they are old, and replace it with the above test.

ODHack12

Prototype for Station, A non-custodial gas paymaster on Fuel

fuel-station

TypeScript

integration test for the gas paymaster

If we look at the [examples](https://x.com/bajpaiharsh244/status/1904536287836598732) directory:
- We have an example for gasless token transfer


We need another example, which is a gasless counter that works with the gas station:
- A small React app
- That connects with the gas paymaster and a local fuel core node
- A small counter contract in sway
- A user can then keep clicking on the counter, and the count keeps on increasing without requiring any transaction signing request { it uses the paymaster for it }
- A readme to explain someone how to run this example

create a gasless counter example

The `signFromChildMultisig` function in `MultisigTask.sol` currently returns `VmSafe.AccountAccess[]` and `Action[]` which are then printed to the terminal. 

This creates unnecessarily noisy output that makes it harder to focus on the important information needed for signing.

enhancement

Refactor signFromChildMultisig to reduce noisy terminal output

Currently the lighthouse p2p private key is stored under beacon-data/network/key binary file. 

This is pretty inconvenient. It would be great if lighthouse would have a flag that would allow me to set the private key for the node using a new flag like `--p2p-priv-key=` that would point to a file. The content of this file is presumed to contain a hex  representing Secp256 key for example `e156614877adbfac274118a3be4b7dbfcd6d994126ab7e758dd7aa688f8ec0da`.

Lighthouse could convert this hex to binary, so that it wouldn't become a breaking change.
Then lighthouse should use this key to initialize its p2p address, which would allow us to test custom subnets for each peer. 

lighthouse

Rust

Feature request: allow me to initialize the p2p private key file with new flag

We should enable electra hard fork in our sim tests.

https://github.com/ChainSafe/lodestar/blob/e6a0cb22b5afe7d640750554f5f4d901f653652b/packages/cli/test/sim/multiFork.test.ts#L21

prio-low

scope-testing

spec-electra :giraffe:

🌟 Ethereum Consensus client for the Zig and TypeScript ecosystem

lodestar

Enable electra in sim tests

### What is the feature you would like to see?

Original message: https://github.com/OpenZeppelin/rust-contracts-stylus/pull/603#discussion_r1995800440

Depends on: https://github.com/OpenZeppelin/rust-contracts-stylus/issues/592

### Contribution Guidelines

- [x] I agree to follow this project's Contribution Guidelines

type: docs

effort: low

A library for secure smart contract development written in Rust

rust-contracts-stylus

[Feature]: update examples to expose ERC165 functionality

since we have the gas price service depending upon the onchain database as well as the gas price database, we need a reliable way to run tests such that the gas price database is known to have been updated by some state change in the onchain database i.e new L2 block, for example. 

https://github.com/FuelLabs/fuel-core/pull/2874#discussion_r2002091367

the relayer provides similar functionality via `await_synced`: https://github.com/FuelLabs/fuel-core/blob/90c855ccef823ea649cb395cfd7b8c15fde206e5/crates/services/relayer/src/service.rs#L298-L309

## Definition of done

- [ ] the gas price service updates the status when it receives a new block to `NotSynced` and when it is done processing the block, updates it to `Synced(height)`
- [ ] The tests(unit + integ) are updated to remove sleep's and instead use the new `await_synced` method with a timeout instead 

tech-debt

Rust full node implementation of the Fuel v2 protocol.

fuel-core

chore(gas_price_service): add a method to wait until storages are synced

Plonky3 [maybe-rayon](https://github.com/Plonky3/Plonky3/tree/main/maybe-rayon) provide a good wrapper to control parallism via "parallel" flag, thus within debug mode we can turn off the flag to avoid messy stack tracing info due to parallel `rayon`.

Do achieve that, we need to clean up all `rayon` import in current codebase and unifying to `use p3::maybe_rayon::prelude::*` instead

debugging tool

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

ceno

Use plonky3 `maybe-rayon` crate for optional parallelism mode

https://github.com/ethereum/portal-network-specs/pull/369#discussion_r1997285499

We want a 
- CI which verifies if the json-rpc spec files are formatted correctly
- A makefile command which formats the json-rpc spec's files in the correct format, so if CI fails the problem can be easily fixed.

Official repository for specifications for the Portal Network

portal-network-specs

JavaScript

Create CI to make sure json-rpc spec's json is properly formatted and a makefile script which formats the files properly

## Issue
Goerli (Görli), Ropsten, Rinkeby testnets are all deprecated, and remaining references to these should be removed.

Of note, some tutorials still reference these. Open for discussion on an individual basis how to handle these, but ideally these are updated to use the Sepolia testnet.


## Tasks
- Remove all remaining non-tutorial references to Goerli (Görli), Ropsten, Rinkeby
- Update any tutorial mentions to use Sepolia; or remove entire tutorial if fully dependent upon a deprecated testnet
- Update any use of "Holesovice" to use "Holesky" naming instead

## Contribute
Please comment for assignment if you'd like to work on this, thanks!


Status: Stale

Ethereum.org is a primary online resource for the Ethereum community.

ethereum-org-website

Markdown

Update all testnet references, removing those deprecated

We should make sure that our log file size is limited as otherwise this can cause issues like we saw with the attestation bug which happened ~1.8 million times a day and added a error log including stacktrace to the log file which was roughly 50-60 GB in size. This is bad as it can exhaust the disk space of the server and stall the node... and might even require manual clean up from operators.

I suggest we come up with a number eg. 5GB and after that limit is reached we stop writing logs to the file or alternative trim it from the beginning or override it in a way.

Could also consider having a max size on the whole log directory, let's say 25 GB and delete old log files if that limit is reached.

In any case I don't see a good reason why we need to keep writing to log file if it's bloated with the same error million times which is really the only case it can get so huge.

This is from one of the EF devops nodes
```
48G    beacon-2025-03-08.log
50G    beacon-2025-03-09.log
60G    beacon-2025-03-10.log
4.8G    beacon-2025-03-11.log
0    beacon-2025-03-12.log
70G    chain-db
1.1G    invalidSszObjects
14M    peerstore
```

`232G ` in total... this is bad, Barnabas is not happy about it

prio-medium

meta-bug

Limit log file size or total log directory size

![Image](https://github.com/user-attachments/assets/bf3192f5-3c84-4d94-b71e-d0d99f1de833)

see [discord discussion](https://discord.com/channels/593655374469660673/1344697108908998797/1347174565851431038)

meta-feature-request

New HTTP endpoint to add trusted peer

This issue is noticeable on devnets and was very apparent when trying to sync holesky in the unfinalized state (commonly referred to as "holesky rescue"). The main problem seems to be that if we just have a single peer (or maybe two) to sync data from we spam them too much causing us to being rate limited and eventually banned. This can be very harmful when trying to sync a network with not a lot of healthy nodes.

Seems like this is an issue with most / all client as peers, even Lodestar itself bans other Lodestar nodes doing this
```
Feb-28 12:58:17.367[network]         debug: Do not serve request due to rate limit peerId=16Uiu2HAmMtMosQ83JyLjAmhYMP5jT16VZtAFMMR1mSGhUEStmsKL
Feb-28 12:58:18.410[network]         debug: Do not serve request due to rate limit peerId=16Uiu2HAmMtMosQ83JyLjAmhYMP5jT16VZtAFMMR1mSGhUEStmsKL
Feb-28 12:58:28.751[network]         debug: Do not serve request due to rate limit peerId=16Uiu2HAmMtMosQ83JyLjAmhYMP5jT16VZtAFMMR1mSGhUEStmsKL
```

Based on these observations it's pretty clear to me that we are not requesting data correctly, see related [comment on discord](https://discord.com/channels/593655374469660673/1344697108908998797/1345019400620605460)



Avoid getting rate limited and banned by our peers

We need to improve our history pruning before we can safely communicate this new feature to operators.

See [discussion thread on discord](https://discord.com/channels/593655374469660673/1346481194061271120) for some thoughts.

Previous PR(s)
- https://github.com/ChainSafe/lodestar/pull/7427
- https://github.com/ChainSafe/lodestar/pull/7448

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity