Mina Multisig lets Mina and ecosystem projects operate through a threshold signature instead of a single key, adapting the FROST protocol to Mina’s Pallas curve and Poseidon hashing. Veridise completed a manual audit of that implementation in June 2026, reviewing the two Rust crates that turn FROST’s signing flow into Mina-compatible signatures. The audit found six issues, all fixed, before Nori becomes its first production user.

TLDR

• Manual audit of Mina Multisig’s FROST signature integration found six issues, fixed
• One high-severity finding bypassed point-at-infinity checks via a custom challenge computation
• Findings tracked on AuditHub with the Raspberry Devs team
• Nori becomes the first production user as o1Labs stewards Mina Multisig for the wider ecosystem

What Veridise reviewed

From June 15 to June 22, 2026, two Veridise analysts spent two person-weeks reviewing the frost-bluepallas and mina-tx crates at commit 1457cdd: the layer adapting Zcash’s frost-core library to Mina’s BluePallas ciphersuite and bridging it to Mina’s transaction format. The review checked whether that bridge held Mina’s conventions: canonical encoding, y-coordinate parity, point-at-infinity handling, and unambiguous message semantics.

Manual review, tracked on AuditHub

This was a line-by-line manual review. Two small Rust crates implementing one cryptographic protocol called for expert reading, not automated static analysis or fuzzing. Analysts used AuditHub, an independent continuous-security platform, to track findings and fixes with the Raspberry Devs team.

What the review found

The review found six issues: one high, two medium, three low, no criticals, all fixed. The high-severity finding was a missing point-at-infinity check: frost-core’s default flow rejects identity-element points during serialization, but Mina Multisig overrides the challenge computation to match Mina’s hashing, reading affine coordinates directly instead, and the check went with it. A related medium finding meant the group commitment could reach zero and derive a challenge from that same point. The other four were data-validation and logic errors, including a network field that could panic a client mid-signing, all detailed in the full audit report.

Why this matters

Nori is building bridge infrastructure on Mina, and the reason it needs a multisig at all is a quirk in the chain: every hard fork or proof-system change forces zkApps built against the old verification key to move to the new one, and a standard multisig would need to be redeployed or brick outright. FROST sidesteps that, since its guarantee lives in the signature scheme, not a proof-system version. Getting that guarantee right took time: Nori has taken longer to reach production than first planned because the team prioritized correctness and safety over a faster timeline, a tradeoff that matters more given how often bridges get exploited industry-wide. Veridise’s audit adds to an existing relationship with the Mina ecosystem that goes back to a 2024 audit of o1js, the TypeScript library o1Labs built for writing zkApps on Mina. Mina Multisig itself is open to the wider Mina developer community, not just Nori: any team building wallet or self-custody tooling on Mina now has an audited FROST implementation to build on.

Karol Podufalski, Founder of Nori, who helped bring the original developers to Veridise, put it this way:

“It gave us a deeper understanding of our own protocol. Developers get closed-minded about their own code after a while. Having auditors go over it, spotting what could get misdiagnosed during development, was critical for us to have that review under the multisig repository.”

Mina Multisig now moves under o1Labs’ stewardship, with Nori as its first production user and Mina positioned to carry the story to its broader community. The six issues in this audit surfaced in a scheduled review, not after the codebase reached production, which is the same standard behind auditing before shipping rather than after.

Working on a similar protocol?

If your codebase overrides a cryptography library’s default challenge computation to match your own chain, check whether that override quietly drops checks the library bundles into serialization, like point-at-infinity rejection. If you want a second pair of eyes before your next deploy, talk to us.

What Did the Mina Multisig Audit Find? The Takeaway

Veridise’s audit of Mina Multisig found six issues, including one high-severity point-at-infinity gap, in the FROST-based signature integration that lets Mina zkApps upgrade safely across protocol changes. All six are fixed. Nori runs the reviewed codebase first in production, with o1Labs stewarding it forward for the wider Mina ecosystem.