Roadmap vs. Reality: BlockDAG Needs One Honest Public Ledger of Every Promise, Deadline and Delivery

BlockDAG does not need another roadmap nearly as much as it needs an accounting of the roadmaps it already published.

The project began in January 2024. Its own development history says the mainnet was fully developed by November 2024. In September 2025, BlockDAG said it was in the final stretch before Awakening. In early 2026, the presale was described as entering its final window. The current mainnet page lists specific February, March and April milestones. Other official material moves the Super App into June and then August. BlockDAG X displayed an August 22 exchange opening. Buyback dashboards displayed an October 1 USDT payment date.

That is a lot of dates.

Some milestones were delivered. BlockDAG says token generation, staking and certain exchange listings were completed in February and March 2026. Those belong in the record.

Other dates remain overdue, revised or disputed.

Those belong in the record too.

The solution is simple: one public accountability ledger.

For every major promise, publish five fields.

What was promised?

When was it promised?

What was the stated deadline?

What actually happened?

If it changed, why?

Do that for mainnet, token generation, exchange listings, BlockDAG X, the Super App, miner deliveries, Tier-1 listings, presale closure, buybacks and investor payments.

Do not delete the old target when a new target is created.

Do not rewrite a missed deadline as though it was never announced.

Do not call something complete without defining exactly what completion means.

A project that has raised money for more than two years should be able to maintain this record.

The reason it matters is trust.

Investors can tolerate a delay when they believe they are being told the truth about it. What destroys confidence is the feeling that every missed date is simply replaced by another promise and that the burden is placed on the investor to remember what came before.

That is exactly why communities matter.

No single investor has every email, every dashboard version and every roadmap screenshot. Collectively, investors may have nearly all of them.

One person has the 2024 mainnet statement.

Another has the Awakening countdown.

Another has the April Super App deadline.

Another has the August 22 BlockDAG X screen.

Another has the October 1 buyback payment screen.

Put those records together and the history becomes much harder to blur.

BlockDAG can participate in that process constructively by publishing its own reconciled timeline and correcting anything investors have wrong.

But the company should not expect the public to accept another future promise without accounting for the old ones.

The project is no longer in its first few months.

It has had years.

And investors who are waiting for money are not asking for another vision of what BlockDAG might become someday.

They are asking what happened to commitments already made.

That is why the accountability ledger should end with the most important category: financial obligations.

For every completed buyback, show the amount due, payment date and transaction record.

For every unpaid obligation, show its status and reason.

No disappearing dates.

No moving goalposts without explanation.

No replacing USDT with something else unless the investor agreed.

BlockDAG wants to legitimize itself as a serious blockchain project.

Then operate like a serious organization.

Keep a record.

Explain failures.

Correct them.

And pay investors what they are legitimately owed.

Source Record

Discuss this article

Have direct experience or documents related to this issue? Add your thoughts below. Please distinguish first-hand experience from information heard elsewhere. Do not post private keys, seed phrases, passwords, full account identifiers or unnecessary personal information.

Leave a Reply

Your comment is submitted through this website. Do not post private keys, seed phrases, passwords, account identifiers, email addresses, or other personal information.

← Back to BlockDAG Investigation