
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


More and more DeFi projects on Ethereum are getting hacked. This is your chance to join the party.

Each challenge can be considered standalone. Depending on the challenge, you should either stop the system from working, steal as much funds as you can, or do some other unexpected things.

Put your black hat on, and break some DeFi projects on Ethereum!

Damn Vulnerable DeFi


This is an interactive tutorial website for learning Vyper while building games using smart contracts, similar to Cryptozombies.

VyperFun


Blockchain is an exciting new discipline in Computer Science. It combines a wide array of skills from math and cryptography to social sciences and understanding organizations. Understanding blockchain decentralization and how/where to apply it is a brand new skill that very few have mastered.

You will build your skills from the ground up with strong fundamentals that will provide you with the ability to adapt in this rapidly evolving ecosystem.

Choose From Multiple Paths to Begin Your Ethereum Coding Journey.

Fast-track your Ethereum Developer career in an instructor-led and challenging bootcamp focused on discussion and application!

ChainShot


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 pratical 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


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

Free resources to learn about Zero Knowledge Proofs (ZKPs) and Cryptography

Road to ZK


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


Nowadays there are countless well-made resources on how to learn blockchain development of all kinds and with different specializations in mind, however, it is still very hard to get guidance and personalized suggestions based on your interests. I am writing this guide in order to provide an aggregator of all the resources that I’ve found over the years, plus give some opinionated commentary on how to approach them and how to use them in order to maximize learning and practical understanding in order to get building cool things in the space as soon as possible.

This guide will focus on the Ethereum ecosystem as that’s where most developers and applications are. If you are interested in other ecosystems that are non-EVM compatible and are not L2s on Ethereum, then check out their respective documentation or guides written by their developer communities. Examples of other non-EVM compatible blockchains that are popular are Solana (Rust/Anchor), Polkadot (Rust/Substrate), Cosmos, Terra, and others. Most of these blockchains do or will support the EVM stack through various initiatives like Neon EVM (Solana), Moonbeam/Moonriver (Polkadot/Kusama), EVMOS (Cosmos), etc.

I really want this guide to become a community-sourced public good that everyone will be able to take advantage of. I will do my best to present it to the wider blockchain developer community to get constructive feedback, proofreading help, and insight into how to make it the best available guide available.

devpill.me


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

### What is wrong?

