Loops Housebonuz ID on NEAR

NEAR HACKATHON
Links
Team
1 member- MAOwner
Matthias Mende
Overview
bonuz is a live consumer app (iOS and Android) where people get rewarded for showing up at real places and events. Every user has a bonuz ID: one public profile at bonuz.id/ with their verified socials and wallets.
Problem: a NEAR account is a 64-character string. Nobody, human or AI agent, can tell who is behind it. And most app users hold no NEAR, so identity tools that cost gas leave them out.
What we built: in the bonuz app's NEAR wallet, one tap ("Show on my bonuz ID") signs one NEP-413 message. No transaction, no gas, the account need not even exist on chain. bonuz verifies it, marks the account verified on the bonuz ID, pays 1,000 bonuz points once, and records the pair in our own registry contract on NEAR mainnet (id.bonuz-id.near). The contract re-checks the signature itself, so bonuz cannot attach a NEAR account to anyone without that account's key. bonuz pays the storage; users pay nothing.
How NEAR fits: implicit accounts make a wallet free and instant, NEP-413 gives a gasless proof of ownership, and a function-call key with a capped allowance lets our backend write links but never move money. Anyone can ask NEAR "which bonuz ID is this account?", and AI agents ask the same through the bonuz MCP server.
Live today: registry 2.1.0 on NEAR mainnet and the bonuz backend in production. The app side is merged and ships with the next app release; the testnet registry runs the full flow for judges now.
Next: Stage 2: users name their NEAR account in the app (alice.near instead of 64 hex characters), the name shows on their bonuz ID, and sending crypto to a bonuz user's handle lands in their verified NEAR account, the way name.bonuz.id works today. Stage 3: more AI: agents, which already get bonuz IDs, get a verified NEAR account of their own, so any app can check who an agent is before it trusts or pays it.
The bonuz app and its Base identity contract existed before the hackathon and are disclosed as baseline in the README.