Loops HouseVeil

NEAR HACKATHON
Team
1 member- UIOwner
Uiriamuzu
Overview
Problem: a .near name is a public ledger. Anyone who knows your name can see every payment you receive, who sent it and your balance, so sharing your name to get paid shares your financial history.
What we built: Veil gives NEAR names private receiving. The owner signs one NEP-413 message; Veil derives a spend key and a view key in the browser and registers only the public keys for the name. A sender looks up the name and pays a fresh one-time account derived from those keys, through a router contract that records an announcement. The owner's inbox scans the announcements with the view key (a one-byte view tag skips almost all others), finds the payment and spends it with the derived key. A read-only auditor key can find payments but never spend them.
How NEAR fits: each one-time account is an ordinary NEAR implicit account whose ID is an Ed25519 public key, so private receiving of NEAR needs no new account type, contract wallet or relayer. The registry and router contracts are live on testnet; the SDK, web app, NEP draft with test vectors and CI are in the repo. Tested with Meteor Wallet on testnet (evidence in results/). Try it without a wallet: the README's 30-second auditor path shows three private payments that the name's public history does not.
Limits: testnet prototype; amounts, timing and senders stay public, and spending links a payment to its destination.
Live Link: https://veil-eta-khaki.vercel.app