
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

good first issue

ready to implement

eipw

Rust

Add a lint that detects bolded or italic UPPERCASE keywords

Some improvements (to be evaluated) I had thought of included: 
- moving the generated reports to a `reports/` directory inside the runner. 
- changing the reports name to include current date in order to keep old reports and be able to identify different runs. In this case adding a command that deletes all the generated reports could be useful. 
- for failing reports, consider making them easier to read. A library like [`pretty-table`](https://crates.io/crates/pretty-table) could be useful. 

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

ethrex

Polish tests reports

It was decided that it is not a major problem now, as post state only gets compared if expected root was not the one obtained (therefore no tests are currently failing because of this), but some post storage checks could fail for some punctual considerations: 
- The information stored in database in `current_accounts_state` and `initial_accounts_state` fields is ONLY the diff and not the full storage pre and post tx. 
- The `.json` files do not include storage slots that have the value `0`. 

Review this in more depth and consider: 
- Filtering storage slots with content `0` in the real post state storage. 
- Include missing original storage slots (that have not changed) taking them from the Genesis. 

Polish post state storage comparisons

When parsing the files, current console output might be too verbose. A possibility could be to override the parsing message with each new file. 
Problems that might come up with this and should be taken into account: 
- Some files get parsed too quickly and would not get printed. 
- As the length of the message could vary, console output could have previous outputs leftovers. 

Improve parsing console output

The current active runner has been improved to parallelize the parsing of tests files, the idea would be to translate this to the new runner (might be a bit different as it is a different implementation but the current code could serve as a guide). 

Parallelize parsing of the test files

Related issue: #9055

We could extend the trace_ endpoints to allow specifying the current fork. In the Nethermind code, this would correspond to the [ReleaseSpec](https://github.com/NethermindEth/nethermind/blob/master/src/Nethermind/Nethermind.Specs/ReleaseSpec.cs) class.

I think the most important endpoint to focus on is trace_block, and we should start with that.
Our short-term goal is to execute blocks containing ModExp on both the Pectra and Fusaka forks.

osaka

A robust execution client for Ethereum node operators.

nethermind

Extending trace_ endpoints with fork as a parameter

There is an edge case in the node where the `Finalized` L1 notification could be issued without a following `NewBlock` notification (in case of provider error for example). This could set the node (in particular the sequencer component) in an incorrect state where the finalized block number > current block number. In order to avoid this issue, return the notification from both `handle_finalized_block` and `handle_latest_block` function, then send them down the channel, starting with the `NewBlock` notification.

watcher

rollup-node

[Watcher] Issue `NewBlock` notification before `Finalized` notification

When you want to launch a local L1 node and the port is not available, initialization does not stop and the error is not logged.
This is replicated by doing:
`make init-local-l1` in the `crates/l2` directory
and then running `RUST_LOG=debug cargo run --bin ethrex -- --network ./fixtures/genesis/kurtosis.json`

tech debt

L1: Error not logged when L1 ports are not available

Few issues:
(1) The startup log is confusing:
```
# Limit trie logs enabled: retention: 512; prune window: 5000                                      #
```
Some ppl mistake "prune window" for retention. 
Suggest:
a) renaming "prune window" to "batch size" perhaps, also in the code as well as startup log
b) removing "prune window" ("batch size") from startup log if the default is being used (still display if explicitly set though).

(2) retention of 512 default is quite short for some use cases (< 2 hours) and may need a devnet-friendly value.
Suggest:
a) Separate option from --bonsai-historical-block-limit (but maybe still use this value as the default?)
b) Consider a new default > 512
Estimates for TRIE_LOG_STORAGE size:
```
| Time Period     | Blocks | Size (MiB) | Size (GiB)  |
| --------------- | ------ | ---------- | ----------- |
| < 2 hours       | 512    | 200        |  ~0.195 GiB | 
| 1 day           | 7,200  | 2,812.5    |  ~2.75 GiB  |
| 2 days          | 14,400 | 5,625      |  ~5.49 GiB  |
| 7 days          | 50,400 | 19,687.5   |  ~19.23 GiB |
```
2 days should be sufficient for the devnet use cases.

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

besu

Java

Limit Trie Log Config Tweaks

We are currently using a hardcoded value for the L2 rpc_url in the Watcher: https://github.com/lambdaclass/ethrex/blob/ce87d548d3a30d75bfe4e5a1ae2cf242a316f3f3/crates/l2/sequencer/l1_watcher.rs#L46
We should pass it using the CLI.

L2: add L2 rpc url to `WatcherConfig` instead of using a hardcoded one

