AnomaPay Pauses Verifier, Halting Access to Deposited Funds

By Elena Vasquez

AnomaPay said it paused its RISC Zero-backed verifier after identifying a vulnerability in the underlying proof system, leaving users unable to access deposited funds for an expected period of about two weeks. The disclosure did not quantify the deposits, report a loss, identify an exploited transaction, or provide a firm restoration date.

The distinction between risk and loss is material. AnomaPay said the vulnerability could put user funds at risk, but the pause presented a preventive containment step, not evidence that an attacker had withdrawn funds through the flaw. The company also said “funds already deposited remain safe,” while acknowledging that the offline verifier prevents users from accessing those balances.

Why did AnomaPay halt the verifier?

The protocol required a coordinated response across two layers: the user-access function and the RISC Zero proof system supporting the verifier. After identifying the vulnerability, AnomaPay took the verifier offline, prioritizing protection over continued availability.

Deposited assets remain described as safe by AnomaPay, but users cannot reach them during the halt. The company says no withdrawal, transfer, or other user-side remedial step is required, which limits action by depositors but does not restore access while the verifier stays down.

AnomaPay described the halt as necessary to protect users and their funds despite the disruption. That wording acknowledges the tradeoff without quantifying it: the company presented reduced access as preferable to leaving a potentially vulnerable proof system operational.

Takeaway: The pause was a containment measure tied to a stated proof-system risk, not a reported theft.

What changes during the two-week pause?

Anoma expects the upgrade of the Anoma protocol to V2 to take about two weeks, equivalent to roughly 14 days. The release will include new security updates for RISC Zero's proof system, and the RISC Zero team will upgrade the paused verifier.

The timetable remains an estimate rather than a committed deadline. The disclosure did not identify a calendar completion date, deployment sequence, rollback criteria, or independent review of the proposed fix. It also gave no number of affected users and did not disclose the chain, token standard, asset type, or total value of affected deposits.

For users, the stated procedure requires no intervention. When the upgrade completes, deposited funds will move automatically to V2, and AnomaPay expects access to return at that point. The company said “users do not need to take any action.”

Takeaway: The promised remedy is an automatic V2 migration, with no user action required during the pause.

How will the upgrade restore access?

The plan links two actions: RISC Zero will upgrade the verifier, and Anoma will release V2 with the new proof-system updates. Once deployment completes, deposited funds are scheduled to move automatically to V2, and AnomaPay expects access to return.

The claim rests on execution. A successful release and verifier deployment would allow migration to begin, but the disclosure does not explain how the teams will test the fix, verify migrated balances, or address interruptions encountered during the pause. Those omissions leave operational questions open despite the simple customer instruction.

The announcement identifies the RISC Zero security updates as one component of the release but does not say whether V2 changes settlement behavior, custody arrangements, or withdrawal timing. Users therefore cannot determine from the disclosure whether the upgrade introduces broader protocol changes.

Takeaway: Restoring access depends on a coordinated RISC Zero deployment and Anoma V2 migration, not an immediate user workaround.

What remains unverified?

AnomaPay's assurance that deposits remain safe is the central claim, but the available information provides no independent validation. The report does not establish that the vulnerability was exploited; it identifies a potential risk that the company said justified stopping the verifier.

No affected-balance total or reported loss appears in the disclosure, and no post-upgrade test result was available. The responsible response is not to assume either safety or compromise, but to separate the company's assurance from independent confirmation.

The next verifiable checkpoint is V2 deployment within the stated two-week window. Until users can demonstrably access migrated balances, the promised restoration and AnomaPay's safety assurance remain unverified claims dependent on the announced work by AnomaPay and RISC Zero.