A critical, honest analysis of where Code Orange stands, what grant givers actually want to see, and what it takes to become the definitive Bitcoin developer pipeline in Asia.
Grant reviewers at these organizations see hundreds of applications. They're not looking for passion or good intentions — they fund those who have already proven they can ship. Here's what separates funded applicants from rejected ones:
1. Upstream Code Contributions (This Is the #1 Signal)
OpenSats funded 10,904 PRs in 2025. Their entire thesis is that open-source contributions are how Bitcoin gets stronger. When they evaluate an education program, they're asking one question: "How many PRs did your graduates ship to real Bitcoin repos?"
Code Orange's current answer: ~15 PRs opened, ~9 merged. That's a start, but Bitshala — your closest peer — has graduates contributing to Bitcoin Core, LDK, and BDK regularly, and they have a funded incubator that puts graduates on 6-month stipends to do nothing but write code.
What to do: Track every PR obsessively. Set a goal of 50 merged PRs by year-end. Create a "first PR" milestone for every cohort graduate. Make the PR dashboard your most-updated repo.
2. Graduate Follow-Through (Not Just Graduation Counts)
49 registered, 21 graduated sounds good. But grant reviewers immediately ask: "What did the 21 do after graduation?" If the answer is "we're not sure," that's a red flag.
What to do: Follow every graduate for 6 months post-graduation. Track: Did they submit a BOSS Challenge? Did they open a PR? Did they apply for a grant? Did they start contributing to a project? Publish this data quarterly. This is your strongest differentiator — no other Asian education program does post-graduation tracking.
3. FOSS Licensing on Everything (Non-Negotiable for OpenSats)
You've already CC0-licensed your curriculum. Good. But several of your existing repos (workshop slides, etc.) still have no LICENSE file. A grant reviewer who clicks on bitcoin-mining-slides and sees no license will wonder if the program is actually committed to open source.
What to do: Add CC0 LICENSE to every single repo. This takes 30 minutes and removes a blocker.
4. Financial Transparency (The Thing Nobody Wants to Talk About)
Grant givers want to know: How much does this cost to run? What's the burn rate? Where does the money go? Programs that can articulate "$X per developer trained" or "$Y per merged PR" get funded. Programs that can't explain their unit economics get passed over.
What to do: Calculate your cost per graduate. Even a rough estimate ("We spend ~$500/month on tools, venue, and internet, training ~20 developers per cohort, so our cost is ~$25/developer/month"). Include this in your next grant application. It signals maturity.
5. Sustainability Signal (Not Just "Give Us Money")
The worst thing you can signal is dependency. Grant givers want to fund programs that will survive without them. They want to see: revenue experiments, corporate sponsorships, community contributions, or a clear path to sustainability.
What to do: Explore at least one revenue/sustainability model: corporate Bitcoin training workshops for companies in Bali, paid advanced workshops, sponsorship from Bitcoin companies (Nunchuk, Fedi, etc.), or a community fund via Fedimint.
1. Physical Hub (Bitcoin House Bali) This is rare and valuable. Most Bitcoin education happens online. Having a physical location with in-person workshops, hardware demos, and community presence is something Bitshala doesn't have. HRF and OpenSats both value grassroots, in-person community building. Lean into this.
2. Geographic Niche (Southeast Asia) There is no other serious Bitcoin developer education program focused on Southeast Asia. Bitshala covers India. Libreria de Satoshi covers Latin America. Code Orange owns Asia. This geographic monopoly is your strongest grant argument. But you need to expand beyond Bali to prove the "Asia" claim.
3. Program Diversity You run 10+ different types of workshops covering everything from absolute beginners (Reading Club) to advanced developers (Bitcoin Dojo, rawBit). This "full funnel" approach — from curious person to open-source contributor — is exactly what grant givers want to see.
4. Partner Network Chaincode Labs, Bitcoin Dev Project, rawBit, Fedi, Soapbox, Bitcoin House Bali — you've built real partnerships with real Bitcoin organizations. This validates your credibility.
5. Consistency 15 months of continuous, documented activity. Monthly workshops without missing a beat. This consistency is your proof of work.
1. Low PR Volume 15 PRs in 15 months is roughly 1 PR per month. For a program with 33+ graduates, that's a low conversion rate. Grant givers will compare this to Bitshala's output and find it lacking.
Specific fix: Create a mandatory "first PR" requirement for Dojo and Decoding Bitcoin graduation. Even a documentation fix counts. Target: every graduate ships at least 1 PR within 30 days of graduation.
2. No Graduate Case Studies You have amazing individual stories — Chaitika working on Silent Payments, Razor contributing to peer-observer — but none of them are written up and published. Grant reviewers love narrative. They want to read a 500-word story about how someone went from zero to merged PR.
Specific fix: Write 3 case studies. Publish them in the impact report repo. This is 3-4 hours of work with massive ROI.
3. "Asia" Claim Is Currently "Bali + Chiang Mai" Your positioning is "Asia's Bitcoin Developer Pipeline" but your physical presence is limited to two cities in two countries. Grant givers who look closely will see this gap.
Specific fix: Expand to 1-2 more countries by end of 2026. The easiest path: your Bitcoiner Mastermind model already trains community leaders. Find one person in Vietnam, Philippines, or Malaysia to run a Sovereign Bitcoiner workshop using your open-source slides. One tweet with photos from Manila or Ho Chi Minh City transforms the narrative.
4. No Website/Landing Page With Impact Data codeorange.dev exists but doesn't showcase your impact data, PR counts, or graduate outcomes. A grant reviewer who visits your website should see your strongest numbers immediately.
Specific fix: Add an impact section to codeorange.dev with key metrics, or at minimum link prominently to your GitHub impact report.
5. Discord Size Unknown/Untracked Bitshala has 1,200+ Discord members and 350+ regular participants. If Code Orange's Discord is significantly smaller, that's a gap. If it's comparable, it's a strength you're not advertising.
Specific fix: Track and publish your Discord member count. Include it in every grant application and impact report.
Goal: Close every gap identified above before your next grant application.
- LICENSE every repo — 30 minutes, do it today
- Write 3 graduate case studies — 4 hours total
- Create a "first PR" graduation requirement — policy change, immediate
- Track Discord size — 5 minutes to check, add to impact report
- Calculate and publish cost-per-developer — 1 hour
- Pin repos, write descriptions, add topics — 1 hour (from existing action plan)
Goal: Double PR output, expand to 2 new countries, launch advanced track.
A. The Developer Pipeline (Your Core Product)
Build a clear, documented path from "curious Bitcoiner" to "Bitcoin Core contributor":
Reading Club / Meetup (Month 1)
↓ "I want to understand Bitcoin deeper"
Sovereign Bitcoiner Workshop (Month 2)
↓ "I want to build things"
Decoding Bitcoin Cohort (Months 3-4)
↓ "I want to code Bitcoin"
Bitcoin Dojo (Months 5-6)
↓ "I want to write production code"
rawBit Study Cohort (Months 7-8)
↓ "I want to contribute to open source"
BOSS Challenge / First PR (Month 9)
↓ "I want to do this full-time"
Grant Application Support (Month 10+)
Document this pipeline visually. Put it on your website, in your README, and in every grant application. This is your unique value proposition: not just workshops, but a complete journey.
B. Geographic Expansion (The "Asia" Proof)
Target cities with existing Bitcoin communities:
| City | Country | Strategy | Timeline |
|---|---|---|---|
| Ho Chi Minh City | Vietnam | Find 1 community leader, ship open-source slides | Q3 2026 |
| Manila | Philippines | Partner with existing Bitcoin meetup | Q3 2026 |
| Bangkok | Thailand | Extend Chiang Mai partnership | Q4 2026 |
| Kuala Lumpur | Malaysia | Partner with local Bitcoin community | Q4 2026 |
| Singapore | Singapore | BitDevs partnership | Q4 2026 |
You don't need to be physically present everywhere. Your Bitcoiner Mastermind "train-the-trainer" model already works. Ship the slides, train one leader per city, let them run it. Document it with photos and tweets.
C. Advanced Track (The Missing Piece)
Your pipeline currently ends at "first PR." The funded programs (Bitshala, Summer of Bitcoin) have an incubator/residency that takes graduates further. You need an equivalent:
Code Orange Fellowship (proposed):
- 3-month program for top Dojo/rawBit graduates
- Dedicated mentorship on a specific Bitcoin project
- Weekly 1:1 calls with a senior contributor
- Goal: 3+ merged PRs during the fellowship
- Funded by grant money (this is what you apply for)
This is the piece that turns your grant application from "education program" to "developer pipeline" — the difference between teaching someone to code and actually producing Bitcoin contributors.
Goal: Become the recognized name in Asian Bitcoin developer education.
A. Publish Research
Write a report on the state of Bitcoin development in Southeast Asia:
- How many Bitcoin developers are in each country?
- What languages do they speak? What tools do they use?
- What are the barriers to contribution? (language, timezone, access to hardware)
- What's the total addressable market for Bitcoin developer education in Asia?
This positions Code Orange as a thought leader, not just a workshop runner. HRF and OpenSats would both value this data.
B. Host a Bitcoin Dev Conference in Asia
A small, invite-only developer conference in Bali (20-50 attendees) focused exclusively on Bitcoin development. Invite Chaincode, Bitcoin Dev Project, Btrust, OpenSats. Livestream it. This creates a flagship event that anchors your brand.
C. Build the Alumni Network
Track every graduate in a public directory (with consent). Show where they are now: which projects they contribute to, which grants they received, what they built. This living proof becomes your best marketing.
If you execute the plan above, here's what a grant reviewer sees in September 2026 when you apply to OpenSats:
- Pipeline: Clear 10-month journey from curious Bitcoiner to Bitcoin Core contributor
- Output: 50+ merged PRs across Bitcoin repos (up from 15)
- Graduates: 50+ with tracked post-graduation outcomes
- Geographic reach: 5+ cities across 4+ countries in Southeast Asia
- Case studies: 5+ published graduate journeys
- Sustainability: Clear unit economics ($X per developer), multiple funding sources
- FOSS: Everything CC0-licensed, open-source, replicable
- Recognition: Bitcoin Asia 2026 speaker, HRF newsletter featured, partnered with Chaincode
- Community: Discord with X00+ members, monthly active contributors
- Physical hub: Bitcoin House Bali as home base, satellite communities across Asia
- Advanced track: Fellowship program producing dedicated Bitcoin contributors
- Thought leadership: Published report on Asian Bitcoin developer landscape
That's not "strong applicant." That's "obvious yes."
If you only take one thing from this assessment, it's this: the PR count is your report card. Everything else — workshops, meetups, cohorts, slides, events — is the process. The PRs are the result. Every decision you make should be filtered through: "Does this lead to more merged PRs in Bitcoin open-source projects?"
The workshops are the funnel. The cohorts are the training. The PRs are the proof. Make the proof undeniable, and the grants will follow.
Written April 2026. This assessment should be revisited quarterly.
Code Orange Dev School | codeorange.dev