Loops HouseShield · Mesh · Coach

NEAR HACKATHON
Links
Team
1 member- OLOwner
Oluwabori
Overview
Shield · Mesh · Coach — post-signature destination verification that catches what pre-sign policy misses. Named against near/intents#384 (open, filed 2026-10-18): confidential swaps return status: SUCCESS while real ETH lands in a solver-routed sink account.
On-chain receipts cited in the issue: NEAR txs 3djtQ3pU...jCUVD and jNeJZQ4...A193j. Quoted recipients b45e...605c6 and 201178...9af97; actual 51e8f94d...de7cbe. The sink holds ~0.0673 ETH of nep141:hood.omft.near and growing. API said success. Money went to the wrong account.
OutLayer (listed partner) runs the pre-signature policy — caps, whitelist, kill switch, TEE attestation on NEAR MPC. All fire before the signature. None would catch #384: the signature is valid; the solver's post-sign routing is where it goes wrong.
Shield reads the on-chain receiver_id back from status.swapDetails.nearTxHashes, compares to status.quoteResponse.quoteRequest.recipient, halts the agent on divergence. Fires after OutLayer approves, not instead of it.
Three primitives, composed:
- Shield: FHE spend mandate + kill switch + new post-sign verifier
- Mesh: N-party atomic escrow (17 contracts live on Arbitrum Sepolia + Robinhood Chain testnet; 8 settlement cycles; 36 on-chain txs)
- Coach: agent orchestration + two new NEAR tools (
callNearIntents,verifyIntentDestination)
Flow: Coach → NEAR Intents (cross-chain execution) → Mesh N-party split → Shield verifies each leg → NEAR Intents on-chain transfer. Chain Signatures sign cross-chain; Function Call Keys scope Shield's emergencyFreeze without root key; Sub-Accounts partition per-agent spend; NEP-141 is the asset class we gate.
Try it: clone the repo, run make replay-384. The two #384 tx hashes replay against Shield; the verifier returns MISMATCH(quoted=b45e..., actual=51e8f94d...); the agent halts before the second signature.
Built at NEAR HACKATHON. Live Mesh settlements at kajota-mesh.vercel.app.