Loops HouseMutuals

NEAR HACKATHON
Links
Team
1 member- CHOwner
Chitransh Nishad
Overview
Problem: A vouch stored only in an application database disappears with that database. The person who was vouched for cannot carry it, and someone else cannot check it without an account in that database.
What we built: Mutuals records a vouch as a soulbound NEP-171 token on NEAR testnet. The contract is mvouch-c-90ac932b.testnet. The recorded holder is mvouch-b-90ac932b.testnet, which holds token #1. The Builders circle on the static page opens from that on-chain vouch count. The same contract can also open the circle from a NEAR balance when the selected rule is "vouches or balance". The page reads the NEAR balance of the Sputnik DAO mb90ac932b.sputnikv2.testnet (version 2.3.1; on 2026-11-14 the liquid figure was 0.5969 NEAR). It does not spend that balance. The vouch contract does not call the DAO.
How NEAR fits: A testnet contract mints a non-transferable NEP-171 token when someone vouches. Token #1 was minted in C8fvmVnA2PGC1ribdSgeKfAFDW8JGwcX9HoRguHovcY8 by mvouch-a-90ac932b.testnet. A later nft_transfer (56LSZgWiAtUWsKLRAVtVgTkhW5VR2LobAaDCTRktu3FJ) failed, and the token is still held by mvouch-b-90ac932b.testnet. The note stored on the token is "Shipped the wallet onboarding. Sharp eye." Circle access is checked from the on-chain vouch count and, optionally, a NEAR balance the caller supplies.
Results and limits: Testnet only. The live site shows the recorded mint and circle check with no wallet. A new mint needs a funded testnet wallet; Connect NEAR wallet was not completed in the 2026-11-14 check (MyNearWallet's testnet login refused new app connections; Meteor's web login was not reached in headless Chrome). The circle decision in the static page is made in the browser. circle_access does not read another account's balance itself. One vouch per (voucher, recipient) pair; the holder can burn the token; nobody can transfer it.
Try it: https://mutuals-near.pages.dev