Skip to main content

3 posts tagged with "community"

View All Tags

Get your project on the map

· 5 min read
Lauren Lee
Director of Developer Relations

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

TopicWhen to use
midnightntwrkRequired for all Midnight ecosystem projects
compactAdd only if your project uses the Compact language
warning

Do not use: midnight, midnight-network, midnight-compact, or midnight-ecosystem. These variants are not tracked and will not associate your project with the ecosystem.

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 typeAttribution 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.

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.

Hacktoberfest Contributor Guide

· 3 min read
Jay Albert
Developer Relations Engineer

Hacktoberfest is a global open-source event held every October, where developers contribute pull requests to public repositories to earn digital rewards.
Midnight is joining the celebration by inviting contributors to improve its open-source ecosystem — from smart contracts and DApps to core libraries and documentation.

Review the guide to get started.

Welcome to the Midnight Community Hub! ✨

· 4 min read
Stevan Lohja
Developer Relations

The Community Hub serves as a collaborative platform for gathering and managing community-driven contributions. Whether you're proposing new content, requesting features, reporting issues, or ideation for dApps, this repo is your entry point. We use GitHub's built-in features like issues, projects, and automations to ensure ideas are triaged efficiently and turned into actionable tasks.

How to Contribute

Ready to jump in? It's as simple as creating an issue.

Our Workflow: From Idea to Reality

Step 1: The Community Board (Triage)

All new issues land here for initial review. This board is public, so everyone can see what's being proposed.

  • New: Your issue has been submitted and is awaiting review.
  • In Triage: The triage committee is actively reviewing your submission for validity, clarity, and priority.
  • Needs Discussion: The issue requires more feedback or clarification from the community or the original poster.
  • Rejected: The issue is out-of-scope or invalid. We will always provide a clear explanation.

Once an issue is approved, it gets a triaged label and is automatically moved to the next stage.

Step 2: The Grab n' Go Board (Development)

This board contains approved, ready-to-work-on tasks. It's the community's backlog!

  • Ready: Triaged issues waiting for a contributor to pick them up. Look for labels like good-first-issue if you're new!
  • In Progress: A contributor has assigned themselves the issue and is actively working on it.
  • Done: The work is complete and the issue has been closed (this happens automatically when a linked PR is merged).

Choosing the Right Issue Template

To help us categorize and review your ideas faster, please use the best template for your submission:

  • 📝 Content Proposal: Suggest new articles, tutorials, or educational resources to engage the community.
  • 💡 Feature Request/Suggestion: Propose new features or enhancements for our tools and processes.
  • 🐛 Bug Report: Report any defects, errors, or unexpected behavior. Please include clear reproduction steps!
  • 🌐 dApp Proposal: Share your vision for a new decentralized application, integration, or improvement.

Selecting a template automatically applies the right labels, helping our automation keep things organized.

Our goal is to foster a truly collaborative environment where the collective wisdom of our community helps us build more robust, community-driven solutions.

Why Now? The Developer Relations Perspective

You might be asking, "Why is the Developer Relations (DevRel) team launching this?" That's a great question, and it gets to the very core of our mission!

At its heart, Developer Relations is about empowering developers.

The Community Board is a natural, powerful extension of this mission. Here’s why it’s so crucial for us:

  1. Direct Feedback Loop: Before, collecting structured feedback could be spread across multiple channels. The Community Board centralizes this, giving us a clear, prioritized view of what matters most to you.
  2. Transparency and Prioritization: You'll be able to see what other developers are asking for, upvote ideas you support, and even watch as issues move from "Under Review" to "Planned" to "Shipped." This transparency helps you understand our roadmap and how your contributions fit in.
  3. Community-Driven Development: We genuinely believe that the best products are built in collaboration with their users. The board allows us to tap into the collective intelligence of our community, surfacing the most impactful ideas and validating them with real-world needs.
  4. Building Stronger Relationships: By giving you a clear, actionable way to contribute, we hope to build an even stronger, more engaged community where everyone feels invested in our shared success.