In December the initiative was approved<\/a>, with a six\u2011month delay to the shutdown. In June 2025 a final vote was held<\/a>, in which a majority of validators backed the decision.<\/p>\n Only 434 accounts took part in the final round, and the post about the proposal on the forum<\/a> was buried, garnering just over 500 views.<\/p>\n Users had a six\u2011month window to move assets, but many retail investors rarely track governance initiatives. The plan to disconnect from Ethereum had limited visibility.<\/p>\n DYDX holders raised the alarm in September. A community member contacted ForkLog, described the problem and asked to publicise it. He also shared a video<\/a> by influencer Andrey Sobolev on the topic.<\/p>\n According to on-chain data and the blogger\u2019s calculations, the volume \u201clocked\u201d on Ethereum reached 4.2% of the coin\u2019s total supply. Some 45,000 ethDYDX holders have positive balances, of whom roughly 11,000 hold more than $100 and 2,500 more than $1,000.<\/p>\n \u201cSelling tokens via Uniswap is almost impossible: there is no liquidity, the price is dozens of times below the market ($0.01 versus $0.7). In effect, the tokens on Ethereum have become \u2018empty shells\u2019. [Retail] investors were not properly notified,\u201d the user who contacted the editorial office said.<\/p>\n<\/blockquote>\n Funds and trading platforms were contacted directly and thus managed to migrate, the speaker added. Large sums that passed through the bridge during the migration point to this.<\/p>\n Sobolev calls the situation \u201ca deliberate scam\u201d. In his words, the team simply froze retail funds to improve token economics. He cited one point from the original proposal, which states:<\/p>\n \u201cReducing the circulating supply of unallocated ethDYDX tokens may help offset DYDX token sales and mitigate inflationary pressure.\u201d<\/p>\n<\/blockquote>\n Sobolev also called the platform\u2019s votes \u201ca fiction\u201d, since only the largest validators participate. The weight of retail investors can simply be ignored because of their small holdings, so their opinion is not considered.<\/p>\n The blogger tried to contact the dYdX team, including the CEO, COO and other members. His messages were ignored.<\/p>\n Affected users eventually brought the issue to public discussion<\/a>.<\/p>\n \u201cMany community members, including me, still hold DYDX tokens in ERC-20 format on Ethereum. Since the official bridge was closed, there is currently no fair and simple way to migrate these tokens to the dYdX blockchain,\u201d wrote the author under the nickname werty.<\/p>\n<\/blockquote>\n Several approaches were proposed as a remedy:<\/p>\n Comments are now being collected. The forum post already has three times more views than the original proposal.<\/p>\n Many investors confirmed the problem and asked the team to enable token withdrawals.<\/p>\n \u201cI understand that the decision to close the bridge was based on a management proposal and applied automatically, but many users, including me, now cannot access their coins. This has created a very difficult situation for us,\u201d one participant said.<\/p>\n<\/blockquote>\n Judging by the comments, most did not keep up with the passed proposal and failed to move coins within the deadline. Some complained they were unwilling to convert in low\u2011liquidity pools.<\/p>\n A dedicated Telegram channel<\/a> has also been created for affected DYDX holders. It publishes updates and news on the situation. According to one of the latest messages, on 17 September the trading platform\u2019s team will hold a call on the stuck coins.<\/p>\n In March, the dYdX community voted<\/a> to distribute $1.5 million in DYDX from the treasury.<\/p>\n![\"image\"](\"https:\/\/forklog.com\/wp-content\/uploads\/img-672ed76aaa45285c-4500086869861345-1024x323.png\")
Hodlers\u2019 anger<\/strong><\/h2>\n
![\"image\"](\"https:\/\/forklog.com\/wp-content\/uploads\/img-0b04532394b552c7-4500086976888824-1024x387.png\")
\n
![\"image\"](\"https:\/\/forklog.com\/wp-content\/uploads\/img-d5188ea8a7bb9e00-4500086892675115-1024x256.png\")
\n
Community pushback<\/strong><\/h2>\n
\n
\n
\n