
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

## Problem

Currently it is not possible to contribute to large circuits > 1M constrains on a browser due to memory restrictions. For that, we use a cli tool instead where we can use the full computing power of a machine.

## Possible solution

Pipelining the contribution of a user.

Flow: 

* Download n chunk -> process n chunk -> (upload n chunk)

By processing the computation on one chunk at a time, we can effectively reduce the memory consumption as we do not need to hold the whole file in memory at all times. This could possibly allow even larger contributions on a mobile phone's browser. 

## What we would need to change

> We would need to first validate this is possible to do the computation on chunks rather than the whole zKey.

1. Amend the current backend step system. This is quite strict, there's certain actions which can only be done on when at a certain step (for instance cannot get an upload pre-signed url when not in the upload phase, etc.). (medium complexity)
2. This approach described above requires some changes on [snarkjs' code](https://github.com/iden3/snarkjs/blob/master/src/zkey_contribute.js).

enhancement

help wanted

question

The MPC suite of tools for conducting zkSNARK Phase 2 Trusted Setup ceremonies

p0tion

TypeScript

pipelining of users contributions

The repository for high quality Trusted setups for groth16 based SNARKS

DefinitelySetup

pipelining of user contributions

Prysm has a slasher feature, which is demanding in resources. However, equivocating blocks are already handled in the usual path for every beacon. We should broadcast immediately a slashing object in the event of receiving an equivocating block. 

Enhancement

Good First Issue

Go implementation of Ethereum proof of stake

prysm

Broadcast slashing on equivocating blocks

## Description
Since mocktimism will initially be released in alpha and subject to breaking changes it is important that changlogs be kept for the npm and go packages. By using changesets with the github plugin release notes will be created in this github and the npm releases

https://github.com/changesets/changesets

## Tasks
- [ ] Add changesets folder https://github.com/ethereum-optimism/optimism/tree/develop/.changeset
- [ ] Add appropriate release version and changeset scripts to package.json https://github.com/ethereum-optimism/optimism/blob/develop/package.json#L30
- [ ] Add github action for releasing https://github.com/ethereum-optimism/optimism/blob/develop/.github/workflows/release.yml
- [ ] Add github action for releasing snapshots https://github.com/ethereum-optimism/optimism/blob/develop/.github/workflows/release-snapshot.yml


good first issue

[WIP!] Coordinates two anvil process (L1 and L2) for testing / forking op-stack chains (mocktimism placeholder name)

mocktimism

Add changesets to create changelogs

## Description

In https://github.com/ethereum-optimism/mocktimism/pull/46 we added a way of publishing mocktimism to npm. To make it cross platform we need to add postinstall scripts.  Example of this is here https://github.com/ethereum-optimism/mocktimism/pull/46

## Tasks

- [ ] Add necessary scripts

Make npm package cross platform

### Component

Cast

### Describe the feature you would like

`cast call` has a `--block` flag but as best as I can tell it has no way of overriding the `timestamp` which means trying to simulate swaps in the past to uniswap ~always fail from getting executed past their deadline

relatedly, it would be very nice to be able to get the timestamp given a block and the closest block given a timestamp

### Additional context

_No response_

T-feature

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

foundry

Rust

cast call option: timestamp

## Description

We don't want to write docs for the cli we want to generate it in a script. It appears pretty easy to do looking at this https://github.com/urfave/cli/pull/830. We also want to make s

## Tasks

- [ ] Add a new `scripts/` package
- [ ] Add a script to generate markdown doc for cli app into docs/cli.md
- [ ] (optional) Add check to circleci config that make sure generated docs are up to date

Generate markdown docs about the cli from urfavecli

Not really sure if this is a problem as it appears to be working fine on Android but according to Android docs, the permission should be `USE_BIOMETRIC` instead of `USE_BIOMETRICS`

https://developer.android.com/reference/android/Manifest.permission#USE_BIOMETRIC

https://github.com/hyperledger/aries-mobile-agent-react-native/blob/2f80d8f8efd43457560a44fcd4a3837c1ef8de6c/packages/legacy/app/android/app/src/main/AndroidManifest.xml#L4

Aries Mobile Agent React Native - Part of the Aries Bifold effort to provide SSI capabilities in a production ready app.

aries-mobile-agent-react-native

[Android] Typo in permission name?

A node version prior to 18 will not work, then devs should use a node version >= 18 to run Bandada. 

documentation  :book:

A system for managing privacy-preserving groups.

bandada

Add info in the Readme file about the node version required to run Bandada 

Context:
https://github.com/privacy-scaling-explorations/bandada/pull/311#discussion_r1345494305


refactoring :recycle:

Add more info about the config parameter in the API SDK

**Scenario:** Validate that transactions initiated outside of Multix (created in Polkadot.js portal) for the watched/connected accounts are accurately displayed as "Unknown" transactions within the Multix UI.

**Acceptance Criteria:**

- Test fixture for a multisig with one of these transactions is created (create the tx and never approve)
- New cypress tests are added, suggestions:
  - [ ] can see the expected state of an "Unknown" transaction in the queue
  - [ ] can open an "Unknown" transaction and see the expected state in the modal *do not approve


Priority: 🟡 P2

Good first issue

🧪 Test

Use a Multisig to do anything, on Polkadot

Multix

Add UI Test: Inspecting "Unknown" transactions

### Description
The node would be added to denyList if block validation failed.
However, some block import failure is caused by busy RocksDb or BONSAI data incorrect, instead of bad node.
Especially in private network, the nodes are already listed in `static-nodes.json` file.

**Even though there is a logic to avoid add nodes to denyList if the node is listed as maintenance peers, it still exist a bug on detecting whether current Peer object is in maintenance peer list**.

it was because the maintenance peers Set is an object set and for Peer object, there is no override about equals method. If the peer object changes port or something else, there would create a new peer object and add valid peerId to denyList

### Acceptance Criteria


### Steps to Reproduce (Bug)


**Expected behavior:**
the Peer object should override Equals and hashCode method. The peer should detected base on the peerId instead of object equals

**Actual behavior:** 
valid peers are added into denyList adn cause private network peers found non peers in the future

**Frequency:** 
quite offen.

### Logs (if a bug)
![image](https://github.com/hyperledger/besu/assets/4539861/157a4fc6-4857-4fa7-b72f-643383aba131)


### Versions (Add all that apply)
* Software version: 23.7.3
* Java version:openjdk version "17.0.8" 2023-07-18 LTS
* OS Name & Version: CentOS7.2
* Kernel Version: Linux 4.9.151-015.ali3000.alios7.x86_64

peering

snack

non mainnet (private networks)

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

besu

Java

bug in recognization maintainer peers  as well as denyList

Currently we have at least two files that cause issues when the repo is cloned in a case-insensitive environment:
`_data/icons/LaChain.json`
`_data/icons/lachain.json`

It would be cool if we fixed these issues and maybe even tried to prevent this from happening later in the future.

chains

Kotlin

Fix case-sensitive file names in the repo

Opening up discussion for requirements / ideas for creating an open-source registry for any and all OP Chains & OP Stack Forks.

**Problem:**
Crypto data teams have a super hard time keeping track of deployed OP Chains & OP Stack Forks. Some chain deployers attempt to get in touch with OP Labs / OP Foundation, but otherwise this requires sleuthing through Twitter, blog posts, news aggregators, etc. Many people maintain their own lists with varying degrees of comprehensiveness (nobody knows how many production mainnet chains actually exist)

To solve for this, want to create a shared open-source resource for analysts, developers, educators, etc to identify OP Chains & OP Stack Forks with the relevant information about them.

See [Key Definitions for Chain Segments](https://community.optimism.io/docs/contribute/important-terms/#the-superchain)

**Goals:**
- Be the best "source of truth" for identifying metadata for OP Chains & OP Stack Forks
- Store relevant information for analysts (i.e. Name, RPC, Block Explorer, L1 Contracts, Chain Configuration)
- Make it SUPER easy to contribute to (i.e. easy to add new chains, easy to modify data, easy to add bespoke attributes)
- Make it SUPER easy to read from (i.e. if we input in yml, outputs are available in csv, json, sql, etc)
- Provide the necessary metadata for analysts to create chain segments (i.e. RAAS provider, DA Layer, other Config Changes, potential superchain compatibility)
- Be scalable, we don't want to have to re-do this if/when there are thousands of chains

**Existing Version(s):**
- op-analytics Repo [`chain_metadata`](https://github.com/ethereum-optimism/op-analytics/blob/main/op_chains_tracking/inputs/chain_metadata.csv)
- Dune Upload from OP Labs CRM [`dataset_op_stack_chain_metadata`](https://dune.com/queries/3109219)
- [superchain-registry](https://github.com/ethereum-optimism/superchain-registry) repo
- [superchain.eco](https://www.superchain.eco/ecosystem/chains)

**Other Inspiration / Attempts:**
- [L2Beat](https://l2beat.com/scaling/summary)
- [growthepie](https://www.growthepie.xyz/)
- [Kofi's Rollup Economics](https://dune.com/niftytable/rollup-economics)
- [OP Stack Data Dashboard](https://dune.com/oplabspbc/op-stack-chains-l1-activity)
- [ethereum-lists/chains](https://github.com/ethereum-lists/chains)

**Open Questions:**
- What are the top use cases for this? (_Non-Labs teams, please share!_)
- What fields do we need to track? What "requirements" should this have?
--
- What's the best input format (i.e. csv, yml), output formats to be available (i.e. csv, json, sql cte)?
- What is the right organizational structure? (i.e. one ecosystem/chain deployer can have multiple chains, there may be a gazillion chains)
--
- How can we "automate" parts of this? (i.e. identify new L2s via L1 contracts - somehow tie that back to metadata)
- What could/should be onchain?
--
- What's the process for accepting/rejecting/verifying changes?
- How do we incentivize chain deployers to "register"?

Onchain Data, Utilities, References, and other Analytics on Optimism

op-analytics

Jupyter Notebook

[Idea Discussion] Open-Source OP Chain & OP Stack Forks Metadata Source

### Version Information

* vyper Version (output of `vyper --version`): 0.3.10

### What's your issue about?

currently, coverage is sitting around 89% (https://app.codecov.io/gh/vyperlang/vyper)

![Screenshot from 2023-10-13 13-10-21](https://github.com/vyperlang/vyper/assets/3867501/47b38d59-37cd-4641-ae61-7fcf93ec885b)

it would be great to get that up to high 90s, especially in the codegen and typechecking parts of the codebase. this is a great area for newcomers to the codebase to contribute, since it can be done piecemeal / in arbitrarily small chunks.

Easy Pickings

Pythonic Smart Contract Language for the EVM

vyper

Python

chore: increase coverage

### Describe the issue:

DETECTOR_INFO contains information about the detected vulnerability, but it is difficult to read due to missing "\n" in some parts.

### Code example to reproduce the issue:

# Nothing was found in the outer scope
                    info: DETECTOR_INFO = [
                        "Modifier ",
                        mod,
                        " does not always execute _; or revert",
                    ]

this code in "slither/slither/detectors/functions/modifier.py" line 88-93.

### Version:

slither WalletLibrary.sol

(https://github.com/crytic/not-so-smart-contracts/blob/master/unprotected_function/WalletLibrary_source_code/WalletLibrary.sol)

### Relevant log output:

```shell
Modifier WalletLibrary.onlyowner() (WalletLibrary.sol#84-87) does not always execute _; or revertModifier WalletLibrary.onlymanyowners(bytes32) (WalletLibrary.sol#91-94) does not always execute _; or revertReference: https://github.com/crytic/slither/wiki/Detector-Documentation#incorrect-modifier

Pragma version^0.4.9 (WalletLibrary.sol#12) allows old versions
solc-0.4.22 is known to contain severe issues (https://solidity.readthedocs.io/en/latest/bugs.html)Reference: https://github.com/crytic/slither/wiki/Detector-Documentation#incorrect-versions-of-solidity
```


slither

[Bug]: there's "\n" missing from DETECTOR_INFO.

# What is the feature? 
These test vectors are needed to directly test our circuit, they make abstraction of the PCD and the typescript implementation.

# Additional context (optional) 
These vectors will enable testing new frameworks.
Check the following [example]( https://github.com/vocdoni/keccak256-circom/blob/master/test/keccak.js#L21-L27)

circuits

Anon Aadhaar is a zero-knowledge protocol that allows Aadhaar ID owners to prove their identity in a privacy preserving way.

anon-aadhaar

JavaScript

Create test vectors

Currently, mirroring can make a chunk of commits. We can do some check if previous commit is made by us in this action, and if so, squash (what's the best way to combine commits? not do multiple pushes?)
![image](https://github.com/AztecProtocol/aztec-packages/assets/163993/6fe9198b-a139-4dae-928c-6953e98f6778)


devops

aztec-packages

[ci] Only ever make one mirror commit in nightly mirror action

In this section https://stack.optimism.io/docs/build/getting-started/#deploy-the-l1-contracts, after you broadcast the L1 contracts the folder that gets updated is deployments/goerli and the folder you make deployments/getting-started remains empty. The follow command to generate the genesis and rollup files assumed deployments/getting-started is populated but it's empty and errors. I have been copying the goerli folder to getting-started to be consistent with the command
Step 4 in https://stack.optimism.io/docs/build/getting-started/#configure-your-network asks you to put your PRIVATE_KEY in the .envrc but doesn't specify using the raw privkey and not the hex prepended 0x... key
I don't think there's a section on which address/steps on how to bridge back out (understand this takes a while to actually execute, but unless I missed it I don't think the info is there)
Small note when you're configuring your files to change the batcher inbox address to something arbitrary would be helpful to users
Proposed ETH amounts for Admin — 2 ETH Proposer — 5 ETH Batcher — 10 ETH is probably a bit high, Goerli is super cheap 🙂
Pin the optimism and geth tags/versions here https://stack.optimism.io/docs/build/getting-started/#build-the-optimism-monorepo - trying this guide from a latest tag has many config values missing or missing steps, I am using v1.1.4 and it seems fine
The RPC port by default is 8545, a note on which piece of the software has the flag to change this and a note about ssl setup with it would help

documentation

user-feedback

docs

[FEEDBACK] Update op-stack getting started

### Describe the bug

H4's on /staking pages appear to have grown in size to 36px from 20px.

### To reproduce

1. Go to https://ethereum.org/en/staking/#comparison-of-options
2. See size of H4's


### Expected behavior

This is what is was previously like (and would expect):

<img width="1731" alt="image" src="https://github.com/ethereum/ethereum-org-website/assets/54227730/e5a34abf-5048-4362-830e-4aafde240cde">


### Screenshots

Currently:

![image](https://github.com/ethereum/ethereum-org-website/assets/54227730/3f5794a6-327f-4602-bbf2-8268a2c46c62)


### Desktop (please complete the following information)

_No response_

### Smartphone (please complete the following information)

_No response_

### Additional context

@nloureiro or @konopkja if you could confirm this

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

- [ ] Yes
- [X] No

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity