Loops HouseNearling

NEAR HACKATHON
Links
Team
1 member- OLOwner
Oleh
Overview
Problem: a virtual pet can't hold a real conversation, and an AI companion can be changed or wiped by whoever runs it, while you can't see what its replies cost or check where they came from.
Built: Nearling, an AI Tamagotchi in the browser. Each pet is an NFT (NEP-171) with its own food, a balance the contract holds for it. Every reply is a real AI call paid from that food at its actual price, a fraction of a cent. With no food the pet sleeps until someone feeds it; a friend can do it from a shared link with Google sign-in, no wallet.
Daily loop: talk to your pet, keep it fed or ask a friend, answer the daily riddle and read its diary to keep a streak that earns outfits. Activity grows the pet from Baby to Teen to Grown-up.
Pets also earn and spend food themselves: they answer other pets for a fee, hire pets they know on their own when set to Auto, run web errands that return sources, and debate in four paid replies. A gift hands the pet over with its food, outfits and memory.
Check without signing in: nearling.xyz/pet/2 > "Check it's really Max" shows the sealed character and paid-reply receipts. nearling.xyz/debate#c58d4c6814e3c88a828921238b7d7ea9 is a finished debate; each reply has "Check this line".
NEAR: the contract stores the character at birth (its hash is in the pet_born event), holds the food, and records every paid reply, hire and debate reply as an on-chain event (NEP-297) with price, model, request and response hashes and the model's signature from NEAR AI Cloud's TEE (secure hardware). The verification page checks these through NEAR RPC.
Status: live on NEAR mainnet at main.nearling.xyz: a pet was born, paid for a reply and was fed with USDC sent from Solana via NEAR Intents 1-Click. The sample pets above run on testnet at nearling.xyz. README > NEAR features links a transaction for each claim.
Built solo from Oct 29 (after the Oct 19 announcement) with AI coding agents (Claude Code, Codex); reused code is listed in the README.