CoinFLEX named Roger Ver in a disputed 47 million USDC claim

CoinFLEX chief executive Mark Lamb publicly identified Roger Ver on June 28, 2022 as the customer he said had failed to meet a 47 million USDC obligation, linking the allegation to the cryptocurrency exchange’s continuing withdrawal freeze. Ver denied owing the money and asserted that the unnamed counterparty instead owed him funds.

The verified event is therefore a public disclosure and dispute—not a finding that either side’s account was correct. No reviewed court order, arbitral award, contract, default notice or independently audited balance sheet established the debt on June 28.

From an unnamed exposure to a named dispute

CoinFLEX had stopped withdrawals on June 23, citing extreme market conditions and uncertainty involving a counterparty. Its initial statement said the counterparty was neither Three Arrows Capital nor a lending firm, but it did not name the customer or quantify the exposure.

A CoinFLEX whitepaper then described a “non-liquidation recourse account.” Under the company’s account, the customer’s position was not automatically liquidated when equity ran low because the customer had agreed in writing to guarantee the account’s equity. The whitepaper said the account went negative during market volatility and proposed Recovery Value USD, or rvUSD, as a way to finance the resulting shortfall.

On June 28, Lamb supplied the name. He alleged that Ver owed 47 million USDC, was contractually required to guarantee negative equity and top up margin, and had been served a default notice. Ver’s post, published the same date without naming CoinFLEX, rejected rumors that he had defaulted and claimed a counterparty owed him a substantial amount.

Axios reported that Lamb confirmed to the publication that Ver was the customer and repeated that CoinFLEX would seek recovery. Bloomberg News independently documented both positions. Those reports corroborate that the dispute became public on June 28; they do not independently prove the underlying liability.

The recovery token exposed the risk structure

The rvUSD whitepaper scheduled an issuance period from June 28 through July 1, with a maximum of 47 million tokens offered at one USDC per rvUSD. Eligibility was limited to non-U.S. “sophisticated investors” who completed CoinFLEX identity checks, met stated income or net-worth thresholds, and subscribed at least 100,000 USDC.

CoinFLEX advertised a 20% annual percentage rate, accrued and paid daily in rvUSD. The primary repayment route depended on recoveries from the individual being converted into USDC for rvUSD holders. The terms also contemplated FLEX-token incentives and alternative exit mechanisms if the liability was not recovered within 15 months. The document said final subscription terms could change.

That structure mattered because it made an internal credit exception visible. A centralized venue could offer continuous crypto trading while carrying a private, bilateral exposure that users could not inspect on-chain. When that exposure became disputed, customers experienced the consequence through restricted withdrawals, while the proposed token would place recovery risk with a new set of investors.

What June 28 did not establish

The reviewed records do not establish how much rvUSD was actually sold on June 28, whether CoinFLEX possessed enforceable collateral, or when all customers regained unrestricted access to funds. The 47 million figure was CoinFLEX’s stated USDC claim, not an independently verified dollar valuation or an audited loss.

No bitcoin, ether, FLEX or USDC price move is attributed to the disclosure. Digital assets trade continuously across fragmented venues, and the available event-day sources do not isolate a reliable announcement window from the wider June 2022 credit selloff.

The defensible conclusion is narrower: on June 28, CoinFLEX turned an unnamed counterparty problem into a named, contested claim and attached that claim to a tokenized recovery proposal. The episode showed how opaque credit terms at a centralized crypto intermediary could migrate quickly from one customer’s account to a platform-wide liquidity constraint.