1Principles
ValuesBeliefsControls
One tap, one transaction, settled.
- EVM prediction: install wallet, approve tokens, place bet, wait for oracle, claim winnings — 4-5 transactions
- Sui PTB: predict + stake + settle + payout in one atomic operation
- The value stream compresses 2-5 minutes to under 10 seconds
| Problem | Question | Decision |
|---|---|---|
| Multi-tx settlement creates 5 failure points | Can atomic composition eliminate them? | PTB composes all steps — one tx or nothing |
The Vision
A split screen: left shows 5 blockchain transaction confirmations stacking up with gas fee popups. Right shows a single tap on a rugby match card and a green checkmark.
2Performance
ValuesBeliefsControls
No wallet, no gas, no friction.
- zkLogin: OAuth credentials → Sui address via zero-knowledge proof
- Sponsored transactions: platform pays gas, user never holds SUI
- First prediction in under 60 seconds from first visit
| Problem | Question | Decision |
|---|---|---|
| Wallet setup kills conversion | Can onboarding feel like Web2? | zkLogin + sponsored tx = zero crypto prerequisite |
The Vision
A phone showing Google sign-in flowing directly into a rugby prediction confirmation. No wallet popup, no gas estimation, no extension install banner.
3Platform
ValuesBeliefsControls
Hot potato prevents the bugs.
- Move's type system makes double-settlement impossible at compile time
OracleResulthas nostore,copy, ordrop— must be consumed atomically- Clock guard prevents early settlement
- The compiler catches what auditors miss on EVM
| Problem | Question | Decision |
|---|---|---|
| Oracle bugs cause fund loss | Can the language prevent the bug? | Hot potato + linear types = compiler-enforced safety |
The Vision
A diagram showing an OracleResult object with no abilities — it must be consumed in the same transaction that created it. No way to store, copy, or reuse it.
4Protocols
ValuesBeliefsControls
Contracts, oracle, frontend, dogfood.
- Sprint 1: Core contracts + zkLogin + sponsored tx
- Sprint 2: Oracle + settlement + receipts
- Sprint 3: Frontend polish + history + onboarding
- Sprint 4: Admin tools + leaderboard + 50 real predictions
| Problem | Question | Decision |
|---|---|---|
| Settlement stack unproven | What's the fastest path to proof? | 4-sprint build → testnet dogfood with rugby community |
The Vision
A 4-track Gantt chart showing parallel workstreams converging at 'First Settlement' milestone. Move contracts on top, oracle integration second, frontend third, dogfood at bottom.
5Players
ValuesBeliefsControls
Rugby fans who back convictions.
- First users: rugby community who already predict informally
- Zero-friction entry: no crypto knowledge required, no money at risk on testnet
- Dynamic NFT receipts: proof of conviction that evolves with results
- Kill signal: zero predictions after 30 days = thesis wrong
| Problem | Question | Decision |
|---|---|---|
| Crypto products repel normies | Can sports be the trojan horse? | Rugby fans + gasless UX + testnet = zero-risk dogfood |
The Vision
A group watching rugby on a big screen, phones out, each showing a prediction card with their pick. One phone shows a 'Won' receipt NFT glowing green.
1 / 5