Have you ever watched funds you believed were safely held suddenly become unreachable, only to find the person in charge of the platform simply stops responding? That uneasy feeling is exactly what some BitMart users describe right now. They claim that after publicly asking for the return of project tokens and related balances, they were blocked on social media by the exchange founder. The amounts involved are not small. One project alone points to roughly 800000 ATEG tokens still sitting inaccessible, alongside an unspecified USDC balance, while another user reported holdings near 391000 USDT. The exchange itself is deep in a wind-down process, and the official recovery options come with no firm withdrawal date. In my view, this combination of public silence and delayed clarity creates the kind of uncertainty that can quickly erode whatever trust remains.
What Users Are Saying About the Blocked Appeals
The latest wave of complaints centers on a project known as ATEG Capital. Its representatives state that they listed on the exchange in mid-June and kept building their ecosystem even while the platform faced operational problems. They describe the holdings as legitimate project assets rather than promotional allocations or special favors. On successive days they posted public requests asking for a review of the outstanding balance, an update on the status of the assets, and a practical timeline for return.
One message from the project’s chief financial officer noted that after making those public appeals the founder’s account blocked him. Screenshots circulating with the posts show the blocked status notices together with an exchange balance screen. The same post referenced another customer’s unresolved holdings of approximately 391000 USDT, matching a figure visible on the displayed balance image. A separate message from the project founder asked for the tokens to be released while allowing the exchange more time to resolve its stablecoin obligations.
These are legitimate project holdings, not promotional allocations or requests for preferential treatment.
Other users joined the conversation, urging engagement and in some cases mentioning possible public discussions or reports to authorities if the matter stayed unresolved. From the outside it is impossible to verify every detail of every account. Still, the pattern of public requests followed by reported blocks has clearly raised the temperature around an already difficult situation.
The Scale of the Reported Holdings
Eight hundred thousand tokens is a substantial figure for a project still in its growth phase. When those tokens sit inside an exchange that has halted normal operations, the practical effect is that the project cannot use, move, or deploy them. The accompanying USDC balance, even if smaller, adds another layer of locked value. One additional user claim of roughly 391000 USDT further illustrates that the problem is not limited to a single project wallet.
I’ve found that in crypto the difference between “temporarily inaccessible” and “effectively frozen” often comes down to communication. When the only visible response is a block, the perception of permanence grows quickly. That perception can matter as much as the underlying technical or legal status of the funds.
How the Exchange Describes Its Current Path
BitMart has published a restructuring roadmap that proposes converting outstanding account balances into dollar-denominated claims. Valuations would rely on weighted average token prices calculated over a defined window ending at a record time. A court-appointed officer would handle adjudication. The plan outlines three main choices for affected users.
- An upfront proportional distribution drawn from liquid assets currently available
- A Restitution Token linked to any future recoveries of previously hacked funds
- A Continuum Token backed by investments, asset disposals, and possible profits if the business eventually restarts
November is set aside for revisions after stakeholder feedback. Management aims to file court applications in December or January. Account adjudication would then depend on court approval and local rules. Critically, the document does not set any specific withdrawal date. The proposed election deadline would arrive only after the plan receives the necessary approvals for implementation.
In practical terms this means users cannot yet know when, or even whether, they will regain direct access to original tokens or equivalent value. The roadmap is structured more as a claims process than a simple return of assets. That distinction is important for anyone still hoping to receive the exact tokens they deposited.
The Feedback Portal and Its Limits
A user engagement portal was launched earlier to accept withdrawal questions and restructuring feedback. The exchange has been clear that submitting a ticket does not change an account’s status or trigger an individual withdrawal. Users must select the correct portal option, enter an email, and verify the submission through a link. Ordinary customer support handles other issue types. The platform asks for one ticket per issue and notes that it may not answer every submission individually.
An earlier notice directed certain users to close positions and withdraw remaining assets by a fixed August deadline. Later restrictions could apply, and withdrawals might require identity checks, source-of-funds documentation, or proof of wallet ownership. Once trading stopped at the end of August, the practical avenues for moving funds narrowed sharply.
Perhaps the most interesting aspect is how little the portal changes the core problem for users whose balances remain locked. It creates a channel for information, yet it does not accelerate the return of assets. That gap between communication tools and actual fund movement is where much of the current frustration appears to live.
A Separate Security Incident Adds Pressure
While the ATEG discussion was unfolding, a separate security breach was acknowledged. Researchers estimated that roughly 391000 dollars moved across three networks from wallets mostly linked to the exchange. Transfers began shortly before a larger incident involving another platform and reached the same attacker address. Some of the wallets involved had previously appeared in public proof-of-reserves data.
On one network a rapid series of token movements occurred within a short window, followed by numerous small deposits from other addresses. The timing and destination patterns have drawn attention because they coincide with broader security concerns already facing the platform. The founder described the security team as severely understaffed at the time of the acknowledgment.
These events sit alongside the larger wind-down process. Even if the amounts involved in the traced drain are smaller than the total locked balances across all users, they reinforce the sense that operational control has been imperfect. For project teams waiting on their own tokens, every additional incident adds weight to the request for clearer timelines.
Why Project Tokens Matter Differently
When an ordinary trader cannot withdraw, the impact is personal and financial. When a project cannot access its own tokens, the impact can reach product development, liquidity planning, and community commitments. Tokens held for ecosystem growth or operational use are not the same as speculative holdings. Returning them, even while stablecoin issues remain unresolved, could reduce pressure on both sides.
One message from the project side explicitly offered that approach: release the tokens and keep the USDC until the exchange’s broader problems are sorted. That kind of compromise is worth examining because it separates two different categories of asset. Project tokens often have utility beyond simple price exposure. Keeping them locked may delay development milestones that were planned months earlier.
In my experience, exchanges under stress sometimes treat all balances the same way for administrative simplicity. Yet the practical needs of a project team can differ sharply from those of a retail holder. Recognizing that difference early can reduce public conflict later.
The Human Side of Waiting for Clarity
Anyone who has followed crypto long enough knows that recovery processes after operational breakdowns are rarely fast. Court involvement, valuation windows, and multiple recovery instruments all take time. Still, the absence of even a provisional withdrawal schedule leaves users in a prolonged state of uncertainty. That uncertainty is amplified when public appeals are met with blocks rather than replies.
Social media blocks are a blunt instrument. They stop one conversation, yet they do not stop the underlying claim. In some cases they may even draw more attention to the original request. A measured public response, even if it only restates the existing roadmap, often carries more weight than silence.
I’ve noticed that the most constructive exchanges in similar past situations usually include three elements: acknowledgment of the specific holdings, a restatement of the process that will apply, and a realistic indication of the next milestone date. When any of those three is missing, trust erodes faster.
Looking at the Proposed Recovery Options More Closely
The three choices on the table each carry different risk and reward profiles. An upfront proportional distribution offers the quickest path to some liquidity, yet the total pool of liquid assets may be limited relative to overall claims. A Restitution Token ties recovery to future success in reclaiming previously compromised funds, introducing both upside and uncertainty. A Continuum Token depends on the longer-term performance of remaining investments and any restarted business activity.
Users will need to weigh these options carefully once the formal election period opens. The valuation method based on a weighted average over a past window means that price movements after the record time will not alter the claim amount. That design protects the process from later market swings, yet it also locks in a historical value that some holders may find lower than expected.
Court approval remains a necessary step. Local rules will shape how adjudication actually works. Until those approvals arrive, the plan stays provisional. That reality explains why the document contains no withdrawal date. Setting one before the legal framework is in place would create expectations the exchange could not reliably meet.
Practical Steps Users Can Take While Waiting
Even without a firm timeline, certain actions remain available. Documenting balances with screenshots, transaction histories, and any prior correspondence creates a clearer record. Submitting feedback through the official portal, even if individual replies are limited, places the concern into the formal channel. Monitoring the restructuring roadmap for updated versions after the November feedback period is another useful habit.
- Preserve all account statements and balance records from before trading stopped
- Note any specific token quantities and the dates they were last accessible
- Use the engagement portal for structured questions rather than relying solely on public posts
- Watch for announcements about court filing dates and the opening of the election window
- Evaluate the three recovery instruments once full details become available
None of these steps guarantees faster access. They do, however, keep the user’s position organized and ready for whatever formal process emerges. In situations like this, preparation often proves more valuable than repeated public demands.
Broader Lessons for Token Projects and Exchanges
The current episode highlights a recurring tension. Projects list on exchanges for liquidity and visibility. Once tokens move into exchange wallets, control shifts. If the exchange later faces operational or security challenges, those project assets can become collateral damage. Clearer contractual language around the treatment of project-owned tokens during distress events could reduce future friction.
Exchanges, for their part, benefit from maintaining open channels even when answers are incomplete. A short acknowledgment that specific project holdings are under review often carries more weight than silence. Blocking accounts may feel efficient in the moment, yet it rarely resolves the underlying request and can invite wider scrutiny.
Security staffing levels also matter. When a team is described as severely understaffed, the risk of additional incidents rises. Investing in robust monitoring and response capacity before problems appear remains one of the more reliable ways to protect both user and project assets.
What Comes Next in the Timeline
The next visible milestones are the November feedback revisions, followed by targeted court applications in December or January. Once those applications move forward, the adjudication process and the election window for recovery options should become clearer. Until then, balances remain subject to the broader restructuring framework.
For the ATEG representatives and other users who have raised the issue publicly, the immediate desire is straightforward: access to the tokens they consider project property. Whether that request can be separated from the larger claims process is a question only the exchange and its advisors can answer. The public record so far shows requests followed by reported blocks rather than detailed replies.
I keep returning to the same observation. In crypto, trust is easier to lose than to rebuild. Transparent process, even when outcomes remain uncertain, tends to preserve more of that trust than silence. The coming months will show whether the roadmap can deliver concrete progress or whether additional friction will accumulate.
Balancing Claims and Practical Constraints
Every recovery plan after a major operational interruption faces the same basic tension. Users want their assets back as quickly and completely as possible. The platform must work within the assets that remain, the legal requirements that apply, and the need to treat similarly situated claimants consistently. Project tokens introduce an extra variable because their owners often argue for special treatment based on the purpose of the holdings.
A process that can distinguish between different categories of claim without creating unfairness is difficult to design. Still, the attempt is worth making. Returning project tokens while continuing to work through stablecoin and other balances might reduce the most vocal sources of dissatisfaction without undermining the overall framework.
Whether such a separation is legally or operationally feasible remains outside public view. What is visible is the continued absence of a withdrawal date and the reported blocking of users who asked publicly. Those two facts alone keep the story active.
Final Thoughts on Communication During Distress
When an exchange enters a wind-down or restructuring, every public interaction carries extra weight. Users are already anxious. Project teams are trying to protect development timelines. The founder and management team face legal, financial, and operational constraints that limit what they can say or do. In that environment, even small gestures of acknowledgment can matter.
Blocking accounts after public requests may feel like a way to reduce noise. In practice it often amplifies the original complaint. A brief, factual restatement of the recovery process, coupled with a note that specific project holdings are being reviewed under the same rules as other claims, would at least keep the conversation inside the formal framework.
The coming court filings and the eventual opening of the election window will provide more concrete information. Until then, the combination of locked project tokens, reported blocks, and an open-ended roadmap continues to generate legitimate questions. How those questions are answered, or whether they are answered at all, will shape the next chapter of this particular story.
Crypto markets move quickly, yet recovery processes move slowly by design. Bridging that gap with clear, consistent communication remains one of the more effective tools available. In the present case that tool has so far been used sparingly. The result is visible frustration from users who believe their assets should already be accessible. Whether the formal process can close that gap remains the central open question.
