Release v0.9.0

The engine's deployable build.

Node binaries and every chain runtime are not built here — they are
pinned in config/versions.env
and downloaded by ppn fetch from the release of the repo that
builds each one. This release only carries what has no upstream home.

Docker

docker run -p 10000-10030:10000-10030 -p 8545:8545 paritytech/previewnet-engine:v0.9.0

Upstream Pins

• bulletin: v0.0.26-paseo
• individuality: v0.3.3 — resolved from latest at release time
• paseo-runtimes: v2.4.4
• polkadot-sdk: polkadot-weekly2026w41-rc2 — resolved from latest at release time
• web3-storage: v0.4.1-paseo — resolved from latest at release time
• doppelganger (bite only): v0.2.1

Per-chain bindings: networks/previewnet.json

DotNS is not built here either — since dotns v0.5.6-rc1 its release carries
the pallet-revive genesis, and ppn fetch takes it from the tag
config/versions.env pins.

Device Uniqueness Backend

Not built here — ppn fetch takes the dub binary from
device-uniqueness-backend-community's
own release at the tag config/versions.env pins, and every service is a
--role of it: dub-api (all-in-one), device-attestation-chain-writer,
registration-queue and invite-tickets-pool.

Fork bundles

Not here: they live on the rolling bites
pre-release, refreshed nightly, which is where ppn fork fetch-bundle reads them.

What's Changed

• DUB to v0.6.0 by @Zebedeusz in #49

New Contributors

• @Zebedeusz made their first contribution in #49

Full Changelog: v0.8.0...v0.9.0

Release v0.8.0

The engine's deployable build.

Node binaries and every chain runtime are not built here — they are
pinned in config/versions.env
and downloaded by ppn fetch from the release of the repo that
builds each one. This release only carries what has no upstream home.

Docker

docker run -p 10000-10030:10000-10030 -p 8545:8545 paritytech/previewnet-engine:v0.8.0

Upstream Pins

• bulletin: v0.0.26-paseo
• individuality: v0.3.3 — resolved from latest at release time
• paseo-runtimes: v2.4.4
• polkadot-sdk: polkadot-weekly2026w40-rc1 — resolved from latest at release time
• web3-storage: v0.4.1-paseo — resolved from latest at release time
• doppelganger (bite only): v0.2.1

Per-chain bindings: networks/previewnet.json

DotNS is not built here either — since dotns v0.5.6-rc1 its release carries
the pallet-revive genesis, and ppn fetch takes it from the tag
config/versions.env pins.

Device Uniqueness Backend

Not built here — ppn fetch takes the dub binary from
device-uniqueness-backend-community's
own release at the tag config/versions.env pins, and every service is a
--role of it: dub-api (all-in-one), device-attestation-chain-writer,
registration-queue and invite-tickets-pool.

Fork bundles

Not here: they live on the rolling bites
pre-release, refreshed nightly, which is where ppn fork fetch-bundle reads them.

What's Changed

• Reset HRMP&DMP on every bite by @andrzejSulkowski in #40
• Add ppn version and rewrite the README around use cases by @mordamax in #37

Full Changelog: v0.7.0...v0.8.0

Release v0.7.0

The engine's deployable build.

Node binaries and every chain runtime are not built here — they are
pinned in config/versions.env
and downloaded by ppn fetch from the release of the repo that
builds each one. This release only carries what has no upstream home.

Docker

docker run -p 10000-10030:10000-10030 -p 8545:8545 paritytech/previewnet-engine:v0.7.0

Upstream Pins

• bulletin: v0.0.26-paseo
• individuality: v0.3.3 — resolved from latest at release time
• paseo-runtimes: v2.4.4
• polkadot-sdk: polkadot-weekly2026w39-rc2 — resolved from latest at release time
• web3-storage: v0.4.1-paseo — resolved from latest at release time
• doppelganger (bite only): v0.2.1

Per-chain bindings: networks/previewnet.json

DotNS is not built here either — since dotns v0.5.6-rc1 its release carries
the pallet-revive genesis, and ppn fetch takes it from the tag
config/versions.env pins.

Device Uniqueness Backend

