October 1, 2026 was not supposed to be another vague milestone in the BlockDAG story. The dashboard gave investors a specific date, a specific time and a specific payment method: October 1 at 10:00 UTC, with USDT sent to the investor's wallet.

After more than two years of BlockDAG announcements, that specificity mattered.

The project had already taken investors through a long presale, multiple pricing stages, bonuses, launch plans, exchange schedules and product announcements. BlockDAG's own January 2026 development releases described the presale as entering its “final window” and then “concluding.” Its mainnet material later published detailed dates for token generation, claims, staking and exchange expansion.

So when a buyback screen finally told an investor when payment would occur, that was not just another roadmap aspiration. It was a financial representation attached to a transaction.

The recovered dashboard evidence is direct. It says “Payment Date: 1 Oct 2026, 10:00 UTC.” It says “Payment: USDT sent to your wallet.” It shows sold BDAG entries. Other BlockDAG screens presented liquidity wallets as the wallets that would pay USDT.

For an investor, those words create an expectation that is easy to understand: I performed under the buyback terms; on October 1, I will be paid in USDT.

If that payment was not received, the response cannot simply be another future date.

That is where frustration turns into anger, and understandably so. People may have been waiting years to recover money. Some may have arranged bills around the expected payment. Some may have reassured family members that there was finally a definite date. They did not invent October 1. They did not choose the payment method. BlockDAG displayed those terms.

And now the burden belongs with BlockDAG.

If payment was made, identify the transaction.

If the payment obligation was changed, identify the provision that allowed BlockDAG to change an accepted transaction without the investor's agreement.

If a new program replaced the old one, explain when each investor consented to that replacement.

A company cannot reasonably expect its customers to be bound by every rule on the screen while treating its own payment date as optional.

The blockchain makes one part of this especially simple. USDT payments leave transaction records. A transaction hash can show the sending address, destination, amount, timestamp and success status. That is not a demand for proprietary information. It is the ordinary evidence that a blockchain payment occurred.

Investors should also stop facing this issue one at a time.

If October 1 was your payment date, find other people who were shown the same thing. Compare sold status, amounts, eligibility terms and support responses. Preserve the dashboard as it appeared before and after the deadline. Do not expose private keys or seed phrases, but do preserve the evidence necessary to show what you were promised.

There is strength in a group of investors presenting the same dated commitment and asking the same unanswered question.

BlockDAG has spent years telling people to pay attention to its milestones.

October 1 was a milestone too.

It should not disappear because a new promotion or new timeframe arrived afterward.

BlockDAG made the representation. Investors relied on it. If investors fulfilled the requirements of the agreement, BlockDAG needs to fulfill its side.

Show the payment.

Explain the change.

Or pay what is owed.

Source Record

• BlockDAG Mainnet & Roadmap
• BlockDAG FAQ
• BlockDAG Six-Week Launch Plan
• BlockDAG Dev Release 235 — January 12, 2026
• BlockDAG Dev Release 236 — January 26, 2026