Loops HouseUnpair

NEAR HACKATHON
Team
1 member- MOOwner
Mohammad Zakeri rad
Overview
Problem: a cross chain swap links the sender's old wallet to their new one in public. The deposit and the payout sit on public chains, and amount and time match them. Confidential modes hide the swap record, but both ends stay on chain.
What we built: Unpair breaks that link. NEAR Intents, through the 1Click API, does two separate swaps. The first swaps the sent asset into ZEC and pays a fresh Orchard address in Zcash's shielded pool. The second spends that note and swaps it into the asset the user wants, at a new address on the chain they pick. No transaction connects the two ends.
How NEAR fits in: NEAR Intents gives one API that swaps assets on many chains into ZEC and back out. Both swaps settle through it, and the user sees a live quote of both, with every fee, before anything is created.
Engineering: we built the Zcash wallet that holds the ZEC between the swaps. It is a Rust crate on Zcash's libraries, compiled to WebAssembly, and it runs in the browser tab: it makes the Orchard address, syncs the chain and builds the proof that spends the note, so the key stays on the user's device. The same crate runs natively on our server for users who prefer a server held swap. For the second swap the page quotes 1Click itself, screens the address against a hashed list locally and checks the quote before it pays, so our API never gets the destination address.
Modes: fast mode finishes in about 20 minutes. Quiet mode rounds the amount and waits a random time, up to 12 hours, to resist amount and timing matching.
Limits we state: NEAR Intents sees each swap, and fast mode can still be matched by amount and time. The README lists them and has checks a judge can run with no funds or keys.
Live at unpair.xyz. Code: github.com/unpairxyz/unpair