Loops HouseWhere's My ZEC

NEAR HACKATHON
Links
Team
1 member- ANOwner
Anirudh Tumuluru
Overview
Problem: when ZEC goes missing (a swap that went quiet, a deposit into a bridge, a withdrawal to an address the wallet can't pay, or a restored wallet that shows zero), people rarely know where the coins are or whose move it is. The answers are spread across explorers, THORChain, the NEAR Omni bridge and forum threads that volunteers answer by hand.
Product: Where's My ZEC (https://cryppit.github.io/wheres-my-zec/) is a keyless, read-only rescue desk. Paste a Zcash transaction ID or address and it shows where the ZEC is (Proven from the chain, or Reported by THORChain or the bridge), who acts next (you, a service, or nobody) and a ready message with only public facts. For an address it says which of 39 exchanges and wallets can pay it, from a dated table with a source for every row. "My wallet shows zero" walks through 14 known causes, each dated and sourced. It never asks for a seed or key, and refuses one if pasted.
How NEAR fits: (1) For ZEC sent into the NEAR Omni bridge, it reads the bridge's Zcash light client on NEAR (zcash-client.bridge.near, public view calls) to tell the depositor how many days are left to request a refund themselves if the bridge never credited the deposit, and links to the Refund Helper for the status and refund steps. (2) A NEAR contract, Cryppit Pin v2 (near-sdk, MIT, locked account wmz-pin.cryppit.testnet), pins one fingerprint of the published tables per closed UTC day. The page checks the tables it loaded against the latest pin, so nobody, including us, can quietly rewrite what the tables said. Swaps through NEAR Intents are handed to our other, independent entry, Intent Sentinel (rule Q-015). Baseline code ported from our earlier MIT projects is listed in the README.