Skip to main content

← Pictures · Outcome Map · Dependencies

Value Stream Map

What does a prediction lifecycle look like on EVM vs Sui — and where does time compress?

EVM Flow (Current State)

StepActionTransactionsWait TimeFailure Modes
1. ConnectInstall wallet, connect dApp030-120sExtension install, wrong network
2. ApproveApprove token spend1 tx15-60s confirmGas estimation, nonce issues
3. PredictPlace prediction + stake1 tx15-60s confirmInsufficient gas, revert
4. SettleOracle pushes result1 tx15-60s confirmOracle delay, gas spike
5. ClaimUser claims winnings1 tx15-60s confirmForgot to claim, gas cost > payout
Total4-5 txs2-5 min5 failure points, each requires gas

Sui Flow (Target State)

StepActionTransactionsWait TimeFailure Modes
1. AuthenticatezkLogin via Google/Apple0 (off-chain ZKP)3-5sOAuth provider down
2. Predict + StakeSingle sponsored PTB: create prediction + transfer stake1 PTB (sponsored)~390msSponsored tx backend down
3. Settle + PayOracle result consumed atomically: settle + calculate + payout1 PTB~390msOracle data stale, clock guard
Total1-2 PTBs<10s2 failure points, zero user gas

Compression Ratio

DimensionEVMSuiCompression
Transactions4-51-22-5x fewer
User wait time2-5 min<10s12-30x faster
Gas decisions4-5 (user pays each)0 (platform sponsors)Eliminated
Failure points5260% fewer
Wallet setupRequired (extension + seed phrase)None (zkLogin)Eliminated

The Insight

The value stream doesn't just compress — it changes shape. EVM is a sequence of independent transactions the user must shepherd. Sui is a composed pipeline the platform operates on the user's behalf. The user's job changes from "manage blockchain operations" to "pick a winner."

Questions

Does the compression hold under load — or do shared objects and consensus create new bottlenecks that don't appear in the happy path?

  • What happens to the sponsored transaction model when gas prices spike during a popular match?
  • If the oracle PTB fails, does the user even know — or does the receipt just stay "pending" forever?