
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

Ref https://github.com/foundry-rs/foundry/issues/2477

add more examples how to use test matchers like `forge t --match-path`

T-enhancement

good first issue

A-forge

A-reference

A book on all things Foundry, available at https://book.getfoundry.sh.

book

Solidity

Add more forge test filter examples

### Which Caliper version are you using?

V0.2.0

### Which Node.JS version are you using?

v8

### Which operating system are you using?

Ubuntu22.04

### Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?

I tried to use the stress test guide in the official fisco-bcos documentation to test the performance of bcos. After deployment, an error occurred.
https://fisco-bcos-documentation.readthedocs.io/zh_CN/v2.8.0/docs/tutorial/stress_testing.html
2.1-2.2

### What was the observed incorrect behavior?

![image](https://user-images.githubusercontent.com/71952068/180732486-8d69735e-0d88-424c-9b88-2dc0cc2ff019.png)
![image](https://user-images.githubusercontent.com/71952068/180732532-af68a6ed-9e9f-411d-a520-93701d4532ab.png)
![image](https://user-images.githubusercontent.com/71952068/180735199-7b48c05d-1ae6-43f2-b65f-7583df1db7a3.png)



### Please provide the error logs and their surroundings.

```text
node0 log information：
error|2022-07-25 16:22:46.537263|[NETWORK][Host]TCP Connection refused by node,endpoint=172.17.0.1:30915,message=Connection refused
warning|2022-07-25 16:22:46.537322|[P2P][Service] onConnect,errorCode=5,nodeID=00000000...,nodeName=,endpoint=unknown,what=Connect failed
error|2022-07-25 16:22:46.537334|[NETWORK][Host]TCP Connection refused by node,endpoint=172.17.0.1:30916,message=Connection refused
warning|2022-07-25 16:22:46.537350|[P2P][Service] onConnect,errorCode=5,nodeID=00000000...,nodeName=,endpoint=unknown,what=Connect failed
error|2022-07-25 16:22:46.537380|[NETWORK][Host]TCP Connection refused by node,endpoint=172.17.0.1:30917,message=Connection refused
```


### Please provide your benchmark configuration file content, if possible.
config.yaml
```yaml
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

---
test:
  name: Hello World
  description: This is a helloworld benchmark of FISCO BCOS for caliper
  clients:
    type: local
    number: 1
  rounds:
    - label: get
      description: Test performance of getting name
      txNumber:
        - 10000
      rateControl:
        - type: fixed-rate
          opts:
            tps: 1000
      callback: benchmarks/samples/fisco-bcos/helloworld/get.js
    - label: set
      description: Test performance of setting name
      txNumber:
        - 10000
      rateControl:
        - type: fixed-rate
          opts:
            tps: 1000
      callback: benchmarks/samples/fisco-bcos/helloworld/set.js
monitor:
  type:
    - docker
    - process
  docker:
    name:
      - all
  process:
    - command: node
      arguments: fiscoBcosClientWorker.js
      multiOutput: avg
  interval: 0.5
```


### Please provide your network configuration file content, if possible.
docker-compose.yaml
```yaml
version: "3"

services:
  node0:
    image: fiscoorg/fiscobcos:latest
    ports:
      - "20914:20914"
      - "8914:8914"
      - "30914:30914"
    working_dir: /data
    volumes:
      - ./node0:/data
    container_name: node0
    command: /usr/local/bin/fisco-bcos -c config.ini

  node1:
    image: fiscoorg/fiscobcos:latest
    ports:
      - "20915:20915"
      - "8915:8915"
      - "30915:30915"
    working_dir: "/data"
    volumes:
      - ./node1:/data
    container_name: node1
    command: /usr/local/bin/fisco-bcos -c config.ini
    depends_on:
      - "node0"

  node2:
    image: fiscoorg/fiscobcos:latest
    ports:
      - "20916:20916"
      - "8916:8916"
      - "30916:30916"
    working_dir: "/data"
    volumes:
      - ./node2:/data
    container_name: node2
    command: /usr/local/bin/fisco-bcos -c config.ini
    depends_on:
      - "node1"

  node3:
    image: fiscoorg/fiscobcos:latest
    ports:
      - "20917:20917"
      - "8917:8917"
      - "30917:30917"
    working_dir: "/data"
    volumes:
      - ./node3:/data
    container_name: node3
    command: /usr/local/bin/fisco-bcos -c config.ini
    depends_on:
      - "node2"

```
fisco-bcos.json
```json
{
  "caliper": {
    "blockchain": "fisco-bcos",
    "command": {
      "start": "docker-compose -f networks/fisco-bcos/4nodes1group/docker-compose.yaml up -d; sleep 3s",
      "end": "docker-compose -f networks/fisco-bcos/4nodes1group/docker-compose.yaml down"
    }
  },
  "fisco-bcos": {
    "config": {
      "privateKey": "bcec428d5205abe0f0cc8a734083908d9eb8563e31f943d760786edf42ad67dd",
      "account": "0x64fa644d2a694681bd6addd6c5e36cccd8dcdde3"
    },
    "network": {
      "nodes": [
        {
          "ip": "127.0.0.1",
          "rpcPort": "8914",
          "channelPort": "20914"
        },
        {
          "ip": "127.0.0.1",
          "rpcPort": "8915",
          "channelPort": "20915"
        },
        {
          "ip": "127.0.0.1",
          "rpcPort": "8916",
          "channelPort": "20916"
        },
        {
          "ip": "127.0.0.1",
          "rpcPort": "8917",
          "channelPort": "20917"
        }
      ],
      "authentication": {
        "key": "/home/augety/fisco/benchmarks/caliper-benchmarks/networks/fisco-bcos/4nodes1group/sdk/node.key",
        "cert": "/home/augety/fisco/benchmarks/caliper-benchmarks/networks/fisco-bcos/4nodes1group/sdk/node.crt",
        "ca": "/home/augety/fisco/benchmarks/caliper-benchmarks/networks/fisco-bcos/4nodes1group/sdk/ca.crt"
      },
      "groupID": 1,
      "timeout": 100000
    },
    "smartContracts": [
      {
        "id": "helloworld",
        "path": "src/fisco-bcos/helloworld/HelloWorld.sol",
        "language": "solidity",
        "version": "v0"
      },
      {
        "id": "parallelok",
        "path": "src/fisco-bcos/transfer/ParallelOk.sol",
        "language": "solidity",
        "version": "v0"
      },
      {
        "id": "dagtransfer",
        "address": "0x0000000000000000000000000000000000005002",
        "language": "precompiled",
        "version": "v0"
      }
    ]
  },
  "info": {
    "Version": "2.0.0",
    "Size": "4 Nodes",
    "Distribution": "Single Host"
  }
}

```

### Please provide your workload module content, if possible.



### Please provide any additional information you deem relevant to the error.

I use VMware Workstation to configure Ubuntu22.04 virtual machine.

help wanted

component/fisco

 A blockchain benchmark framework to measure performance of multiple blockchain solutions https://wiki.hyperledger.org/display/caliper

caliper

JavaScript

I had some problems testing the Fisco-bcos with calipers

While we were developing the backend of the Cello project, we didn't put much effort into structuring log information, which would be a painful technical debit in terms of maintainability and testability. We want to refine our log events for every error handling.  Ultimately, we will achieve good observabilities and will be beneficial for long-term development.   There is an example of PR we did for this task.  #465



Operating System for Enterprise Blockchain

cello

Python

Improve log observability of backend. 

### Component

Anvil

### Have you ensured that all of these are up to date?

- [X] Foundry
- [X] Foundryup

### What version of Foundry are you on?

latest

### What command(s) is the bug in?

_No response_

### Operating System

macOS (Apple Silicon)

### Describe the bug

Many nodes (hardhat, ganache) will work with ill-formatted RPC requests and will assume that they are dealing with JSON data. For example:

```
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' http://127.0.0.1:8545
```

Works with hardhat node, but anvil will throw:

```
{"jsonrpc":"2.0","id":null,"error":{"code":-32600,"message":"Invalid request"}}
```

My suggestion would be to either:
1. Improve error message (wrong content-type?)
2. Assume it's JSON and make it work anyway.

I can work on a fix if you all agree this is a good idea.

T-bug

C-anvil

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

foundry

Rust

Assume json content type

### Component

Forge

### Describe the feature you would like

## Issue
`forge inspect <ContractName> abi` only prints a json formatted abi. 

That wouldn't be an issue, if it were possible to easily pipe the output to `jq` however the warnings printed at the beginning of the output prevent that work working. 

## Suggested Feature

A `--pretty` formatting (similar to what's available for `storageLayout`) of the output would be great to have.

### Additional context

Current output looks like this (I see now that the warnings are pretty easy to resolve):

```shell
$ forge inspect --pretty L1CrossDomainMessenger abi
warning: Unknown section [ci] found in foundry.toml. This notation for profiles has been deprecated and may result in the profile not being registered in future versions. Please use [profile.default] instead or run `forge config --fix`.
warning: Unknown section [default] found in foundry.toml. This notation for profiles has been deprecated and may result in the profile not being registered in future versions. Please use [profile.default] instead or run `forge config --fix`.
warning: Unknown section [default] found in node_modules/excessively-safe-call/foundry.toml. This notation for profiles has been deprecated and may result in the profile not being registered in future versions. Please use [profile.default] instead or run `forge config --fix`.
[
  {
    "inputs": [
      {
        "internalType": "contract OptimismPortal",
        "name": "_portal",
        "type": "address"
      }
    ],
    ...
```

T-feature

C-forge

P-low

D-easy

Cmd-forge-inspect

Pretty printed ABI from Forge Inspect

Referencing to https://github.com/ConsenSys/gnark-crypto/blob/master/ecc/bn254/fr/mimc/mimc.go

There should be a way to set [mimcNbRounds](https://github.com/ConsenSys/gnark-crypto/blob/master/ecc/bn254/fr/mimc/mimc.go#L29), [seed](https://github.com/ConsenSys/gnark-crypto/blob/master/ecc/bn254/fr/mimc/mimc.go#L30) and [exponent](https://github.com/ConsenSys/gnark-crypto/blob/master/ecc/bn254/fr/mimc/mimc.go#L142) (which is currently set to 5). 
I find that this modularity would help us get more control over the hash. 

I was using the snark to verify on ethereum and the mimc implementation on solidity was using a different seed and exponent value, so I had to change it manually in the go modules which I think is not a great way to do things. 

If I get an idea of how I should implement this issue, I would love to make a PR to solve this. 

Thanks!

gnark-crypto provides elliptic curve and pairing-based cryptography on BN, BLS12, BLS24 and BW6 curves. It also provides various algorithms (algebra, crypto) of particular interest to zero knowledge proof systems.

gnark-crypto

Ability to set seed, number of rounds and exponent in MIMC hash

ready to implement

eipw

Preamble lint to ensure `last-call-deadline` is not in the past

### Component

Forge, Cast, Anvil

### Describe the feature you would like

### Add Examples in CLI

This is from GitHub's CLI, it offers examples as well as a reference back to their documentation. 

Forge/Cast should include this, especially when introducing new CLI arguments/commands

```console
EXAMPLES
  $ gh issue create --title "I found a bug" --body "Nothing works"
  $ gh issue create --label "bug,help wanted"
  $ gh issue create --label bug --label "help wanted"
  $ gh issue create --assignee monalisa,hubot
  $ gh issue create --assignee "@me"
  $ gh issue create --project "Roadmap"

LEARN MORE
  Use 'gh <command> <subcommand> --help' for more information about a command.
  Read the manual at https://cli.github.com/manual
```

### Additional context


part of https://github.com/foundry-rs/foundry/issues/2396

A-docs

C-cast

Feature:  Examples for CLI 

### Component

Forge

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

- [X] Foundry
- [ ] Foundryup

### What version of Foundry are you on?

_No response_

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

_No response_

### Operating System

_No response_

### Describe the bug

Here, we set the balance of `CALLER` and other addresses  to `U256::MAX` to make sure they can execute deploys.
https://github.com/foundry-rs/foundry/blob/7e12adbc30d56174320d12be52f94a34d7405c69/forge/src/runner.rs#L69-L71

A few lines below, we set the balances to the user-specified initial balance.
https://github.com/foundry-rs/foundry/blob/7e12adbc30d56174320d12be52f94a34d7405c69/forge/src/runner.rs#L128-L131

However, `CALLER` is left out of there, so if a fuzz test chooses the `CALLER` address and that test sends ETH to that address, the test reverts with balance overflow.

Proposed fix is to set the `CALLER` balance after L132 to either 0, or to `self.initial_balance`. I believe either should be suitable since `CALLER` isn't used afterwards AFAIK.

This is partially related to #2322 in that I don't think the default balance of an account should ever be kept at `U256::MAX`, so in that PR I'd suggest using the default `self.initial_balance` that's typically used instead.

Cmd-forge-script

Don't keep `CALLER` balance as `U256::MAX`

### Component

Cast

### Describe the feature you would like

We can sign and verify **messages** using `cast wallet sign`, they get the `\x19Ethereum Signed Message:\n` prefix before being hashed. It'd be great to be able to do the same with arbitrary payloads.

This could be used to tinker around with all kinds of signed things:
- ERC-712 messages. Currently there's no way to create or verify a `permit` payload.
- Raw transactions. There's no way to verify an arbitrary supposedly signed transaction. There's also no way to manually build a transaction because it can't be signed.

It's crucial to be able to provide a raw 256-bit payload (hash) to be signed. Being able to provide a payload which needs to be hashed first would be a nice addition, but not necessary, it'd save a call to `cast keccak`.

### Additional context

_No response_

Sign and verify arbitrary payloads

component/besu

Failed round 1 (open): Error: Error: connection not open on send()

Like the title says - there was an accident where we merged pr that passed tests into main with a wrong tool path. We should write a test that checks if the page doesn't throw a 404 at us. 

enhancement

A handy toolset for every Ethereum developer ⚒️

dethtools

TypeScript

Add tests for the tool tree component

### Summary

After submitting the form using the default "submit" button the submit button is disabled and and cannot be resubmitted. On one hand this is good to prevent double submission, but on the other hand if the request fails- like invalid password on login- there is currently no way to reset the form state so it can be submitted again.

### Steps to reproduce

1. Create a form with the default "Submit" button
2. Fill out the form and press submit

### Current Behaviour

The Submit button is permanently disabled and cannot be resubmitted

### Expected Behaviour

If the request fails there should be a way to clear the form state so the form can be resubmitted.

### Possible Solutions

Add a `formClear()` function to the arguments of the `onSubmit` function- i.e.
```ts
onSubmit(data: FormDataReturned, utils: { formClear: () => void, etc }): void;
```

### Other feedback

It would be more convenient for consumption if `FormDataReturned` returned the values as an object instead of an array. It could even be a generic so the type could be user defined. This would however be a breaking change.

feature

ready for dev

Lightweight reusable Web3 UI components for dapps. 

web3uikit

Form submit button disabled after submit

### Component

Forge

### 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 (3c49efe 2022-07-14T00:05:10.018576Z)

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

forge build

### Operating System

macOS (Intel)

### Describe the bug

I run

```console
root:~ $ forge flatten src/3.sol > src/4.sol
```
contracts, 1, 2, 3, get flattened into 4.sol

Then when I run build I get this:

```console
root:~ $ forge build
[⠊] Compiling...
[⠒] Compiling 17 files with 0.8.15
[⠢] Solc 0.8.15 finished in 63.73ms
Error:
Compiler run failed
error[3716]: ParserError: Multiple SPDX license identifiers found in source file. Use "AND" or "OR" to combine multiple licenses. Please see https://spdx.org for more information.
```


Also I get this error message three times?


```console
warning: Implied profile [default] found in foundry.toml. This notation has been deprecated and may result in the profile not being registered in future versions. Please use [profile.default] instead.
warning: Implied profile [default] found in foundry.toml. This notation has been deprecated and may result in the profile not being registered in future versions. Please use [profile.default] instead.
warning: Implied profile [default] found in foundry.toml. This notation has been deprecated and may result in the profile not being registered in future versions. Please use [profile.default] instead.
```


Cmd-forge-flatten

Bug: Forge flatten does handle multiple differing SPDX licenses 

This ticket is to generate a diagnostic message for code blocks within the EIP itself. For example, this should generate an error:

````markdown
## Abstract

...

## Specification

All compliant tokens MUST implement:

```solidity
// SPDX-License-Identifier: MIT

interface FooToken {
    // ...
}
```

## Rationale

...
````

Markdown lint to ensure inline solidity with a `SPDX-License-Identifier` has a license of CC0.

For example:

```
Error: error[markdown-rel-links]: non-relative link or image
  --> EIPS/eip-5190.md
   |
17 | This EIP also extends account-bound token from [EIP-4973](https://eips.ethereum.org/EIPS/eip-4973), but the difference is that it can be transferred to other account for mobility between managing device.
   |
   = help: use `./eip-4973.md` instead
```

Special case `markdown-rel-links` to help when linking to eips.ethereum.org

Once the build is configured using `CMAKE_PREFIX_PATH`, subsequent parameters passed as `--prefix` to `cmake --install` are ignored.

weggli-native

The CMake build hardcodes `CMAKE_PREFIX_PATH` into the installed files

We have found that some webhook notifications to the controller (such as RFC 0160 Connections) do not have the `~thread` decorator from the protocol being executed.  This is at minimum useful and in some cases required for the controller to track requests across many protocol instances. For the initial message of a protocol, the `~thread` decorator is (often) not present in the message and so the `id` for the message must be included in the webhook data (the `id` of the first message becomes the `thid` of the protocol instance). The `id` could always be added to all of the webhooks as well.

The task is to review all webhooks related to protocol messages and add the `~thread` decorator or `id` (for first messages of a protocol only) to all webhooks.

Hyperledger Aries Cloud Agent Python (ACA-Py) is a foundation for building decentralized identity applications and services running in non-mobile environments.

aries-cloudagent-python

Add ~thread decorator information to webhooks that don't have it

@chriseth reports that search hits in our docs look like this in Google:
![image](https://user-images.githubusercontent.com/137030/178474001-f26cf55c-76ca-4346-a7ef-ce3e407bd094.png)

Here's what Googles's help says about this: [No page information in search results](https://support.google.com/webmasters/answer/7489871).

I'm pretty sure this has something to do with the [`robots.txt`](https://docs.soliditylang.org/robots.txt) changes we did some time ago #10898. The search result seems to be from `develop`, which our `robots.txt` block. We only allow `latest`, `v0.7.6` and latest release. The question is - why is `develop` still getting indexed (and appears in results before those other allowed versions) if we blocked it?

bug :bug:

documentation :book:

low effort

low impact

Solidity, the Smart Contract Programming Language

solidity

No summary for our documentation pages in Google search results

Launched a fabric network using fabric cli with a total of 3 firefly nodes. Deployed asset-transfer-basic chaincode by following the steps mentioned in the documentation https://hyperledger.github.io/firefly/tutorials/custom_contracts/fabric.html.

Ran three blockchain transactions from org1 and then created an event listener from org2. After creating an event listener, org2 didn't receive any events. Ran fourth transaction from org1, now org2 received the fourth transaction but not the previous transactions.

Below is the payload used for creating event listener in org2
```
{
  "interface": {
    "id": "f1e5522c-59a5-4787-bbfd-89975e5b0954"
  },
  "location": {
    "channel": "firefly",
    "chaincode": "asset_transfer"
  },
  "event": {
    "name": "AssetCreated"
  },
  "options": {
    "firstEvent": "oldest"
  },
  "topic": "assets"
}
```
### Expected: 
Org2 should receive all the events emitted before creating an event listener
### Actual: 
Org2 didn't receive events emitted before creating an event listener

Hyperledger FireFly is the first open source Supernode: a complete stack for enterprises to build and scale secure Web3 applications. The FireFly API for digital assets, data flows, and blockchain transactions makes it radically faster to build production-ready apps on popular chains and protocols.

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity