BlockDAG's own support page still displays an exchange schedule with dates that are now long past.

March 5: trading on LBank and Coinstore.

March 10: futures expansion across several exchanges.

March 20: four more exchanges.

March 24: Hyperliquid and dYdX.

March 28: four additional exchanges.

April 5: seven more exchanges.

April 20: BlockDAG Super Application.

It is October 2026.

Why is this old schedule still being presented to people seeking support?

Some of these milestones may have been completed. BlockDAG's current mainnet page marks several March milestones as completed and describes a broader exchange rollout.

Other milestones need reconciliation.

The point is not to pretend the entire schedule failed.

The point is that a support page should tell users the current truth.

If March 24 happened on March 24, link to the live markets.

If it happened later, publish the actual date.

If the plan changed, mark it changed.

If an exchange never launched BDAG as represented, remove the outdated implication and explain what happened.

The same applies to the April 20 Super Application date.

BlockDAG's other official materials have presented later Super App timing, including June and August references. Leaving April 20 on the support page without an update forces users to reconcile BlockDAG's own conflicting timelines.

That is not the user's job.

BlockDAG controls the websites.

Update them.

This matters because support pages are where people go when something is wrong. A customer with a miner problem, exchange-access problem or token issue should not encounter stale deadlines that create more confusion.

The page should become an accountability resource.

For every historical milestone, display the original target and actual outcome.

That would preserve the record without misleading current visitors.

For example:

Original target: March 24.

Actual outcome: [date and result].

Status: completed, delayed, replaced or canceled.

Reason for change: [brief explanation].

That simple format would eliminate much of the uncertainty investors have spent years trying to reconstruct.

It would also help BlockDAG rebuild credibility.

A serious organization does not need to pretend every target was hit. Serious organizations document misses and explain corrections.

Investors understand that software and exchange integrations can change.

What they resent is feeling that the old date disappears once it becomes inconvenient.

And that frustration is now amplified by financial disputes.

When an investor has already seen August 22 pass on BlockDAG X and October 1 pass on a buyback screen, stale March and April dates reinforce the sense that deadlines are treated as promotional when announced and optional afterward.

BlockDAG can change that pattern.

Start with the support page.

Reconcile every date.

Link every completed exchange.

Explain every changed milestone.

Then apply the same discipline to financial commitments.

A support page should reduce uncertainty.

It should not preserve a museum of deadlines without telling investors what actually happened.

Investors should insist that the answer be documented in writing and tied to the exact terms and dates that applied when they acted. That record protects everyone from later confusion and makes accountability possible.

Accuracy matters.

Source Record

• BlockDAG FAQ
• BlockDAG Support & Exchange Schedule
• BlockDAG Dev Release 236 — Presale Concluding
• BlockDAG Published Mainnet Wallet Allocations & Fundraising Counter
• BlockDAG Presale & Launch FAQ
• BlockDAG Mainnet Roadmap