Loops HouseTerra matcher

NEAR HACKATHON
Links
Team
1 member- ANOwner
Andreas Grobe
Overview
Terra matcher is a non-custodial order-matching layer for a NEAR Intents exchange.
Problem: an order book needs a matcher, and a matcher that holds user funds, or must be trusted on its word, is the custodian NEAR Intents is meant to remove.
What it does: limit orders are paired off-chain by a deterministic matcher that never holds funds (price-time priority at the maker's price, self-trade prevention, post-only and IOC orders). Every fill becomes a pair of unsigned token_diff intents that nets to zero for each token. Each party signs only its own half; the NEAR Intents verifier settles it. 22 public conformance vectors let any other matching engine prove it behaves the same; the browser demo runs them in the tab.
Proven on NEAR mainnet: two fills settled through intents.near, each in a single execute_intents call, one in each direction. 7 Nov 2026: 1 NEAR for 3.68 USDC, tx BSCk4kvxsxvDBEZyhfMrGAjh6WBTL5SUwN5a9dTeawDe. 8 Nov 2026: 0.9 NEAR for 3.33 USDC, tx AForJs3YZG491cECZCcekMtNqkA3rdyx8Z8pBPYG5WBj. Both final and successful; NEP-413 signatures, verifier fee (1 pip) handled, gas about 0.0009 NEAR each. python3 scripts/check-mainnet-tx.py reads both from a public RPC node and checks them (9 checks each, no keys). A live check against the 1Click API (dry quotes, no funds) compares each fill with the market.
Second path: an escrow contract on NEAR testnet holds NEP-141 deposits, verifies ed25519-signed limit orders and applies fills when anyone calls settle. Three end-to-end testnet runs; the code on chain matches the repository by code hash.
Try it: https://archtum66-dev.github.io/terra-matcher/ (offline demo) or cargo test --all (68 tests).
Status, stated plainly: the mainnet settlements are two fills between the same two throwaway accounts of the author at the prices of the example orders, not a running exchange. The escrow is testnet only and not audited.