Loops HouseRelevo

NEAR HACKATHON
Links
Team
1 member- EDOwner
Edouard Pogu
Overview
THE PROBLEM Payouts abroad fail quietly. DAOs, grant programs and payroll platforms send money to bank accounts abroad every day. One mistyped account pays the wrong person, transfers bounce, and "I never got paid" disputes end in screenshots. Nobody can prove what was checked before a payout, or who was actually paid after.
WHAT WE BUILT Relevo Payout Guard: check every payout before it leaves, prove every one after.
Check before: /check tests every row in the browser (CLABE check digits, unknown banks, duplicate accounts, unusual amounts, accounts changed since last run) and anchors a signed check report. Prove after: one signed receipt per payroll (ed25519 plus post-quantum ML-DSA-65). Each worker gets a private proof link, in English or Spanish, that shows their payment was in the batch and nobody else's. Anyone can verify in the browser, and one edited number breaks the signature. Escrow for DAO payouts: one vote locks USDC, bonded payout firms deliver, and a late firm is rerouted while its bond pays a penalty. Two Rust contracts, a TypeScript verifier, a Next.js app and 767 tests. Live at relevo-amber.vercel.app. HOW NEAR FITS IN NEAR is the shared record that payer, worker and auditor all trust:
A registry contract anchors check reports and receipt hashes, and holds each issuer's public keys. Issuing costs about 0.025 NEAR. Sputnik DAO casts the vote that funds a batch, and council members attest receipts with their NEAR accounts. A NEAR escrow contract holds the funds; only proofs release them. Chain Signatures: the issuer's NEAR account signs an Ethereum Sepolia transaction that mirrors the receipt hash. NEAR Intents: /fund brings USDC from Base or Arbitrum into NEAR via 1Click on mainnet, and the demo shows a real 1.60 USDC mainnet transfer from NEAR Intents to elivo.near.