
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

Inspired by this article: https://vercel.com/blog/agents-md-outperforms-skills-in-our-agent-evals

We should maintain robust documentation for every component of medusa so that future bug fixes and features can be implemented rapidly with the necessary context.

documentation

help wanted

high-priority

not-an-issue

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

medusa

Add thorough documentation for agents

Create a separate folder for the testnet
- New folder `providers-testnet`
- Update the CI to use this new folder for the testnet deployment.
- Keep the [_example.json](https://github.com/AztecProtocol/staking-dashboard/blob/main/providers/_example.json) and [README.md](https://github.com/AztecProtocol/staking-dashboard/blob/main/providers/README.md) files in the new `providers-testnet` folder.

staking-dashboard

TypeScript

Separate metadata folder for testnet

Create a dropdown switcher similar to [Dashtecs](https://dashtec.xyz/).
- Should show "Mainnet ˅" on the mainnet version
- Should show "Testnet ˅" on the testnet version
- When clicking the button, show a dropdown to switch to the other version.
- When clicking on another version name in the dropdown, direct the user to that version.

Network switcher

## Description
Remove unnecessary `zkStateRootHash` field from `FinalizationMonitor.FinalizationUpdate`. This will simplify FinalizationMonitor implementation logic and reduce requests on L1.

## Motivation
Simplify code and reduce queries on L1

good first issue

Coordinator

TechDebt

The principal Linea repository. This mainly includes the smart contracts covering Linea's core functions, the Prover in charge of generating ZK proofs, the Coordinator responsible for multiple orchestrations, and the Postman to execute bridge messages

linea-monorepo

Coordinator - FinalizationMonitor remove FinalizationUpdate.zkStateRootHash

All of the jobs in the [test-network-k8s.yaml](https://github.com/hyperledger/fabric-samples/blob/d669a3fccf7b9508997abd8ce3d070fa107bef8c/.github/workflows/test-network-k8s.yaml) workflow fail with errors similar to this:

> ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged kind-control-plane kubeadm init --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1
> 
> Command Output: I0128 21:32:02.099389     207 initconfiguration.go:260] loading configuration from "/kind/kubeadm.conf"
W0128 21:32:02.099846     207 common.go:100] your configuration file uses a deprecated API spec: "kubeadm.k8s.io/v1beta3" (kind: "ClusterConfiguration"). Please use 'kubeadm config migrate --old-config old-config-file --new-config new-config-file', which will write the new, similar spec using a newer API version.
W0128 21:32:02.100237     207 common.go:100] your configuration file uses a deprecated API spec: "kubeadm.k8s.io/v1beta3" (kind: "InitConfiguration"). Please use 'kubeadm config migrate --old-config old-config-file --new-config new-config-file', which will write the new, similar spec using a newer API version.
W0128 21:32:02.100549     207 common.go:100] your configuration file uses a deprecated API spec: "kubeadm.k8s.io/v1beta3" (kind: "JoinConfiguration"). Please use 'kubeadm config migrate --old-config old-config-file --new-config new-config-file', which will write the new, similar spec using a newer API version.
W0128 21:32:02.100782     207 initconfiguration.go:361] [config] WARNING: Ignored configuration document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration
[init] Using Kubernetes version: v1.35.0
[certs] Using certificateDir folder "/etc/kubernetes/pki"
I0128 21:32:02.101765     207 certs.go:111] creating a new certificate authority for ca
[certs] Generating "ca" certificate and key
I0128 21:32:02.149978     207 certs.go:472] validating certificate period for ca certificate
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [kind-control-plane kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 172.18.0.2 127.0.0.1]
[certs] Generating "apiserver-kubelet-client" certificate and key
I0128 21:32:02.259787     207 certs.go:111] creating a new certificate authority for front-proxy-ca
[certs] Generating "front-proxy-ca" certificate and key
I0128 21:32:02.355405     207 certs.go:472] validating certificate period for front-proxy-ca certificate
[certs] Generating "front-proxy-client" certificate and key
I0128 21:32:02.415463     207 certs.go:111] creating a new certificate authority for etcd-ca
[certs] Generating "etcd/ca" certificate and key
I0128 21:32:02.455783     207 certs.go:472] validating certificate period for etcd/ca certificate
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [kind-control-plane localhost] and IPs [172.18.0.2 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [kind-control-plane localhost] and IPs [172.18.0.2 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
I0128 21:32:02.593927     207 certs.go:77] creating new public/private key files for signing service account users
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
I0128 21:32:02.650844     207 kubeconfig.go:111] creating kubeconfig file for admin.conf
[kubeconfig] Writing "admin.conf" kubeconfig file
I0128 21:32:02.712766     207 kubeconfig.go:111] creating kubeconfig file for super-admin.conf
[kubeconfig] Writing "super-admin.conf" kubeconfig file
I0128 21:32:02.904332     207 kubeconfig.go:111] creating kubeconfig file for kubelet.conf
[kubeconfig] Writing "kubelet.conf" kubeconfig file
I0128 21:32:02.940341     207 kubeconfig.go:111] creating kubeconfig file for controller-manager.conf
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
I0128 21:32:02.959152     207 kubeconfig.go:111] creating kubeconfig file for scheduler.conf
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I0128 21:32:03.005512     207 local.go:67] [etcd] wrote Static Pod manifest for a local etcd member to "/etc/kubernetes/manifests/etcd.yaml"
I0128 21:32:03.005548     207 manifests.go:125] [control-plane] getting StaticPodSpecs
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
I0128 21:32:03.005794     207 certs.go:472] validating certificate period for CA certificate
I0128 21:32:03.005870     207 manifests.go:151] [control-plane] adding volume "ca-certs" for component "kube-apiserver"
I0128 21:32:03.005883     207 manifests.go:151] [control-plane] adding volume "etc-ca-certificates" for component "kube-apiserver"
I0128 21:32:03.005888     207 manifests.go:151] [control-plane] adding volume "k8s-certs" for component "kube-apiserver"
I0128 21:32:03.005892     207 manifests.go:151] [control-plane] adding volume "usr-local-share-ca-certificates" for component "kube-apiserver"
I0128 21:32:03.005896     207 manifests.go:151] [control-plane] adding volume "usr-share-ca-certificates" for component "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
I0128 21:32:03.006478     207 manifests.go:178] [control-plane] wrote static Pod manifest for component "kube-apiserver" to "/etc/kubernetes/manifests/kube-apiserver.yaml"
I0128 21:32:03.006496     207 manifests.go:125] [control-plane] getting StaticPodSpecs
I0128 21:32:03.006705     207 manifests.go:151] [control-plane] adding volume "ca-certs" for component "kube-controller-manager"
I0128 21:32:03.006714     207 manifests.go:151] [control-plane] adding volume "etc-ca-certificates" for component "kube-controller-manager"
I0128 21:32:03.006717     207 manifests.go:151] [control-plane] adding volume "flexvolume-dir" for component "kube-controller-manager"
I0128 21:32:03.006719     207 manifests.go:151] [control-plane] adding volume "k8s-certs" for component "kube-controller-manager"
I0128 21:32:03.006721     207 manifests.go:151] [control-plane] adding volume "kubeconfig" for component "kube-controller-manager"
I0128 21:32:03.006725     207 manifests.go:151] [control-plane] adding volume "usr-local-share-ca-certificates" for component "kube-controller-manager"
I0128 21:32:03.006732     207 manifests.go:151] [control-plane] adding volume "usr-share-ca-certificates" for component "kube-controller-manager"
I0128 21:32:03.007302     207 manifests.go:178] [control-plane] wrote static Pod manifest for component "kube-controller-manager" to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
I0128 21:32:03.007319     207 manifests.go:125] [control-plane] getting StaticPodSpecs
[control-plane] Creating static Pod manifest for "kube-scheduler"
I0128 21:32:03.007517     207 manifests.go:151] [control-plane] adding volume "kubeconfig" for component "kube-scheduler"
I0128 21:32:03.007903     207 manifests.go:178] [control-plane] wrote static Pod manifest for component "kube-scheduler" to "/etc/kubernetes/manifests/kube-scheduler.yaml"
I0128 21:32:03.007920     207 kubelet.go:69] Stopping the kubelet
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/instance-config.yaml"
[patches] Applied patch of type "application/strategic-merge-patch+json" to target "kubeletconfiguration"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
I0128 21:32:03.129737     207 loader.go:405] Config loaded from file:  /etc/kubernetes/admin.conf
I0128 21:32:03.130174     207 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false
I0128 21:32:03.130216     207 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false
I0128 21:32:03.130225     207 envvar.go:172] "Feature gate default state" feature="InOrderInformers" enabled=true
I0128 21:32:03.130232     207 envvar.go:172] "Feature gate default state" feature="InOrderInformersBatchProcess" enabled=true
I0128 21:32:03.130240     207 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=true
I0128 21:32:03.130262     207 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=true
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests"
[kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s
[kubelet-check] The kubelet is not healthy after 4m0.001144769s
> 
> Unfortunately, an error has occurred, likely caused by:
> 	- The kubelet is not running
> 	- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
> 
> If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
> 	- 'systemctl status kubelet'
> 	- 'journalctl -xeu kubelet'
> 
> error: error execution phase wait-control-plane: failed while waiting for the kubelet to start: The HTTP call equal to 'curl -sSL http://127.0.0.1:10248/healthz' returned error: Get "http://127.0.0.1:10248/healthz": context deadline exceeded


fabric-samples

Kubernetes test network samples fail

### Description
Discovery v5 logging is currently overly verbose, especially at the debug level, making logs difficult to interpret in real deployments.

discovery-v5

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

besu

Java

Tune Discovery v5 Logging Levels

**Current behavior:**

When a tx has multiple messages, the CLI shows a selection prompt. After executing one message, the CLI exits.

**Requested behavior:**

After executing a message (success or fail), return to the selection prompt instead of exiting. This allows users to cycle through multiple failed messages without re-running the command.

**Use case:**

A tx with 6 failed messages currently requires running ccip manual-exec 6 times. With this change, run once and cycle through all.

**Proposed flow:**

1. Show message list
2. User selects message
3. Execute
4. Show result (success/fail)
5. Return to step 1
6. Repeat until user selects “Exit.”

<img width="720" height="276" alt="Image" src="https://github.com/user-attachments/assets/13af154e-96c3-436c-85f6-7a7ca45e5436" />

enhancement

Typescript CLI and library to interact with CCIP

ccip-tools-ts

Enhance CLI manual exec to cycle through multiple failed messages

### Current State

This is a new field in execution info v3

### Objective

Add cheats for `proof_facts`

### Additional Context

_No response_

blocked

snforge

Blazing fast toolkit for developing Starknet contracts.

starknet-foundry

Rust

Add cheats for `proof_facts`

## Background

Many RPC method implementations in Forest are missing the `DESCRIPTION` constant, which should provide documentation about what each method does.

## Task

Add the `DESCRIPTION` field to all RPC method implementations throughout the codebase. This will improve API documentation and help users understand what each method does.

## Example

```rust
impl RpcMethod<2> for EthTraceReplayBlockTransactions {
    const NAME: &'static str = "Filecoin.EthTraceReplayBlockTransactions";
    const NAME_ALIAS: Option<&'static str> = Some("trace_replayBlockTransactions");
    const DESCRIPTION: Option<&'static str> = Some(
        "Replays all transactions in a block returning the requested traces for each transaction.",
    );
    // ...
}
```

## Context

Related PR: #6444
Related comment: https://github.com/ChainSafe/forest/pull/6444#discussion_r2709084181

cc: @akaladarshi

forest

Add DESCRIPTION to all RPC methods

🧐 Motivation
In `ReentrancyGuard.sol`, the comment in `_nonReentrantAfter()` states:
```
// By storing the original value once again, a refund is triggered (see
// https://eips.ethereum.org/EIPS/eip-2200)
```
However, the current implementation uses values `1` and `2` (NOT_ENTERED = 1, ENTERED = 2), and the operation `2 → 1` is a **non-zero to non-zero** storage change, which does **not** trigger a refund according to EIP-2200.

📝 Details
The comment should be updated to accurately reflect the gas behavior:

```
function _nonReentrantAfter() private {
// Restore the original value to allow future calls
// Note: Using 1/2 instead of 0/1 avoids EIP-2200 refunds and makes gas costs predictable
_reentrancyGuardStorageSlot().getUint256Slot().value = NOT_ENTERED;
}
```

Or simply remove the misleading part about refunds:
```
function _nonReentrantAfter() private {
// Restore the original value to allow future calls
_reentrancyGuardStorageSlot().getUint256Slot().value = NOT_ENTERED;
}
```

typo

OpenZeppelin Contracts is a library for secure smart contract development.

openzeppelin-contracts

Solidity

Incorrect comment about EIP-2200 refund in ReentrancyGuard

seeing frequent occurrences of this warning on burn-in nodes. Seems to be genuine invalid incoming data, similar to sending an invalid tx.
`Invalid input length for P256VERIFY precompile: expected 160 bytes but got 100`

change this log to DEBUG. May need a besu-native change?

example from `dev-elc-bu-ls-mainnet-burn-snap-507b1635b5891d1289465bd2c6da21f834c4148e`

100 x 

```
{"@timestamp":"2026-01-12T05:13:00,723","level":"WARN","thread":"pool-2-thread-4","class":"P256VerifyPrecompiledContract","message":"Invalid input length for P256VERIFY precompile: expected 160 bytes but got 100","throwable":""}
{"@timestamp":"2026-01-12T05:13:00,786","level":"WARN","thread":"vert.x-worker-thread-0","class":"P256VerifyPrecompiledContract","message":"Invalid input length for P256VERIFY precompile: expected 160 bytes but got 100","throwable":""}
```



Turn down this log: Invalid input length for P256VERIFY precompile: expected 160 bytes but got 100

# Summary

Migrate https://github.com/filecoin-project/lotus/issues/13256 to Forest (`forest-wallet`). 

The implementation in Go is done is done so it could be used as a reference.

# Completion Criteria



- [ ] Implementation
- [ ] Tests
- [ ] Docs

# Additional Links & Resources

Type: Task

Implement FRC-102 in `forest-wallet` for consistency across Filecoin wallets

`/configure` accepts` auth.cosigner_commitments` from the client and only verifies that the signer’s pubkey exists in the account state. The full list isn’t validated against the actual account storage, so incorrect or malicious auth config could be stored.

When configuring an account, extract signer commitments from `initial_state` and ensure they match `auth.cosigner_commitments` (same set/order as expected), otherwise reject

cla: allowlist

security

Cloud backup and syncronization layer for Miden private accounts

private-state-manager

Validate cosigner_commitments on configure

It seems that `misleading_variable_name` starts matching names from the end and only a small part of them. Is this normal behavior? If so, I suggest adding a setting to this lint that allows you to specify which side to start the comparison from.

```rust
let up: UpdateSchemePath = path.into_inner(); // negative
let query: UpdateSchemeQuery = query.into_inner(); 
    ^^^^^
// `dropshot::extractor::query` exports a type `Query`, which is not     
// the type of `query` use a name other than `query`
```

dylint

`misleading_variable_name` works weirdly

**🧐 Motivation**
Function [`_quickSort()`](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/Arrays.sol#L115-L137) is limited in the number of items that can be sorted, especially for the worst case where the array is already (largely) sorted (in a reverse way). 

**📝 Details**
The limitation is relateed to the stack dept of 1024 and the relatively large usage of stack per recusion (3 parameters passed and 2 variables allocated). This allows for a recurstion dept of only 169.

The function `_quickSort()` does two recursive calls. In most programming languages that is fine because they support tail recursion, which optimizes stack usage for a recursive call at the end of the function. However Solidity does not do this optimization.

**📝 POC**

The following POC shows the issue:
- test_sort1: N1=169 gas=1943416   
- test_sort2: N2=1000 gas=67212880

Setting N1 to 170 results in: [FAIL: EvmError: StackOverflow]

```solidity
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.28;

import 'forge-std/Test.sol';

contract TestRecursion {

    function gtComparator(uint256 a, uint256 b) internal pure returns (bool) {
        return a > b;
    }
  
    uint constant N1 = 169; // 170 -> StackOverflow with _quickSort1  
    function test_sort1() public view {
        uint256[] memory a1 = new uint256[](N1);
        for (uint i=0;i<N1;i++) {
           a1[i] = 1000 -i ;//% 20;
        }
        uint g1;uint g2;      
        g1 = gasleft();_quickSort1(_begin(a1), _end(a1),gtComparator);g2=gasleft();console.log("1 N1=%d gas=%d", N1,g1-g2);
    }

    uint constant N2 = 1000; 
    function test_sort2() public view {
        uint256[] memory a2 = new uint256[](N2);
        for (uint i=0;i<N2;i++) {
           a2[i] = 10000 -i ;//% 20;  
        }
        uint g1;uint g2;      
        g1 = gasleft();_quickSort2(_begin(a2), _end(a2),gtComparator);g2=gasleft();console.log("2 N2=%d gas=%d", N2,g1-g2);
    }
  

    function _quickSort1(
        uint256 begin,
        uint256 end,
        function(uint256, uint256) pure returns (bool) comp
    ) private pure {
        unchecked {
            if (end - begin < 0x40) return;
            uint256 pivot = _mload(begin);
            uint256 pos = begin;
            for (uint256 it = begin + 0x20; it < end; it += 0x20) {
                if (comp(_mload(it), pivot)) {
                pos += 0x20;
                _swap(pos, it);
                }
            }
            _swap(begin, pos); // Swap pivot into place
            _quickSort1(begin, pos, comp); // Sort the left side of the pivot
            _quickSort1(pos + 0x20, end, comp); // Sort the right side of the pivot
        }
    }

    function _quickSort2(
        uint256 begin,
        uint256 end,
        function(uint256, uint256) pure returns (bool) comp
    ) private pure {
        unchecked {
            while (true) {
                if (end - begin < 0x40) return;
                //console.log(begin,end);
                uint256 pivot = _mload(begin);
                uint256 pos = begin;
                for (uint256 it = begin + 0x20; it < end; it += 0x20) {
                    if (comp(_mload(it), pivot)) {
                      pos += 0x20;
                      _swap(pos, it);
                    }
                }
                _swap(begin, pos); // Swap pivot into place
                if (pos - begin < end - (pos + 0x20) ) {
                    _quickSort2(begin, pos, comp); // Sort the left side of the pivot
                    begin = pos + 0x20; // do another loop without recursion 
                }
                else {
                    _quickSort2(pos + 0x20, end, comp); // Sort the right side of the pivot
                    end = pos; // do another loop without recursion           
                }
            }
        }
    }
    function _begin(uint256[] memory array) private pure returns (uint256 ptr) {
        assembly ('memory-safe') {ptr := add(array, 0x20) }
    }
    function _end(uint256[] memory array) private pure returns (uint256 ptr) {
        unchecked {
            return _begin(array) + array.length * 0x20;
        }
    }
    function _mload(uint256 ptr) private pure returns (uint256 value) {
        assembly { value := mload(ptr) }
    }
    function _swap(uint256 ptr1, uint256 ptr2) private pure {
        assembly {
          let value1 := mload(ptr1)
          let value2 := mload(ptr2)
          mstore(ptr1, value2)
          mstore(ptr2, value1)
        }
    }
}
```

**📝 Suggestion**

If the recursion of the largest subset is replaced by a loop, then the total amount of recursions is reduced considerably.

This can be done in the following way:
```diff
function _quickSort( uint256 begin, uint256 end, function(uint256, uint256) pure returns (bool) comp) private pure {
    unchecked {
+       while (true) {
            if (end - begin < 0x40) return;
            uint256 pivot = _mload(begin);
            uint256 pos = begin;
            for (uint256 it = begin + 0x20; it < end; it += 0x20) {
                if (comp(_mload(it), pivot)) {
                    pos += 0x20;
                    _swap(pos, it);
                }
            }
            _swap(begin, pos); // Swap pivot into place
+           if (pos - begin < end - (pos + 0x20) ) {
                _quickSort(begin, pos, comp); // Sort the left side of the pivot
+               begin = pos + 0x20; // do another loop without recursion 
+           } else {
                _quickSort(pos + 0x20, end, comp); // Sort the right side of the pivot
+               end = pos; // do another loop without recursion           
+           }
+       }
    }
}
```

Further optimization is also possible by reducing the size of the parameters passed and by reducing the allocated variables in the function. All used variables could be fit in a `uint64` and multiple `uint64`s could be combined in one `uint256`. However this makes the code more complicated.

Alternatively other sort algoritms could be used: iterative quicksort / three-way partitioning / timsort

idea

gas optimization

Function `_quickSort()` can be optimized

### Description
To simplify log analysis across different monitoring stacks, please add an option to output logs in JSON format. While export `LOG4J_CONFIGURATION_FILE=./debug.xml` allows for custom log configurations, it is a bit of an overhead for most users.

### Additional Information (Add any of the following or anything else that may be relevant)
Previously, users who wanted structured JSON logging (e.g., for Elasticsearch, Google Cloud Logging, or Graylog) had to:

- Create a custom Log4j2 XML configuration file
- Mount or inject this file into their deployment
- Specify `LOG4J_CONFIGURATION_FILE=./debug.xml`

New --logging-format CLI option that enables users to programmatically select structured logging formats without requiring custom Log4j2 configuration files. This is particularly useful in containerized and cloud environments where injecting configuration files is cumbersome.

New CLI option: --logging-format= with support for:

- PLAIN (default) - Traditional pattern-based console logging
- ECS - Elastic Common Schema JSON format
- GCP - Google Cloud Platform JSON format
- LOGSTASH - Logstash JSON Event Layout V1
- GELF - Graylog Extended Log Format

feat: Add --logging-format CLI option for structured logging (ECS, GCP, LOGSTASH, PLAIN)

We currently assume that branches don't have values, and our API keeps this assumption. However, we don't currently have this proven at the type-level.

Minimalist, stable, modular, fast, and ZK native implementation of the Ethereum protocol in Rust. L1 and L2 execution client.

ethrex

Set trie branch values to empty at the type level

Right now, `cargo-test-fuzz` stops immediately when it cannot generate a corpus for a fuzz target:
https://github.com/trailofbits/test-fuzz/blob/4e6e3ab47233196d25440cc190e5fbb03a80e161/cargo-test-fuzz/src/lib.rs#L1325-L1330

A better approach would be to try to generate a corpus for each fuzz target and, at the end, show the ones for which the operation failed.

I think this should be an easy change.

test-fuzz

Show all targets for which corpora could not be generated

> We lost context [here](https://github.com/lambdaclass/ethrex/pull/5713/changes/BASE..f93276bf1246a7bba5b58f4defd178aa0e72ae80#diff-8398e9197a9beb1ece5b777c9c6f9c5662438c649cd7377341724c64eb41a67cR556-R560), maybe for a follow-up but we might want better info for this error (like node/path) to understand where to look instead of just the difference? Not sure if right now that info is useful or not, i didn't debugged these cases before, if it is indeed useful we can create a small issue for later.
> 
> _Originally posted by @rodrigo-o in https://github.com/lambdaclass/ethrex/pull/5713#discussion_r2664632949_

Add more context to count mismatch in trie validation function

**Client version**
ethrex client version: 8.0.0
Network: custom genesis (large file, ~1GB)


We’re seeing very slow startup when using a large (~1GB) custom genesis.json. On the second run the client logs that the genesis matches a previously stored one (“nothing to do”), but the startup time is still long.

Observed behavior:

Second startup still spends a lot of time before the RPC server comes up, despite reusing the stored genesis.

**Expected behavior**:

When the DB already contains the genesis, startup should skip heavy parsing/hash computation and be noticeably faster.


<img width="1380" height="828" alt="Image" src="https://github.com/user-attachments/assets/127bd4f2-498f-40d8-a218-e1d3d09202b9" />

<img width="1395" height="802" alt="Image" src="https://github.com/user-attachments/assets/2cea7e0d-fcef-4fbd-8a90-9cd80bf826f7" />



Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity