2 posts tagged with "devrel"

Deployment on the Midnight network during this phase is open to applications that meet the risk self evaluation rubric. This guide explains how to assess your DApp and understand the risk before moving forward.

Step 1: Read the rubric​

Start with the Contract Deployment Rubric. It defines the three risk categories your DApp will be evaluated against:

• Privacy-at-risk: If a ZK fault surfaces, what does a user lose?
• Value-at-risk: If there is an exploit, how much can users lose and is that loss recoverable?
• State-space-at-risk: How much permanent ledger state does your contract generate, and can that growth be attacked?

Each category is scored 1 to 3. The score reflects what is actually at stake if something goes wrong, not how likely it is.

Step 2: Self-assess your contract​

Score your DApp honestly across all three categories using the rubric's tier definitions.

If you score a 3 in any category, your application should not go live until the underlying issue is resolved. A score of 3 is not a permanent state. It is a prompt to rethink your architecture. Drop into Discord #dev-chat or the developer forum and share your contract structure. The DevRel team and the Aliit community can help you understand what a lower-risk design looks like.

If you score 1 or 2 across all categories, you are ready for the next steps.

Step 3: Pull Request via GitHub​

Deployment proposals are submitted as Pull Requests to the Midnight Improvement Proposals repository.

To submit:

1. Fork the repository
2. In the deployments/ folder, create a new file named your-dapp-name.md
3. Open a Pull Request against the main branch with the title: [Deployment Request] Your DApp Name

Include the following in your file:

• A brief description of what your DApp does
• Your self-assessed score for each category (1, 2, or 3) with a short rationale for each
• Any mitigations you have implemented for higher-scoring categories
• A link to your contract code or repository

Step 4: What happens next​

The Midnight Foundation will work with you on your submission. If your scores are correct, you will receive deployment credentials. If the review identifies concerns, you will receive feedback on what needs to be addressed before re-submission.

There is no fixed timeline published at this stage. We will communicate clearly when a decision has been made.

Questions? Drop into Discord #dev-chat or post in the developer forum.

Three quick updates to make sure your work is visible, counted, and recognized as part of the Midnight ecosystem.

Why this matters​

Midnight is approaching mainnet. The ecosystem already has hundreds of active developers building with Compact, deploying on Preprod, and shipping real applications. But activity that isn't attributed doesn't get counted, and that invisibility has real consequences for the ecosystem you're helping to build.

Establishing a clear public record of development activity ensures that the broader blockchain industry recognizes the growth of Midnight Network. Accurate attribution is a functional necessity for the ecosystem and establishes a standardized framework for documenting technical contributions.

The attribution process​

Electric Capital produces the most widely cited developer report in blockchain. Investors, protocols, and media use it to understand which ecosystems are growing, which are stagnant, and where to pay attention. Their methodology is public: they track GitHub commits, contributor counts, and repository metadata across every major blockchain ecosystem. If your repo doesn't have the right metadata, their tooling won't associate it with Midnight, regardless of how active or high-quality the work is.

Midnight is submitting its ecosystem map to Electric Capital for the first time, ahead of mainnet. This is a one-time window to establish a credible public record of where the ecosystem stands from day one. Developer counts from the weeks surrounding a mainnet launch are captured in a rolling window that informs how new ecosystems are ranked and covered. Ecosystems that show up in that window with strong numbers get recognized. Ecosystems that don't, start from a deficit they spend months correcting.

Compounding developer results​

The changes below take under five minutes per repository. They are small, permanent, and consequential. Beyond writing code, implementing these metadata standards is a high-imact action for ecosystem growth. Every repo that completes them is a developer who gets credited for building on Midnight.

TL;DR: Midnight's developer ecosystem is real and growing. These three steps make sure that growth is visible to the tools and reports that the wider industry pays attention to.

Step 1: Add GitHub topics​

GitHub topics are how Electric Capital (and other ecosystem trackers) programmatically identify which repos belong to which ecosystem. Without them, even actively maintained repos are invisible to the tooling.

To add topics to your repository:

1. Go to your repository on GitHub

2. In the right-hand sidebar, find the About section

3. Click the ⚙️ gear icon next to it

4. In the Topics field, add the relevant topics from the table below

5. Click Save changes

Topic	When to use
midnightntwrk	Required for all Midnight ecosystem projects
compact	Add only if your project uses the Compact language

Step 2: Add one attribution sentence to your README​

Electric Capital's tooling scans README files for signals that confirm a repo's relationship to an ecosystem. One sentence, placed near the top of your README, is sufficient. Please use exact wording from the table below. Customising the phrasing means the automated system may not recognize it.

Your project type	Attribution sentence
dApps, contracts, or tooling that run 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."

Step 3: Open a PR to the Awesome dApps list​

The Midnight Awesome dApps list is the community-maintained directory of ecosystem projects. Opening a PR adds your project to that record and makes it discoverable by other developers, partners, and the teams evaluating the ecosystem.

Submit your project at: github.com/midnightntwrk/midnight-awesome-dapps.

Earn Zealy points while you're at it!​

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

• Quest 1: Add the midnightntwrk GitHub topic

• Quest 2: Add the attribution sentence to your README

• Quest 3: Open a PR to the Midnight Awesome dApps list

Three steps, once per repo, permanent record​

These changes don't affect how your code works. They affect how your work is seen. Midnight's first public developer count will be used in every industry report, investor briefing, and ecosystem comparison that references the network for years to come. Your repo being in that count matters.

Questions? Find us in the Midnight Discord in #dev-chat, or reply to this post.