
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

Seaport and other platforms allow "batch transfers" of NFTs and other assets. This is a potentially harmful action that we should warn on. We should probably create a new class of warnings "Batch Transfers" that checks whether these kinds of signatures or transactions are sent.

We should also investigate which big platforms exist that have this functionality besides Seaport.

good first issue

🛡 Protect yourself from crypto scams online

browser-extension

TypeScript

Add warnings for Batch Transfers

To be precise, I think you can add a func like api.Printf("this is my var %fv. ", circuit.x), and hope it have the same performance with fmt.Printf()

```go
func (circuit *Circuit) Define(api frontend.API) error{
    api.Printf("this is my var %fv. ", circuit.x)
}
go
cmd output: this is my var 2

new feature

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

feat: add format specifiers for `api.Println` or implement `api.Printf`

### Describe the issue:

If a structure contains custom types, the read_storage tool cannot determine the storage layout of that struct variable.


### Code example to reproduce the issue:

#### test.py
```
from slither.tools.read_storage import SlitherReadStorage
srs = SlitherReadStorage([c], 20)
srs.get_all_storage_variables()
srs.get_storage_layout()
```
#### error.sol
```solidity
type MyUint64 is uint64;
contract C {
    struct S {
        MyUint64 y;
        MyUint64 z;
    }
    S s;
}
```
#### correct.sol
```solidity
contract C {
    struct S {
        unit64 y;
        unit64 z;
    }
    S s;
}
```

### Version:

0.10.3

### Relevant log output:

```shell
When perform test.py for program of error.sol, there is an error

  File "/mnt/sdd1/sbw/slither/slither/tools/read_storage/read_storage.py", line 837, in _all_struct_slots
    info = self.get_storage_slot(
  File "/mnt/sdd1/sbw/slither/slither/tools/read_storage/read_storage.py", line 256, in get_storage_slot
    info, type_to, slot, size, offset = self._find_struct_var_slot(elems, slot, struct_var)
  File "/mnt/sdd1/sbw/slither/slither/tools/read_storage/read_storage.py", line 597, in _find_struct_var_slot
    return info, type_to, slot_as_bytes, size, offset
UnboundLocalError: local variable 'size' referenced before assignment
```
```


slither

Python

”read_storage cannot determine the storage layout of custom type variables within a struct.

I think there is an interesting issue with respect to validation of field elements.  Specifically, whenever we see a field element which fits within 256bits we are happy.  But, in fact, it should be within 254 bits.  It would be useful to sanity check this.

go-corset

Validation for Field Elements

### Problem description

As the size of spec test files increases in every release (from ~670MB for v1.4.0 to ~780MB for v1.5.0-alpha.3), it takes 20+ minutes for me to download all files.

Currently downloading spec test provides minimal log output on the download progress. Only at the beginning of download, and when the download is finished, which could be 10-20 minutes apart. It would be great to provide more info (eg. a progress bar, download time remaining) during download such that users/devs know what to expect. Here is a sample log of the current behaviour:
```
NC@Chainsafe beacon-node % yarn download-spec-tests
yarn run v1.22.22
$ node --loader=ts-node/esm test/spec/downloadTests.ts
outputDir = /Users/NC/Documents/lodestar/packages/beacon-node/spec-tests
Downloading new version v1.4.0-beta.6
Cleaning existing version v1.5.0-alpha.3 at /Users/NC/Documents/lodestar/packages/beacon-node/spec-tests
outputDir = /Users/NC/Documents/lodestar/packages/beacon-node/spec-tests-bls
version v0.1.1 already downloaded
Downloading https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/general.tar.gz - 15889101 bytes
Downloading https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/mainnet.tar.gz - 421709376 bytes
Downloading https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/minimal.tar.gz - 239776755 bytes
Downloaded  https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/general.tar.gz
Download attempt 2 for https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/mainnet.tar.gz failed: aborted
Downloading https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/mainnet.tar.gz - 421709376 bytes
Downloaded  https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/mainnet.tar.gz
Download attempt 2 for https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/minimal.tar.gz failed: aborted
Downloading https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/minimal.tar.gz - 239776755 bytes
Download attempt 3 for https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/minimal.tar.gz failed: aborted
Downloading https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/minimal.tar.gz - 239776755 bytes
Downloaded https://github.com/ethereum/consensus-spec-tests/releases/download/v1.4.0-beta.6/minimal.tar.gz - 239776755 bytes
```

Moreover, partially downloaded files are deleted when reattempting to download spec test. This is an issue when having slow and unstable internet, a user may already have downloaded `general` and `minimal` spec tests, but internet drops when downloading `mainnet`. When he runs `yarn download-spec-tests` again, `general` and `minimal` are deleted and everything is being re-downloaded.

### Solution description

- Provide more helpful log output on the progress of spec test download
- Only download missing spec tests

### Additional context

_No response_

scope-testing

meta-feature-request

🌟 Ethereum Consensus client for the Zig and TypeScript ecosystem

lodestar

Improve experience of `download-spec-tests`

Rather than using .env variables, we should be getting these details from the EASGatekeeper contract - use the `getEASGatekeeperData` function implemented here: https://github.com/privacy-scaling-explorations/maci/pull/1701

MACI Platform - Voting and Funding using MACI

maci-platform

Get approval schema and attester from EASGatekeeper

See https://github.com/FuelLabs/fuel-vm/pull/780#discussion_r1676371537

fuel-vm

Rust

Refactor check_unique_rules to be more modular

### Is your feature request related to a problem? Please describe.

Our markdown page template includes "edit" button leading users to github to edit the content. Currently we do not track how many people click on this. We would like to have more information about this component.

See examples where this button is:
https://ethereum.org/en/guides/
https://ethereum.org/en/guides/how-to-create-an-ethereum-account/
https://ethereum.org/en/web3/
https://ethereum.org/en/developers/docs/

This is how the button looks like:
<img width="232" alt="Screenshot 2024-07-18 at 17 44 02" src="https://github.com/user-attachments/assets/f60aa060-0c24-4c54-a34b-e4508988a94c">


### Describe the solution you'd like

Implement custom event tracking code:

Event Category
edit_page

Event Action
gh_edit_click

Event Name
{page url}


### Describe alternatives you've considered

NA

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
- [X] No

feature ✨

help wanted

Status: Stale

dev required

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

ethereum-org-website

Markdown

include event tracking for "edit" button globally 

## Description

There is an implementation of the IMT data structure in TS/JS: https://github.com/privacy-scaling-explorations/zk-kit/tree/main/packages/imt

There is also an implementation of the IMT data structure in Rust: https://github.com/privacy-scaling-explorations/zk-kit.rust/tree/main/crates/imt

The idea of this issue is to compare the performance of IMT written in TS/JS and Rust in Node.js and browser.

## Resources

Guide to convert the Rust implementation to wasm: https://rustwasm.github.io/docs/book/

Library to create benchmarks in Node.js and browser: https://github.com/tinylibs/tinybench




documentation  📖

A monorepo of reusable libraries for zero-knowledge technologies.

zk-kit

Compare performance of IMT written in JS and Rust in Node.js and browser

### Is your feature request related to a problem? Please describe.

https://ethereum.org/en/developers/docs/apis/json-rpc/

Our JSON-RPC page recently added a "playground" link above all the endpoints (<https://ethereum-json-rpc.com/>)...  But, while a user is scrolling through or reading about a specific endpoint, there is no convenient way to jump to this playground to try out the endpoint.

### Describe the solution you'd like

Proposing we add a link to each endpoint that takes user straight to that endpoint in the playground... ie: `eth_accounts`... <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_accounts> could have a link such as `[Try this endpoint](https://ethereum-json-rpc.com/?method=eth_accounts)`

### Describe alternatives you've considered

- Build out our own playground (high effort, lower impact given alternative)
- Don't do anything (limits UX by lacking convenient ways to try out an endpoint)

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
- [X] No

Add JSON-RPC endpoint playground links

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

cairo-contracts

Check indexed keys in event assertions (snforge migration)

Currently we just add constraints and return new elements when we normalize field elements and reduce bigfield elements. This means that a call to the same field element twice to normalize it can produce 2 sets of identical constraints. Ideally, we would cache the result and just return it

optimization

barretenberg

Caching field normalize and bigfield self_reduce

### Problem
`waku node metrics` values are initialisated to an (seemingly) arbitrarily high value.

### To reproduce
@stubbsta were using `waku-simulator` when we noticed this, so I'll use that for steps:
1. Clone the waku-simulator repo https://github.com/waku-org/waku-simulator.
2. Create an `.env` with the contents detailed below.
3. `source .env`
4. Wait for a while. I believe log messages are printed every 10 minutes. So I recommend waiting at least 20m to get two rounds of logs.
5. When a significant amount of time has passed, run `docker logs waku-simulator_nwaku_1 | grep Total`.

#### `.env`
```.env
export NWAKU_IMAGE=harbor.status.im/wakuorg/nwaku:v0.30.1
export NUM_NWAKU_NODES=30
export TRAFFIC_DELAY_SECONDS=0
export MSG_SIZE_KBYTES=3
export PRIVATE_KEY=0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80
export ETH_FROM=0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266
# RLNv2 limits
export RLN_RELAY_MSG_LIMIT=200
export RLN_RELAY_EPOCH_SEC=60
MAX_MESSAGE_LIMIT=300
```

### Expected behavior
`waku node metrics` values are "realistic".

### Screenshots/logs
```
INF 2024-07-12 17:54:43.840+00:00 Total connections initiated                topics="waku node metrics" tid=1 file=waku_metrics.nim:43 count=1720806373.0
INF 2024-07-12 17:54:43.841+00:00 Total messages                             topics="waku node metrics" tid=1 file=waku_metrics.nim:44 count=1720808710.0
INF 2024-07-12 17:54:43.841+00:00 Total store peers                          topics="waku node metrics" tid=1 file=waku_metrics.nim:45 count=1720806279.0
INF 2024-07-12 17:54:43.841+00:00 Total peer exchange peers                  topics="waku node metrics" tid=1 file=waku_metrics.nim:46 count=1720806279.0
INF 2024-07-12 17:54:43.841+00:00 Total lightpush peers                      topics="waku node metrics" tid=1 file=waku_metrics.nim:47 count=1720806279.0
INF 2024-07-12 17:54:43.841+00:00 Total filter peers                         topics="waku node metrics" tid=1 file=waku_metrics.nim:48 count=1720806279.0
INF 2024-07-12 17:54:43.841+00:00 Total errors                               topics="waku node metrics" tid=1 file=waku_metrics.nim:49 count=0.0
INF 2024-07-12 17:54:43.841+00:00 Total messages                             topics="waku rln_relay" tid=1 file=protocol_metrics.nim:100 count=1720808703.0
INF 2024-07-12 17:54:43.841+00:00 Total spam messages                        topics="waku rln_relay" tid=1 file=protocol_metrics.nim:101 count=1720806279.0
INF 2024-07-12 17:54:43.841+00:00 Total invalid messages                     topics="waku rln_relay" tid=1 file=protocol_metrics.nim:102 count=0.0
INF 2024-07-12 17:54:43.841+00:00 Total valid messages                       topics="waku rln_relay" tid=1 file=protocol_metrics.nim:103 count=1720825668.0
INF 2024-07-12 17:54:43.841+00:00 Total errors                               topics="waku rln_relay" tid=1 file=protocol_metrics.nim:104 count=0.0
INF 2024-07-12 17:54:43.841+00:00 Total proofs verified                      topics="waku rln_relay" tid=1 file=protocol_metrics.nim:105 count=1720808703.0
INF 2024-07-12 18:04:43.841+00:00 Total connections initiated                topics="waku node metrics" tid=1 file=waku_metrics.nim:43 count=0.0
INF 2024-07-12 18:04:43.841+00:00 Total messages                             topics="waku node metrics" tid=1 file=waku_metrics.nim:44 count=1720814554.0
INF 2024-07-12 18:04:43.841+00:00 Total store peers                          topics="waku node metrics" tid=1 file=waku_metrics.nim:45 count=1720806279.0
INF 2024-07-12 18:04:43.841+00:00 Total peer exchange peers                  topics="waku node metrics" tid=1 file=waku_metrics.nim:46 count=1720806279.0
INF 2024-07-12 18:04:43.841+00:00 Total lightpush peers                      topics="waku node metrics" tid=1 file=waku_metrics.nim:47 count=1720806279.0
INF 2024-07-12 18:04:43.841+00:00 Total filter peers                         topics="waku node metrics" tid=1 file=waku_metrics.nim:48 count=1720806279.0
INF 2024-07-12 18:04:43.841+00:00 Total errors                               topics="waku node metrics" tid=1 file=waku_metrics.nim:49 count=0.0
INF 2024-07-12 18:04:43.841+00:00 Total messages                             topics="waku rln_relay" tid=1 file=protocol_metrics.nim:100 count=5844.0
INF 2024-07-12 18:04:43.841+00:00 Total spam messages                        topics="waku rln_relay" tid=1 file=protocol_metrics.nim:101 count=0.0
INF 2024-07-12 18:04:43.841+00:00 Total invalid messages                     topics="waku rln_relay" tid=1 file=protocol_metrics.nim:102 count=0.0
INF 2024-07-12 18:04:43.841+00:00 Total valid messages                       topics="waku rln_relay" tid=1 file=protocol_metrics.nim:103 count=46752.0
INF 2024-07-12 18:04:43.841+00:00 Total errors                               topics="waku rln_relay" tid=1 file=protocol_metrics.nim:104 count=0.0
INF 2024-07-12 18:04:43.841+00:00 Total proofs verified                      topics="waku rln_relay" tid=1 file=protocol_metrics.nim:105 count=5844.0
INF 2024-07-12 18:14:43.841+00:00 Total connections initiated                topics="waku node metrics" tid=1 file=waku_metrics.nim:43 count=1.0
INF 2024-07-12 18:14:43.841+00:00 Total messages                             topics="waku node metrics" tid=1 file=waku_metrics.nim:44 count=1720820401.0
INF 2024-07-12 18:14:43.841+00:00 Total store peers                          topics="waku node metrics" tid=1 file=waku_metrics.nim:45 count=1720806279.0
INF 2024-07-12 18:14:43.841+00:00 Total peer exchange peers                  topics="waku node metrics" tid=1 file=waku_metrics.nim:46 count=1720806279.0
INF 2024-07-12 18:14:43.841+00:00 Total lightpush peers                      topics="waku node metrics" tid=1 file=waku_metrics.nim:47 count=1720806279.0
INF 2024-07-12 18:14:43.841+00:00 Total filter peers                         topics="waku node metrics" tid=1 file=waku_metrics.nim:48 count=1720806279.0
INF 2024-07-12 18:14:43.841+00:00 Total errors                               topics="waku node metrics" tid=1 file=waku_metrics.nim:49 count=0.0
INF 2024-07-12 18:14:43.841+00:00 Total messages                             topics="waku rln_relay" tid=1 file=protocol_metrics.nim:100 count=5847.0
INF 2024-07-12 18:14:43.841+00:00 Total spam messages                        topics="waku rln_relay" tid=1 file=protocol_metrics.nim:101 count=0.0
INF 2024-07-12 18:14:43.841+00:00 Total invalid messages                     topics="waku rln_relay" tid=1 file=protocol_metrics.nim:102 count=0.0
INF 2024-07-12 18:14:43.841+00:00 Total valid messages                       topics="waku rln_relay" tid=1 file=protocol_metrics.nim:103 count=46776.0
INF 2024-07-12 18:14:43.841+00:00 Total errors                               topics="waku rln_relay" tid=1 file=protocol_metrics.nim:104 count=0.0
INF 2024-07-12 18:14:43.841+00:00 Total proofs verified                      topics="waku rln_relay" tid=1 file=protocol_metrics.nim:105 count=5847.0
INF 2024-07-12 18:24:43.842+00:00 Total connections initiated                topics="waku node metrics" tid=1 file=waku_metrics.nim:43 count=1.0
INF 2024-07-12 18:24:43.842+00:00 Total messages                             topics="waku node metrics" tid=1 file=waku_metrics.nim:44 count=1720826251.0
INF 2024-07-12 18:24:43.842+00:00 Total store peers                          topics="waku node metrics" tid=1 file=waku_metrics.nim:45 count=1720806279.0
INF 2024-07-12 18:24:43.842+00:00 Total peer exchange peers                  topics="waku node metrics" tid=1 file=waku_metrics.nim:46 count=1720806279.0
INF 2024-07-12 18:24:43.842+00:00 Total lightpush peers                      topics="waku node metrics" tid=1 file=waku_metrics.nim:47 count=1720806279.0
INF 2024-07-12 18:24:43.842+00:00 Total filter peers                         topics="waku node metrics" tid=1 file=waku_metrics.nim:48 count=1720806279.0
INF 2024-07-12 18:24:43.842+00:00 Total errors                               topics="waku node metrics" tid=1 file=waku_metrics.nim:49 count=0.0
INF 2024-07-12 18:24:43.842+00:00 Total messages                             topics="waku rln_relay" tid=1 file=protocol_metrics.nim:100 count=5850.0
INF 2024-07-12 18:24:43.842+00:00 Total spam messages                        topics="waku rln_relay" tid=1 file=protocol_metrics.nim:101 count=0.0
INF 2024-07-12 18:24:43.842+00:00 Total invalid messages                     topics="waku rln_relay" tid=1 file=protocol_metrics.nim:102 count=0.0
INF 2024-07-12 18:24:43.842+00:00 Total valid messages                       topics="waku rln_relay" tid=1 file=protocol_metrics.nim:103 count=46800.0
INF 2024-07-12 18:24:43.842+00:00 Total errors                               topics="waku rln_relay" tid=1 file=protocol_metrics.nim:104 count=0.0
INF 2024-07-12 18:24:43.842+00:00 Total proofs verified                      topics="waku rln_relay" tid=1 file=protocol_metrics.nim:105 count=5850.0
INF 2024-07-12 18:34:43.842+00:00 Total connections initiated                topics="waku node metrics" tid=1 file=waku_metrics.nim:43 count=1.0
INF 2024-07-12 18:34:43.842+00:00 Total messages                             topics="waku node metrics" tid=1 file=waku_metrics.nim:44 count=1720832102.0
INF 2024-07-12 18:34:43.842+00:00 Total store peers                          topics="waku node metrics" tid=1 file=waku_metrics.nim:45 count=1720806279.0
INF 2024-07-12 18:34:43.842+00:00 Total peer exchange peers                  topics="waku node metrics" tid=1 file=waku_metrics.nim:46 count=1720806279.0
INF 2024-07-12 18:34:43.842+00:00 Total lightpush peers                      topics="waku node metrics" tid=1 file=waku_metrics.nim:47 count=1720806279.0
INF 2024-07-12 18:34:43.843+00:00 Total filter peers                         topics="waku node metrics" tid=1 file=waku_metrics.nim:48 count=1720806279.0
INF 2024-07-12 18:34:43.843+00:00 Total errors                               topics="waku node metrics" tid=1 file=waku_metrics.nim:49 count=0.0
INF 2024-07-12 18:34:43.843+00:00 Total messages                             topics="waku rln_relay" tid=1 file=protocol_metrics.nim:100 count=5851.0
INF 2024-07-12 18:34:43.843+00:00 Total spam messages                        topics="waku rln_relay" tid=1 file=protocol_metrics.nim:101 count=0.0
INF 2024-07-12 18:34:43.843+00:00 Total invalid messages                     topics="waku rln_relay" tid=1 file=protocol_metrics.nim:102 count=0.0
INF 2024-07-12 18:34:43.843+00:00 Total valid messages                       topics="waku rln_relay" tid=1 file=protocol_metrics.nim:103 count=46808.0
INF 2024-07-12 18:34:43.843+00:00 Total errors                               topics="waku rln_relay" tid=1 file=protocol_metrics.nim:104 count=0.0
INF 2024-07-12 18:34:43.843+00:00 Total proofs verified                      topics="waku rln_relay" tid=1 file=protocol_metrics.nim:105 count=5851.0
INF 2024-07-12 18:44:43.843+00:00 Total connections initiated                topics="waku node metrics" tid=1 file=waku_metrics.nim:43 count=0.0
INF 2024-07-12 18:44:43.843+00:00 Total messages                             topics="waku node metrics" tid=1 file=waku_metrics.nim:44 count=1720837954.0
INF 2024-07-12 18:44:43.843+00:00 Total store peers                          topics="waku node metrics" tid=1 file=waku_metrics.nim:45 count=1720806279.0
INF 2024-07-12 18:44:43.843+00:00 Total peer exchange peers                  topics="waku node metrics" tid=1 file=waku_metrics.nim:46 count=1720806279.0
INF 2024-07-12 18:44:43.843+00:00 Total lightpush peers                      topics="waku node metrics" tid=1 file=waku_metrics.nim:47 count=1720806279.0
INF 2024-07-12 18:44:43.843+00:00 Total filter peers                         topics="waku node metrics" tid=1 file=waku_metrics.nim:48 count=1720806279.0
INF 2024-07-12 18:44:43.843+00:00 Total errors                               topics="waku node metrics" tid=1 file=waku_metrics.nim:49 count=0.0
INF 2024-07-12 18:44:43.843+00:00 Total messages                             topics="waku rln_relay" tid=1 file=protocol_metrics.nim:100 count=5852.0
INF 2024-07-12 18:44:43.843+00:00 Total spam messages                        topics="waku rln_relay" tid=1 file=protocol_metrics.nim:101 count=0.0
INF 2024-07-12 18:44:43.843+00:00 Total invalid messages                     topics="waku rln_relay" tid=1 file=protocol_metrics.nim:102 count=0.0
INF 2024-07-12 18:44:43.843+00:00 Total valid messages                       topics="waku rln_relay" tid=1 file=protocol_metrics.nim:103 count=46816.0
INF 2024-07-12 18:44:43.843+00:00 Total errors                               topics="waku rln_relay" tid=1 file=protocol_metrics.nim:104 count=0.0
INF 2024-07-12 18:44:43.843+00:00 Total proofs verified                      topics="waku rln_relay" tid=1 file=protocol_metrics.nim:105 count=5852.0
```

### nwaku version/commit hash
- waku-simulator hash: 16e0e2c

effort/days

nwaku

bug: (most) waku node metrics weird initial value

**Describe the package you'd like**

ZK-Kit already provides a [package](https://github.com/privacy-scaling-explorations/zk-kit/tree/main/packages/eddsa-poseidon) to generate EdDSA keys that uses [Poseidon](https://www.poseidon-hash.info/) hashes and is based on the [BabyJubjub elliptic curve](https://eips.ethereum.org/EIPS/eip-2494). The Rust crate should be compatible with the JS version.

Possible dependencies:
* https://github.com/arnaucube/babyjubjub-rs
* https://github.com/arnaucube/poseidon-rs

It is worth checking whether an implementation in Rust already exists.



feature :rocket:

A monorepo of reusable crates for zero-knowledge technologies.

zk-kit.rust

Create a crate for EdDSA Poseidon (BabyJubjub curve)

metrics

Elixir implementation of an Ethereum consensus client, which offers high reliance & fault tolerance

lambda_ethereum_consensus

Elixir

Separate networking metrics from the rest

The idea is to increase coverage of API with unit-tests where it could be done, so the code will be more reliable 

enhancement

testing

zksync-remix-plugin

Cover API with rust unit tests

priority-medium

indexer

multiplier

Add `WRITES_VALUE` reference between function arguments and function parameters

Hi. I am using version 0.1.3 and seems that there is a bug when `hevm.prank` is used, as after transferring ETH from the account pranked, its balance does not change. The following test succeeds with Echidna and Foundry, but fails with Medusa.

```solidity
event LogBalanceChange(uint256 balanceChange);

contract Tester {
    function sendETH() public payable {
        uint256 balanceBefore = msg.sender.balance;
        assert(balanceBefore > 10000);

        address payable recipient = msg.sender == address(0x30000) 
            ? payable(address(0x10000)) : payable(address(0x30000));
        hevm.prank(msg.sender);
        recipient.transfer(1000);

        uint256 balanceChange = balanceBefore - msg.sender.balance;
        emit LogBalanceChange(balanceChange);

        assert(balanceChange > 0);
    }
}
```

Logs:
```js
     => [event] LogBalanceChange(0)
     => [panic: assertion failed]
```

high-priority

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

medusa

`hevm.prank` does not reduce balance of the actor

### Describe the bug

In [Piper Merriam's Devcon talk on Portal Networks](https://youtu.be/0stc9jnQLXA?t=89) his presentation includes one more Portal network that is missing on the table at the bottom of [this section](https://ethereum.org/en/developers/docs/networking-layer/portal-network/#how-does-portal-network-work)

### To reproduce

1. Go to https://ethereum.org/en/developers/docs/networking-layer/portal-network/#how-does-portal-network-work
2. Scroll down to the table at the bottom of that section
3. See error - "Canonical Txn Index" is missing


### Expected behavior

Include "Canonical Txn Index" on the table

### Screenshots

![Screenshot 2024-07-09 at 09 00 25](https://github.com/ethereum/ethereum-org-website/assets/9151261/e851aa7f-786a-4252-9d97-96453e0a2ca7)


### Desktop (please complete the following information)

_No response_

### Smartphone (please complete the following information)

_No response_

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
- [ ] No

bug 🐛

One of the portal networks is missing on the table

<img width="921" alt="image" src="https://github.com/trailofbits/vscode-sarif-explorer/assets/6371919/5253709f-b49d-4e1a-b54f-e9d4b2ea3f89">

Long messages are truncated without ability to expand/shrink columns. There is a lot of empty space between the columns that could be used to display message.

Whole message is shown in the bottom panel, but you have to click on the finding to open that panel and that action switch focus to code, making navigation of messages slow.

enhancement :sparkles:

priority:low

SARIF Explorer: A VSCode extension that helps you visualize and triage static analysis results

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity