Octez v20.0~rc1 has been published

:mega: A release candidate for Octez v20.0 (v20.0~rc1) is available! If this release candidate proves to be stable, it will be released as version 20.0.

We invite you to test this release candidate on Oxfordnet, Ghostnet or the upcoming Parisnet test networks, and to report any issue on Issues · Tezos / tezos · GitLab so that they can be addressed in time for the release of 20.0.

This release candidate contains a new version (V12) of the protocol environment, which is the set of functions that protocols can call.

This new version of the protocol environment is required by Paris B, part of the Paris protocol upgrade proposal to replace Oxford 2 on Tezos Mainnet. The Paris B protocol is currently subject to Tezos on-chain governance process, which has just moved into the Exploration period.

Octez v20.0~rc1 includes the Paris B protocol itself and its associated executables. As Paris B uses the new protocol environment, Octez v20.0 will be the minimal compatible version with the Paris protocol, once released and if and when Paris B is adopted.

Since Octez version 18, RPC endpoints accept both endorsements and attestations as input and/or output, with endorsement as default value but deprecated.

Starting from version 20, attestation output is now the default. endorsement is still available, but it is deprecated and will be removed in a future version.

The Smart Rollup node from version 20 introduces support for rollup storage snapshots, in order to allow bootstrapping Layer 2 rollup nodes without having to replay rollup history from their origination.

Smart Rollup node operators can now import or export snapshots using the brand new snapshot import command for octez-smart-rollup-node – See the Smart Rollup node’s guide.

The DAL node will be released with Octez v20.0, as the Paris protocol proposals (if adopted) would activate the DAL on Tezos Mainnet upon protocol activation.

Check the documentation for more details on the DAL node and how to operate it.

Note that the DAL node is not mandatory and one can participate in the upcoming Parisnet without running a DAL node.

:zap:Starting from Octez version 20, packages for different Linux distributions are provided with each release on the release page. Binary packages are now available for each Octez executable for the following Linux distributions:

  • Debian Linux
  • Fedora Linux
  • Rocky Linux

You may now install binaries by downloading their packages from the Octez release page, browsing to your distribution and then installing them with your package tool manager.

:open_book: A full changelog and update instructions are available in the version 20 release page.

:placard: The Git tag for this release is v20.0-rc1 and the corresponding commit hash is e38cf66691356c28745abca1cc3125d049628eb7.


Regarding the Linux distribution, what should Ubuntu users do? Will Serokell keep on proposing Ubuntu versions of the octez suite?

1 Like

We are not aware of Serokell’s plans regarding the maintenance of their Octez packages, tezos-packaging. Still, we believe providing packages for standard environments is important, and that’s why we decided to integrate them with the Octez release process.

Over the last few months, we have been developing a new set of packages – not only for Ubuntu, but also for Debian, Fedora, and Rocky Linux – in order to provide users a simple way to operate Octez nodes and infrastructure using native packages.

We welcome feedback and bug reports on these new packages. We look forward to providing more personalized installation and configuration options to cater for different user profiles: bakers, Smart Rollups node operators, etc.

In particular for Ubuntu users, you can refer to our online documentation at:


You can install packages first by downloading each deb package from the release page:

then, using dpkg or apt, you can install the deb packages manually.

Most of the configuration options are accessible by the user in /etc/default/<package>.

We plan to set up a secure apt repository soon that will allow for a more streamlined installation and upgrade process.

If you are upgrading from a different package distributor such as Serokell’s tezos-packaging, do pay attention to possible differences between the two packages, in particular regarding the configuration of the home directory for the tezos user.