Loops HouseWaybill

NEAR HACKATHON
Team
1 member- TEOwner
Team Saber
Overview
Waybill checks a NEAR Intents deposit address before you send, then reads every leg of the swap on its own chain after, and writes a hashed case file when a documented promise breaks.
The problem: when a 1Click swap stalls, the user gets one status string and a support queue. Real reports in near/intents show what goes wrong: ETH sent on Base to an address quoted for Ethereum (#382), a SUCCESS that ends at the private chain (#384), a swap PROCESSING for weeks with no intent (#399).
How it works: paste a deposit address. Before sending, Waybill reads the quote 1Click signed and says exactly what to send, on which chain, before when, and stops you if the address was used, the quote expired, or too little time is left to confirm. After sending, it asks 1Click, the Explorer API and the chains separately and draws four legs: quote (signature checked), deposit, settlement (intents.near events read from NEAR RPC) and payout. Deposits and payouts are read on eight EVM chains, Bitcoin, Solana, Tron and TON; a payout is "verified" only when a final transaction paid the quoted token to the quoted recipient.
The standout number: a day of Explorer API history, 19,937 real swaps: 98.51% completed, but NEAR to NEAR only 63.9%, mostly NO_LIQUIDITY refunds. Every rate has a 95% interval and every stuck swap opens in the tracker.
How NEAR fits: NEAR Intents is the settlement layer Waybill audits. It reads intents.near on NEAR mainnet, 1Click and the Explorer API, and treats the Confidential Intents treasury as private by design.
Live: https://waybill-gules.vercel.app. Read-only, no keys, no custody. 36 tests replay recorded mainnet responses. Honest gaps: about half of genuine live quotes fail the official SDK's signature check (shown as a note, cause unknown), TON jetton payouts and refunds are reported, not yet read on-chain.