OtterPot

Tech Stack

Rust

Nextjs

Cloudflare

Description

OtterPot turns friendly bets into on-chain challenges. A group creates a challenge in a Telegram bot, each friend stakes into a shared pot, and the group confirms the result by consensus. The smart contract pays the winner automatically. There are no wallets to install and no apps to download, because everything happens in the Telegram bot and Mini App.

Funds sit in a ChallengePool contract. While the challenge runs, idle capital is delegated to a TreasuryVault that routes it to a yield strategy through a swappable adapter. Participants get their stake back plus a fair share of the yield, even if the challenge is cancelled or refunded. The Worker's operator account can only send funds to the winner the contract calculates, so no one can redirect the pot.

Progress During Hackathon

- Built the full monorepo: smart contracts, Telegram bot/orchestrator (Cloudflare Workers), Mini App (Next.js) and a scheduled sweeper. - Implemented the ChallengePool lifecycle (create, join, resolve, refund) in Rust/Stylus, then ported and deployed it on Arc testnet. - Added persistent consensus in the Worker with Durable Objects and SQLite. Challenge resolution now goes through a single on-chain path with a full transaction lifecycle. - Implemented the TreasuryVault and a Sweeper that moves idle funds into a yield strategy (Aave). - Added yield accrual on deposit, redeem and realize_yield. This includes fair-split math, loss handling, and guards for the no-strategy and failed-read cases. A mock strategy with loss simulation backs the tests. - Wrote a design spec (SDD v8, decisions DD-01 to DD-10) and a testing strategy. Contracts are covered by cargo test and devnode integration tests.

Fundraising Status

Not currently fundraising. [Replace with your real status, for example: "Bootstrapped, no external funding. Open to grants and pre-seed conversations after the hackathon."] Two things to check before you submit: 1. Chains. The repo mentions both Arbitrum (Stylus) and Arc. Tell me which chain is your main deployment and I'll tighten the Description and Tech Stack. 2. Aave. The commit history says the Sweeper generates yield via Aave. Confirm it works on the network you deploy to, or I'll reword that as "yield strategy (Aave adapter)." I can also trim any section to a character limit if the form has one.