Protocol / Analysis
Nockchain's AI lane went live in August and capacity followed. The team says demand is now the constraint.
Logos took a longer road than first planned. It was roadmapped for June, moved three times and blocked by its maintainers pending a reviewed fork-choice fix, then went live on Aug 14. Mining capacity followed. The protocol meant to bring compute demand into the lane is listed for Q4 2026, and the Lockstep paper published in September sets out reproducible inference.
Nockchain’s AI lane is up and running. The live roadmap lists “AI Compute Network Launch” for August 2026, and it is marked completed.2 Back in June, the roadmap listed an “AI Compute Market Launch” for June 2026.1
The upgrade behind it, Logos, added a matrix-multiplication puzzle that Pearl miners also run.21 It sits alongside the ZK proof-of-work puzzle.21 This means miners now have two ways to win blocks on Nockchain.
The road from June to block 126,000
The first Logos pull request opened on July 18.22 It set activation at block 114,300, with a July 31 target.22 Logan Allen announced that height on July 20: “Logos and AI inference mining are proposed to activate at block 114,300, targeted for the end of this month.”3
Five days later, the @nockchain account moved the target: “Mainnet activation retargets to block 122,000 unless issues are found.”4 The Logos code on GitHub never carried that height, and it kept 114,300 until August 11.510
On July 28, a reviewer described an attack on the new fork-choice rule in a comment on the Logos pull request.5 The reviewer wrote that activation should wait for a reviewed fix.5
The maintainers’ own write-up followed on July 29: “Activation must remain blocked pending a reviewed fork-choice fix.”23 The document now lists the issue as resolved.6 It says the fix is a rule that credits each block with the expected work at its own puzzle’s target.6
The final date came on August 10 at 20:58 UTC: “The new AI Compute Network goes live on Friday (8/14) at Block 126,000. Code is being merged today.”7 Block 126,000 arrived at 02:05 UTC on August 14.8 The first AI-mined block, 126,859, followed at 16:27 UTC.9
The split between the two puzzles changed along the way. Until August 11, the code aimed for about 60% AI blocks.10 The commit that set the final height changed the target to about 30% AI and 70% ZK.10 A month later, the Anthropos upgrade at block 147,500 flipped it to 70% AI and 30% ZK.11
Blocks are landing close to that target. Over the seven days to 12:06 UTC on October 10, AI puzzles won 69.6% of 3,971 blocks, counted by puzzle type in Nockscan’s prover statistics.12
Capacity followed
Nockscan measures the AI lane in multiply-accumulates per second. Over a trailing seven-day window, it read about 0.06 EMAC/s on August 16, two days after activation.13
Nockscan restarted the series at block 154,500, when a coordinated upgrade re-anchored both difficulty lanes.1311 Readings from before that block can’t be compared with readings after it.13 Within the new series, the same seven-day measure rose from 12.5 EMAC/s at block 154,530 on September 26 to 23.0 EMAC/s at 12:45 UTC on October 10.13
Three weeks into the lane, the team described the next problem in a post on September 4: “Capacity is no longer the constraint. Demand is: turning it into inference someone paid for.”14
Routing and Lockstep
The roadmap’s plan for demand is the “Useful Inference Routing Protocol”.2 It is listed for Q4 2026 with status current.2 The roadmap describes it as “A major milestone that funnels compute demand into the AI Compute Network.”2 It is absent from the Internet Archive’s June 16 capture of the roadmap and appears in the next capture, on September 30.124
The team has also shared new research. On September 10, @nockchain published Lockstep, a paper and code release on verifiable inference.15
The 27-page paper defines a canonical inference contract for dense and mixture-of-experts transformer models.16 Under that contract, an optimized GPU engine and a portable CPU reference must return bit-identical outputs.16 The paper reports identical digests from the same source on Hopper, Ada and Blackwell GPUs.16
The serving implementation is a vLLM plugin that the paper describes as proprietary.16 The public release carries the specification, CPU references, a Lean formalization and conformance kits.1516 The paper also specifies a sampled-replay audit, with its primitives gated and integration disabled.16 It is open about its own limit: “Canonical execution is not a cryptographic proof”.16
Every use of “routing” in the paper refers to expert routing inside mixture-of-experts models.16 The paper never mentions Nockchain or proof-of-work.16 In Nocktane’s reading, the paper specifies the inference function itself and leaves the routing of paid requests to other work.
The announcement places Lockstep at the service layer, where “it can give customers and auditors a precise meaning for the inference work being routed among independent providers,” and adds that “the integration is not live and Lockstep is not currently a Nockchain consensus rule.”15 Nocktane found no published specification for the routing protocol as of October 10. That specification is the next piece to watch for.
The usefulness debate
In June, Abhinaba Basu posted “The Usefulness Gap in Proof-of-Useful-Work” to arXiv.17 The paper studies Pearl. Its headline finding is that Pearl’s network “produces zero useful AI computation.”17
The paper says Pearl’s verifier checks that a matrix multiplication was computed correctly.17 According to the paper, the verifier does not check whether the matrices came from an AI model, so miners can earn rewards on random matrices.17 An open-source miner Basu wrote had 44 shares accepted by a pool using random matrices.17
Logan Allen answered on September 2: “I didn’t find this paper’s methodology to be compelling.”18 The post argues that networks like this start out farmed by GPUs chasing the subsidy.18 It adds that the pieces needed for useful inference routing already exist and need a small amount of further work.18 On October 4, Allen described Pearl compatibility as a starting move: “Bootstrapping our AI puzzle with Pearl merge-mining compatibility was a tactic chosen to broaden mining distribution and improve initial network security.”19
Nockchain’s AI puzzle is Pearl-compatible by design.21 The Logos specification describes its matrices as “miner-chosen (arbitrary model, Pearl parity)”.21 Merge-mining is near universal in recent blocks: of the 7,043 AI blocks among the last 10,000 blocks, 7,042 declare a Pearl merge-mining commitment (Nockscan, 12:47 UTC on October 10).20
The paper’s argument is therefore relevant to Nockchain’s lane too. That link is Nocktane’s inference. The paper itself never mentions Nockchain.
Next on the roadmap is the routing protocol. The roadmap describes it as the milestone that “funnels compute demand into the AI Compute Network” and lists it for Q4 2026.2 Our tracker will record whether that date holds.
Sources24Show
- 1nockchain.org/roadmap, Wayback snapshot of Jun 16, 2026
- 2nockchain.org/roadmap (live page)
- 3Logan, "Announcing National Compute" (X article, Jul 20, 2026)
- 4Nockchain, "Logos Upgrade: Testnet Launch & Bug Bounty" (X article, Jul 25, 2026)
- 5nockchain/nockchain, PR #145 (Logos) and conversation comments
- 6nockchain/nockchain, crates/ai-pow/docs/2026-07-29_TIME_BANKED_FORK_EXPLOIT.md
- 7Nockchain, post naming block 126,000 (Aug 10, 2026)
- 8Nockscan API, block 126,000
- 9Nockscan API, block 126,859
- 10nockchain/nockchain, commit 9e98a16790 (Logos cadence set to 30/70)
- 11nockchain/nockchain, changelog/protocol/017-anthropos.md
- 12Nockscan API, prover-stats over 7 days
- 13Nockscan API, ai-pow-rate (7-day window) and its OpenAPI description
- 14Nockchain, post on AI compute (Sep 4, 2026)
- 15Nockchain, "Lockstep: verifiable inference at full speed, with a fully deterministic transcript" (X article, Sep 10, 2026)
- 16Lockstep: Bit-Exact, Verifiable Transformer Inference at Parity Across Devices, for Dense and Mixture-of-Experts Models (v0.2.0)
- 17Abhinaba Basu, "The Usefulness Gap in Proof-of-Useful-Work" (arXiv 2606.04819)
- 18Logan, post on the Usefulness Gap paper (Sep 2, 2026)
- 19Logan, post on Pearl merge-mining (Oct 4, 2026)
- 20Nockscan API, merge-mining
- 21nockchain/nockchain, changelog/protocol/016-logos.md
- 22nockchain/nockchain, PR #143 (first Logos proposal, opened Jul 18, 2026)
- 23nockchain/nockchain, 2026-07-29_TIME_BANKED_FORK_EXPLOIT.md as first committed (2056cabc1c)
- 24nockchain.org/roadmap, Wayback snapshot of Sep 30, 2026
New to a term? The glossary explains it. Spotted an error? Write to info@nocktane.com.