
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

enhancement

good first issue

Multi-party computation libraries written in Rust 🦀

Rust

Replace `bytemuck` with `zerocopy`

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

consolidate

perf

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

gnark

perf/refac: Groth16 MPC setup improvements

# 🚀 Feature Request

### Description

prysm e2e now must start at post merge ( bellatrix or above) but the system isn't very configurable to start at the fork you would like it to start at. instead because of how it previously worked, the system must for a dozen epochs before it's able to get to the desired fork. 

### Describe the solution you'd like

ideally we can start from any fork and evaluators will work accordingly.

### Describe alternatives you've considered

kurtosis is a viable alternative although there is usually more control over prysm specific items and finding prysm specific bugs using our own e2e setup.

Help Wanted

E2E Tests

Go implementation of Ethereum proof of stake

prysm

reduced epoch start times for e2e

## Description

Move the contract examples from the current location to a dedicated package to avoid mixing them with the core contracts. This will help in maintaining a clear separation between example contracts and core contracts, improving the overall project structure and maintainability.

## Steps

1. Create a new directory named `examples` at the root of the project
2. Move all example contract files from `contracts/src/examples` to `examples`
3. Update any import paths in the example contracts to start using the `@verax-attestation-registry/verax-contracts` library
4. Ensure that the new `examples` directory has its own build and test configurations
5. Run all tests to verify that the changes do not break any functionality
6. Add a GitHub Actions pipeline to cover the examples

## Acceptance Criteria

- All example contracts are moved to the `examples` directory
- Import paths in the example contracts are updated correctly
- Build and test configurations are updated to use the npm package
- All tests pass successfully after the changes

Tech Debt

Good first issue

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

linea-attestation-registry

TypeScript

[TASK] Move the contracts examples to a dedicated package

### Wallet name

Family

### What type of wallet?

EOA

### Wallet description

Family is the perfect self-custody Ethereum wallet for those who want to keep their crypto close to home. With Family, you can easily send and receive tokens, as well as manage your favorite digital collectibles. Plus, our user-friendly interface makes it easy for anyone to get started with crypto. So whether you're a beginner or a seasoned pro, Family is the perfect wallet for you.

### Wallet logo

