
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


Node Guardians is a gamified educational platform that creates lore-rich programming challenges for experienced Solidity, Huff, Cairo and Noir developers. Think of it as a skill-based RPG where developers can become familiar with specific stack components and a place where they can showcase their abilities. 

### Skills Upgrade

We have created a series of coding challenges called “quests” to engage smart contract developers, providing them with the knowledge to build safe and gas efficient applications. In addition to practical skills, we also provide theoretical knowledge about crypto history, technology and economics through building a library of articles that break down complex concepts of distributed systems & decentralized finance.


### Public Good

Node Guardians is a public good for developers and will always remain so. 
In addition to supporting the growth of cool ecosystems, we plan to make the platform sustainable by managing [infrastructure](https://infra.nodeguardians.io/) across various networks.

Rewarding non-contributing operators wastes funds, we prefer community-building and education.


Node Guardians is a gamified educational platform that creates lore-rich programming challenges for experienced Solidity, Cairo, Huff and Noir developers.

Node Guardians


Speed Run Ethereum aims to provide a structured learning path for onboarding developers to Ethereum.

Ethereum Dev Speed Run with a framework for submitting challenges, get feedback from ethereum builders, and in the process unlocking new challenges and proof of completion.

Speedrun Ethereum

Teaching the next generation of smart contract developers and auditors. Learn from industry-leading experts how to build the next generation of web3 applications and level up your career.


Level up your web3 career through industry leading comprehensive courses

Cyfrin Updraft


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 practical 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


Navigating conversations and understanding key concepts in web3 sometimes requires its own terminology. In this regard, web3 is not just a technological shift, but also a cultural one.

This guide will provide you with the **most essential terms** to decode the language and become a web3 citizen. It is tailored to provide you with clear and concise definitions for the unique terms that define this industry.

Dive in, discover, and enhance your fluency in the unique lexicon of the web3 industry. (-:

If you want to contribute to the glossary, [have a look on Github](https://github.com/wslyvh/useWeb3/tree/main).

## Glossary a-z

- **Airdrop**  
  Distribution of free tokens, usually to promote a product or incentivise early users

- **Altcoin**  
  Alternative coin, any cryptocurrency other than Bitcoin

- **AMM**  
  Automated Market Maker, popular mechanism among decentralized exchanges (DEXes) involving liquidity pools instead of an orderbook-based system

- **Anon**  
  Anonymous, entity that wishes to remain anonymous or pseudonymous

- **Beacon Chain**  
  Ethereum’s proof-of-stake (PoS) consensus layer

- **Bridge**  
  Service that transfers tokens between multiple blockchains (cross-chain)

- **BUIDL**  
  Term to describe the web3 building ethos, even despite a bear market, inspired by HODL

- **CeFi**  
  Centralized finance, the “traditional” finance sector, in contrast to DeFi (decentralized finance)

- **CEX**  
  Centralized Exchange, app for swapping tokens run by a company, often used for fiat exchange; in contrast to DEX (Decentralized Exchange)

- **Cypherpunks**  
  Cypher + punks, movement originating in the early 90s, emphasizing the need for privacy in the digital age, enforced by cryptography

- **DAO**  
  Decentralized Autonomous Organization, blockchain-based organizations that are owned and governed by their members via tokens

- **DApp**  
  Decentralized Application, blockchain-based services that use smart contracts in their backend and thus have a distributed nature, without the need for intermediaries

- **DeFi**  
  Decentralized Finance, general term for decentralized services in the financial sector, that are permissionless and globally available, e.g., DEXes (decentralized exchanges) or lending protocols

- **Degen**  
  Degenerate, term for a person that is deeply involved in crypto or a specific sector, e.g., DeFi Degens

- **DEX**  
  Decentralized Exchange, blockchain-based app for swapping tokens that use smart contracts to be permissionless

- **Diamond Hands**  
  Holding a digital asset through very volatile times

- **DYOR**  
  Do Your Own Research, principle of self-verification instead of trusting others

- **EIP**  
  Ethereum Improvement Proposal, a process to describe standards for the Ethereum platform

- **ERC**  
  Ethereum Request for Comments, form of EIP to specify application layer standards; the most popular ones are ERC20 for fungible tokens and ERC721 for non-fungible tokens

- **EVM**  
  Ethereum Virtual Machine, the environment in which all Ethereum accounts and smart contracts live, the EVM defines the rules for computing a new valid state from block to block

- **Exchange**  
  An application that allows users to buy and sell crypto assets

- **Exit Scam**  
  Scenario in which a project or a part of a team steals the investors’ money and leaves

- **Explorer**  
  Webpage that displays information about the transaction history of a blockchain

- **Faucet**  
  Service that dispenses free tokens, usually for test networks

- **Flippening**  
  Term to describe a pivotal change in price or perception, e.g., when the market cap of a token exceeds the one of another token

- **FOMO**  
  Fear Of Missing Out, term to describe the feeling of not being included in something, e.g., a crypto investment or news

- **Fork**  
  Split of a blockchain or project due to technical issues or a dispute

- **FUD**  
  Fear, Uncertainty and Doubt, the opposite of FOMO

- **Gas**  
  Term for the fee that Ethereum transactions cost; it is used to reward validators and prevents malicious use of the blockchain

- **Genesis Block**  
  The first block recorded in a blockchain

- **Gm**  
  Good morning, form of greetings in crypto communities; due to the global nature of web3 it can be used at any time of the day

- **Hash**  
  Function that can be used to map data of arbitrary size to fixed-size values, e.g., for encryption, cryptographic hash functions are used in many parts of the web3 industry

- **HODL**  
  A frequent term referring to a strict buy-and-hold strategy, became famous after a misspelling in the bitcointalk forum in 2013

- **ICO**  
  Initial coin offering, the process of selling tokens when launching a new crypto project, inspired by the initial public offering (IPO) for stocks.

- **JOMO**  
  Joy Of Missing Out, converting FOMO into a positive feeling

- **KYC**  
  Know Your Customer, a process to verify the identity of customers; often used by centralized exchanges or entities

- **Layer 1**  
  Base blockchain architecture that serves as the foundation for other layers, also called mainnet, e.g., Ethereum

- **Layer 2**  
  Built on top of layer 1, usually for scaling purposes, e.g., Optimism

- **Minting**  
  Process of creating new token(s)

- **Mixer**  
  Decentralized Application that “mixes” tokens to cover their transaction history, used for private transactions

- **NFT**  
  Non-Fungible Token, a type of token that is not interchangeable or divisible, in contrast to fungible tokens; often used for digital collectibles

- **Node**  
  An instance holding a copy of the blockchain, it is connected to other nodes, synchronizing the blockchain and thus forming the network

- **OG**  
  Original Gangster, a person who was very early involved in crypto or a specific project

- **Oracle**  
  Data bridge to bring real-world information onto the blockchain

- **P2P**  
  Peer-to-peer, referring to a transaction between two people without other (central) parties involved

- **Rollups**  
  Popular type of layer 2, scaling solution that uses transaction bundling (“rolling up”) transactions before publishing them to the main chain

- **Rug Pull**  
  Scenario in which a team abandons a project and/or removes its liquidity, similar to exit scams

- **SBTs**  
  Soul-Bound-token, type of NFT that is non-transferrable

- **Smart contract**  
  Programs that run on the blockchain that follow the "if this then that" logic, they execute themselves when certain conditions are met

- **Snapshot**  
  Record of a blockchain at a particular block height, also the name of a popular DAO voting tool

- **Solidity**  
  Smart Contract Programming Language, created for the Ethereum blockchain but popular for other chains as well

- **Stablecoin**  
  A cryptocurrency that is pegged to another asset, mostly USD

- **Staking**  
  Process of locking tokens to contribute to validation in a proof of stake blockchain

- **Token**  
  Representation of a digital asset on a blockchain

- **TVL**  
  Total Value Locked, equivalent of USD locked in a blockchain or protocol, often used as an indicator in DeFi, e.g. in lending protocols

- **Validator**  
  Virtual entity participating in the consensus of a proof of stake blockchain, they participate in producing blocks and validating transactions

- **WAGMI**  
  Acronym for “We're All Gonna Make It”, expression used to show an optimistic attitude about the future of web3

- **Whale**  
  An entity holding a large amount of cryptocurrency, sometimes even a significant part of a project

- **Whitepaper**  
  Document that is released with new crypto projects to explain the details of the project.

- **ZKP**  
  Zero-Knowledge-Proof, cryptographic mechanism to verify an information without revealing it, often used for scaling solutions of privacy applications


The glossary provides you with definitions for the most important terms to navigate the web3 landscape.

Crypto glossary – important terms to navigate web3


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


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


ETH Gas Tracker helps you discover how gas works, why it matters and help you set optimal gas fees to use the Ethereum network more efficiently. Get real-time gas prices, historical data, and average fees to time your transactions and save money. Ethereum Gas Tracker is the best way to track gas prices and provides an API for developers to integrate gas data into their applications.

Monitor and track the Ethereum, and L2 gas prices to reduce transaction fees and save money

ETH Gas Tracker


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

Teku implemented this recently https://github.com/Consensys/teku/pull/8168 and it should be quite easy to add in Lodestar as well.

Seems useful to have since with [EIP-7044](https://eips.ethereum.org/EIPS/eip-7044) signed voluntary exit messages are perpetually valid and more people might wanna prepare exit messages without actually publishing them.

The alternative to this right now is to use [signVoluntaryExit](https://ethereum.github.io/keymanager-APIs/?urls.primaryName=dev#/Voluntary%20Exit/signVoluntaryExit) API of the keymanager or external tooling.

prio-low

good first issue

help wanted

meta-feature-request

🌟 TypeScript Implementation of Ethereum Consensus

lodestar

TypeScript

Allow voluntary exit command to write to file rather than publish 

### Is your feature request related to a problem? Please describe.

Currently there is a page titled [How The Merge impacted ETH supply](https://ethereum.org/en/upgrades/merge/issuance/) which was originally created to focus on the changes taking place with the issuance of ether via the transition to proof-of-stake via The Merge. With a successful Merge behind us, this page has been updated with post-merge figured, but is still primarily focused on how ether issuance changed as a result of this network upgrade.

### Describe the solution you'd like

A new generalized page on the issuance of ether. This page would likely live at `/eth/issuance` instead of nested within the upgrade section of the site, and should more broadly educate on how ETH is issued for people who are newer to the ecosystem, without complicating the topic with comparisons to proof-of-work days. 

The existing page will not last forever as the pages related to network upgrades continue to evolve and progress, leaving the need for a long term resource that clearly lays out the factors that influence ether supply.

Content from the existing page could be rolled forward and updated to remove unnecessary copy, along with work that has already been prepped and tabled in PR #7921.

### Describe alternatives you've considered

- Leave the existing page `/upgrades/merge/issuance` as the primary resource to direct people to regarding ether supply. 
- Link to external resources for this information

Would prefer neither of these myself.

### Additional context

- Re-surfaced from issue #8444 to raise awareness/attention

feature ✨

content 🖋️

Status: Stale

Ethereum.org is a primary online resource for the Ethereum community.

ethereum-org-website

Markdown

Feature request: General ether issuance page

https://github.com/hyperledger/firefly-evmconnect/pull/112 removed a check for odd-length revert hex strings, which some EVM nodes (such as Besu) _**can**_ return in some cases. We need to reinstate support for padding with a leading `0` for any odd-length hex in revert reasons.

firefly-evmconnect

Revert hex processing needs to support odd-length hex strings

### Issue
My compiled_contract_class.json generated with snfoundry fails when i try to declare it.
The size of file is `28 megabytes` and when snfoundry tries to send it to `juno` it `errors` following msg:
```
command: declare
error: Unknown RPC error: data did not match any variant of untagged enum JsonRpcResponse: data did not match any variant of untagged enum JsonRpcResponse
```
But i expect to see:
```
command: declare
error: Contract class size is too large
```

The log-level `trace` is `not` yet `available` as mentioned here https://github.com/NethermindEth/juno/issues/1767
I cannot provide much more info then this (no important logs in debug log-level) but i am happy to help with reproduction of this issue.

There is `no` such `issue` when i send `10 megabytes` contract class to juno it behaves as expected.

Do u know how to solve this issue? And why it happens?

### Versions
snfoundry v0.20.1
scarb nightly-2024-03-16 
nethermindeth/juno:v0.11.4

Good first issue

no-stale

juno

RPC fails with large contract class size

# Description
If selector is written incorrectly and it doesn't match any rpcs, the build just skips generation of actix (server?). This issue becomes non-trivial to debug :)
Instead, it would be useful to fail and report the faulty selector to the user.

# Possible solutions
Result of `.get` there could be used to indicate it:
https://github.com/blockscout/actix-prost/blob/32188ff27483da72a6fb8a40ad6ba8d685b07cf1/actix-prost-build/src/generator.rs#L43-L53

enhancement

actix-prost

Rust

actix-prost: Fail build when selector does not match anything

## Description

Every time, the functions `handleRefresh` and `toggleIsEnabled` are called, there are two requests to the Bandada API. Just one request is required, the one related to updating the info in the backend (`updateApiKey`), the other to get the admin information (`getAdmin`) shouldn't be necessary since all the info is already in the frontend. 

The idea is to write the component in a way that only the `updateApiKey` request is sent to the Bandada API. 

refactoring :recycle:

A system for managing privacy-preserving groups.

bandada

Refactor the `ApiKeyComponent` code in the dashboard

indexer

multiplier

Handle `DecompositionDecl` in reference kind classification

This is a change request

## Problem

We currently have camel case as well as snake case exports within our codebase:

![image](https://github.com/waku-org/js-waku/assets/35004822/09e6e898-119e-4ec1-a580-0ee371e30b76)

## Proposed Solutions

Standardise it to use camel case


## Notes

- Related to https://github.com/waku-org/js-waku/pull/1913#discussion_r1536298429

js-waku

chore: standardise exports to camel case

We currently have documentation on how to send/receive/check balances of assets in multiple places throughout the book. There should be a section which covers assets from start to end.

- [Custom Asset Transfer](https://rust.fuel.network/master/calling-contracts/custom-asset-transfer.html)
- [Output Variables](https://rust.fuel.network/master/calling-contracts/variable-outputs.html)
- [Call Parameters](https://rust.fuel.network/master/calling-contracts/call-params.html)
- [Accounts](https://rust.fuel.network/master/accounts.html)
- [Checking Balances and Coins](https://rust.fuel.network/master/wallets/checking-balances-and-coins.html)
- [AssetId](https://rust.fuel.network/master/types/asset-id.html?highlight=asset#assetid)

documentation

dev-experience

fuels-rs

Add an Asset documentation section to the book

We should add https://hackmd.io/@dapplion/lodestar_attestation_summary to our docs to make it more discoverable / visible. We could also create a dedicated page about effectiveness and provide instructions on how to debug sub optimal performance, e.g. what metrics to look at in which order, what logs to look at, important timings etc.

Similar to https://lighthouse-blog.sigmaprime.io/attestation-analysis.html 

scope-documentation

Add attestation performance explainer to docs

**Problem**
Currently, the information section for use of Private Keys in an `.env` file for local development states:

> The private key of your wallet will be included in the `.env` file of the project and won't be pushed to GitHub.

We teach to always avoid [private keys in .env files](https://www.youtube.com/watch?v=VQe7cIpaE54) as it's one of the most common ways new web3 developers (experienced or not) lose funds. We even have students pledge to never put private keys with funds in them, and it's an anti-pattern that has been propagated across web3 hurting new people. [pledge one](https://github.com/smartcontractkit/full-blockchain-solidity-course-js/discussions/5) and [pledge 2](https://github.com/Cyfrin/foundry-full-course-f23/discussions/5#discussioncomment-8839188)

**Proposed Update**

> The private key of your wallet will be included in the `.env` file of the project and won't be pushed to GitHub. However, as this means the private key is in plain text, it's recommended to use a private key that isn't associated with any real funds.

Developer documentation site for zkSync community.

zksync-docs

Update warning of using private keys in `.env` file

Related issue https://github.com/FuelLabs/fuel-core/issues/1560

Due to `connection_limits`, it is not possible to connect to bootstrap nodes and get information about other peers in the network. Because of that, if all connections are occupied, it is impossible to connect to the network without knowing other available bootstrap nodes.

SDK team

Rust full node implementation of the Fuel v2 protocol.

fuel-core

Bootstrap nodes should help discover other nodes in the network before shutting down the connections

- `messages` https://github.com/hyperledger/aries-vcx/tree/main/aries/messages crate typically types DID attributes (for example in did-exchange `ResponseContent` message type) as `String`.
- Use `did_parser_nom`'s https://github.com/hyperledger/aries-vcx/tree/main/did_core/did_parser_nom `Did` type instead so we parse&verify DIDs upon message deserialization.



aries-vcx is set of crates to work with DIDs, DID Documents, DIDComm, Verifiable Credentials and Hyperledger Aries.

aries-vcx

Use `Did` type in `messages` crate

**Describe the improvement you're thinking about**

This issue is conceptually similar to #188, now applied to the `message` argument to eddsa-poseidon's `signMessage` rather than the private key.  This argument is typed as `BigNumberish` and the docs don't say anything special about how it's interpreted.  The message of the underlying Poseidon algorithm is expected to be a single field element (bigint mod r).

The `checkMessage` function used to check this input allows arbitrary strings.  If a string is valid decimal or hex, it'll be converted to a bigint as digits.  Otherwise it'll be converted to a Buffer as raw bytes.  This works so long as the string isn't more than 32 characters.  If it's longer, it'll trigger an exception later from `leBigIntToBuffer` which uses a size argument.

This might be intended to be a convenience feature for signing string messages.  If so, it would need to be more clearly documented.  I think the size limitation and the potential for confusion about whether a small string should be treated as digits or bytes suggests it would be better to remove this case and reject string inputs which can't be interpreted as stringified bigints.

**Additional context**
I came across this when writing tests for handling of bad inputs in the Zupass repo.  I passed a string expecting a TypeError and was surprised to get no exception.  I've added my own type check to avoid the potential confusion here, so I'm not blocked by this issue.

A monorepo of reusable libraries for zero-knowledge technologies.

zk-kit

Restrict types of `message` in eddsa-poseidon's `signMessage`

The current implementation of `VerificationMethod` looks as follow:

```
#[derive(Serialize, Deserialize, Clone, Debug, PartialEq, TypedBuilder)]
#[serde(rename_all = "camelCase")]
pub struct VerificationMethod {
    id: DidUrl,
    controller: Did,
    #[serde(rename = "type")]
    verification_method_type: VerificationMethodType,
    #[serde(flatten)]
    public_key: PublicKeyField,
}
```

and 

```
#[derive(Serialize, Deserialize, Clone, Debug, PartialEq)]
#[serde(untagged)]
#[serde(deny_unknown_fields)]
pub enum PublicKeyField {
    #[serde(rename_all = "camelCase")]
    Multibase { public_key_multibase: String },
    #[serde(rename_all = "camelCase")]
    Jwk { public_key_jwk: JsonWebKey },
    #[serde(rename_all = "camelCase")]
    Base58 { public_key_base58: String },
    #[serde(rename_all = "camelCase")]
    Base64 { public_key_base64: String },
    #[serde(rename_all = "camelCase")]
    Hex { public_key_hex: String },
    #[serde(rename_all = "camelCase")]
    Pem { public_key_pem: String },
    #[serde(rename_all = "camelCase")]
    Pgp { public_key_pgp: String },
}

```

The current internal representation `VerificationMethod` maps 1:1 with how Verification Method object is described. This makes it de/serialization simple, given that it default serde de/serialization is sufficient. However, it's not data model one would naturally come up if this was designed if de/serialization wasn't concern, for following reasons:
  - it's doesn't follow Law of Demeter - encoded representation is concern of de/serialization, in-memory encoding serves here no purpose
  - it's not efficient - whenever we want to read raw key value from a Verification Method, we need to re-decode they key value
   - deserialization of `VerificationMethod` does not provide guarantee as to whether the key is correctly encoded - it only guarantees the value is a String. Decoding is indirectly verifier upon upon an attempt to read raw key value from `public_key`

That being said, we likely want to keep attached information about "how should the raw key be encoded"  upon serialization. Upon deserialization, we can set the value based on key encoding in the input.

Addressing this will be mainly matter of changes to `VerificationMethod` struct:
- getting rid of `PublicKeyField` struct in favor of storing raw bytes
- introducing flag signalling encoding to be used upon serialization
- customizing process of serde de/serialization 
      

Improve didcore `VerificationMethod` in-memory representation

This is a **feature request**

## Problem

Right now is https://github.com/waku-org/js-waku/actions/workflows/pre-release.yml is triggered - all packages will be released.

## Proposed Solutions

We want to release only those that actually have any changes so that if edit happened in `@waku/interface` and `@waku/core` - only they should be published to npm.

feat: improve rc release to release only affected package 

Optimism SDK is now in maintenance mode and we want to start sending developers to viem instead since it supports fault proofs. This means all the sdk tutorials will need to revised for viem. This issue if for 1 of 7 SDK tutorials that needs to be rewritten for [viem](https://viem.sh/) 💟 

tutorial

docs

[TUTORIAL] update communicating between chains in solidity (using the sdk) to viem

[TUTORIAL] update using the optimism sdk (for chain operators) to viem

[TUTORIAL] update bridging erc-20 with the sdk to viem

For example:

```markdown
Full specification: <https://github.com/ethereum/consensus-specs/blob/5d80b1954a4b7a121aa36143d50b366727b66cbc/specs/_features/eip7002/beacon-chain.md>
```

Generates the following diagnostic:

```
error[markdown-re-eip-dash]: proposals must be referenced with the form `EIP-N` (not `EIPN` or `EIP N`)
   --> EIPS/eip-7002.md
    |
535 | Full specification: <https://github.com/ethereum/consensus-specs/blob/5d80b1954a4b7a121aa36143d50b366727b66cbc/specs/_features/eip7002/beacon-chain.md> 
    |
    = info: the pattern in question: `(?i)eip[\s]*[0-9]+`
    = help: see https://ethereum.github.io/eipw/markdown-re-eip-dash/
```

Reported by @lightclient in [this run](https://github.com/ethereum/EIPs/actions/runs/8348890291/job/22851815218?pr=8228) on [this PR](https://github.com/ethereum/EIPs/pull/8228).

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity