Loops HouseWayfarer

NEAR HACKATHON
Links
Team
1 member- JOOwner
JOSEPH ALEONOMOH
Overview
The problem. Crypto is easy to hold and hard to spend. To pay for a coffee you sell on an exchange, wait, withdraw to a bank, and then pay.
What Wayfarer does. The buyer keeps NEAR in their own on-chain vault. At a shop, the merchant's phone shows a price. The buyer's phone shows the same price in their local currency and in NEAR, and the buyer approves with a fingerprint. The phone signs a cheque with an ML-DSA-65 (FIPS 204) key. That key is registered in the vault with a mandate: a cap per payment, a daily cap, an end date and an optional list of allowed payees. It cannot withdraw or change the policy, so a stolen phone cannot empty the vault.
Settlement. The merchant checks the cheque offline and shows "accepted, pending settlement". Then pay_with_cheque runs on the vault contract, which verifies the ML-DSA signature on-chain with NEAR's ml_dsa_verify host function, enforces the mandate, and emits NEP-297 events.
Merchant order agent. The shopkeeper types or dictates an order. A model on NEAR AI Cloud picks items and counts from the shop's own menu. The total is computed in code from the menu, never by the model. Unknown items block the charge, and the merchant confirms first. The agent cannot move money.
Receipts. Every sale produces a JSON receipt. verifier/index.html re-checks 20 things in the browser (offline checks and on-chain events). It passed 20 of 20 against a real testnet receipt.
Cash-out. The merchant can cash out toward a bank with one button. Only sandbox legs exist; no bank was paid and no swap was executed.