
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

As of #183, the supported method for overriding or extending the configuration of the underlying Docker containers is via a `docker-compose.override.yml` file.

As a convenience, it would be nice to have an option to `ff init` which allows pointing to an existing file that will be copied in as `docker-compose.override.yml` instead of the default empty stub file. This would allow reusing the same overrides multiple times without manual copy steps, such as if you delete and recreate a stack.

good first issue

firefly-cli

Add an "init" option to copy in a custom docker-compose.override.yml file

Links should open in a new tab when you click them with CMD + Click

firefly-ui

TypeScript

CMD + Click Support for links

Query params should support start/stop times to timebound requests.

enhancement

E-hard

Start/Stop times in query params

There is a little typo in the following file :

`scripts/vrf_scripts/01_deploy_vrf.py`

The deploy function is called :
```python
depoly_vrf()
```
It should obviously be called : 
```python
deploy_vrf()
```

It's nearly invisible because as it's called the same way in the main function it's still working properly: 

```python
def main():
    depoly_vrf()
```
Have a good day!

Working with smart contracts with eth-brownie, python, and Chainlink. 

chainlink-mix

Solidity

Little typo in 01_deploy_vrf.py

Some long JSON items (such as contract schemas) are truncated in the template display for readability, like the following:
```
const ffi = {"name":"m ... event1"}]};
```

If this truncation results in a mismatched number of quotation marks, the syntax highlighting is wrong (as it colors the rest of the snippet as a string constant).

firefly-sandbox

Mismatched quotes in truncated template blurbs causes highlighting issues

 Support for extracting certificate features like sign date, expire date, sign algorithm, thumbprint, sign key, cert hash , certdata values etc.

help wanted

C:uthenticode

A cross-platform library for verifying Authenticode signatures

uthenticode

Support to extract additional certificate feature

Document the artefacts that are available to supplement a distribution:
See: https://docs.tessera.consensys.net/en/latest/HowTo/Get-started/Install/Distribution/ 

For info about the artifacts see:
https://github.com/ConsenSys/tessera/tree/tessera-22.1.1#optional-artefact

Documentation site for Tessera, the ConsenSys Quorum privacy enclave

doc.tessera

Document the available Tessera artifacts

When we declare a constant variable that has an initializer, e.g. `bool constant x = 0 < 2`, we evaluate the actual constant value in compiler time. Currently, there is no support to evaluate constants in comparisons, so the aforementioned example is evaluated in run time.

We need to calculate comparisons with constants during compilation. The `eval_const_number` function should become `eval_const_expression` to evaluate boolean operators too. This function should be called at `fn var_decl` in `src/sema/variables.rs` so that the initializer of a constant is evaluated at compile time.

Solidity Compiler for Solana and Substrate

solang

Rust

Comparisons should support constants

### Description
If I sync besu using FOREST storage format, then specify `--data-storage-format=BONSAI` without deleting the database, besu fails to start with a very cryptic message:

```
{"timestamp":"2022-04-20T08:50:34,880","level":"INFO","thread":"main","class":"ProtocolScheduleBuilder","message":"Protocol schedule created with milestones: [Frontier: 0, Homestead: 1150000, DaoRecoveryInit: 19200
00, DaoRecoveryTransition: 1920001, Homestead: 1920010, TangerineWhistle: 2463000, SpuriousDragon: 2675000, Byzantium: 4370000, Petersburg: 7280000, Istanbul: 9069000, MuirGlacier: 9200000, Berlin: 12244000, London
: 12965000, ArrowGlacier: 13773000]","throwable":""}
Cannot read field "nativeHandle_" because "<parameter1>" is null

To display full help:
besu [COMMAND] --help
```

Besu should at least provide a meaningful error message that the existing database doesn't match.  Ideally it would continue using the existing database (possibly logging a warning). When a new database is created it would use the specified format.

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

besu

Java

Besu fails to start when storage-mode doesn't match existing database

**Is your feature request related to a problem? Please describe.**

We do not have any way to show data on ledgers.
The Hyperledger Explorer project only supports Fabric and the development has slowed so there is an opportunity for us to deliver value.

**Describe the solution you'd like**

