Midnight Foundation is launching another round of the Content Bounty Program to support community members who want to create educational content about building on Midnight. Whether you write tutorials, make videos, or build technical guides, there’s room for you here.
The pilot round helped us test the waters and gather valuable feedback from both contributors and reviewers. Based on what we learned — including issues with submission quality, AI-generated content, and non-functional code- we’ve refined the program. Welcome to Eclipse.
What We’re Looking For
We need content that helps developers understand and build on Midnight. This includes:
- Written tutorials and guides
- Video walkthroughs and explainers
- Technical documentation
- Code examples and sample projects
- Educational content about zero-knowledge proofs, privacy tech, and Midnight’s architecture
The goal is simple: make it easier for developers to learn Midnight and start building.
Where to Find Bounties
We post content bounties as GitHub issues on our Contributor Board, tagged with "bounty". Each issue describes what we’re looking for, the deliverables, and the payout range.
Effort Tiers and Compensation
Bounties are organized into three effort levels. Each tier has a payout range, the final amount depends on the quality of your work and how well it meets the requirements.
| Tier | Effort Level | Payout Range |
|---|---|---|
 Tier 1 |
Light | $300 – $500 |
 Tier 2 |
Medium | $500 – $700 |
 Tier 3 |
Deep | $700 – $1,000 |
Payout ranges are denominated in USD but paid in NIGHT tokens. See Bounty Program Terms for conversion details.
What’s Changed in Eclipse
- Open participation: Bounties are no longer first-come, first-served. Anyone can submit an entry for any open bounty. The best valid submission wins.
- AI content policy: We actively check for AI-generated content (see below).
- Code must compile: For Compact-related bounties, your code must compile successfully. Non-compiling code is automatically disqualified.
- Zealy prerequisite: For Compact-related bounties, contributors are encouraged to complete the designated Zealy task to demonstrate baseline familiarity before submitting.
- Structured review cycle: One round of feedback before rejection.
AI-Generated Content Policy
All submissions are checked for AI-generated content. We use a combination of detection tools and manual review to identify content that has been substantially generated by AI.
Submissions found to be AI-generated will be disqualified.
We expect original work that reflects your understanding of the topic. Using AI tools to assist with grammar, formatting, or code suggestions is acceptable, but the core content, explanations, and code must be your own. If a submission reads like it was prompted and pasted, it will not be accepted.
Code Compilation Requirement
For all Compact-related bounties, your code must compile successfully. This is a hard requirement.
- Before submitting, run your Compact code through the compiler and verify it builds without errors.
- Submissions with non-compiling code will be immediately disqualified — no review rounds, no revisions.
- This applies to code examples in tutorials, sample projects, and any content that includes Compact code snippets.
If you’re new to Compact, make sure you’ve gone through the Midnight documentation and understand the basics before attempting a code-related bounty.
Tooling: Midnight MCP
We provide Midnight MCP (midnight-mcp), a Model Context Protocol server that integrates with AI-assisted development tools like Claude Desktop, Cursor, and VS Code. It gives you access to:
- Real compilation: Compile your Compact code against the actual compiler service and get real error messages with line numbers before submitting
- Contract analysis: Static analysis for security patterns, structure checks, and common mistakes
- Syntax reference: Up-to-date Compact syntax with common pitfalls and correct patterns
- Search: Semantic search across Midnight docs, Compact code examples, and TypeScript SDK
Install it with:
npx midnight-mcp@latest
We strongly recommend using this tool to validate your Compact code before submission.
Zealy Prerequisite for Compact Bounties
If you’re planning to work on a Compact-related bounty, we strongly recommend completing the designated Zealy task first. It’s designed to give you a working understanding of the Compact language and Midnight’s development environment which will save you time and improve the quality of your submission.
Complete the Zealy task here: https://zealy.io/cw/midnightnetwork/questboard/092af843-4e8e-469f-9b0b-94d2a9fe3275
You don’t need to complete it to submit, but contributors who do tend to produce stronger entries.
How Participation Works
Eclipse uses an open submission model, bounties are not assigned on a first-come, first-served basis. Instead:
- Browse open bounty issues tagged with
bountyon the GitHub Contributor Board. - Pick a bounty that matches your skills and interests.
- Work on your submission and post the published copy in the issue thread.
- The best valid submission is selected based on quality, accuracy, and completeness.
Multiple contributors can work on the same bounty simultaneously. The strongest entry wins.
Timeline
Each Eclipse round runs for 4 weeks from today [13/04/2026]. Submissions posted after the round closes won’t be reviewed.
Submission Process
Before you start, check the issue description for full details on deliverables.
Content Categories:
| Type | What to do |
|---|---|
| Video | Share a link to your draft (Google Drive, unlisted YouTube, etc.) for review before publishing |
| Blog post | Share your submission in the issue thread |
| Documentation | Submit a PR to the docs repo and share the link in the issue thread for submission |
| Code | Submit a PR to the relevant repo and share the link in the issue thread for submission |
Important: When you’re ready for formal review/submission, explicitly state “Ready for review” in your comment. Progress updates are encouraged, but only submissions marked as ready will enter the review cycle.
Review Process
We use a structured feedback cycle for potential valid submission:
- Review: Initial review with specific, actionable feedback on what needs to change.
- Validation: We check that the feedback has been addressed. If the submission meets requirements, it’s approved. If not, it will be rejected, and the bounty will remain open to other contributors.
One review cycle gives you a fair opportunity to address feedback while keeping the program moving for everyone.
Disqualification Criteria
A submission will be disqualified or rejected when:
- AI-generated content: Submissions identified as substantially AI-generated
- Non-compiling code: Compact code that doesn’t compile (immediate disqualification)
- Requirements not met after review and validation
- Feedback not addressed: Revisions must demonstrate understanding of the feedback provided
- Non-functional submissions: Empty files, placeholder code, or code that doesn’t run
- Unresponsive contributor: No reply to reviewer comments within a reasonable timeframe
Where Your Content Gets Published
For written content, Dev.to is the default publishing platform. Some contributions may also go directly into the Midnight docs. Other platforms (Medium, Hashnode, personal blog) work too.
If you prefer to publish on your own blog (Medium, Hashnode, personal site), that’s fine but coordinate with us so we can align on timing and promotion.
Additional ways we use Dev.to:
- The official “Eclipse Content Bounty is Live” announcement will be published on Dev.to
- If your contribution goes on the docs directly you will be asked to cross post on dev.to and submit on Zealy for publishing your Dev.to reflection, giving you XP and visibility
For all content types, share on your personal social media (X / LinkedIn) using your own voice and style. Tag Midnight on X or LinkedIn so we can amplify your work.
Use #MidnightforDevs when posting on DEV.to and all social media platforms.
How Midnight Foundation Promotes Your Work
We don’t just review and approve, we actively promote strong contributions across Midnight’s channels. Here’s what accepted contributors can expect:
- Social amplification: We reshare your content from Midnight’s X and LinkedIn accounts
- Dev.to feature: Top submissions get featured placement on the Midnight Dev.to publication
- Newsletter inclusion: Standout content may be highlighted in Midnight’s developer newsletter
- Discord spotlight: Approved content gets shared in our community channels
To help us promote your work effectively, make sure to tag @MidnightNtwrk on X/LinkedIn and use #MidnightforDevs when posting.
Style Guide
All work must follow our technical style guide to ensure consistency and quality across the board.
Quality Standards
We care more about creating genuinely helpful content than volume. Before submitting:
- Follow the style guide
- Test all code examples; they must compile and run
- Explain concepts clearly for your target audience
- Ask questions on the issue thread if you’re unsure about something
The best content gets rewarded at the higher end of the tier range, featured more prominently, and can lead to deeper involvement with the Midnight DevRel team.
Bounty Program Terms
By submitting work or participating in the bounty program, you agree to the Midnight Bounty Program Terms.
Key points:
- All contributions are licensed under Apache License 2.0
- Bounty rewards are paid in NIGHT tokens after KYC verification via SumSub
- Token conversion rate is determined as of the date your submission is accepted and published
- You must meet all eligibility requirements, including sanctions compliance
- See the full terms for details on licensing, liability, and dispute resolution
Questions
If you’re unsure about feedback or requirements, ask in the issue thread before submitting. We’d rather clarify upfront than go through unnecessary review cycles.
You can also reach out in our Discord via the #dev-chat channel.