The full rules.

Judging runs in order and the stages do not blend. First a pass/fail gate. Then a 100-point rubric, a PMF bonus, and a partner multiplier.

Final score = (rubric + PMF bonus) × multiplier. The leaderboard shows all three.

Every project is reviewed by a panel of judges. The gate is decided by a majority of that panel, and a tie fails the gate. Rubric and PMF scores are the mean of the judges who passed you through the gate.

• Cold-start recall in the demo video. A fresh session recalls state written earlier, as one continuous unedited segment with an on-screen timestamp or commit hash.
• Critical-path calls in the repo. The README points to where memory is written and read; a judge can find them in under two minutes.
• The deletion test. Remove the memory calls and the core function breaks.

Load-bearing is about dependence, not volume. One entity your whole build hinges on passes. Ten thousand rows you never read does not.

Only projects that pass the gate are scored. Each criterion is scored to its max; the sum is the rubric score.

• Memory is load-bearing · 40%

  How central and sophisticated the memory use is. Recall is competitive; coordination and dynamic-storage patterns top the band.

• Innovation & originality · 25%

  A novel idea and real usefulness. Clever but useless caps out low.

• Technical execution · 20%

  Clean and robust, no smoke and mirrors. Survives a second run and a curious judge.

• Pitch & presentation · 15%

  A tight 2 to 5 minute story where the load-bearing moment is unmistakable.

A build that solves a real pain point for a real audience earns bonus points on top of the rubric. Genuine means evidenced: a named audience with a validated pain point, a waitlist or design partners, real usage, or pilots. A market-size slide or a claim that users will love it earns nothing.

The default is 0, and that is fine for most prototypes. Any nonzero bonus needs a publicly verifiable artifact a judge can check in five minutes. Fabricated evidence is a disqualification, including after payout.

Verified partner stacks lift your score on a diminishing schedule: +15% for the first, +10% for the second, capped at x1.25. The second stack adds less on purpose, so a two-partner build cannot swamp the rubric or the PMF bonus. Sibyl Memory is mandatory, so it is never a multiplier. A stack counts only when a judge can see it doing real work in the demo, serving the product’s actual function. A claimed stack that is not exercised loses that bonus.

• Base. Deployment is the eligibility floor. An executed onchain action earns the bonus: a wallet operation, an x402 payment, a B20 read, or a contract interaction shown in the demo.
• Virtuals. An ACP job, a registered or transacting agent, or another Virtuals-native integration exercised in the demo.

$10,000 in USDC across the top five.

1. 01$4,000USDC on Base + Network School residency
2. 02$2,500USDC on Base + one entry into a Base Support Program
3. 03$1,500USDC on Base
4. 04$1,000USDC on Base
5. 05$1,000USDC on Base

You keep all IP. By submitting, you grant Sibyl Labs and the named partners a non-exclusive, royalty-free license to feature your video, repo, screenshots, and description in event coverage, always with attribution.

Sibyl Labs reference builds and staff are showcase-only and prize-ineligible. Entrants must be 18+, excluding sanctioned jurisdictions. Prizes pay in USDC on Base; to receive one, winners provide payout details, and top-five teams join a short case-study interview. The Network School residency is non-transferable; if a winner cannot take it, it passes to the next rank.