Loops HouseSigned by NEAR?

NEAR HACKATHON
Links
Team
1 member- BHOwner
Bhargav Chowdary
Overview
Problem: NEAR's cross-chain story is often summed up as a "28-chain moat". An investor needs to know how much of that flow depends on NEAR's own technology, Chain Signatures (the MPC signer, v1.signer), and how much would run the same without it.
What I built: "Signed by NEAR?", an evidence-first investment thesis with a live dashboard. Five tests were fixed, and their hash was in a Bitcoin block, before any counted result was read. Each test names a result that would have gone against the reading. The data is a seeded sample of NEAR Intents' bridge flow over 90 days, read from public sources that need no key.
What it found: on Bitcoin the flow runs on Omni, the NEAR bridge whose withdrawals the signer signs: [99.7%, 100.0%] of the bitcoin that moved through NEAR Intents. On the other seven chains the sample can read, that is not shown; on Arbitrum, Base, Ethereum, Tron and XRP every sampled dollar moved on a custodial bridge that does not use the signer. The signer took 14,046 calls a day in October, but 34.0% came from one app that ends in its present form on Dec 30, 2026. It charges no fee; NEAR paid its operators 0.1065 NEAR per request in September. The reading: narrow today, not yet shown to be a broad moat. No test went against it, and the tests are one-sided: "not met" means not shown, never disproved.
How NEAR fits: the subject is NEAR's own stack (Chain Signatures, the Omni bridge, NEAR Intents), measured on chain. Three dated reads that would change the reading are written down with their thresholds and timestamped before publication.
Reproduce: sh check.sh rebuilds every number, table and chart offline with the Python standard library: no key, no install, no network. A second implementation, written apart from the analysis code, recomputes the numbers.