The Race to Build JAM: 43 Teams, 15 Languages, and Polkadot's Next Protocol

I opened the JAM testnet dashboard on a Tuesday afternoon expecting the usual incremental progress report. Instead I found something genuinely unusual: 43 independent teams, working in 15 different programming languages, all racing to build the exact same protocol from the same specification. Not a hackathon. Not a grant round. A multi-year competition with 10 million DOT on the line and the future architecture of Polkadot at stake.

That is not how blockchain protocols are typically built.

Key Metrics at a Glance

What JAM Actually Is

JAM stands for Join Accumulate Machine, the protocol Polkadot's Relay Chain is evolving into. Today the Relay Chain checks parachain blocks, coordinates validators, runs governance, and routes cross-chain messages. JAM keeps all of that while widening what the network can actually execute.

Under JAM, almost any computation can operate as a service on Polkadot's shared infrastructure. A blockchain is one kind of JAM service. So is a privacy system. An AI inference engine or a file storage layer could just as easily be another. The key shift is from "validate parachains" to "host arbitrary services" on shared validator infrastructure.

Gavin Wood is one of a very small number of people to have formally specified two major blockchain protocols. He wrote Ethereum's Yellow Paper in 2014. In 2024 he released JAM's equivalent, the Gray Paper, written in the same rigorous mathematical style. Every one of the 43 competing teams builds from it.

The Prize Structure and Why Competition Matters

The Web3 Foundation set aside a 10 million DOT prize pool plus 100,000 KSM for the JAM Implementer's Prize. Teams earn milestone payments as they pass conformance tests verifying their implementation matches the Gray Paper exactly.

The language categories span from Category A — high-performance systems languages including C, C++, Rust, and Go — down to Category E, which includes Brainfuck and Whitespace. Those last two are not jokes. They are deliberately included to stress-test the protocol's resilience.

If one company writes all the software behind a network in one language, a serious bug threatens the entire network at once. Spread the same protocol across 43 independent teams in 15 different languages, and a bug in one implementation is unlikely to exist in the rest. Ethereum arrived at this same conclusion after its early years and gradually pushed for multiple independent client implementations. Polkadot is building that diversity into JAM from day one.

Who Is Building and What They Are Building

Teams are building in Rust, Go, OCaml, Zig, TypeScript, Haskell, Java, Python, and more. Every implementation must pass conformance tests that verify it behaves exactly as the Gray Paper specifies.

The Polkadot Technical Fellowship — a decentralized body of senior protocol developers — judges submissions. Final prize payment is held until the Fellowship formally ratifies JAM protocol version 1.0, so every team is working toward the same externally judged finish line.

The standout result so far belongs to JamZig, the Zig implementation led by developer Boy Maas. Zig is a low-level systems language most developers outside hardware work have never touched. Maas used it to build a proof of concept that runs Solana's Virtual Machine inside JAM, contracts calling across that boundary included. His team is now building Polana, aimed at bringing Solana's full developer toolchain into the JAM ecosystem.

That is the core claim being tested: if JAM can host essentially any computation as a service, then porting an entirely different blockchain's execution environment inside it should work. And it did.

The Testnet: Toaster and Tart

Since January 2026, all 43 teams share a public testnet to check their implementations against real network conditions rather than isolated machines. Two environments are active:

• Toaster: The primary testnet for running implementations
• Tart (Testing, Analysis and Research Telemetry): The analytics and benchmarking environment

Teams use both to confirm their implementations handle the full protocol requirements and to benchmark performance against each other. Anyone outside the competition curious about building on JAM can start exploring there.

Competitive Landscape: Protocol Implementation Contests

JAM's approach is unique in scale and structure. No other protocol has launched with 43 independent teams competing from a single formal specification. Ethereum's client diversity was built reactively over years. JAM is engineering it proactively before mainnet.

Strategic Implications

The JAM competition signals a maturation in how blockchain protocols are built. Instead of a single reference implementation that becomes the de facto standard, Polkadot is distributing the risk of implementation failure across dozens of independent teams.

For validators, this means more client choices and reduced risk of correlated failures. For developers, it means the protocol specification is the source of truth, not any single codebase. For the ecosystem, it means JAM's mainnet will launch with a level of implementation diversity that took Ethereum nearly a decade to achieve.

The open question is timing. Gavin Wood has acknowledged that JAM ranks among the most complex protocol upgrades Polkadot has taken on. With ~15 of 43 teams having submitted first milestones by January 2026, the Q3-Q4 mainnet target is ambitious but not impossible.

TL;DR

• What: 43 teams are competing to implement JAM, Polkadot's next protocol, in 15 languages
• How: Teams build from the Gray Paper specification and pass conformance tests for milestone payments
• Edge: Hardware-agnostic approach with built-in implementation diversity from day one
• Impact: JamZig already proved Solana's VM runs inside JAM, validating the "any computation as a service" claim
• Watch: Mainnet governance proposals targeted for Q3-Q4 2026; milestone acceleration signals real progress

Sources

• Polkadot Academy: The Race to Build JAM
• JAM Gray Paper
• Web3 Foundation: JAM Implementer's Prize
• Polkadot Technical Fellowship

Gemma Nguyen is TotesTek's Content Lead and Journalist, covering the intersection of decentralized infrastructure, protocol development, and the competitive dynamics that make both sustainable.