![]() ![]() If your node is running EOSIO 2.0 and needs to keep blocks and state history, you can use a snapshot for your upgrade.Other than the bolded section, the content will be different. The second number in the output (top row, second column from the left) corresponds with the blocks.log version. (The will be the “data” directory where nodeos stores blockchain data, for example, “.local/share/eosio/nodeos/data”) To determine if your blocks.log file is compatible, use the following command with your node: An incompatible blocks.log file needs to be removed. If you are using EOSIO 2.1, your block log may or may not be compatible.If you are using EOSIO 2.0 your block log is compatible.If your blocks.log was created before EOSIO 2.1, the blocks.log file is compatible with 3.1 and you can start from a snapshot without removing existing block logs. For 2.1 nodes that keep a blocks.log file but do not keep state history, the version of the blocks.log file is important.2.1 Nodes that don’t keep a blocks.log file or state history are the easiest to upgrade.If you are using EOSIO 2.1, you may have additional work: Leap 3.1 is based on EOSIO 2.0, so upgrading nodes from EOSIO 2.0 is straightforward. However, blocks.log files may be compatible if the node upgraded from an earlier version of EOSIO. SHiP files from 2.1 are always incompatible with 3.1. EOSIO 2.1 used state history plugin (SHiP) files and blocks.log files that are incompatible with Leap. ![]() The trace history plugin is a native migration option.Īt this point, if you’re upgrading your 2.0 (NOT 2.1) node with a snapshot, you can move on to preparing for the upgrade. ![]() Operators can migrate their solutions to services like Hyperion or Chronicle. History v1 “ history_plugin” + “ history_api_plugin”.Nodes that use these plugins must adapt their solutions prior to activation, ideally immediately: Ensure nodes are NOT configured to use any plugins that are no longer available in Leap 3.1 (as noted under deprecations in the GitHub Release pages for Leap 3.1 and the releases codenamed Mandel).Decide if you are using the pre-built binaries or compiling binaries yourself.The instructions assume you are upgrading. You can install Leap 3.1 on a fresh server or upgrade an existing server. ![]() Use one of the supported operating systems (Ubuntu 18.04, 20.04, 22.04).Make sure a test server is available to try out these steps before performing them on production nodes.Previous versions are on the releases page. Once the ENF publishes the final release, node operators can upgrade to Leap. Some specific steps may vary based on existing node configuration, but these general steps work for most nodes.ĭevelopers can fill out a survey form to help determine the most-used API nodes and help prioritize resources. This document provides an upgrade checklist to facilitate the node upgrade process and avoid disrupting operations. Once the software is released, node operators must validate prerequisites, remove obsolete plugins, and change configuration settings before updating binaries. Like the previous EOSIO 1.8 release, Leap 3.1 requires coordination between block producers and other network participants to ensure a smooth network consensus upgrade. This testing continues as developers put the finishing touches on Leap 3.1 and related software ahead of their anticipated release in the coming days. However, with consensus upgrades, all nodes in the network need to be updated.įor weeks now, many people have been testing Leap 3.1, and the ENF engineering team has pushed out release candidates regularly. The Leap upgrade represents the network assuming ownership of its own codebase.Īs guardians of the network, block producers on EOS assume responsibility for stable network upgrades. This emancipation enables cross-chain collaboration and pushes the network into the future. With this release, a coalition of EOSIO networks officially replaces the previously inattentive EOSIO developers with the EOS Network Foundation (ENF) core development team. The coordinated consensus upgrade to the Leap 3.1 release includes priorities guided by network consensus. On Wednesday, September 21, 2022, EOS block producers will begin carving a new path toward self-determination by executing a coordinated consensus upgrade to Leap 3.1.Īnyone running a node must upgrade their nodes before September 21 to continue syncing with the network. Preparing for the September 21st Consensus Upgrade Preparing for the September 21st Consensus Upgrade. ![]()
0 Comments
Leave a Reply. |