Hassan Maishera
TL;DR
-
Velocity has opened claims for users affected by the April exploit, issuing one DFX recovery token per USDT lost.
-
Users can redeem DFX for USDT, sell it on the secondary market or hold it for potential future recovery funding.
-
Initial redemption value is slightly above 0.01 USDT per DFX, far below full reimbursement.
Velocity, the decentralized exchange formerly known as Drift, has opened recovery-token claims for users who lost funds in its April exploit.
Eligible users can claim one DFX token for every USDT lost. The tokens provide access to a recovery pool, but current redemptions return only slightly more than one cent for each dollar of losses.
The launch establishes a mechanism for distributing available funds. It does not mean users have been fully reimbursed, and future recovery depends on additional contributions, protocol revenue and potentially recovered assets.
Users Can Redeem, Sell or Hold DFX
DFX holders have three options: redeem and burn their tokens for USDT from the recovery pool, sell them on the secondary market or retain them while awaiting additional funding.
Each route involves a different outcome. Redemption provides an immediate payout based on available pool funds and removes the redeemed tokens from circulation. A secondary-market sale depends on buyers and market pricing, which may differ from the pool’s redemption value.
Holding DFX preserves exposure to future recovery deposits, but neither their timing nor their amount is guaranteed.
As tokens are burned, subsequent funding is distributed across fewer outstanding DFX. That could improve the recovery available per remaining token, although it does not establish that holders will eventually receive full reimbursement.
At launch, each DFX could be redeemed for slightly more than 0.01 USDT. With one token allocated per USDT lost, that represents a recovery of roughly 1% rather than repayment at face value.
On Friday, the recovery dashboard showed 216,480 DFX redeemed for approximately 2,250 USDT in payouts.
The pool contained approximately 3.11 million USDT, comprising protocol assets. Velocity also plans to direct between 60% and 90% of its net protocol revenue into the pool.
After the first day, the dashboard recorded just 31 USDT from that revenue mechanism. The early figure offers limited evidence of how much the channel might contribute over time.
Major Funding Commitments Are Not Yet Reflected
The dashboard had not recorded a contribution from Tether, which committed up to $127.5 million to support the platform’s relaunch and user recovery.
It also did not reflect up to $20 million pledged by strategic partners. Those commitments are distinct from funds already available for redemption. The “up to” amounts should not be treated as confirmed deposits into the recovery pool.
Their eventual contribution could materially affect payouts, but the supplied report does not establish a payment schedule or how much of the pledged support will enter the pool.
In a September 30 update, the Drift Foundation said approximately $295.4 million was stolen in the April 1 attack. Cybersecurity firm Mandiant attributed the incident to UNC6862, which it identified as a North Korean threat group.
The stolen assets were bridged to Ethereum. According to the foundation, three attacker wallets still held 107,165 ETH worth nearly $286 million, while another wallet moved 23,094 ETH through Tornado Cash in July.
These balances and movements provide an update on the assets being tracked; they do not mean those holdings are available for reimbursement.
Frozen Funds Could Add to Recovery
The foundation said approximately $9.2 million in stolen funds has been frozen. Those assets could enter the DFX recovery pool once cleared by law enforcement. Freezing therefore represents progress toward possible recovery, but remains separate from funds already distributed to users.
For claimants, the immediate choice is between a small available payout and retaining or selling a token tied to uncertain future funding. The recovery mechanism is operational, while the extent of eventual reimbursement remains unresolved.
