FWakeFi
An alarm that stakes and wakes
Demo
About
The problem it solves Every alarm app on the planet has the same fatal flaw: zero consequences for ignoring it. You set an alarm. You snooze it. You feel guilty for 5 minutes. Nothing happens. The app still gives you a badge tomorrow. There's no real cost to failing — so the brain learns to ignore it. Behavioral economics calls this the commitment problem: humans consistently intend to do things tomorrow that they resist doing when tomorrow arrives. The solution proven by decades of research is credible pre-commitment: locking in a real cost before the moment of weakness arrives. Traditional accountability apps can't do this because they're just software. They can threaten, but they can't enforce. WakeFi can. Because it uses the blockchain. What People Can Use It For ⏰ Wake-Up With Real Stakes Stake HBAR before you sleep. If you wake up and answer a crypto news quiz within 15 minutes of your alarm — your stake is safely returned. If you sleep through, snooze, or ignore it — Hedera Consensus automatically executes the burn, even if your phone is off. Proving Discipline On-Chain Every successful wake-up is a verifiable event: a ScheduleDeleteTransaction on the Hedera ledger. You get an actual on-chain record of your consistency, not just a local streak badge. Morning Crypto Briefing The quiz pulls a live crypto news article every morning (via CryptoCompare). You don't just wake up, you wake up informed. The question tests whether you actually read it, not just whether you're physically present. Use of AI tools and agents WakeFi was built using Cursor (AI-powered IDE) with Antigravity as the primary agentic assistant running inside it. It handled the full development loop autonomously reading and writing source files, running terminal commands, debugging Hedera SDK errors, executing test scripts against testnet, capturing browser screenshots to verify UI, and pushing commits to GitHub. It maintained context across the entire overnight build session without losing the thread of the architecture. Gemini 3.0 generated the alarm clock splash screen asset (alarm.png). Using all these the system design, architecture decisions, and prompt engineering was done.
How it's made
Challenges we ran into The hardest blocker was discovering that Hedera's ScheduleCreateTransaction does not auto-execute by default you must explicitly call setWaitForExpiry(true), which is buried in the SDK docs with minimal examples. Without it, the schedule just expires silently and nothing burns. We found this after debugging why scheduled transactions were creating successfully but never executing. A second critical bug: the Hedera SDK silently rejected our private key because it was ECDSA but being parsed as ED25519 the default. This produced a cryptic signing failure with no useful error message; we isolated it by running a raw Node.js reproduction script against the testnet until the signing algorithm mismatch surfaced.