
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

Building OOB invitation is fundamental way for anyone to get started with aries-vcx, in its current state. The first thing you ever need if you want to simulate a basic use case with aries-vcx is to create the oob invitation.
This need came up for example in:
- https://github.com/hyperledger/aries-vcx/issues/870
- mentorship mediator project https://github.com/nain-F49FF806/axum-test-server/tree/main/src

Currently in `aries_vcx/src/handlers/out_of_band` there's `OutOfBandSender` which is position on same level like other protocol handlers, but in fact, this is just a builder for OOB messages. 
More-over, working with the `OutOfBandSender` is currently difficult, because it's method
```
pub fn append_service(mut self, service: &OobService) -> Self {
```
ultimately requires you to import `diddoc_legacy` into your project, which is not obvious.

###  Proposal:
- There's already established consensus that builder for messages crate is necessary, and constructing message by hand is currently cumbersome.
- So let's use this as opportunity to create first message builder, specifically for oob invites; also get rid of `OutOfBandSender` in the process

### Additional note:
There's also `OutOfBandReceiver` - we'll get rid of that in separate step - it contains method. `nonmediated_connection_exists` which is being used in some NodeJS tests.



good first issue

AriesVCX is a Rust library for building web and mobile applications issuing, holding, presenting and verifying Verifiable Credentials in accordance to the standards set by Hyperledger Aries.

aries-vcx

Rust

Oob builder for messages crate

This should generate skeleton taking into account:
- pass name
- source/target dialect
- options
- dependentDialects


enhancement

generator

VAST is an experimental compiler pipeline designed for program analysis of C and C++. It provides a tower of IRs as MLIR dialects to choose the best fit representations for a program analysis or further program abstraction.

vast

Support interactive generation of passes.

This should generate skeleton taking into account:

- dialect name
- type name
- mnemonic
- type traits/attributes (it might be nifty to provide checkbox list of most common attributes)
- assembly format

Script appends new operation to `Dialect/DialectTypes.td` respectively `Dialect/DialectAttributes.td`  file.

Support interactive generation of types/attributes.

This should generate skeleton taking into account:
- dialect name
- operation name
- optional traits?
  - it might be nifty to provide checkbox list of most common traits/attributes
- arguments
- results
- regions
- whether generate builders
- assembly format?

Script appends new operation to `Dialect/DialectOps.td` file

Support interactive generation of operations.

### To what component is your feature request related to?

Cast

### Feature Request

It would be nice to have:
- `account delete` 

Someone could delete an existing account from the `accounts-file` with such a command. A new file named `delete.rs` should be added to https://github.com/foundry-rs/starknet-foundry/tree/c04585092890f3cd351b36b411a4dae651c35feb/crates/cast/src/starknet_commands/account and included in mod.rs placed there. 

This new command should take additional arguments in the form of flags:
- `--name` - a name of an account to be added (required)
- `--network` - a chain id of the network where account to be added was deployed (optional - if not passed we should require --url or --profile with configured rpc url to be passed to cast)

The command should take all the necassary info and remove the account (with all its data) from the accounts file specified by the user using flag `--accounts-file` passed to cast. An example of a command would be:

```
sncast --accounts-file ~/myfile.json account delete --name mariusz --network alpha-goerli
```


Component: Cast

Blazing fast toolkit for developing Starknet contracts.

starknet-foundry

Add `account delete` command

