# Zcash Refund Helper: check a ZEC deposit stuck in the NEAR Omni bridge, and who can refund it (read-only, no keys)

**URL:** <https://forum.zcashcommunity.com/t/zcash-refund-helper-check-a-zec-deposit-stuck-in-the-near-omni-bridge-and-who-can-refund-it-read-only-no-keys/58382>\
**Category:** Zcash Apps\
**Created:** [October 20, 2026, 4:15pm UTC](https://forum.zcashcommunity.com/t/zcash-refund-helper-check-a-zec-deposit-stuck-in-the-near-omni-bridge-and-who-can-refund-it-read-only-no-keys/58382 "2026-10-20T16:15:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anirudh-712](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/anirudh-712/32/49694_2.png) [@Anirudh-712](https://forum.zcashcommunity.com/u/Anirudh-712)\
**Post date:** [October 20, 2026, 4:15pm UTC](https://forum.zcashcommunity.com/t/zcash-refund-helper-check-a-zec-deposit-stuck-in-the-near-omni-bridge-and-who-can-refund-it-read-only-no-keys/58382/1 "2026-10-20T16:15:26Z")

</div>

Hi all, I’m Anirudh from Hyderabad. New here.

Earlier this month I came across a Bitcoin deposit stuck in the NEAR Omni bridge. Someone had requested its refund on 19 Aug, and then nothing happened, for two months. The bridge does have refund steps, they’re just buried in the contract. So I wrote a small tool that digs them out.

You paste the deposit’s tx hash (ZEC or BTC) and it tells you where the coins are right now and whether a refund is possible. Since 16 Oct that comes down to one thing. If the deposit named a refund address, anyone can run the bridge’s own refund after a 2-day lock, and the coins can only go back to that address. If it didn’t, the bridge now locks the refund for 100 years, and the tool says so plainly instead of showing steps that can’t work.

It never asks for a key, seed or viewing key, and it never signs anything. It also can’t do anything about 1Click compliance holds. That’s a separate system and only NEAR can act on those.

That August deposit (0.1 BTC) went back to the address it came from on 15 Oct, following those steps. It’s on chain, the “Try a real one” link on the page opens it.

A couple of honest limits: it queries public services from your browser, so they see your IP (Tor or a VPN if you care). And some deposits need the operator to act. When that’s the case it says so, it doesn’t guess.

To be upfront: I’m independent, not part of NEAR, Omni or any Zcash org. My small company, Cryppit, also runs a NEAR Intents swap checker called Where’s My Swap.

Along the way I ended up filing a few Zcash issues: TEX in Keystone (#2313, they said next release), a TEX memo bug in Unstoppable (#7295, fixed in #7300), and unified address handling in zebra (#11803, confirmed this week) and zcash-test-vectors (#135). Zingo also merged two small fixes of mine (#1663, #1665).

Code (MIT): [GitHub - cryppit/zec-refund-helper: Keyless, read-only checker for BTC and ZEC deposits stuck in the NEAR Omni bridge. Prints the bridge's own refund steps. · GitHub](https://github.com/cryppit/zec-refund-helper)  
Try it: [Zcash Refund Helper](https://cryppit.github.io/zec-refund-helper/)

If you’ve got ZEC stuck in the bridge, give it a go and tell me where it’s wrong.

---

<div class="post-metadata">

**Author:** ![Anirudh-712](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/anirudh-712/32/49694_2.png) [@Anirudh-712](https://forum.zcashcommunity.com/u/Anirudh-712)\
**Post date:** [October 22, 2026, 2:50pm UTC](https://forum.zcashcommunity.com/t/zcash-refund-helper-check-a-zec-deposit-stuck-in-the-near-omni-bridge-and-who-can-refund-it-read-only-no-keys/58382/4 "2026-10-22T14:50:00Z")

</div>

A visual follow-up, because the first post was mostly text.

The helper is deliberately a diagnosis tool before it is a refund tool. You paste one Zcash or Bitcoin transaction hash—no wallet connection, seed phrase, viewing key or signing—and it checks the chain, the Omni indexer and the connector contract against each other.For every hash it returns one plain verdict: unconfirmed, not a deposit, crediting, credited, absorbed below the minimum, refundable, requested, ready, executed, refunded, or too old to request. It only prints paid refund commands when the deployed contract can actually complete them.

Here is a real 50 ZEC deposit funded directly from the Ironwood shielded pool. The checker identifies that there is no transparent sender, verifies the bridge deposit address and NEAR order account, and reports that the deposit was credited:

 ![clipboard](https://global.discourse-cdn.com/zcash/original/3X/e/b/eb7e068e38fdb9c6ec02f50ed82c5c58d792d5da.jpeg)

 ![clipboard](https://global.discourse-cdn.com/zcash/original/3X/4/f/4f5256a5f48c9e5e72ef86d13abfd632266433d9.jpeg)
