Version 2.0¶
Note
Mavryk/Tezos Version Mapping: Mavryk Version 2 (Boreas) is a merge of Tezos ParisB (v20)
and ParisC (v21). Git tags follow Tezos versioning for compatibility (e.g., 20.3 for this release).
Version 2 contains a new version (V12) of the protocol environment, which is the set of functions that a protocol can call. This new version is used by the Boreas protocol, the successor to Atlas. This release contains the Boreas protocol itself, as well as its associated protocol-specific executable binaries (baker, accuser, etc).
Key Features¶
10-Second Block Time
Boreas reduces block time from 15 seconds to 10 seconds, increasing throughput while maintaining the same cycle duration and inflation rate. Related protocol parameters have been adjusted accordingly.
Data Availability Layer (DAL)
Full integration of the Data Availability Layer, including:
New
dal_publish_commitmentmanager operation for publishing commitmentsDAL attestation field in consensus operations
Smart Rollup integration with
dal_pageanddal_parametersreveal inputs
Adaptive Issuance Improvements
Per-block voting for Adaptive Issuance activation
Delayed slashing applied at end of denunciation period
Improved denunciation handling with chronological ordering
Slashing amounts now depend on slots owned at time of misbehavior
Smart Rollups
Bumped Wasm PVM to V4
Removed unnecessary initial PVM state hash
Protocol Parameters
preserved_cyclesreplaced withconsensus_rights_delay,blocks_preservation_cycles, anddelegate_parameters_activation_delayconsensus_rights_delayreduced from 5 to 2 cycles
For a complete list of changes, see the Boreas protocol documentation.
Rollup Node¶
The rollup node continues to be protocol-agnostic as introduced in Version 1.
The single executable mavkit-smart-rollup-node works with all Mavryk protocols.
Update Instructions¶
To update from sources:
git fetch
git checkout 20.3
make clean
opam switch remove . # To be used if the next step fails
make build-deps
eval $(opam env)
make
If you are using Docker instead, use the 20.3 Docker images of Mavkit.
You can also install Mavkit using Opam by running opam install mavkit.
Debian and Redhat packages are available on the release page and in the package registry.