Build with private data without giving up composability.
The CDR Hackathon is a focused virtual event for developers prototyping a new paradigm: one where private data becomes a programmable, composable on-chain object. Powered by Story’s Confidential Data Rails.
What is Confidential Data Rails?
Most approaches to confidential data either keep it fully off chain, losing composability, or rely on FHE that isn’t yet ready to scale. CDR takes a different path.
A decentralized set of Trusted Execution Environments, synchronized by on-chain state, secures private data and enforces dynamic access control. The result is private data that behaves like a programmable, composable on-chain object.
Each vault dynamically enforces all three.
A few starter ideas to get the gears turning.
On-chain private storage
Stash anything secret on-chain. Wallet recovery, dead-man switches, time-locked notes: your call.
Data marketplace
Atomic swaps for private data. Pay → unlock. Subscriptions and recurring access on the house.
Confidential query marketplace
Query a dataset without ever seeing it. Fraud checks, private AI inference, medical lookups.
Agent-to-agent data deals
Agents negotiate over a dataset, settle on a price, mint a license, pay, and the data unlocks: all without a human in the loop.
Autonomous objects
Self-governing on-chain agents with private brains. An ETF that won’t tell you its strategy.
Go weirder
These are vibe checks, not a menu. The most surprising builds tend to win. We dare you.
App ideas, already built on CDR.
Two live examples to poke at: pick a flow, click in, and see CDR in motion.
Scroll
Share text snippets with embedded unlockables — content gated by CDR. Readers pay to unlock a hidden line, paragraph, or asset; the access logic runs on-chain. No trusted middleman.
- Programmable access per unlockable
- On-chain content that other apps can reference
- Polished read + publish experience, not just a demo
AI Negotiate
Two AI agents discover each other, negotiate a price for a private dataset, settle on-chain, and unlock the data: no human in the loop. A2A + AP2 + CDR working together.
- Buyer and seller agents handshake over A2A
- Signed payment mandate via AP2
- License mints on-chain; the vault decrypts on settlement
Two tracks. Three prizes.
One project can win in both.
Technical Implementation
Push what’s possible with read/write conditions, on-chain logic, and dynamic permissioning.
- Advanced read/write conditions (multi-sig, time-based, multi-step)
- Smart contracts enforcing complex or conditional access
- Composable vault systems interacting with other contracts
- Trustless data exchange using CDR vaults
- New patterns for programmable or dynamic permissions
Best CDR Application
The best-executed product idea built on CDR. Strong product thinking, design, and real-world usability.
- Quality and polish of the application itself
- Real traction across Twitter, the app, and LinkedIn
- Evidence that real users actually want it — not just a demo
- End-to-end UX that someone would actually use twice
The full arc.
Subscribe to the live calendar to get every workshop, office hour, and milestone automatically. Recordings of past workshops are posted shortly after each session.
Subscribe to Google Calendar
Jacob TuckerStory · Opening + English dev workshop
Ramtin SerajCo-author of CDR · “What is CDR”
Jongwon ParkStory · Korean dev workshop
Opening CeremonyMay 2710:00 AM ET · 11:00 PM KSTJacob Tucker · Story
What is CDRMay 2710:30 AM ET · 11:30 PM KSTRamtin Seraj · Co-author of CDR
Developing with CDR: 한국어May 287:00 AM ET · 8:00 PM KSTJongwon Park · Korean session- Developing with CDR: EnglishMay 2811:00 AM ET · 12:00 AM KST (+1)Jacob Tucker · English session
Get in, build, demo something real.
Register
Save your spot. You’ll be added to the shared calendar so you never miss a session.
Sign upJoin the Discord
This is where everything happens: team formation, Q&A with the Story team, mentor support, and submissions.
Open DiscordTune into workshops
Two days of workshops led by the Story team, live on YouTube and X (May 27 → 28). Drop in for the parts you need.
Add to calendarShip + submit
Build with your team, post progress, and submit your project by June 3. Submission instructions go out in Discord.
See full schedule