
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

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

Road to ZK


Web3 is about the next evolution of the web. A web that is more open, transparent and permissionless and runs on decentralized infrastructure such as blockchains. Global and decentralized applications (DApps) that anyone can interact with. They often have native assets integrated (such as Ether) to transact value, but are not just about money or payments. These decentralized applications offer a range of digitial services, such as storage, bandwidth and computation without any risk of downtime, censorship, fraud, or 3rd-party interference.

## Benefits

- **Open** - in that they are built from open-source software, by an open and accessible community of developers and executed in full view of the world. 
- **Trustless** - in that the network itself allows participants to interact publicly, or privately without a trusted third party
- **Permissionless** - in that anyone, both users and suppliers, can participate without authorisation from a governing body


## Opportunities

- Financial Tools (payments, fund raising, lending, borrowing,..)
- Identity solutions (self-sovereign, decentralized identifiers,..) 
- More secure voting and governance mechanisms
- Efficient resources management (CO2 tracking, smart grid’s,..)
- Digital ownership registries (e.g. land, collectibles, NFT’s,..)
- Supply chain tracking


## Web3 Development

[useWeb3](https://www.useweb3.xyz/) is a learning platform for developers to explore and learn about Web3. Whether you’re a new dev getting your hands dirty for the first time, or a seasoned developer making the transition into the Web3 space. 

Explore the latest resources, tutorials, challenges, tools, courses and boilerplates and start learning. Once you’re ready, browse the job board to land a job at some of the leading companies that work on core, open-source infrastructure, products, tools, frameworks, DAO's, etc.


## Further reading

- [A Cyberphunk's Manifesto](https://www.activism.net/cypherpunk/manifesto.html), Eric Hughes
- [The Meaning of Decentralization](https://medium.com/@VitalikButerin/the-meaning-of-decentralization-a0c92b76a274), Vitalik Buterin
- [Why decentralization matters](https://onezero.medium.com/why-decentralization-matters-5e3f79f7638e), Chris Dixon
- [What Is Web 3.0 & Why It Matters](https://medium.com/fabric-ventures/what-is-web-3-0-why-it-matters-934eb07f3d2b), Max Mersch and Richard Muirhead
- [What exactly is Web3?](https://youtu.be/l44z35vabvA), Juan Benet (VIDEO)


Web3 is about the next evolution of the web. A web that is more open, transparent and decentralized.

What is Web3


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


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


Introduces great features:

- React hooks - Uses React hooks as your primary building ingredient
- Auto refresh - Refreshes on a new block, wallet change or network change
- Multicall - Combines multiple blockchain calls into a single multicall

Combines the best practices:
- Modern stack - Employs ethers.js, web3-react, multicall & waffle
- Extendability - Extends easily with custom hooks
- Testability - Simple integration tests for UI and blockchain

Framework for rapid Dapp development. Simple. Robust. Extendable. Testable

useDapp


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

We can equal hashes (32 bytes arrays) using just `==`, there is no point to have an `Equal` method, and even less to check equality using the method function body which converts both arrays to bytes slices and then to strings to check for equality

Type: Enhancement

Good First Issue

W3F Approved

🕸️ Go Implementation of the Polkadot Host

gossamer

`lib/common`: remove `Equal` method for `Hash` and replace with `==`

We don't have access to specProvider in Header/BlockDecoder. It is a problem when we're changing how we decode/encode blocks. As a result, we added ugly static EIP1559TransitionBlock, and we're adding one more for withdrawals now: 
https://github.com/NethermindEth/nethermind/blob/master/src/Nethermind/Nethermind.Serialization.Rlp/HeaderDecoder.cs#L29

refactoring

good first issue

low priority

Our flagship Ethereum client for Linux, Windows, and macOS—full and actively developed.

nethermind

Rlp decoders should have access to specProvider

We started adding new version of methods to engine API. For example,
```
engine_newPayloadV2
engine_forkchoiceUpdatedV2
engine_getPayloadV2
```

Some of our [EngineModuleTests ](https://github.com/NethermindEth/nethermind/blob/0934dd2fd7181bfbeea2b9717feedf1f93a12610/src/Nethermind/Nethermind.Merge.Plugin.Test/EngineModuleTests.V1.cs) might be valid for both versions, but we can also have tests that should cover only one version. For the given test, we should be able to specify which version it covers.

test

EngineModuleTests and different versions of Engine API

In case of invalid blocks, BlockValidator & HeaderValidator should return the reason. We can send this info to CL later.

The validationMessage for CL should be set in NewPayloadHandler
https://github.com/NethermindEth/nethermind/blob/master/src/Nethermind/Nethermind.Merge.Plugin/Handlers/V1/NewPayloadV1Handler.cs#L161
https://github.com/NethermindEth/nethermind/blob/0934dd2fd7181bfbeea2b9717feedf1f93a12610/src/Nethermind/Nethermind.Merge.Plugin/Handlers/V1/NewPayloadV1Handler.cs#L301


BlockValidator should return reason/validationMessage

link to token contracts repo, not old monorepo

Type: Bug

Priority: P2 Low

nitro-docs

JavaScript

update ICustomToken links

## Description

We should implement https://github.com/ethereum/beacon-APIs/pull/254.

## Steps to resolve

We can likely use a slot comparison against fork choice's `finalized_checkpoint.epoch` for most of these.


enhancement

HTTP-API

lighthouse

Rust

Add `finalized` to HTTP API responses

This has been reported on discord. We should reproduce it and if necessary, add it to our conflicting extensions warning

Solidity and Hardhat support for Visual Studio Code

hardhat-vscode

TypeScript

Bug report: broken navigation when using tintinweb.solidity-visual-auditor

- Currently we're using the geth API `debug_traceBlockByHash` to get execution traces (with memory disabled, which we reconstruct on our side)
- We're generating a trace of accessed data in the state trie + storage trie on our side currently: https://github.com/privacy-scaling-explorations/zkevm-circuits/blob/93abf023f061c719d8737478b2d87539c517431a/bus-mapping/src/circuit_input_builder/access.rs#L111-L118 . But geth has a preState tracer https://github.com/ethereum/go-ethereum/blob/0c40df5f28b70b4aafee526bed7575520f3b827b/eth/tracers/native/prestate.go which we may use instead.
- Geth recently introduced a functionality to run several traces at the same time https://github.com/ethereum/go-ethereum/pull/26086 .  That can be useful for us

zkevm-circuits

Review usage of geth API calls

**Describe the bug**
The substrate target needs a contract version (semver) to be included in the metadata. Right now this is always just set to "0.0.1" and there is no way for the dev to set this directly, which means you need to edit the metadata file manually after compilation.

In `ink!`, this version comes from the `Cargo.toml` project file, which obv. does not exist for solidity contracts, so this needs some brainstorming on possible solutions. Existing ideas are to provide it in the `.sol` source file directly somehow (for example within a doc comment) or to simply add a CLI flag like `--contract-version X.X.X` for the substrate target.

**To Reproduce**

**Expected behavior**
There is some (documented) way to let the compiler know the contract version. It should work for all targets, as this might be an issue for other targets as well.

Solidity Compiler for Solana and Substrate

solang

Implement some way the specify contract version

 - multiple txs == MAX_TXS
 - multiple txs < MAX_TXS
 - max_rws padding
 - evm_rows padding

Add more super circuit unit tests

## Description

```solidity
pragma solidity ^0.8.17;

interface Foo {}

interface Bar {
    event MyEvent(Foo indexed indexed indexed some);
}
```

The above contract is _compiled_ while my expectation was to get a parse error. Other tools are failing to parse such source. For an instance, `solidity-coverage` HardHat plugin is failing on it. Is it intended to use multiple `indexed` entries for event arguments? Also is it documented somewhere?

## Environment

This is reproducible in Remix IDE.

## Steps to Reproduce

Run code sample from "Description" section in Remix IDE.

Regards.

bug :bug:

should report error

low effort

low impact

must have eventually

Solidity, the Smart Contract Programming Language

solidity

The `indexed` modifier can be specified multiple times for event arguments

Don't create pruning database connection when pruning is disabled

TeamGroot

snack

Web3Signer is an open-source signing service capable of signing on multiple platforms (Ethereum1 and 2, Filecoin) using private keys stored in an external vault, or encrypted on a disk.

web3signer

Java

Once we have a working BlsProvider and BlsSigner that can be imported via `bls-wallet-clients`, we should create an example dApp demonstrating how to use them. 

The example should:
- Demonstrate how to use the BlsProvider and BlsSigner
- Have multi-action transactions working
- Work locally and on testnet

This issue is concerned with creating an example **dApp.** Demonstrating how the provider and signer would work in a browser wallet or non-browser wallet is out of scope.

clients

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

bls-wallet

BLS provider/signer example dApp

Our current implementation of EIP-3540 EOF code validation in `evm/src/eof.ts` uses an older version of the reference implementation that is no longer present in the EIP.  The code still works with all current EIP3540 tests passing but it would be fruitful to update our implementation to match the current spec.  There are several items to be addressed
- [ ] `eofCodeAnalysis` should be updated to match the [current reference implementation](https://eips.ethereum.org/EIPS/eip-3540#reference-implementation) for code validation
- [ ] The current checks for EOF code check for `FORMAT` (0xEF) and `MAGIC` (0x00) separately and this has been merged in the EIP into [the `MAGIC`](https://eips.ethereum.org/EIPS/eip-3540#the-magic) (0xEF00).  These checks should be updated in `evm.ts` and `interpreter.ts` and the `FORMAT` and `MAGIC` constants exported by `eof.ts` should be consolidated to just `MAGIC`
- [ ] `loadEOFCode` in `evm/src/eof.ts` should be revised to just pull the code section from the EOF container directly by reading the `EOF` header to get the code section and do `subArray` (or `slice`) to get the code section rather than using the `codeAnalysis` method to figure out where the code section is since this duplicates the code analysis done at deploy time and is a small, but important performance drag since the whole point of the EIP is to not have to revalidate the code container every time we run the code.

help wanted

type: refactor

package: evm

Monorepo for the Ethereum VM TypeScript Implementation

ethereumjs-monorepo

Update EIP 3540 code

In `beacon-chain/state/state-native/beacon_state_mainnet.go`, instead of having:

```go
type BeaconState struct {
	latestExecutionPayloadHeader        *enginev1.ExecutionPayloadHeader        `ssz-gen:"true"`
	latestExecutionPayloadHeaderCapella *enginev1.ExecutionPayloadHeaderCapella `ssz-gen:"true"`
}
```

we should just have:
```go
type BeaconState struct {
	executionData interfaces.ExecutionData
}
```

Where `ExecutionData` is the superset. This avoids boating the beacon state with more fields of payload whenever it's updated in the future. This is much cleaner

Note that `ssz-gen` currently is unused and can be removed

credit to @Inphi for pointing this out

Help Wanted

Go implementation of Ethereum proof of stake

prysm

Make payload an interface in beacon state

From @errorists:

I’m most curious about having a global shortcut to open the modal. I would love having that, just mash on keyboard to connect to any web3 app, no need to hunt for the button

Research keyboard navigation. → ← ↑ ↓ Arrows to select wallets/networks on the grid, Enter to confirm, Backspace to go back, Escape to close, cmd+k to go straight to Search. cmd+o to open the modal

correct highlighting of selected wallets is dependant on
For items on grids (wallets / networks) use a light overlay background for hover.

feature-request

A single Web3 provider solution for all Wallets

web3modal

Keyboard shortcuts

## Description

Currently, `validator_monitor_validators_total` is a useful metric that can help infer the amount of expected attestations. However, Lighthouse emits high-cardinality metrics (validator-granularity) that make it an expensive operation (both to store and to query) to calculate the overall included/produced attestations by all managed validators.

## Version

N/A

## Present Behaviour

One would need to do a Prometheus `count()` over a metric like `validator_monitor_prev_epoch_attestation_block_inclusions`.

## Expected Behaviour

It would be a great feature to have some metrics along the lines of `validator_monitor_produced_attestations_total`/`validator_monitor_expected_attestations_total`/`validator_monitor_included_attestations_total`.

## Steps to resolve

Please describe the steps required to resolve this issue, if known.


UX-and-logs

Feature request: extend global validator metrics

Got another simple issue for a first-time contributor! We have a variable defined in `contracts-bedrock` that we don't need. Let's remove it!

https://github.com/ethereum-optimism/optimism/blob/8333f0f2c6c3a8fdfce44427cb1ef8b5e459a4f7/packages/contracts-bedrock/src/constants.ts#L28-L30

Simple task, just gotta delete this section.

M-contracts-bedrock

optimism

Remove futurePredeploys from contracts-bedrock

## Description

Now that the merge has occurred, our docs look a bit strange, because the instructions for running a node are split between several pages, including [Merge Migration](https://lighthouse-book.sigmaprime.io/merge-migration.html). I think it would be nice to have a page that steps through setting up a full node at a high-level, including checkpoint sync and connecting to the EL.

This would also be useful for users who want to run nodes without validating, for whom the current [Become a validator](https://lighthouse-book.sigmaprime.io/mainnet-validator.html) page is not relevant.

## Steps to resolve

* Write up a nice new page for the book on how to run a full node, including how to use checkpoint sync and connect to the execution layer. I think this should be written in a style that centres the `lighthouse` binaries and its flags, with no reference to e.g. `systemd` or Docker.
* Link the new page high in the table of contents. I think a sensible order might be:
  1. Introduction
  2. Installation
  3. How to run a node
  4. How to become a validator
  5. \<everything else\>
* Establish redirects from old page names to relevant new ones. The deprecated pages could live in a separate section at the very end of the book (or be hidden from the ToC?).



Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity