Independent · Pearl Network · PRL
KeshiNetwork intelligence for Pearl.
Independent community infrastructure for Pearl Network — not affiliated with Pearl Research Labs.
Keshi runs its own pearld node and Blockbook indexer, computes every metric from its own index, and publishes the source, the formula and the window behind each number.
- Height
- Block age
- from the miner-set header timestamp
- PoUW work rate
- Difficulty
- WTEMA, adjusts every block
- Block subsidy
- no halvings; smooth decay
EH/s — matmul attempts per second — a difficulty-derived consensus measure, not a measure of AI computation performed. Header timestamps are miner-set with a ±5 minute consensus tolerance. This is block age, not network latency.
The measurement caveat
What is proof of useful work?
Pearl's pitch is that the electricity securing the chain could also be doing something. Keshi treats that as a claim about capability, and keeps it separate from what is observed.
Pearl secures its chain with proof of useful work. Instead of hashing a nonce until a header falls below a target, a Pearl miner performs tiled INT8 matrix multiplications with deterministic low-rank noise, then searches for a tile whose BLAKE3 commitment satisfies the consensus predicate. The winning work is wrapped in a recursive zero-knowledge proof and carried in the block as a certificate, versioned rather than nonced. Blocks arrive on a 194-second target and difficulty adjusts with every one of them.
The appeal is obvious: the same GEMM kernels that secure the chain are the kernels that run neural networks, so the electricity could in principle buy two things at once. That is a statement about protocol capability. Whether it also describes what miners are actually doing is a separate question, and it is the question Keshi refuses to blur.
Nothing on-chain proves that any particular block’s matrices served a real workload. The predicate accepts any matrices that satisfy it — an acknowledged property of the design, examined empirically in arXiv:2606.04819 and unrebutted as of 2026-08-02. So Keshi labels the security throughput “PoUW work rate” and footnotes every EH/s figure as matmul attempts per second: a difficulty-derived consensus measure, not a measure of AI computation performed. If verifiable workload attestation ever exists, we will publish the methodology first and the number second.
EH/s on Keshi means matmul attempts per second — a difficulty-derived consensus measure, not a measure of AI computation performed.
docs/metrics.md — language policy, binding on every surface
Elsewhere
The rest of the Pearl ecosystem
Keshi never scrapes another explorer's figures — where these sites disagree with us, the difference is usually the estimator window. All of these links leave Keshi.
Pearl Research Labs
Keshi is not affiliated with any of them. Where a figure here differs from a figure there, check the window before assuming either is wrong — published Pearl work rates for the same chain state have diverged by up to 26% purely from that choice.