Not built here — ppn fetch takes the dub binary from
device-uniqueness-backend-community's
own release at the tag config/versions.env pins, and every service is a
--role of it: dub-api (all-in-one), device-attestation-chain-writer,
registration-queue and invite-tickets-pool.

Fork bundles

Not here: they live on the rolling bites
pre-release, refreshed nightly, which is where ppn fork fetch-bundle reads them.

What's Changed

• Bite args to set parachain cores and collators by @andrzejSulkowski in #39
• Run a TURN/STUN relay for DUB by @mordamax in #38

New Contributors

• @andrzejSulkowski made their first contribution in #39

Full Changelog: v0.6.0...v0.7.0

Release v0.6.0

The engine's deployable build.

Node binaries and every chain runtime are not built here — they are
pinned in config/versions.env
and downloaded by ppn fetch from the release of the repo that
builds each one. This release only carries what has no upstream home.

Docker

docker run -p 10000-10030:10000-10030 -p 8545:8545 paritytech/previewnet-engine:v0.6.0

Upstream Pins

• bulletin: v0.0.26-paseo
• individuality: v0.3.2 — resolved from latest at release time
• paseo-runtimes: v2.4.4
• polkadot-sdk: polkadot-weekly2026w38-rc1 — resolved from latest at release time
• web3-storage: v0.4.1-paseo — resolved from latest at release time
• doppelganger (bite only): v0.2.1

Per-chain bindings: networks/previewnet.json

DotNS is not built here either — since dotns v0.5.6-rc1 its release carries
the pallet-revive genesis, and ppn fetch takes it from the tag
config/versions.env pins.

Device Uniqueness Backend

Not built here — ppn fetch takes the dub binary from
device-uniqueness-backend-community's
own release at the tag config/versions.env pins, and every service is a
--role of it: dub-api (all-in-one), device-attestation-chain-writer,
registration-queue and invite-tickets-pool.

Fork bundles

Not here: they live on the rolling bites
pre-release, refreshed nightly, which is where ppn fork fetch-bundle reads them.

What's Changed

• Polkadot fork: make the seeded runtime upgrade actually enact by @mordamax in #14
• chore: pin DotNS to v0.6.0 by @re-gius in #16
• Bump Bulletin release to v0.0.26-paseo by @csmnprschv in #18
• Add a second code owner by @csmnprschv in #19
• Bump toml from 3.0.0 to 4.2.0 by @dependabot[bot] in #15
• Drop --experimental-webrtc by @csmnprschv in #22
• Select the relay runtime by profile by @csmnprschv in #20
• Move to Node.js 24 by @csmnprschv in #23
• Boot dotNS v0.8.0 from genesis by @re-gius in #24
• Pack bite snapshots with pigz when available by @csmnprschv in #25
• Give a bitten fork a DHT of its own by @csmnprschv in #26
• Put a bitten relay's Asset Hub staking client in Buffered by @csmnprschv in #28
• Let a bite take a parachain's state from a local node by @csmnprschv in #27
• Give the IPFS gateway a health probe it can pass by @csmnprschv in #29
• Set Bulletin's bitswap and transaction-storage log targets to trace by @csmnprschv in #30
• Guard the dashboard against unhandled errors by @csmnprschv in #31
• Endow accounts with 10M instead of 1M by @csmnprschv in #32
• Install the latest polkadot-cli by @csmnprschv in #34
• Revert "Give a bitten fork a DHT of its own (#26)" by @csmnprschv in #35
• Name the artifact npm_publish_automation should take by @csmnprschv in #36

New Contributors

• @csmnprschv made their first contribution in #18
• @dependabot[bot] made their first contribution in #15

Full Changelog: v0.5.0...v0.6.0

Release v0.5.0

The engine's deployable build.

Node binaries and every chain runtime are not built here — they are
pinned in config/versions.env
and downloaded by ppn fetch from the release of the repo that
builds each one. This release only carries what has no upstream home.

Docker

docker run -p 10000-10030:10000-10030 -p 8545:8545 paritytech/previewnet-engine:v0.5.0

Upstream Pins

