Preprod migration and ecosystem attribution

Hi there,

We’re standardizing ecosystem attribution so Midnight projects are correctly recognized in ecosystem-level developer reports, including Electric Capital. This requires a few small but important updates in your repo.

Important: Midnight testnet-02 is scheduled for deprecation on February 28. Repositories that are not migrated to Preprod by this date will be considered inactive for ecosystem reporting purposes and may be excluded from external developer analytics and industry reports.

✅ Preprod + Attribution Checklist

Please confirm each item below by checking it off or leaving a comment if blocked.

• Repo runs against Midnight Preprod
• Any references to testnet-02 are removed or clearly marked as deprecated
• midnightntwrk added as a GitHub topic
• compact added as a GitHub topic (if applicable)
• README includes one required attribution sentence:
  • “This project is built on the Midnight Network.”
  • “This project integrates with the Midnight Network.”
  • “This project extends the Midnight Network with additional developer tooling.”
• Preprod usage or configuration is documented (README or docs)

If you are blocked on Preprod migration, comment with details and the DevRel team will help unblock.

1. Migrate to Preprod (required, deadline Feb 28)

Please ensure your project is running against Midnight Preprod rather than outdated or local-only configurations.

• If your repo already supports Preprod, no changes are needed.
• If not, please update configuration and documentation so Preprod is the default or clearly documented option.
• If you’re unsure whether your repo is Preprod-ready, flag it in a comment and we’ll help unblock.

Testnet-02 will no longer be supported after February 28. Preprod is the only environment that will be considered current going forward.

To help you migrate your app to Preprod, you can use this migration guide that explains the necessary changes.

2. Add GitHub topics (required)

GitHub topics are how ecosystem projects are programmatically discovered and counted.
Required topic:
midnightntwrk

Optional topic (only if applicable):
compact

Do not use:
midnight
midnight-network
midnight-ecosystem

How to add topics (GitHub UI)

1. Go to your repository on GitHub
2. On the repo homepage, look at the right-hand sidebar
3. Find the About section
4. Click the ⚙️ gear icon
5. In the Topics field, add:

• midnightntwrk
• and, if applicable, compact

6. Click Save changes

3. Add a single attribution sentence to your README (required)

Add one sentence near the top of your README that clearly states how your project relates to Midnight.

Use one of the patterns below. Please do not customize the wording:

Built on Midnight
For dApps, contracts, or tooling that run directly on Midnight
“This project is built on the Midnight Network.”

Integrates with Midnight
For SDKs, infrastructure, wallets, or services that connect to Midnight
“This project integrates with the Midnight Network.”

Extends Midnight
For developer tooling, frameworks, or libraries that expand Midnight capabilities
“This project extends the Midnight Network with additional developer tooling.”

4. Collect Zealy points (optional)

If you’re participating in Zealy, completing the steps above may be eligible for points. Details can be found in the quests themselves:

• Add Midnight attribution
• Update to Preprod
• Add topics

Why this matters

Consistent GitHub metadata and README attribution allow Midnight ecosystem projects to be accurately indexed in developer analytics and industry reports. This directly affects how the ecosystem is represented externally and whether your work is visible at that level.

Start by checking the repository's current Preprod and testnet-02 references, then read the linked MIGRATION_GUIDE.md for the required migration details. Review the README and GitHub repository topics against the checklist. Done means Preprod is documented or configured, deprecated references are handled, the required topics are present, and one approved attribution sentence appears in the README.