![Image](https://github.com/user-attachments/assets/823eea35-6807-4928-b1f3-8faa430bd561)

### Background color for brand logo

#ffffff

### URL to the project

family.co

### When did the wallet go live to users?

December 2022

### What are the fees users may be paying for using your wallet product?

There are no service fees. 

### Does the wallet have an active development team?

Yes. 

### Is the wallet globally accessible?

https://github.com/family

### Is the wallet available in multiple languages?

No, just English

### What social links are there for the project?

https://x.com/family

### Does the wallet have a mobile app? If yes, which operating systems are supported (iOS, Android)?

iOS only 

### Does the wallet have a desktop app? If yes, which operating systems are supported (Windows, Mac, Linux)?

No

### Does the wallet have a browser extension? If yes, which browsers are supported (Chromium, Firefox, Safari)?

No

### Is it a hardware wallet?

No

### What is the availability of your source code?

Closed source

### What license is the wallet software released under?

BSD 2-Clause "Simplified" License

### Who holds the private keys?

The wallet is self custodial.

### Please describe the measures taken to ensure the wallet's security and provide documentation wherever possible

Audit https://family.co/media/family-wallet-audit-report-2024.pdf

### Has the wallet's smart contract code or security modules been audited?

It does not have smart contract code

### Does the wallet have an internal security team?

Yes 

### Any other security testing that should be noted?

Family is tested consistently by the Avara internal security team.
Family also uses Tenderly for simulations, transaction analysis and Blockaid for dapp scanning and token scanning.

### Scam protection?

Family also Tenderly for simulations, transaction analysis, and Blockaid for dapp scanning and token scanning.

### Does the wallet support connecting to Ethereum applications?

Yes via Wallet Connect, and through Connect Kit (developed in-house)

### Does the wallet support connecting to a hardware wallet?

No

### Does the wallet support importing Ethereum RPC endpoints?

No

### Does the wallet support viewing and interacting with NFTs?

Yes

### Does the wallet support staking directly?

No

### Does the wallet support swaps directly?

Yes (https://family.co/support/swap-tokens)

### Does the wallet support bridging directly?

No 

### Does the wallet support multi-chain networks?

Yes - Ethereum and L2s

### Which Ethereum Layer 2 networks does the wallet support?

Ethereum, Optimism, ZKsync, Base, Blast, Scroll, World Chain, Arbitrum

### Does the wallet allow the user to customize gas fees?

Yes (https://family.co/support/speed-up-a-transaction)

### Does the wallet support sending transactions to ENS addresses?

Yes

### Does the wallet support importing or automatically querying and displaying ERC-20 tokens?

No

### Does the wallet support EIP-1559 (type 2) transactions?

Yes

### Does the wallet have any recovery options?

Family offers various ways for back-ups including the [in-house built Pocket](https://family.co/support/pocket), which allows you to manage various wallets, create encrypted back-ups, etc. 
iCloud back-up is also available.

### Does the wallet have fiat on-ramps through credit/debit cards, wire transfers, or bank transfers (ACH)?

Yes, via Stripe (https://family.co/support/buy-crypto)

### Does the wallet support withdrawals to fiat?

No

### Is the wallet a multi-signature wallet?

No

### Does the wallet support social recovery?

No

### Does the wallet support bundled transactions?

No

### Who can the ethereum.org team can contact regarding the wallet in future?

Maria Paula Fernandez (mp@avara.xyz)

### Does the wallet have a dedicated support team?

Yes, we offer e-mail support. It takes about 5 hours to answer: support@family.co

### What educational resources/documentation do you provide to users?

We have a comprehensive help center and the app provides education in pop-ups: https://family.co/support

### Does the wallet have any integrated tools not mentioned above?

- MEV protection via Flashbots
- "Refuel" function: quickly top up your gas on all L2s supported
- Encrypted wallet-to-wallet chat via XMTP
- View NFTs in media rich format and gallery mode
- Pocket back-up and onboarding 
- Wallet Groups
- Browser 
- Approval management
- Token hide/view functions
- Spam token filters
- Stealth mode 

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

- [x] Yes
- [ ] No

wallet 👛

dev required

product 🧰

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

ethereum-org-website

Markdown

Add Family Wallet

performance

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

linea-specification

Use IOMF/DONE for  WCP  instead of STAMP

Vertx has deprecated HttpClient.webSocket() methods
it's now a separate class - https://vertx.io/docs/guides/vertx-5-migration-guide/

Refactor EthStatsService and EthStatsServiceTest to use the new class
```
> Task :ethereum:ethstats:compileJava
Note: /workspace/b2/ethereum/ethstats/src/main/java/org/hyperledger/besu/ethstats/EthStatsService.java uses or overrides a deprecated API.
```

Acceptance criteria:
* no deprecation warnings when compiling this module

techdebt

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

besu

Java

Refactor EthStatsService creation of WebSocket

### What happened?

called `event.get_logs(from_block=from_block, to_block=block_current)` with the instantiated parent contract having `address` set to a list of addresses. 

This raised an exception about address validity. It shouldn't have.

### Code that produced the error

```python
contract = contract_factory.ServiceNodeContribution(address[0])
NewContribution = contract.events.NewContribution
NewContribution.address = address
for recent in await NewContribution.get_logs(from_block=from_block, to_block=block_current):
    print(recent)
```

### Full error output

```shell
Traceback (most recent call last):
  File "src/app_events.py", line 19, in <module>
    init_ws_event_scanner(config)
  File "/home/aerilym/git/ssb/src/web3client/event_ws.py", line 516, in init_ws_event_scanner
    asyncio.run(start(config))
  File "/usr/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/aerilym/git/ssb/src/web3client/event_ws.py", line 512, in start
    await monitor
  File "/home/aerilym/git/ssb/src/web3client/event_ws.py", line 472, in monitor_events
    await scan_past_queued_events(w3)
  File "/home/aerilym/git/ssb/src/web3client/event_ws.py", line 420, in scan_past_queued_events
    for recent in await past_event.event.get_logs(from_block=from_block, to_block=block_current):
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/aerilym/git/sent-staking-backend/.venv/lib/python3.12/site-packages/web3/contract/async_contract.py", line 181, in get_logs
    _filter_params = self._get_event_filter_params(
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/aerilym/git/sent-staking-backend/.venv/lib/python3.12/site-packages/eth_utils/decorators.py", line 29, in _wrapper
    return self.method(obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/aerilym/git/sent-staking-backend/.venv/lib/python3.12/site-packages/web3/contract/base_contract.py", line 311, in _get_event_filter_params
    _, event_filter_params = construct_event_filter_params(
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/aerilym/git/sent-staking-backend/.venv/lib/python3.12/site-packages/web3/_utils/filters.py", line 117, in construct_event_filter_params
    for addr in filter_params["address"]:
        ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/aerilym/git/sent-staking-backend/.venv/lib/python3.12/site-packages/web3/_utils/validation.py", line 179, in validate_address
    raise Web3TypeError(f"Address {value} must be provided as a string")
web3.exceptions.Web3TypeError: Address ['0xdA5ba...6763e', '0xFC7880C60...2295122F', '0x36eeDdB5...a71a0698E5B462f299Dec', '0xC212293A2d8255...813cC3FDd7a3ee'] must be provided as a string
```

### Fill this section in if you know how this could or should be fixed

This suggestion is implemented in #3618 

This method internally calls `_get_event_filter_params` which calls `construct_event_filter_params` as such:
contract/base_contract.py:308
```py
_, event_filter_params = construct_event_filter_params(
            abi,
            self.w3.codec,
            contract_address=self.address,
            argument_filters=_filters,
            from_block=from_block,
            to_block=to_block,
            address=self.address,
        )
``` 
By setting `contract_address` and `address` to `self.address` the following code block in `construct_event_filter_params` is executed:
_utils/filters.py:97
```py
if address and contract_address:
        if is_list_like(address):
            filter_params["address"] = [address] + [contract_address]
```

This then causes this later block to raise an exception:
```py
    if "address" not in filter_params:
        pass
    elif is_list_like(filter_params["address"]):
        for addr in filter_params["address"]:
            validate_address(addr)
    else:
        validate_address(filter_params["address"])
```

As `is_list_like` is true, but `filter_params["address"]` has been incorrectly turned into a list of lists:
```py
filter_params["address"] = [["0x...","0x..."]] + ["0x...","0x..."]
```

The simplest fix is to correct `_utils/filters.py:97` to create a list instead of a list of lists, this should probably be de-duplicated because in the code path I'm using above `address` and `contract_address` are the same. (Not sure if this should be the case)

### web3 Version

7.8.0

### Python Version

3.12.3

### Operating System

linux

### Output from `pip freeze`

```shell
aiodns==3.1.1
aiohappyeyeballs==2.4.4
aiohttp==3.10.11
aiosignal==1.3.1
annotated-types==0.7.0
async-timeout==4.0.3
attrs==24.2.0
bitarray==3.0.0
black==24.8.0
blinker==1.7.0
certifi==2023.11.17
cffi==1.17.1
chardet==5.2.0
charset-normalizer==3.3.2
ckzg==2.0.1
click==8.1.7
colorama==0.4.6
coloredlogs==15.0.1
cryptography==40.0.2
cytoolz==1.0.1
distro==1.9.0
eth-account==0.13.4
eth-hash==0.7.0
eth-keyfile==0.8.1
eth-keys==0.6.1
eth-rlp==2.1.0
eth-typing==5.0.0
eth-utils==5.0.0
eth_abi==5.1.0
Flask==3.0.3
frozenlist==1.5.0
hexbytes==1.2.1
humanfriendly==10.0
idna==3.8
iniconfig==2.0.0
itsdangerous==2.1.2
Jinja2==3.1.4
MarkupSafe==2.1.5
multidict==6.1.0
mypy-extensions==1.0.0
oxenc @ file:///home/aerilym/git/ssb/dep-tmp/oxenc
oxenmq @ file:///home/aerilym/git/ssb/dep-tmp/oxenmq
packaging==23.2
parsimonious==0.10.0
pathspec==0.12.1
pillow==10.2.0
platformdirs==4.2.2
pluggy==1.5.0
propcache==0.2.1
protobuf==4.21.12
psycopg==3.2.4
psycopg-pool==3.2.4
py-solc-x==2.0.3
pycares==4.5.0
pycparser==2.22
pycryptodome==3.21.0
pycryptodomex==3.20.0
pydantic==2.9.2
pydantic_core==2.23.4
PyNaCl==1.5.0
pyOpenSSL==23.2.0
pytest==8.3.4
pyunormalize==16.0.0
regex==2024.9.11
requests==2.32.3
rlp==4.0.1
setuptools==68.1.2
simplejson==3.19.3
toolz==1.0.0
types-requests==2.32.0.20240905
typing_extensions==4.10.0
urllib3==2.0.7
uWSGI==2.0.28
web3==7.8.0
websockets==13.1
Werkzeug==3.0.4
wheel==0.42.0
yarl==1.16.0
```

Good First Issue

priority: p4 nice to have

A python interface for interacting with the Ethereum blockchain and ecosystem.

web3.py

Python

construct_event_filter_params improperly formats addresses as lists of lists

E.g., while this compiles:
```sway
library;

fn fun() {
    struct S {
        field: u8,
    }

    const CONST: u8 = 0;
}
```
trying to attribute or comment nested items will result in "Expected an expression." error on every doc comment or attribute:
```sway
library;

fn fun() {
    /// Comment.             // <<<--- ERROR: Expected an expression.
    #[allow(dead_code)]      // <<<--- ERROR: Expected an expression.
    struct S {
        /// Comment.         // <<<--- ERROR: Expected an expression.
        #[allow(dead_code)]  // <<<--- ERROR: Expected an expression.
        field: u8,
    }

    /// Comment.             // <<<--- ERROR: Expected an expression.
    #[allow(dead_code)]      // <<<--- ERROR: Expected an expression.
    const CONST: u8 = 0;
}
```

compiler

P: low

compiler: frontend

compiler: parser

team:compiler

ODHack12

🌴 Empowering everyone to build reliable and efficient smart contracts.

sway

Support doc comments and attributes on nested items

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

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

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

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

Tech Design

Tech Task

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

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

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

help wanted

CI/CD

Ubuntu 22.04

indy-plenum

Workflows are failing to publish test reports

Looks like we have a flaky test:

```
--- FAIL: TestSimulatedBeaconSendWithdrawals (12.08s)
    simulated_beacon_test.go:139: timed out without including all withdrawals/txs
FAIL
FAIL	github.com/ethereum/go-ethereum/eth/catalyst	14.812s
ok  	github.com/ethereum/go-ethereum/eth/downloader	41.536s
```

https://ci.appveyor.com/project/ethereum/go-ethereum/builds/51503642/job/4ff083bblgggkpm8

Go implementation of the Ethereum protocol

go-ethereum

Flaky test

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

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

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

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

indy-node

Remove obsolete `dev-setup` documentation

At the moment, it's not possible to easily deploy a contract which requires a different solidity version than the one used by the medusa tests/fuzzing without hardcoding the bytecode in the file.

Adding the [`vm.getCode` cheatcode](https://book.getfoundry.sh/cheatcodes/get-code) (from Foundry) would allow to dynamically fetch the creation code and we could deploy it with `create`.

medium-priority

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

medusa

Add `vm.getCode` cheatcode

Under PeerDAS, each full node only store a subset of all blob data ("custody data columns"), and these are [computed](https://github.com/sigp/lighthouse/blob/e98209d1186419264868a28591c2b14af3f6abff/consensus/types/src/data_column_custody_group.rs#L21) based on:
1. the node's `NodeId` (generated on first startup)
2. the node's custody group count (this is 4 by default for a full node)

e.g. given a node ID running a full node, it could be a custodian of data column 1, 3, 5, 7

On a restart, if either the node id or custody group count changes (e.g. switching between supernode or full node via the `--subscribe-all-data-column-subnets` flag), its set of custody columns also change, and this would result in a inconsistent data column DB - similar to switching between an archive node and non-archive node.

This means the node would not be able to serve data columns that it's expected to store, and may result in the node getting downscored by all peers. 

## Proposed Solution

Handling custody column changes are likely quite complex, and might be easier and quicker to resync from scratch.

We could persist the custody info in the DB and perform an integrity check on startup to see if the newly computed custody columns matches what's in the database.

If it doesn't match the DB, exit the process and inform the user to re-sync instead.

Note: we may need end up storing this info as part of validator custody (#6767), and we should be able to use the same info from the DB for both features.

database

fulu

lighthouse

Perform integrity check on custody columns against database on startup

For PeerDAS devnet testing, we're starting have stable devnets and looking to start doing some unhappy case testing. 

We already have `--malicious-withhold-count`, which allows the proposer to withhold a specified number of data columns during block publishing. It would be useful to have a flag that withholds custody columns over RPC too, for scenarios like:
1. A proposer uses `--malicious-withhold-count` to withhold some data columns - this may trigger a data column by root request from the mesh peer, and we could make the proposer not serve this requqest and force them to get it via alternatives like distributed blob building and column reconstruction - this would help us test the effectiveness of the solutions
2. A node pretends to be a supernode in the network but don't actually serve the data
 
## Proposed solution

Instead of touching all the RPC code paths to withhold data columns, we could simply have a CLI flag `--advertise-false-custody-group-count`, that just advertise a fake custody group count, and make peers think the node custodies more columns - that way we don't have to touch any RPC logic. The node just won't serve data they don't have.

This flag should be a hidden flag and clearly states it's for testing only and should NOT be used in production.

low-hanging-fruit

Add a beacon node flag to advertise a false custody group count for testing

This vector: 
- [ ] https://github.com/ethereum/tests/blob/develop/src/GeneralStateTestsFiller/stEIP1559/intrinsicGen.js

is no longer can be supported on Prague. we need to convert it to .py or verify that existing .py tests already cover this case

- [ ] https://github.com/ethereum/tests/blob/develop/src/GeneralStateTestsFiller/stEIP1559/intrinsicFiller.yml

- [ ] https://github.com/ethereum/tests/blob/develop/src/BlockchainTestsFiller/InvalidBlocks/bcEIP1559/intrinsicOrFailFiller.yml


I put the issue here because I disable this test for Prague in ethereum/tests
it is too difficult to make a Prague version of it in json format so it worth to reimplement it in python directly. 


related test:
- [ ] https://github.com/ethereum/tests/blob/develop/src/BlockchainTestsFiller/ValidBlocks/bcEIP1559/intrinsicTipFiller.yml
- [ ] https://github.com/ethereum/tests/blob/develop/src/BlockchainTestsFiller/ValidBlocks/bcEIP1559/intrinsicFiller.yml

fork:prague

port

A Python framework and collection of test cases to generate test vectors for Ethereum execution clients

execution-spec-tests

Convert to Prague intrinsic gas test

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

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

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

## Remaining endpoints to check

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


Refactor

juno

Cleanup rpc pkg

There are new spec tests added to Fulu as part of the `1.5.0-beta.2` spec tests, they've been ignored for the time being as we're preparing for a release. Some skipped tests include `random`, `sanity_blocks` etc for Fulu.

The tests need to be updated to cover these.

Update Fulu spec tests to spec `1.5.0-beta.2`

It is definitely a burden to migrate a config file when a new release is made. It would be nice to have a `medusa migrate` command line option that takes an input config file and tries to map it to the new configuration for the new release.

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity