This is a mapping of the current Ethereum ecosystem, a taxonomy of projects and products
ethereum-ecosystem-map
This repository is dedicated to collect and display resources that contribute to an objective mapping or overview of the Ethereum ecosystem.
Background & Motivations
Sometimes, for both newcomers and seniors of the Ethereum community, it can be hard to keep track of the latest advances, as well as the latest conversations concerning research. At the same time, the community lacks access to a data-driven, objective mapping of the Ethereum ecosystem.
From the ECF's perspective, we wish to build automated or semi-automated tools that
provide an objective overview of the state of the ecosystem, so community members can see in what layers, areas or tooling Ethereum is lacking.
For grant managers at the ECF, this overview can be helpful for prioritising research and development in those areas that are essential but less attractive, distribute funding in a balanced manner, and strive for diversity of projects vertically along the stack, and horizontally, in terms of implementations.
Taxonomy (V.0.2)
Taxonomies are an useful way of presenting information in a visual and concise manner. Nonetheless, they are not perfect, as there will always be projects or cases that do not fit limitedly to one layer, as well as others that fit at the same time in more than one layer.
For illustration purposes, the following is one of the first iterations of a taxonomy of projects in the ethereum ecosystem.
Note that all the projects mentioned serve as examples only of each layer, by no means are these mentions any kind of endorsement.
Should you know of any projects that are not yet listed or suggest a correction, choose one of the following. Depending on the contributions, there best way of proceeding are:
Error reporting: GitHub Issue, PRs
Listing new project: GitHub Issue, PRs
Making suggestions: GitHub Issue
Questions: GitHub Issue
Either way, make sure you include the following information:
Add a label: error for corrections, new project for additions
Assign it to me @awasunyin, if this issue has not been dealt with within 7 natural days
And, whenever applicable:
Project name
Project implementation language
Project link to GitHub (must be open-source, if code is not ready, at least some documentation or specifications)
Which layer? See taxonomy figure.
Create a Pull Request
Should you want to make the changes directly, make sure you include the additional information:
Brief description of what changes have been made and why, you can include more than one label
Editing .csv files directly
Currently, I compile the names of projects and their information in csv files, which you can find under /data/*.csv. After some time, I convert the .csv files into markdown tables and add them to the README.md.
Note: GitHub offers this user-friendly .csv viewer. For changes the .csv, open a PR.
