BlockDAG holders cannot claim their coins. The error: "Transaction failed."

A token you cannot move is not an asset, it is a screenshot. On June 9 a large share of BlockDAG holders discovered that the coins their dashboard says are "available to claim" will not actually leave the contract. The button is there. The transaction is not.

The error everyone is seeing

The failure is specific and repeatable. When a holder tries to claim, the wallet returns a revert. The message, shown to ordinary users, reads:

Read who that message is written for. "Run node scripts/test-relayer-claim.js with a single address to debug" is an instruction for a developer with the project's codebase on their machine. It is being shown to retail investors who clicked a "Claim" button. A finished product does not hand its users an internal debug command when something breaks. That alone tells you the claim system is not production ready.

It is widespread, and it is a regression

This is not one unlucky wallet. Across June 8 and 9 the group carried roughly forty separate claim-failure reports against only a handful of confirmed successes. A sample from June 9 alone:

"Can't claim my token allocation Batch 1, 2, 3, saying transaction likely to revert?" — Community member Jmilli, June 9, 2026, 02:17 UTC.

The most telling report is a regression. The same holder, the same wallet, claimed successfully days earlier and cannot now. Jordan Romero, June 9 at 03:33 UTC:

"Why can't I claim my coins, it keeps saying transaction failed? I was able to claim them the last 2 times on the 6th, but now it's not working this time." — Community member Jordan Romero, June 9, 2026, 03:33 UTC.

If the cause were the holder's own wallet setup, the same wallet would not have worked on June 6 and failed on June 9 with nothing changed on their end. Darryl Laird and Claude Villa reported the identical "transaction failed" loop the same morning. Whatever changed, changed on the contract side, not in the users' browsers.

The detail that ends the argument

For two days, accounts defending BlockDAG called this site a "paid fudder" for documenting broken claiming and staking. Then one of them posted this:

"The problem persists in the claim for Batch 3." — An account defending the project, posting the "Transaction Failed" error screen on CoinMarketCap, June 9, 2026.

That is the whole case in one post. The same account insisting the system works published a screenshot of it not working. When the people defending a project are themselves locked out of their coins, the question of who is "spreading FUD" answers itself.

In fairness: what BlockDAG says

We try to give the project's side, and here it is. BlockDAG attributes the failures to the user's environment. The standing fix from admins is: "Clear your browser cache, close all tabs, disconnect wallet from all dapps and try again," along with instructions to add the correct network (Chain ID 1404, RPC rpc.bdagscan.com). Admins also state that "many users have successfully claimed their coins." Some clearly have.

But two things cut against the cache-and-RPC explanation. First, the regression: a wallet that claimed on June 6 with that same network already configured should not fail on June 9. Second, the error itself points at the contract, not the browser: it asks you to verify the merkle root, the proof, and whether the "vesting contract has sufficient balance." Those are server-side and contract-side conditions a user cannot set or fix by clearing a cache.

And the coins that do claim are compressed

Even for holders who get a claim through, the amount that lands is a fraction of the dashboard figure. Clark put it plainly on June 8:

"Coin being on your dash and coin being in your wallet and sendible are not the same thing. You'll find the coins are very compressed." — Community member Clark, June 8, 2026.

So the path from "dashboard balance" to "tokens you can actually use" has two gates, and both are failing for many: the claim itself reverts, and what gets through is heavily compressed. This is the same wall holders hit when they try to reach the buyback's 10 million minimum, the tokens they would need are stuck behind a claim that will not execute.

What we are watching next

Two things, both checkable. First: whether BlockDAG acknowledges a contract-side claim issue and ships a fix, rather than repeating "clear your cache." Second: whether the claim failures clear before the next batch is released, or stack on top of the unclaimed batches 4, 5 and 6 that holders were already waiting on. We will update this story the moment either happens.

Our advice is narrow and practical here. If your claim fails, do not keep paying gas to retry blindly, and never share your seed phrase with anyone offering to "fix" it. Screenshot the error with its timestamp. A documented, repeatable failure is worth more than a dozen retries.