1. A GUI package built with Angular that is called `cactus-scorpion` (the shortlist of names comes from [Top 50 Amazing Sahara Desert Animals](https://owlcation.com/stem/sahara-desert-animals), special thanks to @hartm @takeutak and @sfuji822 for being on the impromptu naming committee for this)
2. The package is compatible with `cmd-api-server` so that it can be served the same way that the `cactus-cockpit` package used to be before it got deprecated
3. In fact, the former `cactus-cockpit` package is a great starting point for the scorpion package to the point that if you look up the git history you can extract the code for it and then copy+rename it to get going the easiest possible way.
4. The application should have a sliding menu
5. One of the menu items should be named `Ledgers`
6. When the user clicks on the `Ledgers` menu item they are taken to a list of ledgers that the current running instance of the API server is connected to.
7. When clicking on any of those ledgers on the list, some metadata is displayed and a list of blocks/transactions are also rendered.
8. What the block/tx data looks/contains/formatted like will be slightly different for each ledger since each ledger has some unique characteristics to it, this is not a problem. We want to make sure that all relevant data is displayed rather than only displaying the common types of pieces of information (lowest common denominator)
9. If a ledger is not yet supported by scorpion then some graceful handling must be done on the UI in a way that is non-ambiguous. For example we could still show the ledger in the list of ledgers but then when the user clicks on it we could show a message that says "The current version of scorpion does not yet support the $LEDGER_NAME". This is preferred to just not showing a ledger in the list at all if it's not yet supported because that confuse people into thinking that they did not configure something correctly.
10. The GUI has to be responsive, work and present well on handheld devices such as phones, tablets laptops and large desktop screens (4k, 5k, etc. resolutions)
11. It would be great if there was no polling involved and instead SocketIO endpoints could be used to stream data changes for each ledger. 
12. End to end test coverage powered by [Angular's Protractor](https://protractor.angular.io/) that verify that certain block/tx data is indeed rendered on the GUI as it gets added to a ledger (the AIO containers can host the ledger and then an instance of cmd-api-server can host the GUI that protractor can run assertions against checking if the block data showed up on the GUI or not) 

**To be defined**:
1. The data to show for each ledger (e.g. what columns to show on a grid)

**Describe alternatives you've considered**

There is another school of thought where we could just make explorer tooling part of a recommended reference deployment architecture and then we don't have to maintain any of the code for such a tool. It is unclear at the time of this writing if we could achieve sufficient coverage of supported ledgers though (e.g. is there such tooling for each ledgers or are we the trailblazers here)

**Additional context**

`N/A`

API_Server

Nice-to-Have

Developer_Experience

Core_API

Hyperledger Cacti is a new approach to the blockchain interoperability problem

cacti

feat(scorpion): ledger explorer graphical user interface

```
public static DeterministicKey createMasterPrivateKeyNist(byte[] seed) throws HDDerivationException {
        return createMasterPrivateKeyWithKeys(seed, "Nist256p1 seed".getBytes());
    }
```

key-tree

Can i got private key which derived by Nist256p1 ?

When the aggregator starts up, it should scan through the current chain it is pointing at to retrieve and store any historical bundles that have been submitted so clients can look them up if need be.
- Add a process on aggregator startup which scan the chain in a block range for bundles.
- Track the block number the aggregator has scanned up (checkpoint) so it does not have to scan the entire chain history on every startup.

aggregator

Core components to use layer 2 smart contract wallets with the BLS signature scheme

bls-wallet

Load submitted onchain bundles into db on aggregator startup

Currently, confirmed/submitted bundles are not persisted in the aggregator. We should add a db table or column for status which tracks them so they can be looked up in the future, or be available between aggregator restarts.

Store confirmed/historical bundles in db

Currently the compilation warnings are not saved by crytic-compile, and they are just being emitted through log:

https://github.com/crytic/crytic-compile/blob/35d95d6cb7716290ff4bf21ba9dcc8e582c6ee04/crytic_compile/platform/solc.py#L534-L541

https://github.com/crytic/crytic-compile/blob/35d95d6cb7716290ff4bf21ba9dcc8e582c6ee04/crytic_compile/platform/truffle.py#L178-L189

etc..

We could save the log, and make them available for third parties analyses. We need to check what errors are reported by every tool (stdout/stderr).

This will require to update our standard export to load/save the new info: https://github.com/crytic/crytic-compile/blob/master/crytic_compile/platform/standard.py

Abstraction layer for smart contract build systems

crytic-compile

Python

Save compilation warnings

https://docs.soliditylang.org/en/v0.8.13/ir-breaking-changes.html#semantic-only-changes

0.8.13 allows to use of the new IR pipeline, but comes with risks due to semantics changes. We should create detectors to help developers to review if they can use the new version without impacting their contracts. 

We can make these detectors directly public to help a larger audience. 

High Priority

slither

Create detectors for semantic changes due to Solidity IR

When sending a credential offer in v1 and creating a bad request (in my case I made a type in one of the attribute names) ACA-Py will send a problem report to the other agent without having initiated the protocol.  

Not sure if other endpoints / protocols are affected, but I find it an quite amusing issue :)

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

problem report is sent when no exchange exists yet

We need to create a way to quickly bootstrap a smartcontract project. 

https://crates.io/crates/cargo-hatch might be a good place to start. Ideally we want to have a small git repository (under hyperledger) which contains a ready-made `Cargo.toml` with all of the optimisations, and the build ready so that it only contains the `iroha_wasm::entrypoint` function. 

iroha2

Iroha - A simple, enterprise-grade decentralized ledger

iroha

Implement a WASM helper tool or Repo

Reference link: https://trufflesuite.com/docs/truffle/reference/truffle-commands/

I didn't check every command, this is just what I noticed on the two I did check.

There's no documentation of the `--config` option that most commands accept.

`truffle migrate` is missing documentation for `--compile-none` and `--quiet`.

`truffle test` is missing documentation for `--compile-none`, `--migrate-none`, `--runner-output-only`, `--grep`, `--reporter`

There could be more missing, but I'm going to leave this issue here, don't have time right now to check them all!

priority2 ⚠️

documentation

trufflesuite.com

HTML

Various options missing from the command reference

## Page
- [Cheatsheet](https://docs.soliditylang.org/en/latest/cheatsheet.html#global-variables)
- [Units and Globally Available Variables](https://docs.soliditylang.org/en/latest/units-and-global-variables.html)

## Abstract
Currently the "Cheatsheet" page mostly contains information already available in "Units and Globally Available Variables". The information is already concise in that original source so the cheatsheet just looks like an inferior copy. Also, having two copies is just an extra maintenance burden that's not worth it unless the cheatsheet actually adds something of value. I think we can make it more valuable by adding summaries of information from other pages and streamlining the way it's presented where possible.

Here's what I think we should do:
- Remove excessive detail from the cheatsheet. If the info is only available there, move it to a different location.
    - [x] Notes/warnings should not be there
    - [ ] (Optional) "Global Variables" section would be better off as a table. This may require tweaking the descriptions or presenting signatures in a more compact way.
        - Marking this as optional since we tried it and it did not look good (#13595). I still think it's possible but will require some editing of the content to make it actually suitable for a table.
    - [ ] Members of `address`, `type`, etc. should be in a separate section, not under "Global Variables".
    - [x] The operator precedence should be under [Types > Operators](https://docs.soliditylang.org/en/latest/types.html#operators). Maybe it makes sense to have a copy here but that's also extra maintenance so I'd just move it.
    - [x] I think that the list of keywords should be moved to "Units and Globally Available Variables". It does not fit that page perfectly but is a bit related.
- Add missing info
    - [ ] Members available on functions, errors, events.
    - [ ] Make sure that the list of "Global Variables" contains every item from "Units and Globally Available Variables"


documentation :book:

Solidity, the Smart Contract Programming Language

solidity

More concise "Cheatsheet" page

A lot of users issues are related to errors like
`crytic_compile.platform.exceptions.InvalidCompilation: Unknown file: @openzeppelin/...`

Which is usually a sign that `npm install`/`yarn install` had an issue, or the files where installed somewhere else. We could improve the error message with recommendations like:
- Check if `ls <path to file>`
- Run `npm install` / `yarn install`

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity