
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

We can add support to markdown in the application form and in the display to improve the design of some texts. This is an example of a text that would be improved with markdown:

![image](https://github.com/user-attachments/assets/64ec7c23-83b4-4971-8ddc-d603fd1f0f36)


enhancement

good first issue

hacktoberfest

MACI Platform - Voting and Funding using MACI

maci-platform

TypeScript

Add support for markdown on application page

## Problem overview

Currently, if we decrease the `--state-rewind-duration` argument, it keeps the old rewind information in the database. 

## Definition of done
The code should clean up the old rewind information outside the current state rewind window.

## Implementation details
Can be tricky to solve it before solving https://github.com/FuelLabs/fuel-core/issues/2095.

Rust full node implementation of the Fuel v2 protocol.

fuel-core

Rust

Handle shrinking of the `--state-rewind-duration` argument

We should be able to run `medusa init --echidna-config <path/to/echidna.yml` to get an equivalent medusa config

https://github.com/crytic/echidna/blob/778f63c2ddfeec143e41d48064804f7432c65797/tests/solidity/basic/default.yaml
https://github.com/crytic/medusa/blob/master/fuzzing/config/config_defaults.go

medium-priority

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

medusa

add tool to convert an echidna config to medusa's format

## Overview

Some Ethereum RPC provides usually don't allow more than `10_000` events per response. Because of that, setting a big value for `--relayer-log-page-size` may lead to a stuck synchronization with L1.

We need to teach the Relayer service to adjust the page size. 

## Definition of done
When the RPC provider returns an error that the response is too big, we need to decrease the page size automatically.

If we decreased the page size, and for some period of time we didn't have any error, we should try to increase it.

The increased page size shouldn't be more than `--relayer-log-page-size`.

Handle too big relayer log page size

# Motivation
We are moving all the p0tion coordinator infrastructure to a single server application (API). This new API was built using NestJS and we are missing e2e tests (end-to-end tests).

# Details
Write e2e tests for each route (endpoint) in the different modules (auth, ceremonies, circuits, participants, storage and users). Remember to check the following:

1. There is some data (circuits, zkeys, etc) that could be used from `@actions` or duplicate it into `/api`
2. We should be able to run the whole pipeline in normal scenarios (create, contribute, finalize)



[Tutorial to setup the API Coordinator application](https://www.notion.so/pse-team/API-Coordinator-Guide-112d57e8dd7e80ea910cdd75463ec501)


The MPC suite of tools for conducting zkSNARK Phase 2 Trusted Setup ceremonies

p0tion

Create e2e tests for `/packages/api`

# Motivation
We are moving all the p0tion coordinator infrastructure to a single server application (API). This new API was built using NestJS and we are missing unit tests.

# Details
Write unit tests for each route (endpoint) in the different modules (auth, ceremonies, circuits, participants, storage and users). Remember to check the following:

1. There is some data (circuits, zkeys, etc) that could be used from `@actions` or duplicate it into `/api`
2. The functions should finalize correctly in normal scenarios
3. Some unit tests might require concurrent requests to check everything works as expected



[Tutorial to setup the API Coordinator application](https://www.notion.so/pse-team/API-Coordinator-Guide-112d57e8dd7e80ea910cdd75463ec501)

Create unit tests for `/packages/api`

# Motivation
We are moving all the p0tion coordinator infrastructure to a single server application (API). We replicated some of the functions from `@actions` to be compatible with this new API. These functions have the same name plus a suffix `API. For example:

`isCoordinator`
`isCoordinatorAPI`

We need to write tests for all these new `API` functions. We can use the existing tests as a guide but make sure to change anything to make it fit.


[Tutorial to setup the API Coordinator application](https://www.notion.so/pse-team/API-Coordinator-Guide-112d57e8dd7e80ea910cdd75463ec501)


Migrate tests from `@actions` functions to `@actions` API functions

### Description
I've noticed that my besu container is accruing a fairly large `tmp` due to `jfr` files.  I do not have `jfr` configured, should I still expect to see the `jfr` files being dumped?

**Expected behavior:** No jfr until configured.

**Actual behavior:** jfr dumps regardless

### Versions (Add all that apply)
* Software version: [`besu --version`] 24.8.0
* Java version: [`java -version`] 21.0.4
* OS Name & Version: [`cat /etc/*release`] Ubuntu 24.04

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

besu

Java

JFR always running?

### Description
As an devops, I want 2 metrics with the size of the `TransactionPool.cacheForBlobsOfTransactionsAddedToABlock` and `TransactionPool.mapOfBlobsInTransactionPool` so that I can monitor how they grow.

Export new metrics to report the size of blob cache and map

From Slack:

> I don't see a GTF opcode defined to get the witnessesCount, witnesses, outputs, outputsCount, inputs, and inputsCount for TransactionUpgrade, TransactionUpload, and TransactionBlob in the [specs](https://docs.fuel.network/docs/nightly/specs/fuel-vm/instruction-set/#gtf-get-transaction-fields) as well as transaction specific types such as subsectionIndex, subsectionsNumber, root, witnessIndex, proofSetCount, and proofSet in TransactionUpload.
>
> This is blocking https://github.com/FuelLabs/sway/pull/6500

fuel-vm

GTF support for new tx types

Regarding the implementation of the `updateMany` method as a result of issue [#117](https://github.com/privacy-scaling-explorations/zk-kit/issues/117), I wrote down an analysis of the worst-case time complexity of the method. I attach it to this description to open a discussion about it.

Using `updateMany` to update m leaves is more efficient than using the `update` method m times because it prevents updating middle nodes several times, which would happen when updating leaves with common ancestors. The worst-case time complexity of the naive approach of calling 'update' m times is O(m\*log(n)) where n is the number of leaves of the tree, while this algorithm offers a complexity of O(m\*(log(n)-log(m)) + m). This is a slight improvement, mostly when m ~ n. This makes sense because if we update a lot of leaves, most of them will have common ancestors.

The proof for this would be as follows: If we have a list of m updates in a tree of depth d ~ log(n), let k be the smallest integer such that m <= 2^k. In the worst case, the paths of the m updates will pass through m different nodes of the level k of the tree. In other words, the m leaves to update have all different ancestors up to the level k (which has 2^k nodes). In this scenario, the number of nodes of level k or higher that need to be updated is exactly m\*(d-k), and the number of nodes of level k-1 or lower to update is at least m/2 (because there are at least m/2 different ancestors of a set of m nodes) and at most 2\*m (because there are not even 2^k of nodes among all those levels, and 2^k < 2m). Therefore, the number of nodes to update is at least m\*(d-k) + m/2 and at most m\*(d-k) + 2m. This gives us that the number of nodes to update, which is the most expensive operation of the method, is O(m\*(log(n)-log(m)) + m) since k ~ log(m). If we consider the worst case of m, which is m = n, the complexity is O(n). This is mainly because each node will be modified at most once, and the total number of nodes of the tree is <= 2\*n.


documentation  📖

A monorepo of reusable libraries for zero-knowledge technologies.

zk-kit

Discuss `UpdateMany` time complexity

At the moment, all metrics definitions live in https://github.com/FuelLabs/fuel-core/tree/master/crates/metrics, and are used in modules differently.

For example, the `rocks_db` metrics, are updated as-is with no way for the operator to "opt-in" to this metric collection, shown in an example here - https://github.com/FuelLabs/fuel-core/blob/9f96573224056aa5a11233b821d34cb8ae4fad20/crates/fuel-core/src/state/rocks_db.rs#L551-L555

furthermore, out of all the modules that use metrics, only 3 modules make use of the cli argument `--metrics` to disable/enable metrics collection, which are `block_producer`, `txpool`, and `p2p`. Please note that `block_producer` has no metrics, but still takes in the metrics flag and does nothing with it, as defined here - https://github.com/FuelLabs/fuel-core/blob/df142c617730ca910ab0042a1f9615e1d7da4a7e/crates/services/producer/src/config.rs#L4-L7

and constructed here - https://github.com/FuelLabs/fuel-core/blob/2caca6145044bef4c92f6c64d8b5731545a4514a/crates/fuel-core/src/service/config.rs#L157-L159

We need to make a decision on a unified interface for the metrics logging, and ensure that each module that exports metrics makes use of the cli arg `--metrics` strictly.

chore(metrics): unify metrics architecture / clean up usage of metrics

See [Storm's talk](https://www.youtube.com/watch?v=FjTle7UxlG4) at Frontiers on what mesc is and a basic usage guide. Support for mesc was merged in https://github.com/foundry-rs/foundry/pull/8760

T-enhancement

A book on all things Foundry, available at https://book.getfoundry.sh.

book

Document MESC support

Add flag to quickly imitate the below behavior without updating the config (should also apply to property and optimization mode).
Exploration mode is useful to build a corpus.
```
      "stopOnNoTests": false,
      "assertionTesting": {
        "enabled": false,
```

help wanted

add `--explore` flag that disables all testing modes and sets `stopOnNoTests` to false

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.

> [!WARNING]
These dependencies are deprecated:

| Datasource | Name | Replacement PR? |
|------------|------|--------------|
| npm | `@nomiclabs/hardhat-etherscan` | ![Unavailable](https://img.shields.io/badge/unavailable-orange?style=flat-square) |
| npm | `@web3modal/wagmi` | ![Unavailable](https://img.shields.io/badge/unavailable-orange?style=flat-square) |

## Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

 - [ ] [chore(deps): pin dependencies](../pull/133) (`@matterlabs/zksync-contracts`, `@nuxt/eslint`, `@nuxtjs/tailwindcss`, `@playwright/test`, `@simplewebauthn/browser`, `@simplewebauthn/server`, `@simplewebauthn/types`, `@types/chai`, `@types/mocha`, `@types/node`, `actions/checkout`, `actions/setup-node`, `actions/upload-artifact`, `cbor-web`, `chai`, `dotenv`, `eventemitter3`, `mocha`, `tailwindcss`, `ts-node`, `typescript`, `viem`)
 - [ ] [chore(deps): pin dependencies](../pull/135) (`ethers`, `zksync-ethers`)
 - [ ] [chore(deps): update actions/setup-node digest to 39370e3](../pull/139)
 - [ ] [chore(deps): update trufflesecurity/trufflehog digest to b715613](../pull/154)
 - [ ] [chore(deps): update all non-major dependencies](../pull/136) (`@eslint/js`, `@nuxt/eslint`, `@nuxt/icon`, `@nx/eslint`, `@nx/js`, `@nx/nuxt`, `@nx/vite`, `@pinia/nuxt`, `@playwright/test`, `@stylistic/eslint-plugin`, `@swc/core`, `@tanstack/vue-query`, `@types/mocha`, `@types/node`, `@vueuse/core`, `@vueuse/nuxt`, `@wagmi/vue`, `cspell`, `eslint`, `globals`, `mocha`, `nx`, `pinia`, `pnpm`, `radix-vue`, `sass`, `typescript`, `typescript-eslint`, `verdaccio`, `viem`)
 - [ ] [chore(deps): update hardhat](../pull/134) (`@matterlabs/hardhat-zksync`, `@matterlabs/hardhat-zksync-deploy`, `@nomicfoundation/hardhat-verify`, `hardhat`)
 - [ ] [chore(deps): update dependency cbor-web to v10](../pull/138)
 - [ ] [chore(deps): lock file maintenance](../pull/140)
 - [ ] **Click on this checkbox to rebase all open PRs at once**

## Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

 - [ ] [chore(deps): update dependency elliptic to v6.6.0 [security]](../pull/117)
 - [ ] [chore(deps): pin dependency @openzeppelin/contracts to 4.9.6](../pull/130)
 - [ ] [chore(deps): update dependency @hexagon/base64 to v2](../pull/101)
 - [ ] [chore(deps): update dependency @simplewebauthn/browser to v11](../pull/108)
 - [ ] [chore(deps): update dependency @simplewebauthn/server to v11](../pull/109)
 - [ ] [chore(deps): update dependency @simplewebauthn/types to v11](../pull/110)
 - [ ] [chore(deps): update dependency @types/node to v22](../pull/132)
 - [ ] [chore(deps): update dependency chai to v5](../pull/59) (`chai`, `@types/chai`)
 - [ ] [chore(deps): update nrwl monorepo to v20 (major)](../pull/111) (`@nx/eslint`, `@nx/js`, `@nx/nuxt`, `@nx/vite`, `nx`)
 - [ ] [chore(deps): update openzeppelin to v5 (major)](../pull/62) (`@openzeppelin/contracts`, `@openzeppelin/contracts-upgradeable`)

## Detected dependencies

<details><summary>github-actions</summary>
<blockquote>

<details><summary>.github/workflows/ci.yml</summary>

 - `actions/checkout v4@11bd71901bbe5b1630ceea73d27597364c9af683`
 - `dutterbutter/era-test-node-action v1@36ffd2eefd46dc16e7e2a8e1715124400ec0a3ba`
 - `pnpm/action-setup v4`
 - `actions/setup-node v4@39370e3970a6d050c480ffad4ff0ed4d3fdee5af`
 - `actions/upload-artifact v4`
 - `actions/checkout v4@11bd71901bbe5b1630ceea73d27597364c9af683`
 - `dutterbutter/era-test-node-action v1@36ffd2eefd46dc16e7e2a8e1715124400ec0a3ba`
 - `pnpm/action-setup v4`
 - `actions/setup-node v4@39370e3970a6d050c480ffad4ff0ed4d3fdee5af`
 - `actions/upload-artifact v4`
 - `actions/checkout v4@11bd71901bbe5b1630ceea73d27597364c9af683`
 - `dutterbutter/era-test-node-action v1@36ffd2eefd46dc16e7e2a8e1715124400ec0a3ba`
 - `pnpm/action-setup v4`
 - `actions/setup-node v4@0a44ba7841725637a19e28fa30b79a866c81b0a6`

</details>

<details><summary>.github/workflows/deploy-auth-server.yml</summary>

 - `actions/checkout v4`
 - `pnpm/action-setup v4`
 - `actions/setup-node v4`
 - `matter-labs/action-hosting-deploy main`

</details>

<details><summary>.github/workflows/deploy-nft-quest.yml</summary>

 - `actions/checkout v4`
 - `pnpm/action-setup v4`
 - `actions/setup-node v4`
 - `matter-labs/action-hosting-deploy main`

</details>

<details><summary>.github/workflows/deploy-preview.yml</summary>

 - `actions/checkout v4`
 - `pnpm/action-setup v4`
 - `actions/setup-node v4`
 - `matter-labs/action-hosting-deploy main`

</details>

<details><summary>.github/workflows/lint.yml</summary>

 - `actions/checkout v4@11bd71901bbe5b1630ceea73d27597364c9af683`
 - `pnpm/action-setup v4`
 - `actions/setup-node v4@39370e3970a6d050c480ffad4ff0ed4d3fdee5af`

</details>

<details><summary>.github/workflows/secrets_scanner.yaml</summary>

 - `actions/checkout v4@11bd71901bbe5b1630ceea73d27597364c9af683`
 - `trufflesecurity/trufflehog 2d1dc73c9eb29d1a533fec59687df1ddcfc8a4c5`

</details>

</blockquote>
</details>

<details><summary>npm</summary>
<blockquote>

<details><summary>package.json</summary>

 - `prettier-plugin-solidity ^1.4.1`
 - `@commitlint/cli 19.5.0`
 - `@commitlint/config-conventional 19.5.0`
 - `@eslint/js 9.11.1`
 - `@nx/eslint 19.8.0`
 - `@nx/js 19.8.2`
 - `@nx/nuxt 19.8.0`
 - `@nx/vite 19.8.0`
 - `@simplewebauthn/browser ^10.0.0`
 - `@simplewebauthn/server ^10.0.1`
 - `@simplewebauthn/types ^10.0.0`
 - `@stylistic/eslint-plugin 2.8.0`
 - `@swc-node/register 1.10.9`
 - `@swc/core 1.7.26`
 - `cbor-web ^9.0.2`
 - `cspell 8.14.4`
 - `eslint 9.11.1`
 - `eslint-plugin-simple-import-sort 12.1.1`
 - `globals 15.9.0`
 - `husky 9.1.6`
 - `lint-staged 15.2.10`
 - `markdownlint-cli2 0.14.0`
 - `nuxt 3.13.2`
 - `nx 19.8.6`
 - `prettier 3.3.3`
 - `typescript 5.6.2`
 - `typescript-eslint 8.7.0`
 - `viem ^2.21.14`
 - `verdaccio 6.0.0`
 - `pnpm 9.11.0`

</details>

<details><summary>packages/auth-server/package.json</summary>

 - `@heroicons/vue ^2.1.5`
 - `@nuxt/eslint ^0.5.7`
 - `@nuxtjs/color-mode ^3.5.1`
 - `@nuxtjs/google-fonts ^3.2.0`
 - `@nuxtjs/tailwindcss ^6.12.0`
 - `@pinia/nuxt ^0.5.1`
 - `@tanstack/vue-query ^5.59.1`
 - `@vueuse/core ^11.1.0`
 - `@vueuse/nuxt ^11.1.0`
 - `@wagmi/core ^2.13.3`
 - `@wagmi/vue ^0.0.49`
 - `nuxt ^3.12.3`
 - `pinia ^2.1.7`
 - `radix-vue ^1.9.6`
 - `sass ^1.77.6`
 - `tailwind-merge ^2.5.2`
 - `viem 2.21.14`
 - `wagmi ^2.12.17`
 - `web3-avatar-vue ^1.0.4`

</details>

<details><summary>packages/bank-demo/package.json</summary>

 - `@heroicons/vue ^2.1.5`
 - `@nuxt/eslint ^0.5.7`
 - `@nuxt/icon ^1.5.5`
 - `@nuxtjs/google-fonts ^3.2.0`
 - `@nuxtjs/tailwindcss ^6.12.0`
 - `@pinia/nuxt ^0.5.5`
 - `@simplewebauthn/browser ^10.0.0`
 - `@simplewebauthn/server ^10.0.1`
 - `@simplewebauthn/types ^10.0.0`
 - `@vueuse/core ^11.0.0`
 - `@vueuse/nuxt ^11.1.0`
 - `cbor-web ^9.0.2`
 - `nuxt ^3.13.0`
 - `pinia ^2.1.7`
 - `radix-vue ^1.9.7`
 - `tailwind-merge ^2.5.3`
 - `viem ^2.21.14`

</details>

<details><summary>packages/contracts/package.json</summary>

 - `@matterlabs/zksync-contracts ^0.6.1`
 - `@nomad-xyz/excessively-safe-call ^0.0.1-rc.1`
 - `@openzeppelin/contracts 4.9.6`
 - `@openzeppelin/contracts-upgradeable 4.9`
 - `bigint-conversion ^2.4.3`
 - `cbor-web ^9.0.2`
 - `hardhat ^2.22.12`
 - `ts-node ^10.9.2`
 - `typescript ^5.5.4`
 - `viem ^2.21.6`
 - `@ethersproject/contracts 5.7.0`
 - `@ethersproject/providers 5.7.2`
 - `@hexagon/base64 1.1.28`
 - `@levischuck/tiny-cbor 0.2.2`
 - `@matterlabs/hardhat-zksync 1.2.0`
 - `@matterlabs/hardhat-zksync-deploy 1.5.0`
 - `@nomicfoundation/hardhat-chai-matchers 2.0.8`
 - `@nomicfoundation/hardhat-ethers 3.0.8`
 - `@nomicfoundation/hardhat-verify 2.0.11`
 - `@peculiar/asn1-ecc 2.3.14`
 - `@peculiar/asn1-schema 2.3.13`
 - `@typechain/ethers-v6 0.5.1`
 - `@typechain/hardhat 9.1.0`
 - `@types/chai 4.3.20`
 - `@types/elliptic 6.4.18`
 - `@types/ini 4.1.1`
 - `@types/mocha 10.0.8`
 - `@types/node 20.16.10`
 - `chai 4.5.0`
 - `dotenv 16.4.5`
 - `elliptic 6.5.7`
 - `ethers 6.13.2`
 - `ini 5.0.0`
 - `mocha 10.7.3`
 - `ts-node 10.9.2`
 - `typechain 8.3.2`
 - `typescript 5.6.2`
 - `zksync-ethers 6.13.0`

</details>

<details><summary>packages/demo-app/package.json</summary>

 - `@nuxtjs/google-fonts ^3.2.0`
 - `@pinia/nuxt ^0.5.5`
 - `@simplewebauthn/browser ^10.0.0`
 - `@simplewebauthn/server ^10.0.1`
 - `@simplewebauthn/types ^10.0.0`
 - `@wagmi/core ^2.13.3`
 - `@web3modal/wagmi ^5.1.11`
 - `cbor-web ^9.0.2`
 - `ethers ^6.13.2`
 - `nuxt ^3.12.3`
 - `viem 2.21.14`
 - `vue ^3.4.21`
 - `wagmi ^2.12.17`
 - `zksync-ethers ^6.12.1`
 - `@nuxt/eslint ^0.5.7`
 - `@nuxtjs/tailwindcss ^6.12.0`
 - `@playwright/test ^1.47.2`
 - `@types/node ^22.7.5`

</details>

<details><summary>packages/nft-quest-contracts/package.json</summary>

 - `@matterlabs/hardhat-zksync ^1.1.0`
 - `@matterlabs/zksync-contracts ^0.6.1`
 - `@openzeppelin/contracts ^4.9.2`
 - `@nomicfoundation/hardhat-verify ^2.0.9`
 - `@types/chai ^4.3.16`
 - `@types/mocha ^10.0.7`
 - `chai ^4.5.0`
 - `dotenv ^16.4.5`
 - `ethers ^6.13.2`
 - `hardhat ^2.22.7`
 - `mocha ^10.7.0`
 - `ts-node ^10.9.2`
 - `typescript ^5.5.4`
 - `zksync-ethers ^6.11.0`

</details>

<details><summary>packages/nft-quest/package.json</summary>

 - `@matterlabs/hardhat-zksync 1.2.0`
 - `@matterlabs/zksync-contracts ^0.6.1`
 - `@nomiclabs/hardhat-etherscan ^3.1.8`
 - `@nuxt/eslint ^0.6.0`
 - `@nuxtjs/color-mode ^3.5.1`
 - `@nuxtjs/google-fonts ^3.2.0`
 - `@nuxtjs/seo 2.0.0-rc.23`
 - `@openzeppelin/contracts 4.9.6`
 - `@pinia/nuxt ^0.5.5`
 - `@vueuse/core ^11.1.0`
 - `@vueuse/motion ^2.2.6`
 - `@vueuse/nuxt ^11.1.0`
 - `@wagmi/core ^2.13.3`
 - `@web3modal/wagmi ^5.1.11`
 - `clsx ^2.1.1`
 - `dotenv 16.4.5`
 - `ethers ^6.13.4`
 - `hardhat ^2.22.12`
 - `nuxt ^3.13.2`
 - `pinia ^2.1.7`
 - `radix-vue ^1.9.6`
 - `sass ^1.77.6`
 - `tailwind-merge ^2.5.2`
 - `ts-node ^10.9.2`
 - `viem 2.21.14`
 - `vue-load-image ^1.1.0`
 - `zksync-ethers ^6.14.0`
 - `@nuxtjs/tailwindcss ^6.12.0`
 - `tailwindcss ^3.4.14`
 - `@playwright/test ^1.47.2`
 - `@types/node ^22.7.5`

</details>

<details><summary>packages/sdk/package.json</summary>

 - `@peculiar/asn1-ecc ^2.3.13`
 - `@peculiar/asn1-schema ^2.3.13`
 - `abitype ^1.0.6`
 - `bigint-conversion ^2.4.3`
 - `buffer ^6.0.3`
 - `cbor-web ^9.0.2`
 - `@simplewebauthn/types ^10.0.0`
 - `@types/node ^22.1.0`
 - `eventemitter3 ^5.0.1`
 - `viem 2.21.14`
 - `@simplewebauthn/browser 10.x`
 - `@simplewebauthn/server 10.x`
 - `@wagmi/core 2.x`

</details>

</blockquote>
</details>

---

- [ ] Check this box to trigger a request for Renovate to run again on this repository

zksync-sso-clave-contracts

Solidity

Dependency Dashboard

### Description
When Besu is receiving a fork choice update it would usually have received the NewPayload containing the blocks before that. The PivotSelectorFromSafeBlock uses the fork choice to set a new pivot block, but under certain circumstances it is downloading the header for the safe block. If the ForkChoiceEvent did provide the Headers for its three blocks this would be unnecessary.

This could be done by caching the block headers from the NewPayload and adding them to the ForkChoiceEvent if they are available.

syncing

Provide Headers with ForkChoiceEvent

As of now, `bb verify` simply returns a code of `0` or `1` when verifying a proof, respectively, and prints no output. The code can be captured with `echo $?`. In my opinion, verification failure should write to `stderr` so the user is informed explicitly. Optionally, a `--quiet` parameter could be implemented, if desired.

```bash
$ bb verify -k ./target/vk -p ./target/proof 
```

Or

```
$ bb verify -k ./target/vk -p ./target/proof --quiet
```

More context: https://github.com/noir-lang/noir/issues/5805 (cc @TomAFrench)

Much appreciated, thanks.

A-ux/devex

C-bb-bin

from-community

A-error-handling

aztec-packages

`bb prove` and `bb verify` should print success & error messages

All the code examples in the documentation have the `ignore` attribute set. Some of them truly require it while others have gone stale as a result. All the code examples in the markdown files in the `docs` folder, as well as the in the in-code documentation, should be checked, have the `ignore` attribute changed to `no_run`, 'should_panic`, or removed to ensure that examples are correct. 

See https://doc.rust-lang.org/rustdoc/write-documentation/documentation-tests.html#attributes for reference. 

documentation

A compiler to convert Cairo's intermediate representation "Sierra" code to MLIR.

cairo_native

Improve doctests

Genesis root is a field in the beacon state that doesn't change. We should be able to hardcode the genesis root per network the node runs on as a configuration. Currently, to get a genesis root, we have to retrieve it from a state, which is cumbersome.

Help Wanted

Go implementation of Ethereum proof of stake

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity