Build a JAM service
on a mixed testnet.

JAM is many clients running many services. Neither is proven until they run together. Start a test net of any mix of clients, run a real JAM service on it, and read a verdict every client team can check: one head, shared finality, and the service's state byte-identical on every node.

Start here Bring your client

Where it runs today

lasair6: six lasair validators, GRANDPA finality, the exchange on top, and JIP-3 telemetry from every node.

pj6: six PolkaJam validators and no lasair; the exchange deploys its service at runtime through the chain's Bootstrap service.

lasair-pj: three lasair and three PolkaJam validators on one chain, one GRANDPA; the exchange's state is byte-identical on both clients.

Each passes jamswap's soak: one head, finality advancing everywhere with the same hash, trades settling, the service's state identical on every node. Both clients pass the one-command JIP-2 check the exchange needs from a node.

Tracks

The pieces

jamswap: an order-book exchange that runs as a JAM service, and the harness that runs it on nets of any mix of clients. Its collaboration guide is the short version of this section.

observability: the stack every net reports into (MIT). Learning Observability teaches reading it.

The standards between clients: the Graypaper, JAMNP-S, and the JIPs (node RPC, telemetry, chain specs, keys). jamswap is a JAM service: running it or reading its code is outside the JAM Prize's clean-room rules, which cover implementation code.