When instantiating a stack the `stack.json` contains images that are not relevant for the current stack.

Raised on Discord https://discord.com/channels/905194001349627914/928377875827154984/1395092589409079416


If you create a Cardano stack for example, you can see that it tries to pull images for EVM Connect and Tezos Connect on `start`. 

This needs a change to the way the manifest is handled and filtered 

firefly-cli

Pulling unnecessary images for stack type

### Describe the bug

I am parsing the struct through a parseAbiParameter initially as follows: 
```ts
let signatures = ['struct Foo { string bar; }', 'Foo']; 
expect(parseAbiParameter(signatures)).toEqual({ type: 'tuple', components: [{ name: 'bar', type: 'string' }] }); 
```
This works as expected. However, subsequent call with the same struct name, but different struct signature leads to the following to fail. 
```ts
signatures = ['struct Foo { address bar; }', 'Foo']; 
expect(parseAbiParameter(signatures)).toEqual({ type: 'tuple', components: [{ name: 'bar', type: 'address' }] });
```
The actual result of this function call is 
```ts
{ type: 'tuple', components: [{ name: 'bar', type: 'string' }] }
```
I investigated it further and this seems to be caused by the caching inside the function. 

https://github.com/wevm/abitype/blob/d153cd678b32783235a6dadd4901262b395eee9a/packages/abitype/src/human-readable/runtime/utils.ts#L198-L204

Since the parseAbiParameter is used as a library function for various ABIs, this leads to unexpected behavior, where using it for structs with same names but different signature always resolves to the result of the first signature parsing due to caching. 

### Link to Minimal Reproducible Example

_No response_

### Steps To Reproduce

_No response_

### Package Version

1.0.8

### TypeScript Version

5.7.2

### Check existing issues

- [x] I checked there isn't [already an issue](https://github.com/wevm/abitype/issues) for the bug I encountered.

### Anything else?

_No response_

Strict TypeScript types for Ethereum ABIs

abitype

TypeScript

bug: parseAbiParameter caching


_Originally posted by @Copilot in https://github.com/lambdaclass/ethrex/pull/3649#discussion_r2208639844_
            

Pin the `pontem-network/get-solc` action to a specific tag or commit SHA instead of `@master`

For some reason we are using `u64` for gas price in Legacy Transactions and I believe we should be using `U256` instead. When first implemented legacy transactions used only 64 bits for that? Check if code is wrong, otherwise close this issue.

Edit: Yes, we should change this, but not only on Legacy Transactions. The gas price should be U256 in every place in which it's used. There are some functions related to gas price that return u64 and that's incorrect. In real case scenarios it's good enough but not technically accurate.

Edit 2: Thinking more about this I don't really know if we want to change this because it seems that other clients don't do this and they may have good reasons not to. Would this make an impact on performance? Because that's the only reason I have not to make this change. Otherwise if performance is kinda the same I'd go on with this but we have to measure that first.

L1: Use 256 bits for gas price in legacy transaction

## Description
We have 2 implementations of the storage. InMemory, for the tests and RocksDB-based persistent implementation for production usage. We implemented 2 testsuite which are practically the same. Feature-wise, RocksDB implementation is different only by persistence support. So we can really reuse the same testsuite for both implementations, rather than copy-pasting the tests

## Motivation
This would save the dev time for the new functionality being added to the `BeaconChain` and maintenance time for the existing functionality

## Tasks
- [ ] Factor out a sharable testsuite for both `InMemoryBeaconChain` and `KvDatabase`
- [ ] Make it runnable on both implementations

## Acceptance criteria
- [ ] A single testsuite is used for both `InMemoryBeaconChain` and `KvDatabase`

## Risks
- [ ] We need to make sure the testsuite is really running for both implementation and that it's possible to extend the suite with tests specific to each implementation

## Remember to
 - [ ] Add the `documentation` label in case there is an impact on the documentation
 - [ ] Add `priority` and `team` labels
 - [ ] Add Task for updating the Runbook or adding/updating existing metrics and alerts. 


Consensus layer client implementing QBFT protocol adhering to Eth 2.0 CL / EL separation and API

maru

Kotlin

Reuse tests for InMemory and KvDatabase implementation

We need to verify that the service works seamlessly on Windows, specifically from a contributor experience perspective. Most of the current development has been done on macOS, and we want to ensure following:

- The project compiles successfully on Windows.
- Developer tooling such as pre-commit hooks, OpenSSL/Cargo dependencies, and other system-level requirements behave as expected.

This helps avoid friction for new contributors when raising PRs or running development workflows locally.

