[PR #1429] [CLOSED] Add Ethereum #9698

New Issue

GiteaMirror · 2026-04-19T03:58:06-05:00

GiteaMirror commented

2026-04-19 03:58:06 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1429
Author: @void4
Created: 10/22/2018
Status: ❌ Closed

Base: master ← Head: patch-1

📝 Commits (1)

c6e4de4 Update readme.md

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

Add awesome-ethereum to decentralized systems, since there is no such resource yet.

https://github.com/void4/awesome-ethereum#readme
There are lists of Bitcoin and other decentralized systems, but not one for the Ethereum system, the second largest system in operation.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

You have to review at least 2 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. I seem to be unable to comment on other PRs
I have read and understood the instructions for creating a list.
This pull request has a descriptive title in the format Add Name of List (Example: Add Swift), not Update readme.md or Add awesome list. ✓
The entry in the Awesome list should:
- Include a short description about the project/theme of the list. It should not describe the list itself.
  Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish.. ✓
- Be added at the bottom of the appropriate category. ✓
The list I'm submitting complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. ✓
It's the result of hard work and the best I could possibly produce. ✓
Non-generated Markdown file in a GitHub repo. ✓
Includes a succinct description of the project/theme at the top of the readme. [(Example)] (https://github.com/willempienaar/awesome-quantified-self) ✓
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics. ✓
Not a duplicate. ✓
Only has awesome items. Awesome lists are curations of the best, not everything. ✓
Includes a project logo/illustration whenever possible. ✓
- Either centered, fullwidth, or placed at the top-right of the readme. (Example)
- The image should link to the project website or any relevant website.
- The image should be high-DPI. Set it to maximum half the width of the original image.
Entries have a description, unless the title is descriptive enough by itself. It rarely is though. ✓
Includes the Awesome badge. ✓
- Should be placed on the right side of the readme heading. ✓
  - Can be placed centered if the list has a centered graphics header.
- Should link back to this list.
Has a Table of Contents section.
- Should be named Contents, not Table of Contents. ✓
- Should be the first section in the list. ✓
- Should only have one level of nested lists, preferably none. ✓
Has an appropriate license.
- That means something like CC0, not a code licence like MIT, BSD, Apache, etc. ✓
- WTFPL and Unlicense are not acceptable licenses.
- If you use a license badge, it should be SVG, not PNG.
Has contribution guidelines. ✓
- The file should be named contributing.md. Casing is up to you. ✓
Has consistent formatting and proper spelling/grammar.
- The link and description are separated by a dash.
  Example: - [AVA](…) - JavaScript test runner.✓
- The description starts with an uppercase character and ends with a period. ✓
- Consistent and correct naming. For example, Node.js, not NodeJS or node.js. ✓
Doesn't include a Travis badge.
You can still use Travis for list linting, but the badge has no value in the readme. ✓

Go to the top and read it again.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/1429 **Author:** [@void4](https://github.com/void4) **Created:** 10/22/2018 **Status:** ❌ Closed **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`c6e4de4`](https://github.com/sindresorhus/awesome/commit/c6e4de4d71ae0cfbdc9f977e3d8e20c887d14fa1) Update readme.md ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description Add awesome-ethereum to decentralized systems, since there is no such resource yet.   https://github.com/void4/awesome-ethereum#readme There are lists of Bitcoin and other decentralized systems, but not one for the Ethereum system, the second largest system in operation. ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** ## Requirements for your pull request - **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. **I seem to be unable to comment on other PRs** - I have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md). - This pull request has a descriptive title in the format `Add Name of List` (Example: `Add Swift`), not `Update readme.md` or `Add awesome list`. ✓ - The entry in the Awesome list should: - Include a short description about the project/theme of the list. **It should not describe the list itself.** Example: `- [Fish](…) - User-friendly shell.`, not `- [Fish](…) - Resources for Fish.`. ✓ - Be added at the bottom of the appropriate category. ✓ - The list I'm submitting complies with the below requirements. ## Requirements for your Awesome list - **Has been around for at least 30 days.** That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. ✓ - It's the result of hard work and the best I could possibly produce. ✓ - Non-generated Markdown file in a GitHub repo. ✓ - **Includes a succinct description of the project/theme at the top of the readme.** [(Example)] (https://github.com/willempienaar/awesome-quantified-self) ✓ - The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). I encourage you to add more relevant topics. ✓ - Not a duplicate. ✓ - Only has awesome items. Awesome lists are curations of the best, not everything. ✓ - Includes a project logo/illustration whenever possible. ✓ - Either centered, fullwidth, or placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron) - The image should link to the project website or any relevant website. - The image should be high-DPI. Set it to maximum half the width of the original image. - Entries have a description, unless the title is descriptive enough by itself. It rarely is though. ✓ - Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge). ✓ - Should be placed on the right side of the readme heading. ✓ - Can be placed centered if the list has a centered graphics header. - Should link back to this list. - Has a Table of Contents section. - Should be named `Contents`, not `Table of Contents`. ✓ - Should be the first section in the list. ✓ - Should only have one level of [nested lists](https://commonmark.org/help/tutorial/10-nestedLists.html), preferably none. ✓ - Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license). - That means something like CC0, **not a code licence like MIT, BSD, Apache, etc.** ✓ - [WTFPL](http://www.wtfpl.net) and [Unlicense](http://unlicense.org) are not acceptable licenses. - If you use a license badge, it should be SVG, not PNG. - Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines). ✓ - The file should be named `contributing.md`. Casing is up to you. ✓ - Has consistent formatting and proper spelling/grammar. - The link and description are separated by a dash. Example: `- [AVA](…) - JavaScript test runner.`✓ - The description starts with an uppercase character and ends with a period. ✓ - Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`. ✓ - Doesn't include a Travis badge. You can still use Travis for list linting, but the badge has no value in the readme. ✓ Go to the top and read it again. --- 🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

GiteaMirror added the pull-request label 2026-04-19 03:58:06 -05:00

GiteaMirror closed this issue

2026-04-19 03:58:07 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#9698