Implementation · Pearl proof-of-useful-work blockchain

Evidence & limits

On this page

R3In production for checking matrix-multiplication work proofs for blockchain consensus

R3 for checking claims of matrix-multiplication work in blockchain consensus. The network is live, but no independent security evaluation exists, and the capacity-bounding use in Proofs of useful work for capacity accounting is not demonstrated.

Assessed use: checking matrix-multiplication work proofs for blockchain consensus

Rubric assessment

  • R1 met: the protocol, verifier and hardness assumption are specified 1, building on a published construction 5.
  • R2 met: code for a full node, a GPU miner and a proof-of-work circuit and verifier is public 4. Pearl reports running it on H200 GPUs alongside LLM serving 2, against miners who try to win more often than honest work allows 1.
  • R3 met for the narrow claim, as production software that is available and relied on by other parties. Pearl reports that the chain went live when the node code became public 2 4. The repository supports mainnet, and no release up to v1.2.1 is labelled alpha, beta or preview 4. An independent study counted 8,012 online workers among the top 15 miners of one mining pool in May 2026, ran experiments on mainnet, and had shares accepted by that pool, whose acceptance rests on the protocol's verification 6.
  • R4 not met: the README mentions no audit 4, and that study measures how the network is used rather than auditing or attacking the protocol 6. As of September 2026 no independent security evaluation has been published.
Gaps to the next level
  • An independent public security evaluation of the protocol or its implementation.
  • For verification use: a demonstration that proof rates can bound the spare capacity of declared hardware.

Assessed 2026-10-08 against rubric v1.1.

Evidence

  • A live network. Pearl's integer whitepaper states that the chain became live when the node code was made public 2. The repository supports mainnet and test networks, and has published release v1.2.1 4.
  • A serving benchmark. Pearl reports a benchmark on four H200 GPUs comparing Llama 3.3 70B with its "two-for-one" Pearl-certified variant, which re-implements a layer with a new quantisation mechanism 2:
    • the variant reached 17,206.26 tokens per second with pipeline parallelism, and 18,291.66 with four-way data parallelism;
    • the original bf16 model reached at most 15,269.81 tokens per second, and ran out of memory with four-way data parallelism;
    • MMLU scores were close: 0.8180 to 0.8198 for the variant against 0.8193 to 0.8198 2.
  • Kernel overhead. In a separate benchmark against stock serving engines, Pearl reports 5.08% end-to-end overhead for Llama 70B with four-way data parallelism on four H200 GPUs, and 3.9% for DeepSeek V3.2 with eight-way data parallelism plus expert parallelism on eight H200 GPUs 3. These are developer-reported measurements of its integer proof-of-useful-work kernel.
  • The underlying theory. The construction behind Pearl proves a multiplicative overhead of 1 + o(1) over naive matrix multiplication 5. Pearl's FP8 specification states a "1 + o(1) factor" overhead, without a measured percentage 1.
  • Independent measurement. Basu measured Pearl's mainnet, running the integer scheme, in May 2026, counting 8,012 online workers among the top 15 miners on the AlphaPool mining pool, which Basu estimates to hold about 21% of network hashrate. String analysis suggests that the dominant mining software, from a third party, contains no inference code and generates matrices from random seeds. Random matrices passed verification in the study's tests, and a mining pool accepted shares mined with them 6.

Limitations

Known speedups. Pearl documents known mining speedups and the checks against them 1. It treats faster honest kernels or hardware as outside the threat model 1.

Hardness assumption. Security rests on an informal hardness assumption specific to quantised, noised matrices 1.

Usefulness is not verified. Verification checks the multiplication, not where the matrices came from 6.

Benchmark caveats. The benchmark compares a Pearl-certified model with the original model, and reports no run of the same certified model without mining 2.

Fit to verification. Pearl's proofs show that work was performed, not that no other work ran. Attestable, which proposes proof-of-work accounting for AI agreements, notes that "a proof of some computation is not a proof of all computation", and that bounding spare capacity needs a credible estimate of the compute available 8.

Known flaws

Blockers

  • Built for consensus rather than capacity bounding; verifying that declared hardware has no spare capacity would also need a credible compute estimate.

  • Performance figures are provider-reported, and the benchmark reports no baseline of the certified model without mining.

  • Bit-exact verification depends on reproducing GPU arithmetic deterministically.

Search

Full search page