• bulletin: v0.0.23-paseo
• individuality: v0.3.1 — resolved from latest at release time
• paseo-runtimes: v2.4.4
• polkadot-sdk: polkadot-weekly2026w35-rc1 — resolved from latest at release time
• web3-storage: v0.4.1-paseo — resolved from latest at release time
• doppelganger (bite only): v0.2.1

Per-chain bindings: networks/previewnet.json

DotNS is not built here either — since dotns v0.5.6-rc1 its release carries
the pallet-revive genesis, and ppn fetch takes it from the tag
config/versions.env pins.

Device Uniqueness Backend

Not built here — ppn fetch takes the dub binary from
device-uniqueness-backend-community's
own release at the tag config/versions.env pins, and every service is a
--role of it: dub-api (all-in-one), device-attestation-chain-writer,
registration-queue and invite-tickets-pool.

Fork bundles

Not here: they live on the rolling bites
pre-release, refreshed nightly, which is where ppn fork fetch-bundle reads them.

What's Changed

• Fork Polkadot with People and Bulletin, runtimes authorized at bite time by @mordamax in #12

Full Changelog: v0.4.0...v0.5.0

Release v0.4.0

The engine's deployable build.

Node binaries and every chain runtime are not built here — they are
pinned in config/versions.env
and downloaded by ppn fetch from the release of the repo that
builds each one. This release only carries what has no upstream home.

Docker

docker run -p 10000-10030:10000-10030 -p 8545:8545 paritytech/previewnet-engine:v0.4.0

Upstream Pins

• bulletin: v0.0.23-paseo
• individuality: v0.3.1 — resolved from latest at release time
• paseo-runtimes: v2.4.4
• polkadot-sdk: polkadot-weekly2026w35-rc1 — resolved from latest at release time
• web3-storage: v0.4.1-paseo — resolved from latest at release time
• doppelganger (bite only): v0.2.1

Per-chain bindings: networks/previewnet.json

DotNS is not built here either — since dotns v0.5.6-rc1 its release carries
the pallet-revive genesis, and ppn fetch takes it from the tag
config/versions.env pins.

Device Uniqueness Backend

Not built here — ppn fetch takes the dub binary from
device-uniqueness-backend-community's
own release at the tag config/versions.env pins, and every service is a
--role of it: dub-api (all-in-one), device-attestation-chain-writer,
registration-queue and invite-tickets-pool.

Fork bundles

Not here: they live on the rolling bites
pre-release, refreshed nightly, which is where ppn fork fetch-bundle reads them.

What's Changed

• bulletin: promote HOP at half retention; drop slot-based authoring by @karolk91 in #11
• Resolve PPN_SECRETS_FILE where custom processes can see it by @mordamax in #13

New Contributors

• @karolk91 made their first contribution in #11

Full Changelog: v0.3.0...v0.4.0

Release v0.3.0

The engine's deployable build.

Node binaries and every chain runtime are not built here — they are
pinned in config/versions.env
and downloaded by ppn fetch from the release of the repo that
builds each one. This release only carries what has no upstream home.

Docker

docker run -p 10000-10030:10000-10030 -p 8545:8545 paritytech/previewnet-engine:v0.3.0

Upstream Pins

• bulletin: v0.0.23-paseo
• individuality: v0.3.1 — resolved from latest at release time
• paseo-runtimes: v2.4.4
• polkadot-sdk: polkadot-weekly2026w35-rc1 — resolved from latest at release time
• web3-storage: v0.4.1-paseo — resolved from latest at release time
• doppelganger (bite only): v0.2.1

Per-chain bindings: networks/previewnet.json

DotNS is not built here either — since dotns v0.5.6-rc1 its release carries
the pallet-revive genesis, and ppn fetch takes it from the tag
config/versions.env pins.

Device Uniqueness Backend

Not built here — ppn fetch takes the dub binary from
device-uniqueness-backend-community's
own release at the tag config/versions.env pins, and every service is a
--role of it: dub-api (all-in-one), device-attestation-chain-writer,
registration-queue and invite-tickets-pool.

Fork bundles

Not here: they live on the rolling bites
pre-release, refreshed nightly, which is where ppn fork fetch-bundle reads them.

What's Changed

• Move what can move to GitHub-hosted runners by @mordamax in #4
• Give each service its own dot config root by @mordamax in #7
• Keep the two network-spawning jobs on separate runner pools by @mordamax in #6
• Cleanup hardcoded file path by @mordamax in #5
• Point DotnsGateway at the controller when a release has no dispatcher by @re-gius in #8
• Last audit items before going public by @mordamax in #9
• Open the README with installing PPN, not cloning it by @mordamax in #10

New Contributors

• @re-gius made their first contribution in #8

Full Changelog: v0.2.0...v0.3.0

Release v0.2.0

The engine's deployable build.

Node binaries and every chain runtime are not built here — they are
pinned in config/versions.env
and downloaded by ppn fetch from the release of the repo that
builds each one. This release only carries what has no upstream home.

Docker

docker run -p 10000-10030:10000-10030 -p 8545:8545 paritytech/previewnet-engine:v0.2.0

Upstream Pins

• bulletin: v0.0.23-paseo
• individuality: v0.3.0 — resolved from latest at release time
• paseo-runtimes: v2.4.4
• polkadot-sdk: polkadot-weekly2026w35-rc1 — resolved from latest at release time
• web3-storage: v0.4.1-paseo — resolved from latest at release time
• doppelganger (bite only): v0.2.1

Per-chain bindings: networks/previewnet.json

DotNS is not built here either — since dotns v0.5.6-rc1 its release carries
the pallet-revive genesis, and ppn fetch takes it from the tag
config/versions.env pins.

Device Uniqueness Backend

Not built here — ppn fetch takes the dub binary from
device-uniqueness-backend-community's
own release at the tag config/versions.env pins, and every service is a
--role of it: dub-api (all-in-one), device-attestation-chain-writer,
registration-queue and invite-tickets-pool.

Fork bundles

Not here: they live on the rolling bites
pre-release, refreshed nightly, which is where ppn fork fetch-bundle reads them.

What's Changed

• Previewnet is not special when forking by @mordamax in #1
• Publish the npm packages as part of the release by @mordamax in #2
• Fold npm publishing into Release by @mordamax in #3

New Contributors

• @mordamax made their first contribution in #1

Full Changelog: v0.1.0...v0.2.0

Release v0.1.0

The engine's deployable build.

Node binaries and every chain runtime are not built here — they are
pinned in config/versions.env
and downloaded by ppn fetch from the release of the repo that
builds each one. This release only carries what has no upstream home.

Docker

docker run -p 10000-10030:10000-10030 -p 8545:8545 paritytech/previewnet-engine:v0.1.0

Upstream Pins

• bulletin: v0.0.23-paseo
• individuality: v0.3.0 — resolved from latest at release time
• paseo-runtimes: v2.4.4
• polkadot-sdk: polkadot-weekly2026w35-rc1 — resolved from latest at release time
• web3-storage: v0.4.1-paseo — resolved from latest at release time
• doppelganger (bite only): v0.2.1

Per-chain bindings: networks/previewnet.json

DotNS is not built here either — since dotns v0.5.6-rc1 its release carries
the pallet-revive genesis, and ppn fetch takes it from the tag
config/versions.env pins.

Device Uniqueness Backend

Not built here — ppn fetch takes the dub binary from
device-uniqueness-backend-community's
own release at the tag config/versions.env pins, and every service is a
--role of it: dub-api (all-in-one), device-attestation-chain-writer,
registration-queue and invite-tickets-pool.

Fork bundles

Not here: they live on the rolling bites
pre-release, refreshed nightly, which is where ppn fork fetch-bundle reads them.

Full Changelog: https://github.com/paritytech/previewnet-engine/commits/v0.1.0

Fork bundles (rolling)

Fork bundles, refreshed nightly. Not a versioned release — this tag is
replaced in place, and ppn fork fetch-bundle reads it directly
(PPN_BITE_TAG in config/versions.env).

Refreshed: 2026-10-08 18:52 UTC from 3e206c9

Bundle	Size
fork-bundle-paseo-next-v2.tar.gz	684M
fork-bundle-previewnet.tar.gz	131M