All articles
solanamagicblockbuildershackathoncommunityephemeral-rollups

MagicBlock Builders: the path from Blitz weekend to funded team

How build.magicblock.app works: Builders directory, Solana Blitz, Forge, Hacker House, and Champions. What each stage gives you, how to join, and why MagicBlock is building the strongest real-time Solana builder funnel.

Share
devrels.xyz/a/166short link

Most Solana infra teams ship docs and hope builders show up. MagicBlock ships the runtime and the builder path. You already know the technical story: Ephemeral Rollups give delegated accounts ~10ms blocks while staying Solana-composable; the delegate → ER → commit loop is clean enough to learn in a weekend. MagicBlock Build is what comes next: a concrete ladder from first commit to funded company, with a public directory of people you can actually reach.

Tagline on the site: You ship. We accelerate. From hackathon to fundraise. That is not fluff. The product maps to three stages, plus Champions and a global builders graph.

The path in one screen

text
01  Blitz Hackathon   →  Build the MVP (weekend, virtual, monthly)
02  MagicBlock Forge  →  Grow users (rolling, high-touch on Mainnet)
03  Hacker House      →  IRL network, GTM, fundraising prep

Also live on build.magicblock.app:
  /builders    public directory (Telegram + proof of work)
  /champions   monthly rewarded community leaders
  Submit PoW   GitHub, demo, explorer proof of ER integration

Open build.magicblock.app/builders, log in with Telegram, finish your profile, and you are in the same system as past winners, Forge teams, and Champions. Fellow builders can message you on Telegram from day one. That is how you find a cofounder without begging for Discord roles.

Builders directory: who is building real-time Solana

The directory is the front door. Three steps:

  1. Register with Telegram (connect a wallet when you submit for prizes or events).
  2. Profile: multi-select roles (founder, engineering, ops, product, community), country, and a proof-of-work link.
  3. Journey: browse builders and winners, open the Builders group, pick Blitz / Forge / House when you are ready.

Telegram-first is the right call for Solana. Builders already live there. Proof of work is a first-class field, not a footnote: ship a public link (for example sol.new) so people can judge you by artifacts. Multi-role profiles match how early teams actually look. You are not forced into a single LinkedIn title.

This is infrastructure for a scene. MagicBlock is not hiding talent behind private forms. The directory makes the ecosystem legible: who is shipping, where they are, what they have built, and how to reach them.

Solana Blitz: the monthly ship machine

Solana Blitz is MagicBlock's recurring weekend hackathon. Logistics are builder-grade: register on Luma, get help in Telegram, cowork in WorkAdventure, submit GitHub + demo before Sunday. Themes rotate (V6 was mobile-first with Solana Mobile and Blueshift resources). Prize pools are real USDC (V6: 1,000 USDC total, 500 / 250 / 150 / 100 Wizardio's Choice).

The rule that makes Blitz special: every submission must integrate Ephemeral Rollups. No sticker on a fork. You use the stack that MagicBlock is known for: real-time execution, zero-fee ER txs, commit back to Solana. Judging weights creativity, technical depth, and how clearly the project shows what only real-time Solana can do.

Cadence is working. Public Blitz rounds have been landing roughly 30–40 projects per weekend (v0 through later editions). That is a dense feedback loop: enough volume to learn what the community builds, small enough that MagicBlock engineers can still talk to teams in chat.

You are not dropped into a blank repo. MagicBlock ships:

  • Docs for Ephemeral Rollups, private ERs, VRF, and plugins
  • magicblock-engine-examples and starter templates (counter, dice, payments, game patterns)
  • RFPs if you want a sharp problem statement for the weekend

Solo or team, the point is the same: force a ship, force a real ER integration, get in front of the people who run the network your app depends on.

Forge: keep shipping after the weekend

Blitz is the proof. MagicBlock Forge is the next step for teams that stay on MagicBlock Mainnet and keep iterating. Rolling admission. High-touch: weekly engineering and growth sessions, async support, milestone reviews, ecosystem intros across product architecture, execution, GTM, and distribution.

This is where MagicBlock separates from "hackathon and goodbye." Forge exists so a strong weekend project becomes a product with users. Exceptional teams get a line into the Hacker House. Related accelerate surface: the Magic Incubator (apply anytime: technical advisory, marketing amplification, optional microgrants or credits, roadmap check-ins, Colosseum prep, exclusive event access). Same company philosophy: if you build on the stack, they invest attention.

Hacker House: IRL, GTM, raise

The third stage is intentional scarcity. Hacker House is for founders who are past the demo: meet the MagicBlock network in person, prepare go-to-market, and get ready for fundraising. Events surface on Luma. The homepage is explicit about the arc: Build MVP → Grow users → Raise funds. That is a full company path, not a merch drop for GitHub stars.

Champions: paid to grow the ecosystem

Parallel to builders who ship apps, MagicBlock Champions are the people who grow the scene: help builders, publish content, run initiatives. Contributions are rewarded monthly, on-chain, to your wallet. Application is referral-based through existing Champs, which keeps the bar high and the network trusted.

Champions get public, shareable badges. Mine is live here:

build.magicblock.app/badge/champion/metasal

Profile cards sit on the same identity system as builders: roles, country, proof of work, journey stages (Blitz, Forge, Hacker House). A Champion is not a spreadsheet row. They are a first-class node in the graph, with a URL you can drop in a bio or a thread. Regional coverage is visible. Recognition is portable. That is how you scale community without turning it into unpaid support labor.

Why this matters for Solana

Real-time on-chain apps (games loops, HFT-adjacent UX, multiplayer state, privacy-preserving sessions) need two things: a runtime that can actually hit game-like latency, and a culture of people who know how to use it. MagicBlock already owns the first with Ephemeral Rollups, private ERs on TEEs, VRF, and plugins. Build owns the second.

Stack for a serious builder:

Very few protocol teams productize all three on one domain. MagicBlock did. That is why the builder funnel around real-time Solana feels ahead of peers who only drop a Discord invite.

How to get started this week

  1. Create your profile on /builders (Telegram + roles + proof of work).
  2. Skim the ER quickstart and clone magicblock-engine-examples.
  3. Join the next Solana Blitz (or pull an RFP and ship offline if the calendar is between editions).
  4. If you are already helping the ecosystem, ask a Champ for a Champions referral and get paid for the work you are doing anyway.
  5. When the MVP has users, apply pressure on Forge / Incubator and aim at Hacker House.

Bottom line

MagicBlock Build is the people product the Ephemeral Rollups stack deserves: monthly forced shipping, real ER constraints, a public directory, paid Champions, and a path that ends in GTM and capital, not a participation certificate. If you are building anything that needs real-time Solana, this is the funnel to join.

Start at build.magicblock.app/builders. Champion badge example: @metasal.

Resources

Keep reading

Get new articles in your inbox

Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.

MagicBlock Builders: the path from Blitz weekend to funded team | devrels.xyz