Forgetting
is a bug.
Build on Sibyl Memory, the dynamic data layer that remembers. Compete for $10,000 and two entries into Base Support Programs on one leaderboard.
#2 on LongMemEval · 95.6% ↗Registration opens Aug 16 · closes Aug 31, 23:59 UTC
Partners
One challenge. Two partner stacks.
Build with persistent Sibyl memory, then use Base and Virtuals where they make your agent stronger. Every verified partner stack increases your Builder Score.
Want to partner? Get in touch ↗
One challenge. One leaderboard.
Build an agent whose persistent memory changes what it knows, decides, or does across sessions.
Eligibility gate
Memory must be load-bearing.
Your agent must recall and use persisted context in a fresh session. Thin wrappers, decorative integrations, and package imports without real execution are not eligible.
Load-bearing. In a fresh session, the agent recalls a customer's past dispute and changes the offer it makes because of it.
Wrapper. The agent writes every message to a memory API but never reads it back to change what it does.
What judges need to see
- 01 · Persist context that matters to the agent.
- 02 · Recall it in a genuinely fresh session.
- 03 · Use it to change a decision, action, or result.
#2 and 95.6% are Sibyl's published LongMemEval results. The 350/350 retrieval and 500-company figures are an independent third-party benchmark run at agent-bench.xyz.
One score · one leaderboard
Builder Score = Judge Score × Stack Multiplier
Two stages. First a pass/fail gate: Sibyl Memory must be load-bearing. Then judges score a 100-point rubric, a genuine product-market-fit (PMF) bonus adds up to 10, and verified partner stacks lift the total, up to x1.25.
100-pt rubric + 10 PMF bonus = 110 max, before multiplier
- Memory is load-bearing 40
- Innovation & originality 25
- Technical execution 20
- Pitch & presentation 15
- PMF bonus +10
| Verified partner stacks | Multiplier |
|---|---|
| 0 | x1.00 |
| 1 | x1.15 |
| 2 | x1.25 (cap) |
A stack counts only when judges confirm it is doing real work in the submitted build. Decorative integrations and unused package imports do not count.
Worked example: a build scores 82/110 (rubric + PMF bonus), the team ships two verified partner stacks, so x1.25. Builder Score: 102.5. Sibyl Memory is mandatory and never counts as a bonus stack.
Sibyl Memory is required and does not count as a bonus stack.
0 verified stacks → x1.00
82Builder Score on the 82-point example
Prizes
Winners get backed.
$10,000 in USDC across the top five. First place also earns a Network School residency, and second place earns one entry into a Base Support Program. Real backing on top of the cash.
sibyl@hackathon:~$ cat prizes.txt
| 01 | $4,000 | USDC on Base + Network School residency |
| 02 | $2,500 | USDC on Base + one entry into a Base Support Program |
| 03 | $1,500 | USDC on Base |
| 04 | $1,000 | USDC on Base |
| 05 | $1,000 | USDC on Base |
sibyl@hackathon:~$
How it runs
- Aug 16 to 31
Registration
Register your team before the build window opens.
- Sep 1 to 10
Build window
Ten days to build and submit an agent with persistent memory.
- Sep 5 to 7
Partner workshops
Live sessions with Base and Virtuals Protocol.
- Sep 11 to 12
Judging
Projects are reviewed and scored on one leaderboard.
- Sep 13 to 15
Winners
The top five are announced, with winner spotlights on X.
Questions
Before you register
Can I compete solo?
Yes. Teams are 1 to 5 people. Register on your own or bring a crew.
What does it cost?
Nothing. Entry is free, and prizes pay in USDC on Base.
Do I have to build on Base or Virtuals?
No. Sibyl Memory is the only required stack. Base and Virtuals are optional and add a scoring multiplier when a judge can see them doing real work in your demo.
Do I need crypto or web3 experience?
No. If you can build an agent, you can enter. Sibyl Memory is a file-based layer you call like any library, and Base and Virtuals are optional. Prizes pay in USDC on Base, and if you have never held crypto we help winners set up a wallet at payout.
What is Sibyl Memory, and where do I learn it?
A file-based memory layer for agents: persistent recall across sessions, no vector database. Explore it before you register ↗
What counts as memory being load-bearing?
Delete the memory layer. If your project still does what it claims, it is a wrapper and does not qualify. If the core function breaks, memory is load-bearing.
Who owns what I build?
You keep all your IP. By submitting you grant Sibyl Labs and the partners a non-exclusive license to feature your work in event coverage, always with attribution.
Who can enter?
Anyone 18 or older, outside sanctioned jurisdictions. Sibyl Labs staff and reference builds are showcase-only and cannot win prizes.
How do I get help or find teammates?
Join the Sibyl Labs Discord: find a team, ask questions, and follow build updates through the window.
What do I submit?
A public repo (MIT or Apache-2.0), a 2 to 5 minute demo with a fresh-session recall moment, a README, and two build-in-public posts. See the full checklist →
Ready to build?
Registration opens Aug 16. Grab your team and claim your spot on the leaderboard.
Register your team →