**What to Test:**

Clone the repository on a clean Windows machine and:

- Run cargo build and ensure there are no OpenSSL or toolchain-related issues;
- Install and run pre-commit hooks;
- Validate whether any pre-commit hooks fail unexpectedly (e.g. line endings, formatters, etc);
- Check for any missing dependencies that should be added to README.md or a setup script.

**Suggested Fixes**

- Update the documentation (CONTRIBUTING.md or README.md) with required setup steps.
- Create a .sh or .md file listing all Windows-specific setup instructions.
- Consider adjusting the pre-commit config or adding OS-specific guidance.

documentation

help wanted

D-easy

T-task

cla: allowlist

openzeppelin-relayer

Ensure Windows Compatibility for Contributors

We need to verify that the service works seamlessly on Ubuntu (or similar Unix environments), specifically from a contributor experience perspective. Most of the current development has been done on macOS, and we want to ensure:

- The project compiles successfully on Ubuntu.
- Developer tooling such as pre-commit hooks, OpenSSL/Cargo dependencies, and other system-level requirements behave as expected.

This helps avoid friction for new contributors (especially Linux users) when raising PRs or running development workflows locally.

**What to Test:**

Clone the repository on a clean Ubuntu machine;

- Run cargo build and ensure there are no OpenSSL or toolchain-related issues;
- Install and run pre-commit hooks;
- Validate whether any pre-commit hooks fail unexpectedly (e.g. line endings, formatters, etc);
- Check for any missing dependencies that should be added to README.md or a setup script.

**Suggested Fixes**

- Update the documentation (CONTRIBUTING.md or README.md) with required setup steps.
- Create a .sh or .md file listing all Ubuntu-specific setup instructions.
- Consider adjusting the pre-commit config or adding OS-specific guidance.

Ensure Ubuntu (Unix) Compatibility for Contributors

Class hash: 0x01b2df6d8861670d4a8ca4670433b2418d78169c2947f46dc614e69f333745c8
Contract address: 0x02ceed65a4bd731034c01113685c831b01c15d7d432f71afb1cf1634b53a2125

contract: https://github.com/OpenZeppelin/cairo-contracts/blob/main/packages/presets/src/universal_deployer.cairo
Docs: https://docs.openzeppelin.com/contracts-cairo/2.0.0/udc

Update functions like `utils.BuildUDCCalldata`, `utils.PrecomputeAddressForUDC`, and `account.DeployContractWithUDC`.
See the new changes, and set it as the default option in our enum.

starknet.go

Update UDC helpers to use the new UDC contract

We could have a validation for the typedData json file to avoid mistakes.

For example, this typed data has an error, but it's considered valid. The `amount` field value contains an object instead of a `u128`.
A validation would be good for the UX. 

SNIP-12 spec: https://github.com/starknet-io/SNIPs/blob/main/SNIPS/snip-12.md

``` json
{
  "domain": {
    "name": "Permit2",
    "version": "v1",
    "chainId": "0x0",
    "revision": "1"
  },
  "primaryType": "PermitSingle",
  "message": {
    "details": {
      "token": "0x1234",
      "amount": { "low": "0x123", "high": "0x0" },
      "expiration": "1234",
      "nonce": "1"
    },
    "spender": "0x1234",
    "sigDeadline": {
      "low": "1234567890",
      "high": "0x0"
    }
  },
  "types": {
    "StarknetDomain": [
      { "name": "name", "type": "shortstring" },
      { "name": "version", "type": "shortstring" },
      { "name": "chainId", "type": "shortstring" },
      { "name": "revision", "type": "shortstring" } 
    ],
    "PermitDetails": [
      { "name": "token", "type": "felt" },
      { "name": "amount", "type": "u128" },
      { "name": "expiration", "type": "u128" },
      { "name": "nonce", "type": "u128" }
    ],
    "PermitSingle": [
      { "name": "details", "type": "PermitDetails" },
      { "name": "spender", "type": "felt" },
      { "name": "sigDeadline", "type": "u256" }
    ]
  }
}
```



Improve SNIP-12 with validation function

### Steps to Reproduce
Run besu in the terminal or use besu with `--color-enabled=true`, output has no ansi coloring.

**Expected behavior:** [What you expect to happen]
Expect output to be colored as previously.

### Versions (Add all that apply)
* Software version: [`besu --version`]: `25.7.0`
* Java version: [`java -version`]: `openjdk 21.0.7 2025-04-15`
* OS Name & Version: [`cat /etc/*release`]: `Void Linux`
* Kernel Version: [`uname -a`]: `6.12.34`

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity