Some tips on contribution

Feel free to make pull requests, however kindly crosscheck in order reduce the number of duplicates that may creep up.

Please use the following format: [Title][link-can be amazon or goodreads]-Author

Watch out for whitespaces!!

Feel free to add more categories as well.

I'm open to further suggestions on how to improve this.

Thanks.

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

• Demonstrating empathy and kindness toward other people

• Being respectful of differing opinions, viewpoints, and experiences

• Giving and gracefully accepting constructive feedback

• Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

• Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

• The use of sexualized language or imagery, and sexual attention or advances of any kind

• Trolling, insulting or derogatory comments, and personal or political attacks

• Public or private harassment

• Publishing others' private information, such as a physical or email address, without their explicit permission

• Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at this address. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

What is a node in blockchain?

A node is essentially a program running on a single computer that allows you to connect with the rest of the blockchain network. It connects with other nodes to send information back and forth, checks that transactions sent between people are valid, and stores important information about the state of the blockchain.

In particular, one of the peculiarities of a blockchain network is that the network is essentially composed of only nodes: that is, the physical hardware running a blockchain such as Ethereum or Bitcoin is just the collection of all the nodes around the world being run by individual people. There's no master server or single source of truth - that's why it's decentralized!

There's typically two main categories of nodes - light nodes and full nodes. Light nodes sync just the block headers and request from full nodes for many queries, while full nodes keep the entire state of a blockchain - every transaction that's ever been created. Most queries work with light nodes, but full nodes are the backbone of the blockchain - they’re necessary to serve most information.

• References:

  • https://www.web3.university/article/what-is-a-node-provider

Community name that is currently listed:

Describe the issue: Is there an invite link that is invalid, or notable channels need to be updated?

Expected: What do you want to replace the community with regarding the aforementioned issue?

Additional context:

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

• Using welcoming and inclusive language

• Being respectful of differing viewpoints and experiences

• Gracefully accepting constructive criticism

• Focusing on what is best for the community

• Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

• The use of sexualized language or imagery and unwelcome sexual attention or advances

• Trolling, insulting/derogatory comments, and personal or political attacks

• Public or private harassment

• Publishing others' private information, such as a physical or electronic address, without explicit permission

• Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [INSERT EMAIL ADDRESS]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Attribution

Introduction and Basics

• Decentralized web - https://blockchainhub.net/web3-decentralized-web/

• https://diode.io/blockchain/Best-Resources-to-Learn-Web3-Blockchain-Decentralized-PKI-and-Ethereum-19262/

• https://web3.career/learn-web3

• https://www.useweb3.xyz/

• https://dev.to/cooper_kunz/educational-resources-for-web-3-0-1jmo

• https://github.com/DavidJohnstonCEO/DecentralizedApplications

• https://www.freecodecamp.org/news/breaking-into-ethereum-crypto-web3-as-a-developer/amp/

• https://moralis.io/the-ultimate-guide-to-web3-what-is-web3/

• https://blog.oliverjumpertz.dev/your-roadmap-to-becoming-a-web-30-developer

• https://ethereum.org/fr/developers/tutorials/set-up-web3js-to-use-ethereum-in-javascript/

• https://vitto.cc/web3-and-solidity-smart-contracts-development-roadmap/

• https://dev.to/pascavld/how-to-get-your-first-job-as-a-developer-web3-2021-developer-roadmap-and-more-4hn1

• https://medium.com/theweb3stack/how-to-get-into-crypto-a-roadmap-for-a-web3-developer-4a5806f61869

• https://gitcoin.co/grants/3150/defi-developer-roadmap

• https://blog.idrisolubisi.com/web-3-a-developer-roadmap-and-resources-to-get-started

• https://rattibha.com/thread/1439980837899055108?lang=en

• https://betterprogramming.pub/transform-into-a-web3-crypto-nft-and-blockchain-development-expert-5-resources-8fdd11037eb8

• https://townhall.hashnode.com/best-web3-resources

• https://dev.to/olanetsoft/web-30-a-developer-roadmap-guide-and-resources-to-get-started-45oa

Blockchain

• How does Ethereum work, anyway? — how it functions at a technical level, without complex math https://medium.com/@preethikasireddy/how-does-ethereum-work-anyway-22d1df506369

• The Ethereum Yellow Paper https://ethereum.github.io/yellowpaper/paper.pdf

• The idea of smart contracts http://www.fon.hum.uva.nl/rob/Courses/InformationInSpeech/CDROM/Literature/LOTwinterschool2006/szabo.best.vwh.net/idea.html

• Making Sense of “Cryptoeconomics” https://medium.com/l4-media/making-sense-of-cryptoeconomics-5edea77e4e8d

• https://dev.to/abdulmaajid/top-programming-languages-to-create-smart-contracts-3n3f

• https://ethereum.org/en/developers/docs/smart-contracts/languages/

• https://moralis.io/best-languages-for-blockchain-development-full-tutorial/

• https://blog.logrocket.com/ethereum-blockchain-development-using-web3-js/

• https://diode.io/blockchain/Best-Resources-to-Learn-Web3-Blockchain-Decentralized-PKI-and-Ethereum-19262/

• https://github.com/Xel/Blockchain-stuff

Some cool web3 Github Repo

Info and Documentation

• https://github.com/JoinColony/awesome-web3

• https://github.com/Web3-Melbourne/learning-resources

• https://github.com/jsjoeio/web3-cheatsheet

• https://ethereumjs.github.io/

• https://github.com/miguelmota/ethereum-development-with-go-book

• https://github.com/ethereumbook/ethereumbook

Libraries, Projects, and tools

• https://github.com/ChainSafe/web3.js

• https://github.com/dappuniversity/web3_examples

• https://github.com/NoahZinsmeister/web3-react

• https://github.com/gochain/web3

• https://github.com/0xProject/tools

• https://github.com/web3rb/your-first-web3-dapp

• https://geth.ethereum.org/docs/dapp/native

• https://github.com/ConsenSys/ethereum-developer-tools-list

• https://github.com/ethereum/remix-ide

Solidity

• https://github.com/willitscale/learning-solidity

• https://github.com/smartcontractkit/full-blockchain-solidity-course-py

• https://github.com/paulrberg/solidity-template

• https://github.com/bkrem/awesome-solidity

• https://github.com/bancorprotocol/contracts-solidity

• https://github.com/OpenZeppelin/openzeppelin-contracts

• https://medium.com/coinmonks/solidity-tutorial/home

• https://medium.com/coinmonks/learn-all-about-solidity-ethereum-45d709c4de77

• https://medium.com/coinmonks/how-to-learn-solidity-in-30-days-78b02e503d23

• https://medium.com/coinmonks/learn-solidity-01-writing-your-first-smart-contract-528cad29ba99

• https://medium.com/coinmonks/learn-all-about-solidity-ethereum-45d709c4de77

• https://101blockchains.com/solidity-tutorial/

Rust

• https://github.com/OpenZeppelin/ethernaut

• https://learn.figment.io/tutorials/write-and-deploy-a-smart-contract-on-near

• http://troubles.md/why-write-smart-contracts-in-rust/

• https://github.com/Concordium/concordium-rust-smart-contracts

• https://medium.com/hackernoon/rust-smart-contracts-demos-challenges-28fc0a48ddd6

• https://github.com/perlin-network/smart-contract-rs

• https://paritytech.github.io/ink-docs/why-rust-for-smart-contracts/

Decentralized DNS and Networks

• Handshake, ENS and Decentralized Naming Services Explained (2018) https://hackernoon.com/handshake-ens-and-decentralized-naming-services-explained-2e69a1ca1313

• Why DNS-on-Blockchain is the next step after DNS-over-HTTPS — our take on the issue: https://diode.io/distributed-infrastructure/Why-DNS-on-Blockchain-is-the-next-step-after-DNS-over-HTTPS-19231/

• IPFS — introducing a peer-to-peer distributed file system https://ipfs.io/ipfs/QmR7GSQM93Cx5eAg6a6yRzNde1FQv7uL6X1o4k7zrJa3LX/ipfs.draft3.pdf

• Swarm: https://github.com/ethersphere/swarm

• State-of-the-art of decentralized web https://hackernoon.com/a-state-of-the-art-of-decentralized-web-part-2-ea630917332a

• https://towardsdatascience.com/decentralizing-your-website-f5bca765f9ed

• https://decrypt.co/resources/how-to-use-ipfs-the-backbone-of-web3

• https://docs.ipfs.io/

• https://medium.com/pinata/web3-data-portability-through-ipfs-saved-hicetnunc-724e3df2948d

• https://bitsofco.de/setting-up-a-decentralised-website/

Smart Contracts:

• https://github.com/blockstack/docs

• https://github.com/smartcontractkit

• https://github.com/ConsenSys/smart-contract-best-practices

• https://github.com/TokenMarketNet/smart-contracts

• https://github.com/ethereum/remix

• https://github.com/trufflesuite/truffle

White Papers:

• https://github.com/xasos/awesome-decentralized-papers

• https://github.com/DavidJohnstonCEO/DecentralizedApplications

• https://github.com/OffcierCia/DeFi-Developer-Road-Map

• https://a16z.com/wp-content/uploads/2021/10/How-to-Win-the-Future-1.pdf

• https://chain.link/whitepaper

• https://github.com/the-dao/whitepaper

• https://whitepaperdatabase.com/category/whitepapers/

DAOs

• https://ethereum.org/en/dao/

• https://academy.binance.com/en/articles/decentralized-autonomous-organizations-daos-explained

• https://consensys.net/blog/blockchain-explained/what-is-a-dao-and-how-do-they-work/

• https://github.com/the-dao/whitepaper

• https://www.singularitydao.ai/file/2021/04/Platform-Whitepaper-3.pdf

Some Cool Projects:

• https://github.com/HelloZeroNet/ZeroNet

• https://github.com/mehrdadrad/radvpn

• https://betterprogramming.pub/blockchain-introduction-using-real-world-dapp-react-solidity-web3-js-546471419955

• https://medium.com/ethereum-developers/the-ultimate-end-to-end-tutorial-to-create-and-deploy-a-fully-descentralized-dapp-in-ethereum-18f0cf6d7e0e

• https://www.moesif.com/blog/blockchain/ethereum/Tutorial-for-building-Ethereum-Dapp-with-Integrated-Error-Monitoring/

• https://github.com/erowell/web3-learn

• https://medium.com/scrappy-squirrels/tutorial-building-a-web3-frontend-with-react-e0a87ea3bad

• https://medium.com/coinmonks/web3-react-connect-users-to-metamask-or-any-wallet-from-your-frontend-241fd538ed39

• https://medium.com/@web3rb/your-first-web3-dapp-react-app-reading-real-ethereum-blockchain-database-6c7af06e85ea

• https://medium.com/@stevelukis/integrating-react-website-to-ethereum-network-with-web3-js-case-study-nft-minting-website-ae94c4107adc

• https://github.com/stevelukis/cafe-nft

• https://www.dappuniversity.com/articles/ethereum-dapp-react-tutorial

• https://dev.to/steadylearner/how-to-make-a-fullstack-dapp-with-react-hardhat-and-ether-js-with-examples-4fi2

• https://blog.infura.io/dapp-frontend-network/

• https://opentaps.org/2021/02/22/tutorial-building-an-ethereum-dapp-using-react-js-web3modal-ethers-hardhat/

• https://maksimivanov.com/posts/ethereum-react-dapp-tutorial/

• https://medium.com/@karin.chechik/create-a-blockchain-app-on-ethereum-dapp-with-react-and-solidity-a8f8c77b09a8

• https://blog.logrocket.com/using-drizzle-react-write-dapp-frontends/

• https://learn.figment.io/tutorials/build-a-social-media-dapp-and-deploy-it-on-polygon

• https://blog.hkwtf.com/ethereum-dapp-tutorial-from-smart-contract-to-frontend-react-development-c0dd31337f1e

Tutorials

• How to create a Smart Contract to mint an NFT : https://dev.to/emanuelferreira/how-to-create-a-smart-contract-to-mint-a-nft-2bbn

• How to create a motherf*cking NFT using Solidity : https://dev.to/abdulrauf11/how-to-create-a-motherfcking-nft-using-solidity-5b5d

• HOW TO WRITE & DEPLOY AN NFT (PART 1/3 OF NFT TUTORIAL SERIES) : https://medium.com/coinmonks/guide-to-creating-your-own-nft-with-javascript-solidity-part-1-of-3-7909b80fae94

Contribution Guidelines

By participating in this project you agree to follow the contributor code of conduct. From here on, the word server and community will be used interchangeably and will mean the same thing.

• Add Community

• Format WebP

• Issues

• Review Policy

Add Community

To include a community to the list, fork this project and add your server under a section or subsection, or you can include a new section if need be, then create a pull request. Make sure your proposal meets these requirements below, if you've Python installed you can take advantage of this script.

✅ Each community follows this template

<img align="left" height="94px" width="94px" alt="Server Icon" src="<static url of the image>"/>

[__Community Name__](url of invite link) [<img height="16px" width="16px" alt="Official Badge" src="images/badges/official.webp">](badges.md#official-identification-badge) [<img height="16px" width="16px" alt="Reddit Badge" src="images/badges/reddit.webp">](badges.md#reddit-badge) [<img height="16px" width="16px" alt="Homepage URL" src="images/badges/homepage.webp">](url of server homepage) [<img height="16px" width="16px" alt="Git Repository" src="images/badges/git.webp">](url of server git repository) \
Notable Channels: `#most-important-channel-1`, `#most-important-channel-2`, `#most-important-channel-3`, `#most-important-channel-4`, `#most-important-channel-5`, `#least-important-channel` \
Language: English, Deutsch, 日本語

✅ Community icon is optimized with WebP, with 75% lossy quality, and at least 128x128 pixel in resolution with moderate PPI

✅ Community name does not contain any emoji (discouraged)

✅ Invite link is permanent, generated from Discord platform itself, or URL whose domain is owned by you that eventually with or without captcha verification redirects to Discord invite page. No third-party URL domain allowed that isn't owned by your community, this includes link shorteners.

• Allowed: https://discord.com/invite/123abc by community A

• Allowed: https://b-community.com/discord-invite by community B when B owns b-community.com domain

• Not Allowed: https://discord-links.com/community-c-invite by community C when C doesn't own discord-links.com domain

✅ Badges are properly placed and aligned

• If you're unsure about whether a badge applies to your community, leave it excluded. After PR submission, a reviewer will let you know about missing badges, or ask the reviewer.

✅ Notable Channels contain the most important and active channels, no off-topic or informational channels, and does not necessarily take up too much space.

• #announcements, #rules, #roles, etc., are informational channels and common across all communities, therefore they shouldn't be included.

• #general, #chat, #tech-talk, etc., casual conversation channels can be included if they aren't meant for off-topic discussions.

• Support channels: #help, #support, #beginners, etc., should be included. If there are multiple support channels with character suffix/prefix, e.g.: #help-1, #help-2, #help-3 -- instead of including them all, just enter #help. But if the suffixes present clear distinction between their topics, i.e., #help-software, #help-hardware -- software and hardware represent two different topics, then both of them can be included.

• Channels that have barely any activity shouldn't be included, even if they're on-topic. E.g., if #help-software has regular activity, but #help-hardware has little to no activity, then only #help-software should be included.

• Off-topic channels: #off-topic, #water-cooler, #random, #memes, etc., shouldn't be included.

• Moderation channels, bot channels, feedback channels shouldn't be included.

• Events or events discussion channels can be included.

✅ Language only contains spoken written languages that the community has active channels for

• English: If only English language is encouraged

• English, Deutsch, español: If there are active channels for all three languages

• Deutsch: If only German language is encouraged

• Don't include languages that has little to no conversation activity in any channel

✅ Moderation team is regularly active

✅ Community is active on a daily or semiweekly basis

✅ All public channels follow Discord community guidelines and ToS

Format WebP

Awesome Discord Communities list hosts the server icon images in its own repository. This allows reduced time to cache and faster rendition by the browser. Discord hosts the icon files as png which can take quite a lot of space and make the README page a lot heavier. Thus, webp was adopted. You can convert your png/jpg icon in the any of the following ways:

Easy WebP Conversion: Drop or paste your png/jpg icon on Sqoosh. Squoosh is open-source and does image compression on the client-side. Once loaded, by default, the original image preview is on the left side of the draggable vertical bar, and the compressed image preview is on the right. From the right 'Compress' sidebar select 'WebP', and drag the 'Quality' slider to 75. You can now download the image.

CLI WebP Conversion: If you prefer command line WebP conversion, you can use native cwebp by Google. It does require installing the library to your system. Use -q option with value 75.

Issues

If you've found an issue with an existing server or have a suggestion to make to improve this list, feel free to file an issue here.

Review Policy

Review policy is meant for reviewers, not necessarily for contributors. There is no real metric provided by Discord that can be used by anyone to evaluate a server. However, a maintainer will manually review the community for a period of time (1-4 days) before it can be accepted.

As an initial requirement, only technical or technology-related communities are considered. A community that is meant for people to hang out with no real active support channel will not be considered as technical. There are certain categories a technical community can be attributed to. Generic, Niche, and Project. There are a few distinct requirements for each of them.

Generic servers try to address multiple-technical-domains-in-one instead of a single specific domain, i.e., a server that offers support for all programming languages vs. a server that offers Java only. These communities are most likely to attract a lot of people in a short period, and more likely to be short-lived as it gets more and more difficult to maintain over time. For this reason, a stricter requirement, a generic server needs to be at least a year old with active moderation and messaging activity on a daily basis (excluding the off-topic channels). This specific precondition affects generic servers only.

Niche servers are the opposite of Generics, they're geared toward a smaller domain. The required minimum age is six months. Communities related to cryptocurrencies are often prone to the risk of getting hacked, for this reason, for now, only open-source owned official cryptocurrency servers will be allowed.

Project servers are part of associated communities of open-source projects or content creators (e.g., Twitch streamers, YouTube creators). Since the activity and growth of the server depend on the creators' contents, they can be accepted as soon as there is daily or semiweekly activity. If you maintain an open-source project you might also be interested in Discord's own open-source recognition.

Attribution

Icon mockup is made by Darius Dan.

Frequently Asked Questions

Answers to a few common questions that may come to your mind while exploring this awesome list:

What is Discord.com exactly?

From :

Discord is a proprietary freeware VoIP application and digital distribution platform designed for creating communities ranging from gamers to education and businesses. Discord specializes in text, image, video and audio communication between users in a chat channel. Discord runs on Windows, macOS, Android, iOS, Linux, and in web browsers. As of 21 July 2019, there are over 250 million users of the software.

Or as I once heard from a critique:

Discord is just IRC with extra features.

A server in Discord mainly refers to the community itself.

What about Discord's poor privacy policy?

How to stay safe in Discord?

How is this list any different from Discord listing sites?

Are you or is this project affiliated?

Neither I nor any part of this project is affiliated with Discord in any way.

Why does this list not follow conventional Awesome list framework?

How to contribute?

How to report any issue with the Awesome list?

How to properly attribute to compliment the license (CC BY 4.0)?

Servers are assigned one or more badges that they conform to. Some badges may redirect to external links that the servers own and generally refer to, e.g., a homepage or official repository. A badge doesn't necessarily mean that the server is better than the others; it is to represent a server's validity, activity, and wiki. Badges selected for a server doesn't relate to .

Official Identification Badge

The server is owned or moderated by an established and registered organization, a company, project members with sufficient headcount. The points to its identity.

Reddit Badge

The server is owned and moderated by moderators of a preexisting forum, though not all subreddit moderators may be involved. The server is officially recognized as an associate community by the subreddit.

Home Badge

Official website of the server, it's a clickable badge. The webpage may contain helpful information about the server, knowledgebase, donation information, social media links, et cetera.

Git Badge

The server has an open git repository, may contain useful resources, Discord bot source code, and other developments. This clickable badge redirects to the hosted repository e.g., GitHub, Gitlab.

Tags

Some servers contain these tags. Tags are nothing but a reference to something generic to save content space.

so much more

A community with a wide range of topics, each of them is equally productive in activities. It has so many active channels that it's impossible to squeeze in all of them in Notable channels.

Awesome Ethereum & Dapps Resources

About Ethereum

Market Information

Videos

Tools

Developer Tools

Where do I start?

Blogs & Article threads

Books

DAPPS

Related Resources

Awesome Solidity

A curated list of awesome resources, libraries, tools and more.

Please check the for information on formatting and writing pull requests.

Contents

Resources

Official

Tutorials

Articles

Security

Audits

Examples

Educational

Deployed on Ethereum Mainnet

Templates

Books

Practice

Jobs

Libraries

Tools

General

Utility

Audit

DevOps

Languages

JavaScript

TypeScript

Rust

OCaml

Editor Plugins

Atom

Eclipse

Emacs

IntelliJ

Sublime

Vim

Visual Studio Code

License

[Please describe your pull request here]

Checklist

• The URL is not already present in the list (check with CTRL/CMD+F in the raw markdown file).

• Each description starts with an uppercase character and ends with a period. Example: solc-js - JavaScript bindings for the compiler.

• Drop all A / An prefixes at the start of the description.

• Avoid using the word Solidity in the description.

[Please describe your pull request here]

Checklist

• The URL is not already present in the list (check with CTRL/CMD+F in the raw markdown file).

• Each description starts with an uppercase character and ends with a period. Example: solc-js - JavaScript bindings for the compiler.

• Drop all A / An prefixes at the start of the description.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Thanks for Looking to contribute to this repo. We are happy to see your interest for crafting a great Pull Request for this project.

Guidelines

• Continue to follow the alphabetical ordering that is in place per section.

• Add one link per Pull Request.

• Make sure the PR title is in the format of Add repository-name for e.g.: Add awesome-python

• Use a short descriptive commit message. for e.g.: ❌Update README.md ✔Add Git to the CheatSheets

• Search previous Pull Requests or Issues before making a new one, as yours may be a duplicate.

• Don't mention "Awesome" in the repository name while adding a link in the README, if you are adding an awesome repository . for e.g.: ❌Awesome-Python ✔Python

Pull Request Pro Tips

• Fork the repository and clone it locally.

• Contribute in the style of the project as outlined above. This makes it easier to understand and maintain in the future.

• Please make sure you squash all commits into a single commit before opening a pull request. If your pull request requires changes upon review, please be sure to squash all additional commits as well.

Thanks you so much for reading the contributing guide. Looking forward to review a great PR from you.

Please ensure your pull request adheres to the following guidelines:

• Search previous suggestions before making a new one, as yours may be a duplicate.

• Make sure your contribution is useful before submitting.

• Make an individual pull request for each suggestion.

• Use the following format: [name](link) - Description.

• Additions should be added in alphabetical order of the relevant category.

• New categories, or improvements to the existing categorization are welcome.

• Keep descriptions short and simple, but descriptive.

• Start the description with a capital and end with a full stop/period.

• Check your spelling and grammar.

• Make sure your text editor is set to remove trailing whitespace.

• The pull request should have a useful title and include a link to the package and why it should be included.

Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub.

A curated list of awesome Web3 resources, libraries, tools and more.

Please check the contribution guidelines for information on formatting and writing pull requests.

• Awesome Web3

  • Awesome List

  • Reference

  • Software Development

    • Sample Code

    • Development Environment

    • Protocol

    • JavaScript

    • Solidity

    • Go

    • C/C++

    • Rust

    • Shell

    • Python

    • VMs

    • Boilerplate

    • Testing

    • Code Quality

  • Open Source Project

  • Tutorial

  • YouTube Channel

  • Book

  • Podcast

  • Newsletter

  • Platform as a Service

  • Other

  • Contribute

Awesome List

• Solidity - Curated list of awesome Solidity resources, libraries, tools and more.

• Ethereum - Awesome Ethereum & Dapps Resources.

Reference

• BIPs - Bitcoin Improvement Proposals.

• EIPs - Ethereum Improvement Proposals.

• Ethereum Yellow Paper - Formal definition of the Ethereum protocol.

• EVM Illustrated - Illustrated explanation of how EVM works under the hood.

• EVM Opcodes - Low level reference for the EVM and a Solidity decompiler which turns bytecode into more readable Solidity-like code.

• evm.codes - An interactive reference to Ethereum Virtual Machine Opcodes (source code).

• Solidity - Solidity is an object-oriented, high-level language for implementing smart contracts.

Software Development

Sample Code

• Solidity by Example - Basic examples on Solidity.

Development Environment

• Brownie - Python-based development and testing framework for smart contracts targeting the Ethereum Virtual Machine.

• Ethereum Code Viewer - View source of deployed Ethereum smart contracts in VS Code.

• EthFiddle - Web-based IDE that lets you write, compile, and debug your smart contract.

• Hardhat - Development environment to compile, deploy, test, and debug your Ethereum software.

• Remix - Online IDE for Solidity development.

Protocol

• WalletConnect - Open protocol connecting wallets to Dapps.

• WalletLink - Open protocol that lets users connect their mobile wallets to your DApp.

• IPFS - Distributed system for storing and accessing files, websites, applications, and data.

JavaScript

• avalanchejs - JavaScript Library for interfacing with the Avalanche Platform.

• Avalanche Wallet SDK - Typescript library to create and manage wallets on the Avalanche network.

• BitcoinJS - Bitcoin library for node.js and browsers.

• dapparatus - Reusable dApp components in React.

• ethers.js - Complete Ethereum wallet implementation and utilities in JavaScript (and TypeScript).

• ipfs-mini - Super tiny module for querying an IPFS node, that works in the browser and in Node.

• js-ipfs - IPFS implementation in JavaScript.

• Truffle - Development environment, testing framework and asset pipeline for Ethereum.

• wagmi - React hooks library for Ethereum.

• web3.js - Ethereum JavaScript API which connects to the Generic JSON-RPC spec.

• web3-react - Simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps.

Solidity

• Date and Time tools - Contract which implements utilities for working with datetime values in ethereum.

• OpenZeppelin - The standard for secure blockchain applications.

Go

• avalanchego - Go implementation of an Avalanche node.

• avalanche-network-runner - Tool to run and interact with an Avalanche network locally.

• ava-sim - Helper tool to spin up a local instance of an Avalanche network to interact with the standard APIs or to test a custom VM.

• ethereum-hdwallet - Ethereum HD Wallet derivations from seed which implements the go-ethereum's accounts.Wallet interface.

• coreth - Code and wrapper to extract Ethereum blockchain functionalities without network/consensus, for building custom blockchain services.

• geth - Official Go implementation of the Ethereum protocol.

• subnet-cli - CLI tool to manage Avalanche Subnets.

C/C++

• Trust Wallet Core - Cross-platform, mobile-focused library implementing low-level cryptographic wallet functionality for a high number of blockchains.

Rust

• OpenEthereum - The fast, light, and robust client for the Ethereum mainnet.

Shell

• avash - Avalanche shell client provides temporary stateful shell execution environment used to deploy networks locally, manage their processes, and run network tests.

Python

• py-evm - Ethereum protocol implementation in Python.

• Vyper - Contract-oriented, pythonic programming language that targets EVM.

VMs

• evmone - C++ implementation of the Ethereum Virtual Machine (EVM), faster.

• SpacesVM - SpacesVM enables authenticated, hierarchical storage of arbitrary keys/values using any EIP-712 compatible wallet.

Boilerplate

• scaffold-eth - Ethereum dev stack focused on fast product iterations.

• create-eth-app - Create Ethereum-powered apps with one command, similar to create-react-app.

• next-web3-boilerplate - Boilerplate in TypeScript using Next.js, NextAuth.js, siwe, Web3modal, useDapp, next-i18next, reactMUI.

Testing

• mock-contract - Simple Solidity contract to mock dependent contracts in truffle tests.

• openzeppelin-test-helpers - Assertion library for Ethereum smart contract testing that you can use with hardhat.

• solidity-coverage - Code coverage for Solidity smart-contracts.

• Waffle - Library for writing and testing smart contracts.

Code Quality

• Slither - Solidity static analysis framework, a suite of vulnerability detectors, prints visual information about contract details etc.

• solhint - Solidity linter providing Security and Style Guide validations.

Open Source Project

• Blockscout - Blockchain explorer for Ethereum based network and a tool for inspecting and analyzing EVM based blockchains.

• MetaMask - Browser extension of MetaMask crypto wallet.

• Rabby - Browser extension crypto wallet for the DeFi ecosystem that works multi-chain.

• Rainbow - Open source Ethereum wallet.

• Remix - Browser-based compiler and IDE that enables users to build Ethereum contracts with Solidity language and to debug transactions.

• UniSwap - Decentralized trading protocol on Ethereum.

Tutorial

• useWeb3 - Learning platform for developers to explore and learn about Web3.

• CryptoZombies - Interactive school that teaches you all things technical about blockchains.

• Figment Learn - Tutorials for various use cases and networks, Avalanche, Solana, Polygon and more.

• Buildspace - Cohort based web3 development courses, learn by building projects.

• The complete guide to full stack Solana development with React, Anchor, Rust, and Phantom. - link

• The complete guide to full stack Ethereum development. - link

• Building a full stack NFT marketplace on Ethereum with Polygon. - link

• Uploading files to IPFS from a web application. - link

• Create your own NFT collection on Ethereum with Solidity. - link

• Intro to dApp's: Create your dApp backend with Solidity. - link

• Intro to dApp's: Create your dApp frontend with React. - link

• What is a crypto wallet & how does it work? - link

• Create your cryptocurrency token. - link

• Solidity and Truffle CI setup. - link

• How to use Slither to find smart contract bugs. - link

• How to mock Solidity smart contracts for testing. - link

• Building EVM from scratch. - link source code

YouTube Channel

• Chainlink - Videos about blockchain basics, oracles, Free Code Camp and more.

• EatTheBlocks - Numerous hands-on development tutorial videos on blockchain Solidity smart contracts.

• Nader Dabit - Tutorials and live coding on dApps, NFTs, DeFi and more.

• Patrick Collins - Smart contract development with Solidity.

Book

• Ethereum development with Go

• Mastering Ethereum

Podcast

• Into the Ether

• Mapping Out Eth 2.0 - Development of Ethereum 2.0.

• BAT Community - BAT, Brave and tech underneath.

Newsletter

• Week in Web3

• EthHub Weekly

Platform as a Service

• Alchemy

• Infura

• Moralis

• QuickNode

• Thirdweb

• Meson Network

Other

• Chainlist - List of EVM networks, Chain IDs and Network IDs.

Contribute

Contributions are welcomed! Please read the contribution guidelines first.

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

• Demonstrating empathy and kindness toward other people

• Being respectful of differing opinions, viewpoints, and experiences

• Giving and gracefully accepting constructive feedback

• Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

• Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

• The use of sexualized language or imagery, and sexual attention or advances of any kind

• Trolling, insulting or derogatory comments, and personal or political attacks

• Public or private harassment

• Publishing others' private information, such as a physical or email address, without their explicit permission

• Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at me@ahmetaygun.net. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version v2.1.

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

• Demonstrating empathy and kindness toward other people

• Being respectful of differing opinions, viewpoints, and experiences

• Giving and gracefully accepting constructive feedback

• Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

• Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

• The use of sexualized language or imagery, and sexual attention or advances of any kind

• Trolling, insulting or derogatory comments, and personal or political attacks

• Public or private harassment

• Publishing others' private information, such as a physical or email address, without their explicit permission

• Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at freeweb3daohq@gmail.com. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

The Web3 Together community is a friendly, encouraging place for anyone aspiring to become a hireable web developer.

This policy was adopted from the . This is a "living" 🌱 document, and subject to refinement and expansion in the future.

The simple version:

• be nice

• be honest

• be supportive

The details:

The Web3 Together community should be a safe place for everybody regardless of

• gender, gender identity or gender expression

• sexual orientation

• disability

• physical appearance

• race

• age

• religion

• anything else you can think of

As someone who is part of this community, you agree that:

• We are collectively and individually committed to safety and inclusivity

• We have zero tolerance for abuse, harassment, or discrimination

• We respect people’s boundaries and identities

If you are addressed for saying something that is found to be offensive, we ask you to:

• Listen without interruption to what the person is saying

• Do not attempt to disqualify what they have to say

• Ask for tips / help with avoiding making the offence in the future

⚠️ Failing to follow the community guidelines as described in this document carries consequences. For minor infractions, you may be banned from the Web3 Together Discussion for 24 hours and issued a final warning. Upon repeat offences, or if the community believes you are not acting in good faith, you may be banned permanently.

Francesco: http://francescociulla.com

BitCoin Whitepaper: https://bitcoin.org/bitcoin.pdf

Ethereum Whitepaper: https://ethereum.org/en/whitepaper/

Smart Contract: https://en.wikipedia.org/wiki/Smart_contract

Blockchain oracles: https://chain.link/

Etherscan.io: https://etherscan.io/

Metamask: https://metamask.io/

Rinkeby Faucet: https://rinkebyfaucet.com/

Blockchain Demo:

• Hash: https://andersbrownworth.com/blockchain/hash

• Block: https://andersbrownworth.com/blockchain/block

• Blockchain: https://andersbrownworth.com/blockchain/blockchain

• Distributed Blockchain: https://andersbrownworth.com/blockchain/distributed

• Tokens: https://andersbrownworth.com/blockchain/tokens

• Public/Private Keys: https://andersbrownworth.com/blockchain/public-private-keys/

Eth Converter: https://eth-converter.com/

Remix IDE: https://remix.ethereum.org/

Solidity Docs: https://docs.soliditylang.org/

🎉 First of all, thanks for taking the time to contribute! 🎉

🤔 How can I contribute?

🛠 Suggesting Enhancements

This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion 📝 and find related suggestions. 🔎

Since GitHub Issue forms we only suggest you to include most information possible.

You can see issues to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.

Note: If you find a Closed issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.

🟩 Your First Code Contribution

Unsure where to begin contributing to this project? You can start by looking through these beginner-friendly issues:

• - issues that require less work.

• - issues that are a bit more involved.

📣 Pull Requests

The process described here has several goals:

• Maintain the project's quality.

• Fix problems that are important to users.

• Engage the community in working toward the best possible outcome!

• Enable a sustainable system for maintainers to review contributions.

Style Guide for Git Commit Messages 📝

How you can add more value to your contribution logs:

• Use the present tense. (Example: "Add feature" instead of "Added feature")

• Use the imperative mood. (Example: "Move item to...", instead of "Moves item to...")

• Limit the first line (also called the Subject Line) to 50 characters or less.

• Capitalize the Subject Line.

• Separate subject from body with a blank line.

• Do not end the subject line with a period.

• Wrap the body at 72 characters.

• Use the body to explain the what, why, vs, and how.

How to Contribute 🚀

• Fork the repository and create a branch for any issue that you are working on.

• Create a pull request which will be reviewed and suggestions would be provided.

• Add Screenshots to help us know what changes you have done.

How to make a pull request 🤔

2. Clone the forked repository.

3. Navigate to the project directory.

4. Create a new branch

Kindly give your branch a more descriptive name like feat-add-ethereum instead of patch-1.

You could follow this convention. Some ideas to get you started:

• Feature Updates: feat-<2-3-Words-Description>-<ISSUE_NO>

• Bug Fixes: fix-<2-3-Words-Description>-<ISSUE_NO>

• Documentation: docs-<2-3-Words-Description>-<ISSUE_NO>

• And so on...

5. Add the resource, please follow the guidelines following

• Add the link: * [project-name](http://example.com/) - A short description ends with a period.

  • Keep descriptions concise and short.

• Search previous Pull Requests or Issues before making a new one, as yours may be a duplicate.

• Don't mention Web3 in the description as it's implied.

• Check your spelling and grammar.

• Remove any trailing whitespace.

Just a gentle reminder: Try not to submit your own project. Instead, wait for someone finds it useful and submits it for you.

6. Stage your changes and commit.

7. Push your local commits to the remote repository.

9. 🎉 Congratulations! You've made your first pull request! Now, you should just wait until the maintainers review your pull request.

🛑 Important

✅ Good Practice

• Comment on the issue to get assigned

• Create an issue before you make a Pull Request

❌ Bad Practice

• Creating PRs without assignment will not be accepted and will be closed.

📈 Getting started

This is a list of the content I shared about Web3 for the upcoming 200 days

You can find Francesco