SP1 stores multidimensional data in Tensors, where SP1's native Rust verifier failed to check whether the number of stored elements matched the product of the tensor's declared dimensions

Overview Debates Related claims Topics Sources

The SP1 soundness flaw affected native Rust verification in sp1_hypercube, sp1_prover, and sp1_sdk versions 6.0.0 through 6.8.0

A high-severity soundness bug in Succinct's SP1 zero-knowledge proving system exposed Succinct's mainnet Prover Network to invalid execution proofs from third-party provers

On-chain Solidity verifiers for Groth16 and Plonk checks and applications whose proof aggregation ended in Groth16 or Plonk proofs were unaffected by SP1's high-severity soundness bug

Succinct deployed the version 6.8.1 patch for SP1's soundness bug to the mainnet Prover Network, requiring no configuration changes from users requesting network proofs

An attacker could exploit SP1 by supplying proof data with mismatched size labels, causing the native Rust verifier to accept an invalid proof

Succinct stated in GitHub security advisory GHSA-p7v2-jjv3-8p8f that its mainnet Prover Network was the only known deployment affected by a high-severity soundness bug in SP1's proving system

Succinct advised users running native Rust verifiers in SP1 who accept proofs from untrusted provers to upgrade their software to version 6.8.1

Groth16 and Plonk proof checks in SP1 remained safe because they used wrapped proofs with fixed shapes that bypassed prover-controlled tensor formats

Succinct released version 6.8.1, which patched a high-severity soundness bug in SP1, on September 24, 2026, 17 days before publishing GitHub security advisory GHSA-p7v2-jjv3-8p8f on October 11, 2026

Security researcher Spreek identified four unexecuted malicious upgrade contracts deployed against Swell DAO's protocol that could have stolen approximately 2,500 ETH

Swaps using Uniswap v4's Aggregator Hooks feature block-refreshed price quotes, atomic single-transaction settlement, and preserve existing token approvals

Uniswap routing guidance updated on October 16, 2026, states that Uniswap's router requires manual allowlisting for hooks using specific permissions, leaving security guarantees outside the guidance's scope

Under Alpenglow's Votor mechanism on Solana, validators send BLS-signed vote messages directly off-chain rather than submitting votes as block transactions

Anza is researching a post-quantum upgrade named Quantumglow to introduce hash-based signatures while preserving 150-millisecond finality

ECDSA authenticates blockchain account ownership by generating digital signatures on transactions across a distributed ledger

ECDSA stands for Elliptic Curve Digital Signature Algorithm

Echo Protocol responded to the May 2026 exploit on its Monad deployment by pausing cross-chain activity, updating smart contracts, and burning 955 eBTC traced to the attacker

TokenLogic's October 15, 2026 proposal specifies zero swap fees for the permissioned GHO Stability Module on Avalanche while leaving contract addresses for Avalanche USAT, waUSAT, reserve, commercial counterparties, and pricing strategies unspecified

Security firm Certora completed a formal specification and verification of the market contract for Templar, a lending protocol deployed on NEAR Protocol, on March 30, 2026.

On October 16, 2026, NEAR Protocol announced plans to apply AI-assisted formal verification to its network protocol, core smart contracts, and developer tools using Lean.