
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

### Overview

Tenderly has a new product called "Virtual TestNets" they recommend Fork users migrate to:
https://docs.tenderly.co/virtual-testnets

Addtionally, most of Tenderly's Fork/TestNet functionality mimics our own `TestProviderAPI` interface, so implement that as well

### Specification

Admin interface (for TestNets)
https://docs.tenderly.co/virtual-testnets/admin-rpc

Fork admin methods:
https://docs.tenderly.co/forks#customizing-tenderly-fork

### Dependencies
n/a

category: feature

help wanted

size: 3 pieces

Tenderly network provider plugin for the Ape Framework

ape-tenderly

Python

Migrate ForkProvider to use Virtual TestNets (and subclass TestProviderAPI)

CampledPercentage currently exists in the `fuel-gas-price-algorithm` but could be useful in many others places. See (https://github.com/FuelLabs/fuel-core/pull/2733#discussion_r1973430403).

## TODO:

- [ ] Move the type to a common folder
- [ ] Use it everywhere

enhancement

good first issue

tech-debt

Rust full node implementation of the Fuel v2 protocol.

fuel-core

Rust

Use CampledPercentage across the whole codebase for percentage

### Protocol

Generic request-response protocol, to be used as base for user define protocols with custom id, request and response types serialized with protobuf

### Details

- **Type:** app layer protocol
- **Spec:**
  *user*:
  - implements custom handling logic that receives REQUEST type and returns object of RESPONSE type; 
  - defines protocol id, 
  - registers protocol
  
  *listener*:
  - accepts a connection, 
  - receives data, 
  - de-serializes it into REQUEST type, 
  - allows handling logic to process the request, 
  - sends serialized response to dialer and 
  - closes the connection
  
  *dialer*: 
  - allows to send custom request and receive response using particular `DialAsync` method override


### TODO

- [ ] Implement generic protocol, that implements `ISessionProtocol<TRequest, TResponse>` protocol;
- [ ] Add a generic extension method that receives logic handling method, protocol id; and registers protocol as `AddAppLayerProtocol` does
- [ ] Add docs
- [ ] Add tests




dotnet-libp2p

Add request-response protocol

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

We have none currently.

### Contribution Guidelines

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

type: test

effort: low

A library for secure smart contract development written in Rust

rust-contracts-stylus

[Feature]: Add unit tests to `Erc20Permit`

The function name is inconsistent with other downcasts, it needs to be updated to try_as_u64, and the old function needs to be deprecated and then later removed.

lib: std

ODHack12

🌴 Empowering everyone to build reliable and efficient smart contracts.

sway

Rename U128.as_64 to try_as_u64 and deprecate the old function

Eleel needs to be updated with Fulu/PeerDAS support.

Eleel is part of PandaOps testing infra, and updating it _prior_ to the fork is incredibly useful to keep monitoring dashboards online.

To test on devnets probably requires the completion of _this_ issue first:

- https://github.com/sigp/eleel/issues/33

eleel

Fulu/PeerDAS support


# Issue summary
The `ValidatorID` type represents a validator's public key, while `ValidatorIndex` is a lightweight uint32 alternative. The similarity in naming can cause ambiguity when referring to these types.

To improve clarity and reduce confusion, we propose renaming `ValidatorID` to `ValidatorPublicKey`. This change will make the distinction between the two types more explicit

# Note
This rename should be implemented in the `feat/parachain` branch

# Acceptance criteria
- [ ] Rename `ValidatorID` to `ValidatorPublicKey`.
- [ ] Update all relevant references in the codebase.

T-refactor

P-low

C-simple

S-subsystems-common

🕸️ Go Implementation of the Polkadot Host

gossamer

Rename `ValidatorID` to `ValidatorPublicKey` for Clarity

# Summary

Concomitant of https://github.com/ChainSafe/forest/issues/5279. While less critical, non-Common Node methods should also follow the same convention for naming.



# Completion Criteria



- [ ] Go through remaining methods (most notably Ethereum ones, and ensure naming is in _camelCase_ and that the names themselves are informative.

# Additional Links & Resources

Type: Task

forest

Change existing RPC params' names to _camelCase_

The onchain decider SNARK without the `light-test` feature now takes longer time and more RAM. In fact, the setup and proof generation could be done with 32GB of RAM in 2 minutes, as reported in https://github.com/privacy-scaling-explorations/sonobe/pull/88. However, the onchain decider now takes more than 3 minutes and eventually fails to run on my machine with 64GB of RAM:

```
> cargo test --package folding-schemes --lib --release -- folding::nova::decider_eth::tests::test_decider --exact --nocapture
    Finished `release` profile [optimized] target(s) in 0.19s
     Running unittests src/lib.rs (target/release/deps/folding_schemes-850178000889a0b5)

running 1 test
Start:   KZG10::Setup with degree 65536
··Start:   Generating powers of G
····End:     Generating powers of G ................................................87.030ms
··Start:   Generating powers of gamma * G
····End:     Generating powers of gamma * G ........................................91.847ms
··Start:   Generating negative powers of h in G2
····End:     Generating negative powers of h in G2 .................................296ns
··End:     KZG10::Setup with degree 65536 ..........................................182.324ms
Start:   Groth16::Generator
··Start:   Constraint synthesis
····End:     Constraint synthesis ..................................................17.176s
··Start:   Inlining LCs
test folding::nova::decider_eth::tests::test_decider has been running for over 60 seconds
error: test failed, to rerun pass `-p folding-schemes --lib`

Caused by:
  process didn't exit successfully: `/home/winderica/ivc/folding-schemes/target/release/deps/folding_schemes-850178000889a0b5 'folding::nova::decider_eth::tests::test_decider' --exact --nocapture` (signal: 9, SIGKILL: kill)
```

decider

sonobe

Investigate the performance regression in onchain decider

Collecting tasks from #1372:
- [ ] currently in Phase 2 in `Initialize` method we first obtain `coeffTau1`, `coeffTau2`, `coeffAlphaTau1` and `coeffBetaTau1` and then compute the updated Phase2 key from the circuit description (the big loop which iterates over constraints). This means that we first need to allocate possibly very big slices and then perform computations on the slice elements. Maybe (needs to be benchmarked) it is fine if we only allocate every slice individually and then iterate for every slice the constraints separately. For large circuits this could potentially save tens of GBs of memory we need to allocate.
- [ ] for the serialization we could additionally implement `io.UnsafeReaderFrom` and `io.BinaryDumper` interfaces. The idea is that when the sequencer stores the contributions, then it doesn't have to do expensive checks when restoring state from storage.
   * However, when we implement `io.UnsafeReaderFrom` then we need to consider that the `Verify` methods of `Phase1` and `Phase2` do not explicitly do subgroup checks and depend that the subgroups checks are done at deserialization. So keep in mind when implementing
- [ ] allow providing randomness source directly to the contribution. We currently by default use `rand.Reader` which is secure, but in some cases would wan't to use something else (for example for [some ceremonial contributions ](https://github.com/ethereum/kzg-ceremony/blob/main/special_contributions.md)).
- [ ] in `srsCommons.update` method we currently don't parallelize the computations. We could do it quite nicely as every loop depends directly on `tau`, so it should be sufficient if we only compute the starting points `tau`, `tau^k`, `tau^2k` etc.
- [ ] we should be able to provide the hash function as a parameter when computing challenge. It would allow to do cool things like SNARK proofs of ceremony contribution correctness

consolidate

perf

gnark is a fast zk-SNARK library that offers a high-level API to design circuits. The library is open source and developed under the Apache 2.0 license

gnark

perf/refac: Groth16 MPC setup improvements

performance

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

linea-specification

Use IOMF/DONE for  WCP  instead of STAMP

## Summary  
It has been suggested that instantiating an `Attestation` struct using `{}` notation could save gas. This ticket aims to validate this claim and, if confirmed, apply the optimization across the codebase.

## Objectives  
1. **Research & benchmark**  
   - Compare gas costs of instantiating an `Attestation` using `{}` notation vs. standard assignment.  
   - Provide concrete gas measurements to determine if the optimization is significant.  

2. **Apply optimization (if confirmed)**  
   - Update all instances where `Attestation` is instantiated to use `{}` notation if it proves beneficial.  
   - Ensure no unintended side effects in contract behaviour.  

## Impact  
- Potential gas savings across Verax contracts.  
- Improved efficiency for attestation-related transactions.  

Tech Design

Tech Task

Good first issue

Verax is a shared registry for storing attestations of public interest on EVM chains, designed to enhance data discoverability and consumption for dApps across the network.

linea-attestation-registry

TypeScript

[TASK] Investigate gas optimization: instantiate `Attestation` with `{}` notation

As identified in the comments of https://github.com/hyperledger/indy-plenum/pull/1709.  The workflows are failing to publish the test reports.

![Image](https://github.com/user-attachments/assets/b89ca5ee-5255-4320-a7fa-aae809efe785)

CI/CD

Ubuntu 22.04

indy-plenum

Workflows are failing to publish test reports

The [dev-setup](https://github.com/hyperledger/indy-node/tree/main/dev-setup) folder contains obsolete documentation on how to setup a local development environment.

The requirement for bare metal setup has been eliminated by implementing devContainers, which provide a repeatable and sharable stable development environment.

References to any of the bare metal setup should be replaced with references to the devContainer utilization documentation.

The server portion of a distributed ledger purpose-built for decentralized identity.

indy-node

Remove obsolete `dev-setup` documentation

https://github.com/FuelLabs/fuels-rs/pull/1595 has been merged and we can use the `context` and `with_context` methods to enrich the error messages we return from our higher level apis.

fuels-rs

add context to errors throughtout the sdk

Currently there is a lot of duplicated code in the rpc `v6`, `v7` and `v8` sub packages. We should remove duplicated code (types, functions, tests) where possible. For example, the `blockHashAndNumber` function (and associated type `BlockHashAndNumber`) has not changed between `v6`, `v7` and `v8`. This means that we can remove this function (and type) from `v7` and `v8`, and have the top level handler use the code in `v6` instead (specifically update the `MethodsV0_8` and `MethodsV0_7` functions). See this [PR](https://github.com/NethermindEth/juno/pull/2436/files) as an example. We should do this for all RPC methods. I would suggest doing the following:

1. Create a PR for each RPC method (this will make it easier to track changes, work on, and review)
2. If the RPC method has not changed between (eg) `v6`, `v7` and `v8`, then we can just re-use the `v6` code in `v7` and `v8`. This means the corresponding code (function, types, tests) should be deleted in `v7` and `v8`.
3. If the RPC function has changed, then we should not remove the function. However, if the associated type has not changed, then we should probably delete it.
4. To keep track of all the changes being made, and still to be made, to the RPC pkg, please add a new bullet point here and link the associated PR.

- [x] [starknet_chainId](https://github.com/NethermindEth/juno/pull/2446)
- [x] [starknet_blockNumber](https://github.com/NethermindEth/juno/pull/2445)
- [x] [starknet_blockHashAndNumber](https://github.com/NethermindEth/juno/pull/2436/files)
- [x] [BlockStatus enum](https://github.com/NethermindEth/juno/pull/2447) (Not really an RPC endpoint but useful for other endpoints, such as starknet_getBlockWithTxHashes)
- [x] [Header struct](https://github.com/NethermindEth/juno/pull/2448) (Not really an RPC endpoint but useful for other endpoints, such as starknet_getBlockWithTxHashes)
- [x] [starknet_getBlockWithTxHashes](https://github.com/NethermindEth/juno/pull/2449)
- [x] [Refactor type Transaction struct](https://github.com/NethermindEth/juno/issues/2458) (Not really an RPC endpoint but useful for other endpoints)
- [x] [starknet_syncing](https://github.com/NethermindEth/juno/pull/2459)
- [x] [starknet_getNonce](https://github.com/NethermindEth/juno/pull/2463)
- [x] [starknet_getClassAt](https://github.com/NethermindEth/juno/pull/2465)
- [x] [starknet_getClassHashAt](https://github.com/NethermindEth/juno/pull/2466)
- [x] [starknet_getClass](https://github.com/NethermindEth/juno/pull/2467)
- [x] [starknet_getEvents](https://github.com/NethermindEth/juno/pull/2469)
- [ ] [juno_version](https://github.com/NethermindEth/juno/pull/2471), [Attempt 2](https://github.com/NethermindEth/juno/pull/2793)
- [x] [starknet_getStorageProof](https://github.com/NethermindEth/juno/pull/2474)
- [x] [starknet_getTransactionByHash](https://github.com/NethermindEth/juno/pull/2486)
- [x] [starknet_getTransactionCount](https://github.com/NethermindEth/juno/pull/2488)
- [x] [starknet_getStateUpdate](https://github.com/NethermindEth/juno/pull/2490)
- [x] [starknet_call](https://github.com/NethermindEth/juno/pull/2491)
- [x] [starknet_estimateMessageFee](https://github.com/NethermindEth/juno/pull/2496)
- [x] [juno/starknet_unsubscribe](https://github.com/NethermindEth/juno/pull/2509)
- [x] [starknet_add...Transaction](https://github.com/NethermindEth/juno/pull/2534)
- [x] [starknet_traceTransaction](https://github.com/NethermindEth/juno/pull/2545)

## Remaining endpoints to check

- ~~starknet_getBlockWithReceipts~~
- ~~starknet_getCompiledCasm~~
- ~~starknet_specVersion~~
- ~~starknet_subscribeEvents~~
- ~~starknet_subscribeTransactionStatus~~
- ~~starknet_getBlockWithTxs~~
- ~~starknet_getTransactionByHash~~
- ~~starknet_getTransactionReceipt~~
- ~~starknet_getBlockTransactionCount~~
- ~~starknet_getTransactionByBlockIdAndIndex~~
- ~~starknet_getStateUpdate~~
- ~~starknet_addInvokeTransaction~~
- ~~starknet_addDeployAccountTransaction~~
- ~~starknet_addDeclareTransaction~~
- ~~starknet_getTransactionStatus~~
- ~~starknet_call~~
- ~~starknet_estimateFee~~
- ~~starknet_estimateMessageFee~~
- ~~starknet_traceTransaction~~ --> decided not to go for refactoring after all. Not exactly straightfoward.
- ~~starknet_simulateTransactions~~
- ~~starknet_traceBlockTransactions~~
- ~~juno_subscribeNewHeads / starknet_subscribeNewHeads~~
- ~~juno_unsubscribe / starknet_unsubscribe~~


Refactor

juno

Cleanup rpc pkg

Similarly to TraceRpcModule and EthRpcModule, DebugRpcModule should return a clear error message when the state is pruned.

Here is an example from TraceRpcModule: [TraceRpcModule.cs#L88](https://github.com/NethermindEth/nethermind/blob/master/src/Nethermind/Nethermind.JsonRpc/Modules/Trace/TraceRpcModule.cs#L88).

We need to review all DebugRpcModule endpoints and add proper error handling where necessary.

This is what will happen in debug_traceTransaction:
`{'jsonrpc': '2.0', 'error': {'code': -32603, 'message': 'Internal error', 'data': 'System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.\n ---> Nethermind.Trie.MissingTrieNodeException: Node 0x671687b7c114dab66c76046659f0daf9a85cc314295dd809883296dd9be2cf48 is missing from the DB\n ---> Nethermind.Trie.TrieNodeException: Failed to load root hash 0x671687b7c114dab66c76046659f0daf9a85cc314295dd809883296dd9be2cf48 while loading key 2b9cfb0759b99df35efc8ee729cb85b86bf83a0c0a7df72c6cb4d92494c36042.\nNode 0x671687b7c114dab66c76046659f0daf9a85cc314295dd809883296dd9be2cf48 is missing from the DB\n   at Nethermind.Trie.Pruning.TrieStore.LoadRlp(Hash256 address, TreePath& path, Hash256 keccak, INodeStorage nodeStorage, ReadFlags readFlags) in /src/Nethermind/Nethermind.Trie/Pruning/TrieStore.cs:line 387\n   at Nethermind.Trie.Pruning.ReadOnlyTrieStore.LoadRlp(Hash256 address, TreePath& treePath, Hash256 hash, ReadFlags flags) in /src/Nethermind/Nethermind.Trie/Pruning/ReadOnlyTrieStore.cs:line 22\n   at Nethermind.Trie.Pruning.ReadOnlyTrieStore.Nethermind.Trie.Pruning.ITrieStoreInternal.LoadRlp(Hash256 address, TreePath& path, Hash256 hash, ReadFlags flags)\n   at Nethermind.Trie.Pruning.OverlayTrieStore.LoadRlp(Hash256 address, TreePath& path, Hash256 hash, ReadFlags flags) in /src/Nethermind/Nethermind.Trie/Pruning/OverlayTrieStore.cs:line 27\n   at Nethermind.Trie.Pruning.ScopedTrieStore.LoadRlp(TreePath& path, Hash256 hash, ReadFlags flags) in /src/Nethermind/Nethermind.Trie/Pruning/ScopedTrieStore.cs:line 15\n   at Nethermind.Trie.Pruning.ScopedTrieStore.Nethermind.Trie.Pruning.ITrieNodeResolver.LoadRlp(TreePath& path, Hash256 hash, ReadFlags flags)\n   at Nethermind.Trie.TrieNode.ResolveUnknownNode(ITrieNodeResolver tree, TreePath& path, ReadFlags readFlags, ICappedArrayPool bufferPool) in /src/Nethermind/Nethermind.Trie/TrieNode.cs:line 398\n   at Nethermind.Trie.PatriciaTree.ResolveNode(TrieNode node, TraverseContext& traverseContext, TreePath& path) in /src/Nethermind/Nethermind.Trie/PatriciaTree.cs:line 573\n   --- End of inner exception stack trace ---\n   at Nethermind.Trie.PatriciaTree.ResolveNode(TrieNode node, TraverseContext& traverseContext, TreePath& path) in /src/Nethermind/Nethermind.Trie/PatriciaTree.cs:line 581\n   at Nethermind.Trie.PatriciaTree.Run(TreePath& updatePathTreePath, CappedArray`1& updateValue, Span`1 updatePath, Boolean isUpdate, Boolean ignoreMissingDelete, Hash256 startRootHash, Boolean isNodeRead) in /src/Nethermind/Nethermind.Trie/PatriciaTree.cs:line 538\n   at Nethermind.Trie.PatriciaTree.Get(ReadOnlySpan`1 rawKey, Hash256 rootHash) in /src/Nethermind/Nethermind.Trie/PatriciaTree.cs:line 334\n   at Nethermind.State.StateTree.Get(Address address, Hash256 rootHash) in /src/Nethermind/Nethermind.State/StateTree.cs:line 45\n   at Nethermind.State.StateProvider.<.ctor>b__49_0(AddressAsKey address) in /src/Nethermind/Nethermind.State/StateProvider.cs:line 646\n   at Nethermind.State.StateProvider.GetStatePopulatePrewarmCache(AddressAsKey addressAsKey) in /src/Nethermind/Nethermind.State/StateProvider.cs:line 675\n   at Nethermind.State.StateProvider.GetState(Address address) in /src/Nethermind/Nethermind.State/StateProvider.cs:line 661\n   at Nethermind.State.StateProvider.GetAndAddToCache(Address address) in /src/Nethermind/Nethermind.State/StateProvider.cs:line 711\n   at Nethermind.State.StateProvider.AccountExists(Address address) in /src/Nethermind/Nethermind.State/StateProvider.cs:line 91\n   at Nethermind.State.WorldState.AccountExists(Address address) in /src/Nethermind/Nethermind.State/WorldState.cs:line 216\n   at Nethermind.Blockchain.Blocks.BlockhashStore.ApplyBlockhashStateChanges(BlockHeader blockHeader) in /src/Nethermind/Nethermind.Blockchain/Blocks/BlockhashStore.cs:line 28\n   at Nethermind.Consensus.Processing.BlockProcessor.ProcessBlock(Block block, IBlockTracer blockTracer, ProcessingOptions options) in /src/Nethermind/Nethermind.Consensus/Processing/BlockProcessor.cs:line 328\n   at`

A robust execution client for Ethereum node operators.

nethermind

HasStateForBlock in debug module

Something to note, we apply the same validation on the api as we do on gossip
https://github.com/ChainSafe/lodestar/blob/06831cfc79ab667f4ce4ee897320ce3f4a495854/packages/beacon-node/src/chain/validation/voluntaryExit.ts#L7

this is due to the fact that we publish it to the network immediately
https://github.com/ChainSafe/lodestar/blob/06831cfc79ab667f4ce4ee897320ce3f4a495854/packages/beacon-node/src/api/impl/beacon/pool/index.ts#L185

but something we could consider is that we separate out some transient checks which would become valid eventually, there are like 3-4 of them and post-electra we add another one which checks that there are no pending withdrawals. Meaning we would keep the volunary exit in the cache and publish it to the network only after those conditions are met.

As this has worked like this since phase0 it seems like no issue but something to consider to improve UX, on the other hand I can also see that accepting the voluntary exit but not publishing it immediately might be confusing as well.

_Originally posted by @nflaig in https://github.com/ChainSafe/lodestar/issues/7379#issuecomment-2602912610_
            

scope-ux

meta-feature-request

🌟 Ethereum Consensus client for the Zig and TypeScript ecosystem

lodestar

Delayed broadcasting of voluntary exits

**Describe the solution you'd like**
Add .NET app to Universal Connectivity app set at https://github.com/libp2p/universal-connectivity that:
- supports TCP
- has optional QUIC support
- has console UI

showcase

Add .NET implementation to Universal Connectivity app

Based on @ivokub's feedback on https://github.com/Consensys/gnark/pull/1372

A custom hash function (i.e. option to use MiMC, Poseidon and the like) can enable in-SNARK verification of setup ceremonies.
A custom randomness source can make debugging easier.

P3: Low

gnark-crypto provides elliptic curve and pairing-based cryptography on BN, BLS12, BLS24 and BW6 curves. It also provides various algorithms (algebra, crypto) of particular interest to zero knowledge proof systems.

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity