Main Street Finance’s msUSD stablecoin lost its dollar peg on June 20 after verification provider Accountable terminated its service agreement with the protocol, saying Main Street had been unable to meet its verification standards.
Accountable announced that the termination was effective immediately and acknowledged that markets had relied on its feed. The company said it was working with ecosystem partners as the situation developed. The statement did not allege that reserves were missing, and it did not quantify a shortfall; it established that Accountable would no longer provide the verification on which market participants had relied.
By the time BeInCrypto reported on the disruption later that day, msUSD was trading near $0.29, about 71% below its intended $1 value over 24 hours, with a reported market value of roughly $30.5 million. Those figures are a time-specific market snapshot rather than a redemption value, and the token’s price can continue to change.
A verification failure became a liquidity event
Main Street had marketed msUSD as a dollar-denominated token redeemable one-for-one for USDC. The protocol also allowed holders to stake msUSD for msY, a yield-bearing strategy token. Accountable supplied a public collateral-verification feed, giving users and integrated protocols an external signal about the assets supporting the system.
Once Accountable switched off that relationship, the dashboard no longer provided the same reserve verification. That information gap appears to have accelerated selling and impaired confidence in both msUSD and msY. Blockchain security firm PeckShield reported an 85% drop for the msUSD contract later on June 20 and separately flagged severe stress around an msY/USDC lending market.
The episode illustrates a practical distinction for payment companies evaluating stablecoin rails: token issuance, redemption, reserve custody, third-party verification and secondary-market liquidity are separate functions. A stablecoin can continue to exist on-chain even when a critical off-chain assurance layer disappears. Merchants and processors therefore need controls for the failure of a verifier or data feed, not only for the failure of the token contract itself.
Implications for payment and treasury integrations
For a payment integrator, a quoted market price below $1 can affect settlement amounts, customer refunds and treasury conversion. A promise of one-for-one redemption is useful only when the redemption channel remains available, adequately funded and operational under stress. Secondary-market liquidity may not preserve that value during a confidence shock.
Due diligence should identify who verifies reserves, how frequently data is refreshed, whether the verifier can suspend service immediately, and what fallback evidence becomes available if it does. Contracts with issuers should also define what happens when a token deviates from its reference value or when an assurance provider withdraws.
Risk controls can include token-specific exposure limits, multiple price feeds, automatic settlement pauses, documented substitution rules and direct testing of redemption procedures. Payment businesses should also avoid treating a verifier’s dashboard as equivalent to an audit or a legal guarantee. In this case, Accountable’s statement concerned its own standards and service relationship; it did not resolve the ultimate value or availability of Main Street’s collateral.
The immediate operational lesson is that stablecoin acceptance depends on more than nominal price stability. It also depends on resilient disclosure, verifiable reserves, executable redemption and sufficient liquidity when counterparties lose confidence. The msUSD disruption shows how quickly those dependencies can become a payment and treasury problem when a single assurance provider exits.