A number of functions defined in [std::evm](https://github.com/ethereum/fe/blob/master/crates/library/std/src/evm.fe) take offsets and lengths for regions of memory and calldata. These should take [buffer](https://github.com/ethereum/fe/blob/master/crates/library/std/src/buf.fe) types instead.

### How can it be fixed

- implement `CalldataBuffer`, `CalldataBufferReader`
- update `revert_mem`, `return_mem`, `call_data_copy`, `code_copy`, `ext_code_copy`, `keccak256_mem`, `create`, `create2`, `call`, and `log` 

run `$ cargo test std_lib` to check changes made to `crates/library`

good first issue

comp: std-lib

Emerging smart contract language for the Ethereum blockchain.

Rust

`std::evm` functions should take buffer types

It would be useful for debugging to see the cheat code calls in traces. 

For inspiration, this is how it looks in Foundry: https://book.getfoundry.sh/forge/cheatcodes.

enhancement

hevm

Haskell

Cheatcodes are missing from traces

### Describe the desired feature

The log panel is great but it can get in the way while debugging. It would be nice to have a toggle to hide it.

While you're at it, maybe also add a toggle for the tests panel in case someone wants to inspect the logs? :slightly_smiling_face: 

echidna

Solidity

Toggle Log panel with 'L' key

### Description
Modify [ethstats option](https://besu.hyperledger.org/en/stable/public-networks/reference/cli/options/?h=ethstats#ethstats) so that it can optionally take ws or wss to specify if it wants to use ssl or plain websocket connection. This will override the current behavior of switching between ssl and non-ssl between retry connections.

### Acceptance Criteria
* ethstats value can take ws and wss://
* If protocol is not specified in URI, keep the current logic i.e. try to connect to plain websocket, then to secure websocket.
* Update relevant unit/AT.

TeamGroot

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

besu

Java

Optionally specify ws:// or wss:// to Ethstats connection url

A lot of tests in https://github.com/NethermindEth/warp/blob/develop/tests/behaviour/expectations/behaviour.ts use plain arrays to express uint256 as input/output. It should be changed to use `toCairoUint256` helper function 

Warp - Bringing Solidity to Starknet at warp speed. Warp is a Solidity to Cairo Compiler, this allows teams to write/migrate Solidity to Cairo for easy onboarding into the StarkNet ecosystem.

warp

TypeScript

Use `toCairoUint256` in tests

Include base RPC endpoints for the State network in `ethportal-api`. [Here](https://github.com/ethereum/trin/blob/master/ethportal-api/src/history.rs) is a history network example of what we also want to implement for the State at this stage.

An Ethereum portal client: a json-rpc server with nearly instant sync, and low CPU & storage usage

trin

ethportal-api: Add base RPC endpoints for State network

Consider updating the MyGovernor snippet on:
https://docs.openzeppelin.com/contracts/4.x/governance

The snippet is missing some mandatory function overrides.

documentation

OpenZeppelin Contracts is a library for secure smart contract development.

openzeppelin-contracts

JavaScript

Fix docs snippets that don't compile

https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/math/Math.sol

The `mulDiv` assembly is memory safe, but is not marked as such. This will cause the Solidity compiler to be more conservative than necessary when optimising code that includes `mulDiv`.

I don't have any data, but as `mulDiv` is fairly low level math, it's probably safe to assume it's included in a lot of contracts downstream and quietly breaking optimisations for people without them realising it.

https://docs.soliditylang.org/en/v0.8.13/assembly.html#memory-safety
https://github.com/OpenZeppelin/openzeppelin-contracts/issues/3336

The assembly in mulDiv is not marked as memory safe

### Component

Cast

### Have you ensured that all of these are up to date?

- [X] Foundry
- [X] Foundryup

### What version of Foundry are you on?

forge 0.2.0 (31fcf5a 2023-05-19T00:10:33.861185000Z)

### What command(s) is the bug in?

cast --abi-decode 

### Operating System

None

### Describe the bug

Currently, `cast --abi-decode --input` behaves identically to `cast --calldata-decode`, in that both expect a function signature. However, I propose a change in this behavior for consistency and clearer distinction between the two. 

In the same way as `cast abi-encode` excludes the selector in its output, while `cast calldata` includes it, I suggest `cast --abi-decode --input` should also not expect the selector in its input. This contrasts with `cast --calldata-decode` that would continue to expect the selector. I believe this change would provide a more intuitive and consistent user experience across these commands. Thoughts?

T-bug

C-cast

Foundry is a blazing fast, portable and modular toolkit for Ethereum application development written in Rust.

foundry

--abi-decode --input should behave as the complement to abi-encode 

# 💎 Issue

### Background

In #12150 , we disabled our slasher e2e run as the evaluators were broken and all our test runs were failing continuously. This issue is to track the eventual re-enabling of it. As without the e2e run, issues such as #12404 end up being undetected until its too late. 

Help Wanted

Good First Issue

E2E Tests

Go implementation of Ethereum proof of stake

prysm

Re-enable Slasher E2E Test

### Description
Migrate `BannerBase` component  in `ui/components/component-library` to TypeScript

### Technical Details

- Convert Objects in `SNAKE_CASE` to enums in `PascalCase` (name and keys)
- Ensure enums use singular not plural e.g. `Size` not `Sizes`
- Update file name from `component-name.contants.js` to `component-name.types.ts` and add types
- Update file name from `component-name.js` to `component-name.tsx` and add types
- Update file name from `component-name.test.js` to `component-name.test.tsx`
- Update file name from `component-name.stories.js` to `component-name.stories.tsx`
- Update all instances of component objects to enums
- Update all documentation

### Acceptance Criteria

- Component has been converted to TypeScript
- Stories, documentation and tests have been updated inside of the `component-name` folder
- Before/After screen cast of component stories in storybook to show no visual regression after migration

### Difficulty: Intermediate

Good first issue for: External contributors who are familiar with TypeScript and want to contribute to improving the stability of the extension


design-system

:globe_with_meridians: :electric_plug: The MetaMask browser extension enables browsing Ethereum blockchain enabled websites

metamask-extension

Migrate components to TS: BannerBase

to reproduce: `besu -h`
Expected output - all the tx-pool options together
Actual (extract from) output - two groups of tx-pool options
```
      --tx-pool-disable-locals[=<Boolean>]
                             Set to true if transactions sent via RPC should
                               have the same checks and not be prioritized over
                               remote ones (default: false)
      --tx-pool-enable-save-restore[=<Boolean>]
                             Set to true to enable saving the txpool content to
                               file on shutdown and reloading it on startup
                               (default: false)
      --tx-pool-limit-by-account-percentage=<DOUBLE>
                             Maximum portion of the transaction pool which a
                               single account may occupy with future
                               transactions (default: 0.001)
      --tx-pool-save-file=<STRING>
                             If saving the txpool content is enabled, define a
                               custom path for the save file (default: txpool.
                               dump in the data-dir)
  -V, --version              Print version information and exit.
...
Tx Pool Options
      --tx-pool-max-size=<INTEGER>
                             Maximum number of pending transactions that will
                               be kept in the transaction pool (default: 4096)
      --tx-pool-price-bump=<INTEGER>
                             Price bump percentage to replace an already
                               existing transaction  (default: 10)
      --tx-pool-retention-hours=<INTEGER>
                             Maximum retention period of pending transactions
                               in hours (default: 13)
```

TeamRevenant

snack

Besu help - unite the tx-pool CLI options

`RwTableTag` is replaced by `Target` in the circuit PR https://github.com/privacy-scaling-explorations/zkevm-circuits/pull/1406

We should rename `RwTableTag` to Target for consistency.

 https://github.com/search?q=repo%3Aprivacy-scaling-explorations%2Fzkevm-specs%20RwTableTag&type=code

_Originally posted by @ed255 in https://github.com/privacy-scaling-explorations/zkevm-circuits/pull/1406#pullrequestreview-1428203917_
            

zkevm-specs

Python

Rename all instances of RwTableTag by Target

## Description

As part of implementation of https://github.com/ConsenSys/scribble/pull/224, there is a request to introduce function to check if arbitrary expression is ABI-encodable.  The feature would help to do sanity check for source fragments, that can be wrapped by an `abi.encode()` call.

## Context

See [the related behavior](https://github.com/ethereum/solidity/blob/0a0c389541c0f247691951edd64451be7145436c/libsolidity/ast/Types.cpp#L314-L339) is of Solidity compiler. Feature most likely would require adding new method to `InferType`, that accepts `TypeNode`.

A TypeScript package providing a normalized typed Solidity AST along with the utilities necessary to generate the AST (from Solc) and traverse/manipulate it.

solc-typed-ast

Introduce function to check that TypeNode is ABI-encodable

- Move functions (and anything else that needs to come with it) 
```
set_requested_attributes_as_string
set_requested_predicates_as_string
```
from
```
aries_vcx/src/common/proofs/proof_request.rs
```
to `libvcx_core`.

- You will also have to updated tests using these functions in aries-vcx integration tests

# Reasoning
These functions perform 2 tasks currently:
- parse JSON formatted arguments
- support 2 formats of JSONs (one of which is deprecated), see comments on those functions. 

The structure `ProofRequestData` is core part of of aries-vcx and the logic described does not belong there. `ProofRequestData` should only deal with the final format, which is the format it stores in its attributes `requested_attributes: HashMap<String, AttrInfo>`, `requested_predicates: HashMap<String, PredicateInfo>`

# Important
Please start working on top of https://github.com/hyperledger/aries-vcx/pull/844 PR branch (if was not yet merged into `main`)



AriesVCX is a Rust library for building web and mobile applications issuing, holding, presenting and verifying Verifiable Credentials in accordance to the standards set by Hyperledger Aries.

aries-vcx

Move string parsing to libvcx_core

Add a LTO build to CI. We can check the performance of Release vs Release+LTO builds but previously difference where neglectable.
However, LTO build can reveal some C++ bugs.

In CMake IPO can be enabled with [`INTERPROCEDURAL_OPTIMIZATION`](https://cmake.org/cmake/help/latest/prop_tgt/INTERPROCEDURAL_OPTIMIZATION.html) property. The Hunter controlled dependencies should be build with IPO enabled too therefore a CMake toolchain file must be used.

build

Fast Ethereum Virtual Machine implementation

evmone

CI: Add a LTO/IPO build

### Component

Anvil

### Have you ensured that all of these are up to date?

- [X] Foundry
- [X] Foundryup

### What version of Foundry are you on?

anvil 0.1.0 (58a2729 2023-05-14T00:16:26.315435000Z)

### What command(s) is the bug in?

anvil

### Operating System

macOS (Apple Silicon)

### Describe the bug

If you use `localhost:8545` as a constant in Node.js code, it will fail because [Node.js now prefers IPv6](https://github.com/nodejs/node/issues/40537). The workaround for this is simple, just use `127.0.0.1:8545` for all constants. But I worry new developers may not be able to figure this out. Maybe it's also not as modern / future-proof. FWIW [geth listens on both IPv4 and IPv6](https://github.com/ethereum/go-ethereum/issues/19174).

(I actually regret filing this as a bug, should be a feature request)

An amusing workaround for GitHub Actions specifically is
```
      - name: Remove IPv6 localhost
        run: sudo sed -i 's/localhost ip6/ip6/' /etc/hosts
```
(it's funny because if you `cat /etc/hosts` you see a bunch of BTC mining websites)
^if you do this then `localhost:8545` in Node.js on GitHub Actions works fine.

C-anvil

`anvil`: listen on ipv6

### Description
Migrate `TextFieldSearch` component  in `ui/components/component-library` to TypeScript

Dependencies
- https://github.com/metamask/metamask-extension/issues/19122

### Technical Details

- Convert Objects in `SNAKE_CASE` to enums in `PascalCase` (name and keys)
- Ensure enums use singular not plural e.g. `Size` not `Sizes`
- Update file name from `component-name.contants.js` to `component-name.types.ts` and add types
- Update file name from `component-name.js` to `component-name.tsx` and add types
- Update file name from `component-name.test.js` to `component-name.test.tsx`
- Update file name from `component-name.stories.js` to `component-name.stories.tsx`
- Update all instances of component objects to enums
- Update all documentation

### Acceptance Criteria

- Component has been converted to TypeScript
- Stories, documentation and tests have been updated inside of the `component-name` folder
- Before/After screen cast of component stories in storybook to show no visual regression after migration

### Difficulty: Intermediate

Good first issue for: External contributors who are familiar with TypeScript and want to contribute to improving the stability of the extension


Migrate components to TS: TextFieldSearch

### Description
Migrate `TextField` component  in `ui/components/component-library` to TypeScript

Dependencies
- https://github.com/metamask/metamask-extension/issues/19122

### Technical Details

- Convert Objects in `SNAKE_CASE` to enums in `PascalCase` (name and keys)
- Ensure enums use singular not plural e.g. `Size` not `Sizes`
- Update file name from `component-name.contants.js` to `component-name.types.ts` and add types
- Update file name from `component-name.js` to `component-name.tsx` and add types
- Update file name from `component-name.test.js` to `component-name.test.tsx`
- Update file name from `component-name.stories.js` to `component-name.stories.tsx`
- Update all instances of component objects to enums
- Update all documentation

### Acceptance Criteria

- Component has been converted to TypeScript
- Stories, documentation and tests have been updated inside of the `component-name` folder
- Before/After screen cast of component stories in storybook to show no visual regression after migration

### Difficulty: Intermediate

Good first issue for: External contributors who are familiar with TypeScript and want to contribute to improving the stability of the extension


Migrate components to TS: TextField

### Description
Migrate `TagUrl` component  in `ui/components/component-library` to TypeScript

### Technical Details

- Convert Objects in `SNAKE_CASE` to enums in `PascalCase` (name and keys)
- Ensure enums use singular not plural e.g. `Size` not `Sizes`
- Update file name from `component-name.contants.js` to `component-name.types.ts` and add types
- Update file name from `component-name.js` to `component-name.tsx` and add types
- Update file name from `component-name.test.js` to `component-name.test.tsx`
- Update file name from `component-name.stories.js` to `component-name.stories.tsx`
- Update all instances of component objects to enums
- Update all documentation

### Acceptance Criteria

- Component has been converted to TypeScript
- Stories, documentation and tests have been updated inside of the `component-name` folder
- Before/After screen cast of component stories in storybook to show no visual regression after migration

### Difficulty: Intermediate

Good first issue for: External contributors who are familiar with TypeScript and want to contribute to improving the stability of the extension


Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity