Skip to main content

A taxonomy of crypto and decentralized web ecosystems and repositories

Project description

Open Dev Data is a taxonomy of open source blockchain, web3, cryptocurrency, and decentralized ecosystems and their code repositories. This dataset is not complete, and hopefully it never will be as there are new ecosystems and repositories created every day.

How to use this taxonomy

The taxonomy can be used to generate the set of crypto ecosystems, their corresponding sub ecosystems, and repositories at a particular time.

🖼️ GUI Mode

You can use the taxonomy viewer at crypto-ecosystems.xyz. Here you can query for ecosystems and repos as well as export all of the repos for specific ecosystems.

image

💻 CLI Mode

For more data science uses, one can export the taxonomy to a json format by using the following command:

./run.sh export exports.jsonl

If you want to export a single ecosystem, its sub ecosystems, and its repositories, you can use the -e parameter to specify a particular ecosystem.

./run.sh export -e Bitcoin bitcoin.jsonl

The export format is one json entry per line like the following:

{"eco_name":"Bitcoin","branch":["Lightning"],"repo_url":"https://github.com/alexbosworth/balanceofsatoshis","tags":["#developer-tool"]}
{"eco_name":"Bitcoin","branch":["Lightning"],"repo_url":"https://github.com/bottlepay/lnd","tags":[]}

By using the branch attribute, you can see how particular repos are attributed to the parent ecosystem.

How to update the taxonomy

There is a domain specific language (DSL) containing the keywords that can make changes to the taxonomy. You specify migrations by using files of the format

migrations/YYYY-MM-DDThhmmss_description_of_your_migration

The datetime format is a loosely ISO8601 but without the ':' characters to make them valid files on Windows.

Some examples migration filenames could be:

migrations/2009-01-03T181500_add_bitcoin
migrations/2015-07-30T152613_add_ethereum

Simply create your new migration and add changes to the taxonomy using the keywords discussed below.

Data Format

Example: Adding an ecosystem and connecting it.

-- Add ecosystems with the ecoadd keyword.  You can start a line with -- to denote a comment.
ecoadd Lightning
-- Add repos to ecosystems using the repadd keyword
repadd Lightning https://github.com/lightningnetwork/lnd #protocol
-- Connect ecosystems using the ecocon keyword.
-- The following connects Lighting as a sub ecosystem of Bitcoin.
ecocon Bitcoin Lighting

How to Give Attribution For Usage of the Electric Capital Crypto Ecosystems

The repository is licensed under MIT license with attribution.

To use the Electric Capital Crypto Ecosystems Map in your project, you will need an attribution.

Attribution needs to have 3 components:

  1. Source: “Electric Capital Crypto Ecosystems”
  2. Link: https://github.com/electric-capital/crypto-ecosystems
  3. Logo: Link to logo

Optional: Everyone in the crypto ecosystem benefits from additions to this repository. It is a help to everyone to include an ask to contribute next to your attribution.

Sample request language: "If you’re working in open source crypto, submit your repository here to be counted."

Sample attribution

Data Source: Electric Capital Crypto Ecosystems

If you’re working in open source crypto, submit your repository here to be counted.

Thank you for contributing and for reading the contribution guide! ❤️

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

open_dev_data-1.2.tar.gz (23.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

open_dev_data-1.2-py3-none-any.whl (25.0 kB view details)

Uploaded Python 3

File details

Details for the file open_dev_data-1.2.tar.gz.

File metadata

  • Download URL: open_dev_data-1.2.tar.gz
  • Upload date:
  • Size: 23.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.7.19

File hashes

Hashes for open_dev_data-1.2.tar.gz
Algorithm Hash digest
SHA256 5ac278490b8f88533fea4134a01400daaaad3da4401f3b9f94f8384b1c6dcc67
MD5 1d188b87ebf3e3ab0f9456e827e56d05
BLAKE2b-256 3e83c98f3fc85653cd94c24b67a73358a6e40c547e70163db7ef0bfbab9f3011

See more details on using hashes here.

File details

Details for the file open_dev_data-1.2-py3-none-any.whl.

File metadata

File hashes

Hashes for open_dev_data-1.2-py3-none-any.whl
Algorithm Hash digest
SHA256 b309445d517a3f6faf30c9cd0ac37e08130b42925d27b6f036ef6ac2d9867027
MD5 69ea7918c5c6b9e5579cb712bd594048
BLAKE2b-256 aea22d46b28c2357a76d61ade24f4d6af0df35e7df6e61880aee6ad9825a6e47

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page