For any public API method that contains the `blockNumber` parameter (for example, [`debug_getRawBlock`](https://besu.hyperledger.org/public-networks/reference/api#debug_getrawblock)), update the description to specify that it's a "hexadecimal integer." Also, include `finalized` and `safe` as possible values.

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

besu-docs

Update `blockNumber` parameter descriptions

Introduce snapshot verification for Key components of Paprika. Use [Verify](https://github.com/VerifyTests/Verify) with its support for [binary comparison](https://github.com/VerifyTests/Verify/blob/main/docs/binary.md) to make sure that all key components of Paprika v1 are captured and covered. 

- [ ] install `Verify`
- [ ] provide a `v1` directory for snapshots and tests aligned with the current version defined [here](https://github.com/NethermindEth/Paprika/blob/e106d7357a33da12e5f74ee322893a3e0bea2505/src/Paprika/Store/Page.cs#L43)
- [ ] cover:
  - [ ] `NibblePath`, read/write, GetHashCode
  - [ ] `SlottedArray`, at least one case for each key type

An experimental storage for Nethermind, removing the whole Trie abstraction and acting as a Trie and a database at once

Paprika

Verify for key components for Paprika v1

Currently, when running `snforge` end of test summary output includes `passed`, `failed` and `skipped` tests. We should also show how many test have been [filtered out](https://foundry-rs.github.io/starknet-foundry/testing/running-tests.html#filtering-tests) (if running `snforge [TEST_NAME]`).

https://github.com/foundry-rs/starknet-foundry/blob/ceaf6c507d04922aecafe8ac1efb684a029d34ea/crates/forge/src/pretty_printing.rs#L27

One possible implementation of that may be including the number of filtered out tests in `TestsFromFile` struct https://github.com/foundry-rs/starknet-foundry/blob/ceaf6c507d04922aecafe8ac1efb684a029d34ea/crates/forge/src/lib.rs#L69. This number can be easily obtained by comparing the number of tests returned by this function https://github.com/foundry-rs/starknet-foundry/blob/ceaf6c507d04922aecafe8ac1efb684a029d34ea/crates/forge/src/lib.rs#L176 call with the original value.


Component: Forge

feature

Print the number of filtered out tests

Given the popularity of the vm.expect* and vm.assume cheatcodes in foundry, we should also support the following:
1. `vm.expectRevert`
2. `vm.expectEmit`
3. `vm.expectCall`
4. `vm.assume`

The core technical requirement of this issue is to ensure that the functionality of these cheatcodes works _exactly_ as they do in foundry.


help wanted

Parallelized, coverage-guided, mutational Solidity smart contract fuzzing, powered by go-ethereum

medusa

Add vm.expect* and vm.assume cheatcodes

Due to issues with forking and `go install` (https://github.com/golang/go/issues/44840), we need to identify a way to have one-line installation for all major platforms (outside of downloading the binaries directly).

We might have to pivot away from `go install` because there does not seem to be any momentum from the Golang team to loosen the restriction on the `replace` directive. More research into alternate solutions is required.

A decent solution could be to create a toolchain manager, similar to `foundryup`, that will manage installation and upgrades of medusa.

One-line installation for medusa

Currently, the execution traces on failed tests can be quite aggressive for more complex systems where we enter into multiple call frames within a single call. Thus, we should introduce various verbosity levels that can allow the user to choose what they want the log output to look like. 

I propose the following log levels:
1. -v: Test results are shown. No execution traces or console.log events are shown
2. -vv: **Top-level** call frame execution traces as well as console.log events are shown for failing tests
3. -vvv: TBD
4. -vvvv: TBD

Add verbosity levels to logging

User feedback
> the top nav bar doesn't indicate the active tab, and that's confusing

@sweetpea22 maybe you can suggest something?

Priority: 🟠 P1

Type: 🫶 Enhancement

Good first issue

Use a Multisig to do anything, on Polkadot

Multix

TypeScript

Add indication of the current selected menu in nav bar

This is good for debugging. Add unit tests when appropriate.

gfi easy

chiquito

Debug and/or Display traits for common items such as TraceWitness and Assignment

Redesign the style of the error message popups generated by the plugin.

medium

icebox

A plugin that brings Starknet to Remix! 🐺 ⭐

starknet-remix-plugin

Improve error pop-ups

Improve the styling and reorder (make more concise) the "Transactions" section of the UI.

Improve Transaction UI section

Currently the "Interact" section is quite pleasant and usable. We want the "Deploy" section to maintain the same standard. This includes:
- styling
- preserving control state (to survive "rollup/rolldown")

Improve deploy interface 


### Description

Currently, the extension is using an outdated `Menu` component, which needs to be replaced with the new `Popover` component.

This is a massive undertaking by itself and creating a single PR would be too large. Smaller PRs can be submitted against this issue to ensure easier review and gradual improvements.

### Technical Details

- Replace instances of `Menu` component (`ui/components/ui/menu/menu.js`) with `Popover` component (`ui/components/component-library/popover/popover.tsx`)
- Component APIs are slightly different so ensure all props have been migrated appropriately

### Acceptance Criteria

- Instances of `Menu` component are completely replaced with the new `Popover` component
- The component APIs are updated to reflect the changes in the new `Menu`` component and there is no functional changes or visual regression
- Each Pull Request (PR) should include **no more than 3 files**
- The code changes should pass Jest tests, linting, and Storybook without any errors.
- The PR must include before and after screenshots of the UI to ensure there are no visual regressions.

If the acceptance criteria is not met, PRs may be closed.

### Difficulty: Intermediate

Good first issue for: External contributors who are familiar with running the extension locally, have knowledge of React, component props, Jest tests, linting, and Storybook, and want to contribute to improving the cohesiveness of UI in the extension


team-design-system

:globe_with_meridians: :electric_plug: The MetaMask browser extension enables browsing Ethereum blockchain enabled websites

metamask-extension

JavaScript

Replace deprecated Menu component with Popover from the component-library

### Description

Currently, the extension is using outdated mixins `@include H1` - `@include H9`. This CSS should be removed and the JSX associated with these styles replaced with the `Text` component. This will reduce the amount of CSS in the extension and improve the cohesiveness of the UI.

This is a massive undertaking by itself and creating a single PR would be too large. Smaller PRs can be submitted against this issue to ensure easier review and gradual improvements.

### Technical Details

- Remove instances of the deprecated mixins from the CSS and replace the JSX element with `Text` component (`ui/components/component-library/text/text.tsx`) or [appropriate component from the component-library](https://metamask.github.io/metamask-storybook/?path=/docs/components-componentlibrary-introduction--docs).
- There will also be CSS that can be removed in favor of the style utility props that are available on the `Text` component. For example, `display: flex` can be replaced with `display={Display.Flex}` prop on the `Text` component. [Check out all the available style utility props in the Text docs in storybook](https://metamask.github.io/metamask-storybook/?path=/docs/components-componentlibrary-text--docs).
- The `Text` component has a `variant` prop that can be used to set the font size and weight. Use the `TextVariant` enum (`ui/helpers/constants/design-system.ts`) to set the appropriate variant.
- There are 9 deprecated mixins that need to be replaced. The following is a mapping of the mixin to the component that should be used to replace it:

`@include H1` => `<Text variant={TextVariant.displayMd}>`
`@include H2` => `<Text variant={TextVariant.displayMd}>`
`@include H3` => `<Text variant={TextVariant.headingLg}>`
`@include H4` => `<Text variant={TextVariant.headingMd}>`
`@include H5` => `<Text variant={TextVariant.bodyMd}>`
`@include H6` => `<Text variant={TextVariant.bodyMd}>`
`@include H7` => `<Text variant={TextVariant.bodySm}>`
`@include H8` => `<Text variant={TextVariant.bodyXs}>`
`@include H9` => `<Text variant={TextVariant.bodyXs}>`

### Acceptance Criteria

- Instances of deprecated mixins `@include H1` - `@include H9` are completely replaced with the `Text` component or appropriate component from the component-library
- Each Pull Request (PR) should include **no more than 3 files**
- The code changes should pass Jest tests, e2e tests, linting, and Storybook without any errors.
- The PR must include before and after screenshots of the UI to ensure there are no visual regressions.

If the acceptance criteria is not met, PRs may be closed.

### Difficulty: Intermediate

Good first issue for: External contributors who are familiar with running the extension locally, have knowledge of React, component props, Jest tests, linting, and Storybook, and want to contribute to improving the cohesiveness of UI in the extension


Replace deprecated mixins `@include H1` - `@include H9` in SCSS with Text component



![Image](https://github.com/privacy-scaling-explorations/bandada/assets/67167307/847fbf54-4688-4cb4-b285-2354cb440b0d)



A system for managing privacy-preserving groups.

bandada

Warn users if a new group has the exact same name

https://discord.com/channels/943612659163602974/1139581328908628078/1141520705658290277

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity