Incident Report: 5 BTC Stuck in a NEAR Intents Swap for Three Days

We are publishing this because we think users deserve to know when a route we integrate fails, and because private channels have not produced a resolution. It is written as an incident report rather than an accusation: we are stating what we observed, what the documentation says should have happened, and what we still do not know.

The facts

• What: a NEAR Intents (1Click) cross-chain swap of approximately 5 BTC — roughly $320,000 at the time of deposit.
• When: deposited August 11, 2026.
• Deposit address: bc1qh24lnnls8fpp90vttch8zwdkeetvvkdfnt3rry
• Current state: the 1Click status endpoint reports PROCESSING. Per 1Click's own documentation, that status means the deposit was detected and passed to solvers for execution — so this is not a deposit-detection problem.
• Outcome so far: no destination-chain transfer recorded, no refund issued, and the original quote deadline has passed.
• Support: requests for status through official channels have not produced a substantive response at the time of writing.

What the documentation says should happen

1Click's documentation is unambiguous about the two possible endings: a swap either succeeds, with tokens delivered to the specified address, or it fails, with funds automatically refunded to the refund address provided at quote time. The product description lists automatic retries and refund handling as built-in features. A swap that sits in PROCESSING for three days past its deadline — delivering neither outcome — is not a state the documented design accounts for.

What we do not know

We think it matters to say this plainly rather than assume the worst.

• We do not allege theft or misappropriation. Nothing we have observed supports that, and we are not claiming it. A solver failure, an internal error, a stuck settlement leg, or a manual review are all consistent with what we can see.
• We cannot see the internal state. A status string is not a diagnosis. Only NEAR Intents can say what actually happened to this intent.
• Delays are not always failures. Cross-chain settlement can legitimately take time under unusual conditions. Three days past deadline with no refund is what moves this from "slow" to "unresolved."

What we are asking for

• Resolution: either completion of the swap or the refund the documentation describes, to the refund address supplied with the original quote, less any documented network fees.
• An explanation: a technical account of why this intent neither settled nor refunded. Not for its own sake — anyone integrating 1Click needs to know whether this is a one-off or a class of failure.
• A support path for stuck swaps. Whatever the cause here, an integration handling user funds needs a channel where a stalled intent gets a human answer within days, not silence.

What this means for TokensFund users

Practical notes, since some of you are mid-swap right now:

• Other routes are unaffected. THORChain, Chainflip, Changee and CCE.Cash are quoting and settling normally. If you are swapping today and want to avoid this route entirely, pick another provider from the comparison — that choice is the reason we show every route rather than a single one.
• Always set a refund address, even where a route treats it as optional. It is the only mechanism that returns funds without anyone's intervention.
• Test with a small amount before moving size through any route, on any aggregator, including ours. It is the cheapest insurance in crypto and it would have made this a $30 problem instead of a $320,000 one.
• Being non-custodial does not mean nothing can go wrong. We never hold your funds — but the protocols we route to are independent systems that can fail, and when they do, the failure is visible to you rather than hidden inside a balance sheet. We would rather say that clearly than pretend otherwise.

Why we are publishing this

We have spent this year writing about exchanges that wind down, platforms that fail with user funds inside, and hardware that ships flawed. It would be inconsistent to hold others to a standard of public disclosure and stay quiet when a route we integrate leaves funds unresolved. This post will be updated when the situation changes, in either direction — including if the fault turns out to be ours.

A note on risk

Nothing here is financial or legal advice. This report reflects our observations as of August 14, 2026. No allegation of wrongdoing is made against NEAR Intents, NEAR Protocol, or any other party. Status descriptions are drawn from 1Click's public documentation and API responses. We will update or correct this post as facts develop.