Loops Housesake

NEAR HACKATHON
Team
1 member- CAOwner
Candra
Overview
Problem: an app, game or DAO that wants its own dollar token has two bad options: run bank-like custody itself, or issue a token nobody can verify. Either way the reserve sits idle, and holders cannot tell what is backed, what left the chain, and what is only an estimate.
What I built: sake, an issuer dashboard plus two Rust NEAR contracts. A factory deploys one NEP-141 token-and-reserve contract per issuer. Anyone deposits USDC and gets the token 1:1 (capped). The issuer can allocate a capped slice (max 50% of the reserve, one allocation at a time) through NEAR Intents (1Click quote, intents.near deposit) toward one Base strategy, and holders can redeem from idle liquidity. Every number in the UI carries its source and timestamp and a label: Realized, Estimated, Pending, Settled, Strategy Deposited, Simulated. No peg or APY is promised.
How NEAR fits: the factory, the per-issuer vault (NEP-141 plus reserve invariants, cross-contract ft_transfer_call and callbacks), wallet signing through near-connect, and NEAR Intents as the cross-chain route out of idle USDC.
What is real: contracts deployed on NEAR testnet and driven end to end from the UI with a real wallet (create issuer, deposit and mint, allocate, pause, redeem), 57 sandbox contract tests, 319 unit tests. What is simulated and labelled: Intents has no testnet, so the Intents and Base legs are simulated on testnet; the funded mainnet run was not done. The operator that attests settlement is a trusted role, written down in the README.
Try it: watch docs/media/video/sake-demo.mp4 (2 min), or pnpm install && pnpm dev, click Launch app, Create, Deposit 50, Allocate 25, Redeem. On-chain proof: contracts/DEPLOYED.md. Tracks: Unstoppable DeFi, Real-World Money.