Arcus, a decentralized exchange running on Robinhood Chain, disclosed on Tuesday, November 10, that it had identified and repaired an accounting bug that allowed a user to withdraw funds to which they were not entitled. The exchange covered the entire shortfall — approximately $2 million — from its own treasury, meaning the platform absorbed the cost of its own mistake so that its customers would not have to.

According to Arcus, the bug was identified on November 9 and patched within one hour of detection. The company says no user balances were affected, and trading and withdrawals are running normally.

What Happened at Arcus

At its core, the problem was an accounting error: somewhere in the system that tracks who owns what, the recorded numbers stopped matching reality. Arcus has not publicly described the specific mechanics of the bug, and it has also not said whether the withdrawal was a deliberate exploitation of the flaw or an opportunistic move by a user who noticed a balance that looked unusually generous.

The company's statement centered on three points: the bug was caught quickly, the resulting gap was filled, and customer funds were left untouched.

The treasury backstop is the detail that matters most here. Arcus absorbed the loss at the company level rather than socializing it across traders — the approach some platforms have taken after past incidents. Under a socialized-loss model, every user takes a small haircut to cover a single hole. Arcus instead chose to eat the cost itself, a decision that keeps customer balances whole but draws down the reserves the company presumably holds for situations exactly like this one.

Who Arcus Is and What It Trades

Arcus launched in beta around June or July 2026 and sits in a niche that has been heating up: on-chain trading of tokenized stocks.

The exchange offers zero-fee spot trading of stock tokens around the clock. Tokenized stocks are blockchain-based representations of traditional equities, a structure that allows them to trade on weekends and outside normal market hours.

Arcus also runs cross-margined perpetual futures with leverage of up to 50x. Perpetual futures, or perps, are derivatives contracts with no expiry date, letting traders bet on price moves without holding the underlying asset. Cross-margining pools a trader's collateral across positions rather than walling it off for each trade. The structure is capital efficient, but it also means the accounting system has a lot of moving parts to track at once.

According to the research, the exchange is built by the dYdX team in partnership with Robinhood Crypto, and it is designed to operate outside the regulatory boundaries of the US, UK, and Canada.

The timing of the incident is notable. Around November 5 to 7, just days before the bug surfaced, Arcus expanded multi-asset collateral support to all traders — a feature that lets users post a wider range of assets as margin. Arcus has not linked the bug to that rollout. Still, new collateral types introduce new math for the system to handle, and anyone watching the timeline will notice the proximity.

What This Means for Traders and the Tokenized Stock Race

For current Arcus users, the immediate takeaway is reassuring. Balances are intact, withdrawals are working, and the exchange has shown it can respond quickly and pay out of pocket when something breaks. Covering approximately $2 million from the treasury sends a clear signal about the company's priorities: customer funds come first, even at the cost of its own reserves.

The flip side is that the bug existed at all. An exchange offering up to 50x leverage on cross-margined positions needs its accounting to be airtight, because errors in that system can compound quickly when collateral is pooled across positions.

The things to watch from here are fairly concrete. First, whether Arcus publishes a detailed post-mortem explaining the root cause and what has changed in its processes. Second, whether the company says anything about recovering the funds from the user who withdrew them — a question Arcus has not addressed publicly. Third, how the incident shapes the exchange's pace of shipping new features, given that Arcus was expanding collateral options right up until the incident occurred.

Source: CryptoBriefing