The current release includes an important automatic participation data fold (the new rule will be activated on epoch 1334000), nodes that do not update will be rejected by the network (it is important to have a common final state for all participants).
Among other things, the lite node will now inherit the bootstrap cluster functionality, where continuity of catching up quorum updates is implemented, lagging nodes will strive to match the maximum network height automatically. Also several important improvements in the runtime and in the computation execution kernel.
Just in case, here's a quick reminder on how to update the node and how to configure it:
sudo -iu octra
cd /opt/octra/libv_litecore
git fetch origin main
git checkout main
git pull --ff-only origin main
test "$(cat SOURCE_COMMIT)" = \
"e0c8e6b438d308340a9daaff1f68186368e6dacd"
sha256sum -c config/network.env.sha256
sh controls/check.sh
exit
Then:
cd /opt/octra/libv_litecore
sudo env \
OCTRA_OPERATOR_USER=octra \
OCTRA_DATA_ROOT=/var/lib/octra \
sh controls/install.sh --source-build
Next:
sudo -iu octra
cd /opt/octra/libv_litecore
export CARGO_HOME="$PWD/runtime_data/toolchains/cargo"
export RUSTUP_HOME="$PWD/runtime_data/toolchains/rustup"
export PATH="$CARGO_HOME/bin:$PATH"
SWITCH="$PWD/runtime_data/toolchains/ocaml"
opam install \
--switch "$SWITCH" \
. --deps-only --with-test --locked --require-checksums -y
mkdir -p mcl/obj mcl/lib
make -C mcl \
MCL_FP_BIT=256 \
MCL_FR_BIT=256 \
lib/libmcl.a
opam exec --switch "$SWITCH" -- \
dune build --root "$PWD" --profile release \
bin/octra_node.exe \
bin/octra_pvac_worker.exe \
bin/octra_state_sync_client.exe \
bin/octra_state_sync_manifest.exe \
bin/bft_control_tx.exe
sh controls/stop.sh
sh controls/run.sh --rebind-runtime
sh controls/stat.sh