OpenZeppelin / OpenZeppelin/docs

Add your project to the Midnight ecosystem map

Open
#132 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
MDX
Stars
6
Forks
23
Avg merge
1d 13h
Merged PRs (30d)
4

Description

Hi! 👋

We noticed this repo might be part of the Midnight ecosystem and wanted to reach out directly.

Midnight is submitting its ecosystem map to Electric Capital ahead of mainnet. Electric Capital produces the industry-standard developer report used by investors, protocols, and media to track which ecosystems are growing. If your repo isn't attributed correctly, it won't be counted — even if the code is active and the work is real.

Two small updates are all it takes.


Step 1: Add GitHub topics

Go to your repo → About section (gear icon in the right sidebar) → add:

  • midnightntwrk — required for all Midnight ecosystem projects
  • compact — add only if your project uses the Compact language

Do not use midnight, midnight-network, midnight-compact, or midnight-ecosystem — these won't be picked up by the tracker.

Step 2: Add one sentence to your README

Add one of the following near the top of your README. Please use the exact wording.

Project type Attribution sentence
dApps, contracts, or tooling running directly on Midnight This project is built on the Midnight Network.
SDKs, infrastructure, wallets, or services This project integrates with the Midnight Network.
Developer tooling, frameworks, or libraries This project extends the Midnight Network with additional developer tooling.

That's it. These two changes take under five minutes and mean your work shows up in the official ecosystem count at mainnet launch.

Earn Zealy points while you're at it

Each of the steps above has a corresponding quest on Zealy. Complete them to earn points and appear on the Midnight ecosystem leaderboard.

If you have questions or need help, find us in the Midnight Discord in #dev-chat, or reply here.

Thanks for building on Midnight! 🕛

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository README and its About section. Determine which project type applies, add the required midnightntwrk topic, and add the matching attribution sentence using the exact wording; done means both updates are present.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.