Skip to main content

Lumera Upgrade

Upgrade to v1.6.1

Manual upgrade​

Loading data...
cd "$HOME" && rm -rf bin && mkdir bin && cd bin && \
wget https://github.com/LumeraProtocol/lumera/releases/download/v1.6.1/lumera_v1.6.1_linux_amd64.tar.gz && \
tar -xzvf lumera_v1.6.1_linux_amd64.tar.gz && \
chmod +x lumerad && \
sudo mv libwasmvm.x86_64.so /usr/lib/ && \
sudo ldconfig && \
sudo mv lumerad $(which lumerad) && \
rm lumera_v1.6.1_linux_amd64.tar.gz && \
sudo service lumera restart && \
sudo journalctl -fu lumera -o cat

Cosmovisor upgrade​

Note

Choose this method only if you're using Cosmovisor to manage binaries and automate chain upgrades.

cd "$HOME" && rm -rf bin && mkdir bin && cd bin && \
wget https://github.com/LumeraProtocol/lumera/releases/download/v1.6.1/lumera_v1.6.1_linux_amd64.tar.gz && \
tar -xzvf lumera_v1.6.1_linux_amd64.tar.gz && \
chmod +x lumerad && \
sudo mv libwasmvm.x86_64.so /usr/lib/ && \
sudo ldconfig && \
mkdir -p $HOME/.lumera/cosmovisor/upgrades/v1.6.1/bin && \
mv lumerad $HOME/.lumera/cosmovisor/upgrades/v1.6.1/bin/ && \
rm lumera_v1.6.1_linux_amd64.tar.gz

Note: if you see this in your node’s logs: UPGRADE "v1.6.1" NEEDED at height: 434000 then force Cosmovisor to point at the new upgrade directory:

cd "$HOME/.lumera/cosmovisor" && ln -sfn "upgrades/v1.6.1" current && ls -l current

This tells Cosmovisor to use the v1.6.1 binary as the “current” release so it won’t error on startup.