
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

This query was introduced only for the purposes of validator. Since #3442 we can use `FindAssetDefinitionById` to do the exact same thing. 

good first issue

iroha2

Iroha - A simple, enterprise-grade decentralized ledger

iroha

Remove `IsAssetDefinitionOwner` query

## Description

The validator client's logic for forming aggregate attestations will currently request an aggregate from the BN _before_ checking whether there are any aggregators that need to sign it:

https://github.com/sigp/lighthouse/blob/2841f60686d642fcc0785c884d43e34e47a800dc/validator_client/src/attestation_service.rs#L494-L518

This is inefficient, but also liable to cause issues with other clients, which may not be expecting to produce an aggregate when they are not subscribed to the attestation subnet. Thanks to @nflaig from Lodestar for finding and reporting this bug.

## Steps to resolve

Check whether there are any aggregators (at least one selection proof that is `Some`) before requesting an aggregate from the BN.


val-client

low-hanging-fruit

optimization

v4.6.0

lighthouse

Rust

Validator client shouldn't request aggregate with no aggregators

There is [Discv5 implementation](https://github.com/Pier-Two/Lantern.Discv5) that can be used for discovery in the Ethereum CL network. Let's wrap it with interface compatible with the implementation.

help wanted

dotnet-libp2p

Discv5 discovery protocol integration

## Description
I'm using LightHouse BN, and validator operated with Teku VC client.
If I'm trying to voluntary exit with Teku VC client, it was failed to retrieve network spec constant `MAX_REQUEST_BLOCKS` from beacon node endpoint as below. but, LightHouse BN didn't provide it.
Teku seems to check network spec configuration before run voluntary exit.

- Teku log, 
```
Loading configuration...
Failed to retrieve network spec from beacon node endpoint 'http://127.0.0.1:3600/'.
Details: Missing value for spec constant 'MAX_REQUEST_BLOCKS'
```

## Version
```
Lighthouse BN : v4.4.1
Teku VC : v23.9.0
```

## Present Behaviour

LightHouse BN didn't provide `MAX_REQUEST_BLOCKS` via beacon API. `/eth/v1/config/spec`
```
# curl -s localhost:5052/eth/v1/config/spec | jq
{
  "data": {
    "CONFIG_NAME": "prater",
    "PRESET_BASE": "mainnet",
    "TERMINAL_TOTAL_DIFFICULTY": "10790000",
    "TERMINAL_BLOCK_HASH": "0x0000000000000000000000000000000000000000000000000000000000000000",
    "TERMINAL_BLOCK_HASH_ACTIVATION_EPOCH": "18446744073709551615",
    "SAFE_SLOTS_TO_IMPORT_OPTIMISTICALLY": "128",
    "MIN_GENESIS_ACTIVE_VALIDATOR_COUNT": "16384",
    "MIN_GENESIS_TIME": "1614588812",
    "GENESIS_FORK_VERSION": "0x00001020",
    "GENESIS_DELAY": "1919188",
    "ALTAIR_FORK_VERSION": "0x01001020",
    "ALTAIR_FORK_EPOCH": "36660",
    "BELLATRIX_FORK_VERSION": "0x02001020",
    "BELLATRIX_FORK_EPOCH": "112260",
    "CAPELLA_FORK_VERSION": "0x03001020",
    "CAPELLA_FORK_EPOCH": "162304",
    "SECONDS_PER_SLOT": "12",
    "SECONDS_PER_ETH1_BLOCK": "14",
    "MIN_VALIDATOR_WITHDRAWABILITY_DELAY": "256",
    "SHARD_COMMITTEE_PERIOD": "256",
    "ETH1_FOLLOW_DISTANCE": "2048",
    "SUBNETS_PER_NODE": "2",
    "INACTIVITY_SCORE_BIAS": "4",
    "INACTIVITY_SCORE_RECOVERY_RATE": "16",
    "EJECTION_BALANCE": "16000000000",
    "MIN_PER_EPOCH_CHURN_LIMIT": "4",
    "CHURN_LIMIT_QUOTIENT": "65536",
    "PROPOSER_SCORE_BOOST": "40",
    "DEPOSIT_CHAIN_ID": "5",
    "DEPOSIT_NETWORK_ID": "5",
    "DEPOSIT_CONTRACT_ADDRESS": "0xff50ed3d0ec03ac01d4c79aad74928bff48a7b2b",
    "GOSSIP_MAX_SIZE": "10485760",
    "MIN_EPOCHS_FOR_BLOCK_REQUESTS": "33024",
    "MAX_CHUNK_SIZE": "10485760",
    "TTFB_TIMEOUT": "5",
    "RESP_TIMEOUT": "10",
    "MESSAGE_DOMAIN_INVALID_SNAPPY": "0x00000000",
    "MESSAGE_DOMAIN_VALID_SNAPPY": "0x01000000",
    "ATTESTATION_SUBNET_EXTRA_BITS": "0",
    "ATTESTATION_SUBNET_PREFIX_BITS": "6",
    "MAX_COMMITTEES_PER_SLOT": "64",
    "TARGET_COMMITTEE_SIZE": "128",
    "MAX_VALIDATORS_PER_COMMITTEE": "2048",
    "SHUFFLE_ROUND_COUNT": "90",
    "HYSTERESIS_QUOTIENT": "4",
    "HYSTERESIS_DOWNWARD_MULTIPLIER": "1",
    "HYSTERESIS_UPWARD_MULTIPLIER": "5",
    "SAFE_SLOTS_TO_UPDATE_JUSTIFIED": "8",
    "MIN_DEPOSIT_AMOUNT": "1000000000",
    "MAX_EFFECTIVE_BALANCE": "32000000000",
    "EFFECTIVE_BALANCE_INCREMENT": "1000000000",
    "MIN_ATTESTATION_INCLUSION_DELAY": "1",
    "SLOTS_PER_EPOCH": "32",
    "MIN_SEED_LOOKAHEAD": "1",
    "MAX_SEED_LOOKAHEAD": "4",
    "EPOCHS_PER_ETH1_VOTING_PERIOD": "64",
    "SLOTS_PER_HISTORICAL_ROOT": "8192",
    "MIN_EPOCHS_TO_INACTIVITY_PENALTY": "4",
    "EPOCHS_PER_HISTORICAL_VECTOR": "65536",
    "EPOCHS_PER_SLASHINGS_VECTOR": "8192",
    "HISTORICAL_ROOTS_LIMIT": "16777216",
    "VALIDATOR_REGISTRY_LIMIT": "1099511627776",
    "BASE_REWARD_FACTOR": "64",
    "WHISTLEBLOWER_REWARD_QUOTIENT": "512",
    "PROPOSER_REWARD_QUOTIENT": "8",
    "INACTIVITY_PENALTY_QUOTIENT": "67108864",
    "MIN_SLASHING_PENALTY_QUOTIENT": "128",
    "PROPORTIONAL_SLASHING_MULTIPLIER": "1",
    "MAX_PROPOSER_SLASHINGS": "16",
    "MAX_ATTESTER_SLASHINGS": "2",
    "MAX_ATTESTATIONS": "128",
    "MAX_DEPOSITS": "16",
    "MAX_VOLUNTARY_EXITS": "16",
    "INACTIVITY_PENALTY_QUOTIENT_ALTAIR": "50331648",
    "MIN_SLASHING_PENALTY_QUOTIENT_ALTAIR": "64",
    "PROPORTIONAL_SLASHING_MULTIPLIER_ALTAIR": "2",
    "SYNC_COMMITTEE_SIZE": "512",
    "EPOCHS_PER_SYNC_COMMITTEE_PERIOD": "256",
    "MIN_SYNC_COMMITTEE_PARTICIPANTS": "1",
    "INACTIVITY_PENALTY_QUOTIENT_BELLATRIX": "16777216",
    "MIN_SLASHING_PENALTY_QUOTIENT_BELLATRIX": "32",
    "PROPORTIONAL_SLASHING_MULTIPLIER_BELLATRIX": "3",
    "MAX_BYTES_PER_TRANSACTION": "1073741824",
    "MAX_TRANSACTIONS_PER_PAYLOAD": "1048576",
    "BYTES_PER_LOGS_BLOOM": "256",
    "MAX_EXTRA_DATA_BYTES": "32",
    "MAX_BLS_TO_EXECUTION_CHANGES": "16",
    "MAX_WITHDRAWALS_PER_PAYLOAD": "16",
    "MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP": "16384",
    "BLS_WITHDRAWAL_PREFIX": "0x00",
    "DOMAIN_BEACON_ATTESTER": "0x01000000",
    "DOMAIN_RANDAO": "0x02000000",
    "DOMAIN_AGGREGATE_AND_PROOF": "0x06000000",
    "DOMAIN_SYNC_COMMITTEE_SELECTION_PROOF": "0x08000000",
    "TARGET_AGGREGATORS_PER_COMMITTEE": "16",
    "DOMAIN_SELECTION_PROOF": "0x05000000",
    "DOMAIN_SYNC_COMMITTEE": "0x07000000",
    "DOMAIN_BEACON_PROPOSER": "0x00000000",
    "DOMAIN_VOLUNTARY_EXIT": "0x04000000",
    "DOMAIN_APPLICATION_MASK": "0x00000001",
    "DOMAIN_CONTRIBUTION_AND_PROOF": "0x09000000",
    "TARGET_AGGREGATORS_PER_SYNC_SUBCOMMITTEE": "16",
    "DOMAIN_DEPOSIT": "0x03000000",
    "SYNC_COMMITTEE_SUBNET_COUNT": "4"
  }
}
```

## Expected Behaviour

Provide `MAX_REQUEST_BLOCKS` constant value through beacon API `/eth/v1/config/spec`

## Steps to resolve

Need to provide `MAX_REQUEST_BLOCKS` constant value for voluntary-exit with Teku VC Client.

enhancement

Compatibility with Teku VC for voluntary-exit

**Describe the bug**

The text on the Manage Connections screen is unreadable in dark mode.

 


**Screenshots**
![image](https://github.com/MetaMask/metamask-mobile/assets/12821081/0dcc6de3-9e78-4071-a345-f8bba48b303f)


**To Reproduce**
Ensure dark mode is enabled on your device. 
Launch the app
Go to privacy and settings
screen down to the "manage connections section"
Tap on the manage connections CTA. 
Notice the text is in dark mode. 

**Expected behavior**
The text should be visible and readable in both light and dark mode. 


**Smartphone (please complete the following information):**
 - Device: [e.g. iPhone6]
 - OS: [e.g. iOS8.1]
 - App Version [e.g. 1.0.0] - find version number in app from Settings > About MetaMask


-------------------------------------------------------------
_to be added after bug submission by internal support / PM_
**Severity**


- How critical is the impact of this bug on a user?
- Add stats if available on % of customers impacted
- Is this visible to all users?
- Is this tech debt?


type-bug

Sev3-low

team-design-system

Mobile web browser providing access to websites that use the Ethereum blockchain

metamask-mobile

JavaScript

BUG] Settings: Security & Privacy: Manage connections: cannot see text in dark mode

### Describe the feature you would like

In EVM circuit, we still manually track read-write indices in many places, which hurts readability and is error-prone. `StepRws` is a struct that can track the read-write index automatically. The task is to use `StepRws` everywhere in the EVM circuits. #1582 is an example of applying StepRws in callops.rs.

If the "everywhere in the EVM circuits" is too much for one PR, we can target the following files first, which are the hot spots that can benefit from StepRws most.

zkevm-circuits/src/evm_circuit/execution/
- [ ] create.rs
- [ ] end_tx.rs
- [ ] error_oog_call.rs
- [ ] error_oog_memory_copy.rs
- [ ] error_oog_sload_sstore.rs
- [ ] error_return_data_oo_bound.rs
- [ ] error_write_protection.rs
- [ ] extcodecopy.rs
- [ ] extcodehash.rs
- [ ] extcodesize.rs
- [ ] logs.rs
- [ ] return_revert.rs
- [ ] returndatacopy.rs
- [ ] sha3.rs
- [ ] sload.rs
- [ ] sstore.rs

### Additional context

The following code snippet shows an example of getting stack values from the read-write table. The 0, 1, 2, 3 are the rw-indices, pointing to the table row values the bus-mapping wrote.

https://github.com/privacy-scaling-explorations/zkevm-circuits/blob/242d38b44730d9766661c885d0a27df00589ce39/zkevm-circuits/src/evm_circuit/execution/extcodecopy.rs#L185-L186

The co-responding values were written here in the bus-mapping.

https://github.com/privacy-scaling-explorations/zkevm-circuits/blob/242d38b44730d9766661c885d0a27df00589ce39/bus-mapping/src/evm/opcodes/extcodecopy.rs#L55-L68

Mismatched reads should cause some tests to fail.

Add this line to get debug information on the read-write operations.

```diff
diff --git a/zkevm-circuits/src/test_util.rs b/zkevm-circuits/src/test_util.rs
index 0cffa92f9..00456b9ad 100644
--- a/zkevm-circuits/src/test_util.rs
+++ b/zkevm-circuits/src/test_util.rs
@@ -201,6 +201,7 @@ impl<const NACC: usize, const NTX: usize> CircuitTestBuilder<NACC, NTX> {
         };
         let params = block.circuits_params;
 
+        block.debug_print_txs_steps_rw_ops();
         // Run evm circuit test
         {
             let k = block.get_test_degree();
```

T-feature

zkevm-circuits

Use more StepRws in EVM circuits

ATM, there are no permissions for registering asset definitions in the default validator, i.e. all `Register<AssetDefinition>` operations are never denied. For example it is allowed that `alice@wonderland` registers a new asset definition `xor#genesis`. Should we disallow `alice@wonderland` from accessing other domains by default and introduce some tokens to grant such a privilege?

Enhancement

question

`Register<AssetDefinition>` permissions

- run `npm init` to create a package.json
- Add the same github action we are using in the optimism superchain tokenlist to publish it to npm (except delete any code that is building or installing node modules since in this case we have neither)
- Add npm secret

superchain-registry

Publish superchain registry as a npm package

eg if you get your password wrong, you get an empty response rather than "Invalid password".

Stepping through it with a debugger I can see the "Invalid password" error but it gets lost somewhere

```

➜  ~ curl -X POST --data '{"username":"username1","password":"NotMyPassword"}' http://localhost:8545/login


➜  ~ curl -X POST --data '{"username":"username1","password":"MyPassword"}' http://localhost:8545/login


{"token":"redacted"}%
➜  ~
```

latest besu
following instructions here to setup username/password auth https://besu.hyperledger.org/stable/public-networks/how-to/use-besu-api/authenticate#json-rpc-permissions


TeamGroot

TeamRevenant

TeamChupa

snack

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

besu

Java

username/password authentication - errors not presented to user

https://github.com/llvm/llvm-project/blob/3af4590506634fa176be5cb5f53161f96609730c/clang/lib/Parse/ParseExpr.cpp#L1071

This works:
```c++
template <bool>
struct _BoolConstant {};

#if __has_builtin(__is_destructible)
template <class _Tp>
struct is_destructible : _BoolConstant<__is_destructible(_Tp)> {};
#endif
```

But this doesn't:
```c++
template <bool>
struct _BoolConstant {};

template <class _Tp>
struct is_destructible : _BoolConstant<__is_destructible(_Tp)> {};
```

This suggests there may be something stateful involved with `__is_destructibe` showing up first in the `__has_builtin`.

pasta

Investigate revertible type traits

The Rationale section says P2SH address types map well enough to EVM accounts for the purposes of CAIP-10 interop, but the examples start with 1 and are thus P2PKH addresses.

https://bitbox.swiss/blog/what-are-bitcoin-address-types/

Also, the regexp doesn't constrain the first byte of the address with an enum, and probably should if only certain BTC address types are valid...

Speaking of which, what about taproot and segwit addresses?

Chain-Agnostic Namespaces host informative specs and profiles of CAIPs (Chain-Agnostic Improvement Proposals) per blockchain ecosystem

namespaces

HTML

BTC/CAIP-10 example doesn't match text - P2SH versus P2PKH

documentation

Component: Forge

Blazing fast toolkit for developing Starknet contracts.

starknet-foundry

Link scarb docs about setting `scarb test` alias to snforge in our docs

The AATH tests are still using Indy SDK. Update the AATH Test Agent to use Askar and the shared components.

High Priority

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

Python

Update ACA-Py AATH Test Agent to Askar

**Describe the problem**
I'm trying to run a dappeteer script on ubuntu 22.04, here is the script test.mjs:

```javascript
import dappeteer from "@chainsafe/dappeteer";
import "dotenv/config";

async function main() {
  const { metaMask, browser } = await dappeteer.bootstrap();
}

main();
```
I run the command 
`node tests.mjs`

And I get the error `Failed to launch both playwright and puppeteer`

**System:**
- OS: Ubuntu 
- OS 22.04
- NodeJs version v18.16.0
- dappeteer version 5.2.0


🏌🏼‍E2E testing for dApps using Puppeteer + MetaMask

dappeteer

TypeScript

Does not work on ubuntu 22.04

### Context

[Barretenberg releases](https://github.com/AztecProtocol/barretenberg/releases) currently captures PRs into their changelogs assuming [PR numbers all belong to this repo](https://github.com/AztecProtocol/barretenberg/blob/297a20d7878a4aabab1cabf2cc5d2d67f9e969c5/.github/workflows/release-please.yml#L28).

### Problem

This works as expected with PRs created in this repo.

But when PRs are mirrored from [_AztecProtocol/aztec-packages_](https://github.com/AztecProtocol/aztec-packages/), the release changelogs would be linking to `https://github.com/AztecProtocol/barretenberg/<aztec-packages_PR_number>`, which points to unrelated / non-existing PRs in this repo.

#### Example

Take [v0.5.0](https://github.com/AztecProtocol/barretenberg/releases/tag/barretenberg-v0.5.0) as an example:

Clicking "#1925" of "update to acvm 0.24.0" would link to [AztecProtocol/**barretenberg**/issues/1925](https://github.com/AztecProtocol/barretenberg/issues/1925), rather than the actual PR [AztecProtocol/**aztec-packages**/pull/1925](https://github.com/AztecProtocol/aztec-packages/pull/1925).

### Happy Case

Either the release-please or mirroring workflow should be fixed to cater for capturing mirrored PRs in changelogs appropriately.

barretenberg

Fix changelog capturing of PRs from _AztecProtocol/aztec-packages_

currently we're using `json!(null)` to create permission token without payload. I think it would be more appropriate to use `json!({})`

Replace `null` with `{}` in token payload

**Describe the bug**
As the title of the ticket says, we have text overflow in the tab bar action sheet. 


**Screenshots**
See screenshot [here](https://app.screencast.com/yjjxzMVVvAAo2)


**To Reproduce**
1. Go to settings
2. change your language to French
3. tap on the action button in the bottom tab bar
4. Notice the text overflows on the sheet.  



**Smartphone (please complete the following information):**
 - Device: [ iPhone 11, iPhone SE]
 - OS: [iOS 16.6]
 - App Version [7.6] 


-------------------------------------------------------------
_to be added after bug submission by internal support / PM_
**Severity**


- How critical is the impact of this bug on a user?
- Add stats if available on % of customers impacted
- Is this visible to all users?
- Is this tech debt?


Text over flow in tab bar action sheet when language is set to French & Greek

`RunnerStatus` https://github.com/foundry-rs/starknet-foundry/blob/621a1a5abb49fe41f459f655901cff0c915809e8/crates/forge/src/lib.rs#L60 should be renamed to `RunnerExitStatus` to better reflect the purpose of this enum.

Additionally, `Default` exit status should be renamed to `Normal` or `Standard` (or other), since `Default` can be confusing considering rust's https://doc.rust-lang.org/std/default/trait.Default.html trait.  

Refactor `RunnerStatus`

In multiple tests across forge codebase different name is used for the rust test and cairo test, e.g. here https://github.com/foundry-rs/starknet-foundry/blob/621a1a5abb49fe41f459f655901cff0c915809e8/crates/forge/tests/integration/deploy.rs#L136 the rust test is named `test_deploy_fails_on_too_many_constructor_arguments` but the cairo one is `deploy_invalid_calldata`.

Change the name of cairo tests so the are the same as rust tests.

Unify cairo and rust test names in forge integration tests

Per MDN: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy

Looks like this got renamed a while back; we should probably flag a `MEH` is a site reports `Feature-Policy`.

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity