
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

Modify the [current implementation](https://github.com/tlsnotary/tlsn/blob/dev/mpc/share-conversion-aio/src/gf2_128/recorder.rs#L44-L72) so that each individual OT choice is checked for correctness. Currently only the end result is checked.

Furthermore add a commitment to the sender's rng seed, which is revealed and checked in the end, when the tape is sent.

enhancement

good first issue

Multi-party computation libraries written in Rust 🦀

Rust

Adapt replay protocol for malicious security of share-conversion

https://github.com/crytic/slither/pull/1346 is a nice addition, which gives us fundamental features to do structure packing optimisations.

However it has a couple of drawback. For example packing storage variables might lead to more costly execution because of the additional opcode cost.

We could improve the detector to add a couple of heuristics. One example that comes to mind is to use https://eips.ethereum.org/EIPS/eip-2929#sstore-changes, and to pack together variables that are read within the same transaction. 

We could make it a tool instead of a detector, and propose different scenario as a result, ie:
- To optimize the run of `contract.function1` pack together .. 
- To optimize the run of `contract.function2` pack together ..

Having a tool would allow us additional fine tuning and flags. 

help wanted

slither

Python

Improve 1346 to make it more efficient

When auto increment ids are enabled, shouldn't the method also then `return tokenId`? Otherwise how would you know what token was minted?

<img width="798" alt="image" src="https://user-images.githubusercontent.com/1127421/210900621-528a4449-f7dd-4bec-b64e-6c9e11e37764.png">


Interactive smart contract generator based on OpenZeppelin Contracts.

contracts-wizard

TypeScript

ERC721 safeMint should return the tokenId

introduced here https://github.com/foundry-rs/foundry/pull/4043

A-cast

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

book

Solidity

Document cast call --data argument

```
  --hardhat-ignore-compile
                        Do not run hardhat compile
  --hardhat-cache-directory HARDHAT_CACHE_DIRECTORY
                        Use an alternative hardhat cache directory (default ./cache)
  --hardhat-artifacts-directory HARDHAT_ARTIFACTS_DIRECTORY
                        Use an alternative hardhat artifacts directory (default ./artifacts)

```
We can reuse --ignore-compile and add global flags for `cache-directory` and `artifacts-directory`

Abstraction layer for smart contract build systems

crytic-compile

deprecate platform specific flags and reuse flags across platforms

Refactor checkbox
1. Add `slots` prop, similar to input component.
2. Add on Tab outline style.
3. Fix checkbox issue controlled state issue https://github.com/web3ui/web3uikit/issues/766
4. Add `TCustomize` prop.

<img width="601" alt="image" src="https://user-images.githubusercontent.com/35369843/210501194-70e3fc5b-bbbe-447b-8450-0da695a13e22.png">

<img width="491" alt="image" src="https://user-images.githubusercontent.com/35369843/210501320-2500b609-5847-4e9c-86ef-de27b940fc2f.png">


feature

ready for dev

Lightweight reusable Web3 UI components for dapps. 

web3uikit

Checkbox: new features

We currently run unit tests as well as a couple of the example Dockerfiles in CI, but this existing coverage does not seem to cover all Polytracker commands. Some features such as grammar generation and now `info` (see #6530, https://github.com/trailofbits/polytracker/tree/fix_polytracker_info) have bitrotted over time.

While I'm not sure if [functional testing](https://www.browserstack.com/guide/difference-between-functional-testing-and-unit-testing) comes from "agile" full stack development, that's where I'm familiar with it from! 

If the existing test suite and example Dockerfiles running in CI are not sufficient to ensure all the Polytracker features continue to work (preventing regressions), some ideas to broaden test coverage: 
- use a "Does It All" Dockerfile which runs all the commands, proving each works on each CI run, or maybe:
- add functional-esque tests to the Polytracker test suite (we currently primarily have unit tests, which to me are more about proving a single unit or function works correctly than proving WYSIWYG from the customer POV / feature level) to prove each command works on each CI run

CI/CD

usability

maintenance

An LLVM-based instrumentation tool for universal taint tracking, dataflow analysis, and tracing.

polytracker

Polytracker CI should run all possible commands for regression purposes

There's no need to repeatedly invoke these requests since once the platform is determined, these should not change

Manage and switch between Solidity compiler versions

solc-select

cache `get_installable_versions` and `get_available_versions`

https://github.com/crytic/solc-select/blob/7b493c684aece2dc3e4f233fe044f23c1606be95/solc_select/solc_select.py#L72

`install artifacts` never returns false

See: https://forum.nim-lang.org/t/9774

https://github.com/status-im/nim-taskpools/blob/89d693d3ffc9e53aa470a9a05166e4f2b58d282a/taskpools/channels_spsc_single.nim#L34

The precondition can in fact raise AssertionDefect https://github.com/status-im/nim-taskpools/blob/89d693d/taskpools/instrumentation/contracts.nim#L91 unless when code is compiled without assertions (danger for example).

An easy fix would be to push that hint off

Lightweight, energy-efficient, easily auditable threadpool

nim-taskpools

Spurious warning: cannot raise 'AssertionDefect' [XCannotRaiseY]

A bit tedious to catch up but it would be good if we add EIP commit versions to our experimental (mostly) EVM (maybe other packages as well) EIP implementations. EIPs - especially if still in DRAFT state - often change frequently, and we had this case repeatedly that we couldn't really reference ourself what EIP state we had actually implemented and if we are "up to date", also for documentation purposes it would be good if we clearly communicate to people who want to test/use what EIP version is actually implemented and so what people can expect.

So task here would be to go through the list of EIPs (I guess more or less everything with `experimental` in it (e.g. transient storage, push0) except the EOF stuff which will likely be updated by @jochem-brouwer along his implementation) in [evm.ts](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/evm/src/evm.ts#L65) and in the corresponding [README section](https://github.com/ethereumjs/ethereumjs-monorepo/tree/master/packages/evm#eip-support) and have a look at the commit history from an EIP page (e.g. [EIP-2315 history](https://github.com/ethereum/EIPs/commits/master/EIPS/eip-2315.md)) and find the commit where we have done the implementation (I guess easiest to find the EIP in the EVM [CHANGELOG](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/evm/CHANGELOG.md) and then compare on the dates) and add something like:

- [EIP-1234](https://eips.ethereum.org/EIPS/eip-1234) - Very big improvement (`experimental`, Version [COMMIT HASH OR PR](LINK) from 2022-05-04)

Something like that, first suggestion.

Side task would be to also have a bit a closer look if an EIP implementation we have is eventually outdated and then eventually open an issue on that, would also be helpful to *then* also label the above EIP reference with `OUTDATED` or something:

- [EIP-1234](https://eips.ethereum.org/EIPS/eip-1234) - Very big improvement (`experimental`, Version [COMMIT HASH OR PR](LINK) from 2022-05-04, OUTDATED)

Bonus addition: the PR which *then* substantially *updates* the EIP later on:

- [EIP-1234](https://eips.ethereum.org/EIPS/eip-1234) - Very big improvement (`experimental`, Version [COMMIT HASH OR PR](LINK) from 2022-05-04, OUTDATED, see EIP PR [#1234567](LINK))

type: docs

effort: E1 hours

package: evm

Monorepo for the Ethereum VM TypeScript Implementation

ethereumjs-monorepo

EVM (potentially other): add commit versions to experimental EIP implementation references

### Which Caliper version are you using?

0.5.0

### Which Node.JS version are you using?

v16.18.0

### Which operating system are you using?

MacOS Ventura

### Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?

I'm trying to submit a round of transaction to my private besu network with 3 node, sometimes when i start the round i get the error `invalid params` as error. When i enabled the logging in besu i see the message: Ex. Invalid transaction: transaction nonce 613 does not match sender account nonce 562.

### What was the observed incorrect behavior?

Caliper stacks and the other transactions are marked as unfinished
![Screenshot 2022-12-26 at 11 26 01](https://user-images.githubusercontent.com/74413257/209538356-2ace9bb3-99c4-43bf-8e9b-77c67ac915bc.png)
![Screenshot 2022-12-26 at 11 28 04](https://user-images.githubusercontent.com/74413257/209538406-ae1abfb6-dd49-44f7-be1a-e873337c06e0.png)


### Please provide the error logs and their surroundings.

```text
info  [caliper] [caliper-worker]        Worker #0 starting workload loop
2022.12.26-11:19:19.538 error [caliper] [ethereum-connector]    Failed tx on Manager calling method StoreInterface nonce 0x232
2022.12.26-11:19:19.539 error [caliper] [ethereum-connector]    Error: Returned error: Invalid params
2022.12.26-11:19:19.546 error [caliper] [ethereum-connector]    Failed tx on Manager calling method StoreInterface nonce 0x233
2022.12.26-11:19:19.546 error [caliper] [ethereum-connector]    Error: Returned error: Invalid params
2022.12.26-11:19:19.547 error [caliper] [ethereum-connector]    Failed tx on Manager calling method StoreInterface nonce 0x234
2022.12.26-11:19:19.547 error [caliper] [ethereum-connector]    Error: Returned error: Invalid params
2022.12.26-11:19:19.554 error [caliper] [ethereum-connector]    Failed tx on Manager calling method StoreInterface nonce 0x235
2022.12.26-11:19:19.554 error [caliper] [ethereum-connector]    Error: Returned error: Invalid params
2022.12.26-11:19:19.556 error [caliper] [ethereum-connector]    Failed tx on Manager calling method StoreInterface nonce 0x236
2022.12.26-11:19:19.557 error [caliper] [ethereum-connector]    Error: Returned error: Invalid params
2022.12.26-11:19:19.557 error [caliper] [ethereum-connector]    Failed tx on Manager calling method StoreInterface nonce 0x237
2022.12.26-11:19:19.557 error [caliper] [ethereum-connector]    Error: Returned error: Invalid params
```


### Please provide your benchmark configuration file content, if possible.

```yaml
simpleArgs: &arg
  Hash: ciao

test:
  name: StoreValue
  description: >-
    To benchmark the network transactions.
  workers:
    type: local
    number: 1
  rounds:
    - label: Store an hash in the smart contract queue
      description: Storing
      txNumber: 200
      rateControl:
        type: fixed-rate
        opts:
          tps: 100
      workload:
        module: benchmarks/scenario/simple/StoreHash.js
        arguments: *arg
```


### Please provide your network configuration file content, if possible.

```yaml
{
    "caliper": {
        "blockchain": "ethereum"
    },
    "ethereum": {
        "url": "ws://192.168.178.21:9092",
        "fromAddressSeed": "0x3f841bf589fdf83a521e55d51afddc34fa65351161eead24f064855fc29c9580",
        "transactionConfirmationBlocks": 1,
        "contracts": {
            "Manager": {
                "address": "0xd54b47F8e6A1b97F3A84f63c867286272b273b7C",
                "estimateGas": true,
                "gas": {
                        "StoreInterface": 22040
              },
                "abi": [
                  {
                    "inputs": [
                      {
                        "internalType": "address",
                        "name": "_AdminAddress",
                        "type": "address"
                      },
                      {
                        "internalType": "address",
                        "name": "_StorageAddress",
                        "type": "address"
                      }
                    ],
                    "stateMutability": "nonpayable",
                    "type": "constructor"
                  },
                  {
                    "inputs": [
                      {
                        "internalType": "address",
                        "name": "_sender",
                        "type": "address"
                      }
                    ],
                    "name": "RetriveInterface",
                    "outputs": [
                      {
                        "internalType": "string",
                        "name": "",
                        "type": "string"
                      }
                    ],
                    "stateMutability": "nonpayable",
                    "type": "function"
                  },
                  {
                    "inputs": [
                      {
                        "internalType": "string",
                        "name": "Hash",
                        "type": "string"
                      }
                    ],
                    "name": "StoreInterface",
                    "outputs": [],
                    "stateMutability": "nonpayable",
                    "type": "function"
                  },
                  {
                    "inputs": [
                      {
                        "internalType": "address",
                        "name": "_sender",
                        "type": "address"
                      }
                    ],
                    "name": "deleteCorresponding",
                    "outputs": [
                      {
                        "internalType": "bool",
                        "name": "isDeleted",
                        "type": "bool"
                      }
                    ],
                    "stateMutability": "nonpayable",
                    "type": "function"
                  },
                  {
                    "inputs": [],
                    "name": "getAdminList",
                    "outputs": [
                      {
                        "internalType": "address[]",
                        "name": "",
                        "type": "address[]"
                      }
                    ],
                    "stateMutability": "view",
                    "type": "function"
                  },
                  {
                    "inputs": [
                      {
                        "internalType": "address",
                        "name": "_sender",
                        "type": "address"
                      },
                      {
                        "internalType": "address",
                        "name": "_receiver",
                        "type": "address"
                      }
                    ],
                    "name": "newCorresponding",
                    "outputs": [
                      {
                        "internalType": "bool",
                        "name": "isAdded",
                        "type": "bool"
                      }
                    ],
                    "stateMutability": "nonpayable",
                    "type": "function"
                  },
                  {
                    "inputs": [
                      {
                        "internalType": "address",
                        "name": "_sender",
                        "type": "address"
                      },
                      {
                        "internalType": "address",
                        "name": "_receiver",
                        "type": "address"
                      }
                    ],
                    "name": "updateEntity",
                    "outputs": [
                      {
                        "internalType": "bool",
                        "name": "isUpdated",
                        "type": "bool"
                      }
                    ],
                    "stateMutability": "nonpayable",
                    "type": "function"
                  }
                ]
            }

        }
    }
}

```


### Please provide your workload module content, if possible.

```nodejs
/*
* 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.
*/


'use strict';

const caliper = require('@hyperledger/caliper-core');
const OperationBase = require('./utils/operation-base');
const SimpleState = require('./utils/simple-state');

/**
 * Workload module for storing hash in smart contract.
 */
class StoreHash extends OperationBase {

    /**
     * Initializes the instance.
     */
    constructor() {
        super();
    }

    /**
     * Create a pre-configured state representation.
     * @return {SimpleState} The state instance.
     */
    createSimpleState() {
        const accountsPerWorker = this.numberOfAccounts / this.totalWorkers;
        return new SimpleState(this.workerIndex, this.Hash, accountsPerWorker);
    }

    /**
     * Assemble TXs for storing hash
     */
    async submitTransaction() {
        const transferArgs = this.simpleState.getStoreArguments();
        const reusult = await this.sutAdapter.sendRequests(this.createConnectorRequest('StoreInterface',transferArgs));
    }
}

/**
 * Create a new instance of the workload module.
 * @return {WorkloadModuleInterface}
 */
function createWorkloadModule() {
    return new StoreHash();
}

module.exports.createWorkloadModule = createWorkloadModule;
```


### Please provide any additional information you deem relevant to the error.

_No response_

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

caliper

JavaScript

Testing Besu Network With Caliper gives error: `invalid params`

**Describe the problem**
Hi, I am trying to use `puppeteer-extra` and its plugins to launch a dappeteer browser instance. In 4.0.2, there is no way to do this. However, in older versions, eg. `3.0.0`, a custom puppeteer instance can be passed in the first argument of `dappeteer.launch()`. Is there any workaround in `4.0.2`?

**System:**
- OS: macOS
- OS version 12.6.1
- NodeJs version v16.15.1
- dAppeteer version 4.0.2

🏌🏼‍E2E testing for dApps using Puppeteer + MetaMask

dappeteer

How to inject and use `puppeteer-extra` in a dappeteer browser in 4.0.2?

Stop using `&str` with lifetime for the params and instead use `impl Into<String>`

ergonomics

An Asynchronous Apple Push Notification (apns2) Client for Rust

feat: Switch `&str` params

The `tracing` feature is missing, it should be added back and the `tracing` dependency should only be added when this feature is enabled

fix: add `tracing` feature back

### Component

Forge

### Describe the feature you would like

I would like for my scripts to skip certain operations in the pre-broadcast simulations. 

```
if (vm.isSimulation() == false) {
    stdJson.write(json, filepath);   
}
```

Without the ability to differentiate whether the script is executing in a simulation at runtime, I can't perform certain operations that require persistent storage because the simulation gets in the way. 

### Additional context

_No response_

T-feature

D-easy

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

foundry

Add a vm.isSimulation() cheatcode

(t8n) Implement a tool based on Nethermind EVM for the generation of new state tests.
More details: https://github.com/ethereum/go-ethereum/tree/master/cmd/evm

security

test

A robust execution client for Ethereum node operators.

nethermind

Nethermind as a tool for tests generation

### Is your proposal related to a problem?

we have some packages without test case or test coverage is less than 50%



(Write your answer here.)

### Describe the solution you'd like

we hope improve code quality by unit test case.


(Describe your proposed solution here.)

### Describe alternatives you've considered



(Write your answer here.)

### Additional context



(Write your answer here.)

golang

Fabric SDK for Admin Capability services 

fabric-admin-sdk

Test coverage

`ChaCha20Rng` does not currently implement `Zeroize`. It seems like there is no trivial way to implement it, so it either requires an upstream contribution or unsafe memory fiddling. Either way, this behavior should be implemented and used in `batch_contribution::derive_taus`. 

kzg-ceremony-sequencer

Make ChaCha20Rng zeroizable

If "poolDataString" is an empty string and therefore "poolData" is nil, this line results in a nil pointer dereference.

https://github.com/hyperledger/firefly/blob/490745489fe98779cff07821d19ba7a83b8421bf/internal/tokens/fftokens/fftokens.go#L335

```
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0xbef3d1]

goroutine 58 [running]:
github.com/hyperledger/firefly/internal/tokens/fftokens.(*FFTokens).handleTokenPoolCreate(0xc0002cf960, {0x1093520, 0xc0007e1ec0}, 0xc000d3a630, 0x0)
	/firefly/internal/tokens/fftokens/fftokens.go:335 +0x371
github.com/hyperledger/firefly/internal/tokens/fftokens.(*FFTokens).handleMessage(0xc0002cf960, {0x1093520, 0xc0007e1d00}, {0xc00087b000, 0x3f3, 0x400})
	/firefly/internal/tokens/fftokens/fftokens.go:511 +0x434
github.com/hyperledger/firefly/internal/tokens/fftokens.(*FFTokens).handleMessage(0xc0002cf960, {0x10935c8, 0xc00024d530}, {0xc000840100, 0x44c, 0x580})
	/firefly/internal/tokens/fftokens/fftokens.go:506 +0x878
github.com/hyperledger/firefly/internal/tokens/fftokens.(*FFTokens).eventLoop(0xc0002cf960)
	/firefly/internal/tokens/fftokens/fftokens.go:553 +0x28f
created by github.com/hyperledger/firefly/internal/tokens/fftokens.(*FFTokens).Init
	/firefly/internal/tokens/fftokens/fftokens.go:234 +0x296

```

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