Loops HouseRounds

NEAR HACKATHON
Team
1 member- OLOwner
Olayemi Samuel
Overview
The problem. A company's cap table (who owns how many shares) is private, but a group that decides things with a DAO still needs its vote to mean something exact. Today a board's "yes" can't be tied to the numbers it approved, and the table lives in a spreadsheet nobody else can check.
What I built: Rounds is a confidential cap table that a Sputnik DAO approves to the exact number. Every change (who pays how much, who gets how many shares, who is paid what) is an exact plan with a SHA-256 fingerprint. The money waits in escrow, the DAO votes on the fingerprint, and the contract only runs a plan that hashes to what was approved. In confidential mode, a zero-knowledge proof (Groth16) stands in for the numbers, so who holds what never appears on chain. The board checks its private copy before approving, and a holder claims a payout with a proof that doesn't say which row is theirs, paid to a brand-new account through a relayer. Payout amounts stay public. There is also a transparent mode with priced rounds, SAFEs, vesting, token sales and pro-rata payouts. How NEAR fits in. The board is an unmodified Sputnik DAO v2. The Rust contract verifies the zero-knowledge proofs on chain with NEAR's alt_bn128 functions and holds the escrow. Payments use NEP-141 tokens. It runs on NEAR testnet, and anyone can re-check it with make verify-onchain.