# Klever Blockchain Mainnet Upgrade (v.1.7.14) – Validators, It’s Time! 🚀 **URL:** \ **Category:** News and Announcements\ **Tags:** kleverchain, validator, kvm\ **Created:** [September 26, 2025, 7:16pm UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042 "2025-09-26T19:16:23Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Duka](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/duka/32/415_2.png) [@Duka](https://forum.klever.org/u/Duka)\ **Post date:** [September 26, 2025, 7:16pm UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/1 "2025-09-26T19:16:23Z")
![image](https://europe1.discourse-cdn.com/flex013/uploads/klever/original/2X/6/61d8462b48697d1cddcde61689ef20e0e0123bc9.jpeg) 📣 MAINNET Upgrade **v1.7.14** Dear Klever [@Validators](https://forum.klever.org/groups/validators) , We are thrilled to announce the release of a **major Klever Blockchain upgrade** that brings powerful advancements across tokens, smart contracts, security, and performance. This release is a milestone that will not only enhance developer flexibility but also strengthen network resilience and scalability for the entire ecosystem. ✨ **Why this matters:** - Developers now have **Semi-Fungible Token (SFT)** support, cross-VM contract execution, and enhanced asset management tools. - Smart contracts gain new powers: royalties processing, raw argument execution, and more efficient deployment and deletion handling. - Critical **security patches** reinforce protection against vulnerabilities and malicious validators. - Infrastructure and consensus improvements ensure smoother performance, stronger reliability, and a more scalable future for **Klever Blockchain**. This upgrade is **mandatory** and requires immediate action from all validators to stay aligned with the network. ⏰ **Deadline:** Please upgrade **before epoch 4860 – Tuesday, 28 October 2025, 13:00:00 UTC**. Nodes not updated by this epoch risk forking from the network, and validators may be jailed. 💡 _Make sure to update **all** configs files prior update the node._ ⚡ **Upgrade Instructions:** 1. **Download new config:** ```bash curl -k https://backup.mainnet.klever.org/config.mainnet.108.tar.gz | tar -xz -C ./node ``` 1. **Download new image version:** ```bash docker pull kleverapp/klever-go:v1.7.14-0-g22769b30 ``` 1. **Update directory permissions:** ```bash chown -R 999 $(pwd)/node chown -R 999 $(pwd)/node/config chown -R 999 $(pwd)/node/db chown -R 999 $(pwd)/node/logs ``` 1. **Stop and remove your current node:** ```bash docker stop klever-node && docker rm klever-node ``` 1. **Run your node again:** ```bash docker run -it -d --restart unless-stopped \ --user "999:999" \ --name klever-node \ -v $(pwd)/node/config:/opt/klever-blockchain/config/node \ -v $(pwd)/node/db:/opt/klever-blockchain/db \ -v $(pwd)/node/logs:/opt/klever-blockchain/logs \ --network=host \ --entrypoint=/usr/local/bin/validator \ kleverapp/klever-go:v1.7.14-0-g22769b30 \ '--log-save' '--use-log-view' '--rest-api-interface=0.0.0.0:8080' ``` 🔥 This is one of the most exciting and impactful updates in Klever’s history, and your role as a validator is crucial in making it a success. Together, we are building a faster, safer, and more innovative blockchain for everyone. Please, use this thread in case you need any support. Let’s move forward. Stronger, smarter, and more **Klever** than ever! 💜 ---
**Author:** ![janill](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/janill/32/187_2.png) [@janill](https://forum.klever.org/u/janill)\ **Post date:** [September 27, 2025, 11:27am UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/2 "2025-09-27T11:27:48Z")
Hey! Thanks for the update guide. It worked quite well for me. I also suggest updating the Klever docs page on how to run a node with permission specifics provided in this post. Unfortunately, I was not able to run the node using the old way provided in the documentation. The page in question is [node-operations - Klever Docs](https://docs.klever.org/node-operations#how-to-run-a-node) P.S.: I keep getting the same permission error while trying to run the container in an old way: _ **libvmexeccapi.so: cannot open shared object file: Permission denied** _ ---
**Author:** ![MathijsBok](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/mathijsbok/32/3_2.png) [@MathijsBok](https://forum.klever.org/u/MathijsBok)\ **Post date:** [September 27, 2025, 11:36am UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/3 "2025-09-27T11:36:35Z")
> [@janill](#): > > P.S.: I keep getting the same permission error while trying to run the container in an old way: _ **libvmexeccapi.so: cannot open shared object file: Permission denied** _ That is because you have in your start command not the user changed Old `--user "$(id -u):$(id -g)" \` New `--user "999:999" \` ---
**Author:** ![janill](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/janill/32/187_2.png) [@janill](https://forum.klever.org/u/janill)\ **Post date:** [September 27, 2025, 11:46am UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/4 "2025-09-27T11:46:37Z")
Yes, I have figured this out, thank you. I suggest updating the existing documentation at [docs.klever.org](http://docs.klever.org). In the example it is still running the container with _**–user “$(id -u):$(id -g)”**_ ![image](https://europe1.discourse-cdn.com/flex013/uploads/klever/original/2X/3/3cc9a6ebc2dc5d05514ec7edc293ee15e218617c.png) ---
**Author:** ![MathijsBok](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/mathijsbok/32/3_2.png) [@MathijsBok](https://forum.klever.org/u/MathijsBok)\ **Post date:** [September 27, 2025, 1:57pm UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/5 "2025-09-27T13:57:26Z")
Correct, The blockchain team will do this. Thats why we have put here the full steps disclosed to be sure people follow this article. Thanks for the feedback ---
**Author:** ![Abbeyfx](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/abbeyfx/32/1995_2.png) [@Abbeyfx](https://forum.klever.org/u/Abbeyfx)\ **Post date:** [October 2, 2025, 2:45am UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/6 "2025-10-02T02:45:56Z")
Great work @Duka and the team. This will make it easy for validators to work with within the given time. ---
**Author:** ![Ender](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@Ender](https://forum.klever.org/u/Ender)\ **Post date:** [October 2, 2025, 6:54am UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/7 "2025-10-02T06:54:27Z")
Was the user 999 hard coded? I tried with a different name, to separate from what was 999 time related process…. And was not successful. ---
**Author:** ![MathijsBok](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/mathijsbok/32/3_2.png) [@MathijsBok](https://forum.klever.org/u/MathijsBok)\ **Post date:** [October 2, 2025, 9:27am UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/8 "2025-10-02T09:27:56Z")
@Ender did you chown the 999:999 ? And did you changed that also in the start command? ---
**Author:** ![Ender](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@Ender](https://forum.klever.org/u/Ender)\ **Post date:** [October 2, 2025, 9:41am UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/9 "2025-10-02T09:41:24Z")
Yes I did, in the end. Tried differently the first time. Instead of 999, tried differently. Of course when starting the node everything was properly mentioned. Did not work with anything else but the 999. The reason for asking if 999 is arbitrarily chosen or hard coded in the node code. ---
**Author:** ![MathijsBok](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/mathijsbok/32/3_2.png) [@MathijsBok](https://forum.klever.org/u/MathijsBok)\ **Post date:** [October 2, 2025, 10:17am UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/10 "2025-10-02T10:17:08Z")
chown 999 is mandatory for the folders as it gives an extra security layer for the blockchain. So yes, it is mandatory set in the config. ---
**Author:** ![Duka](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/duka/32/415_2.png) [@Duka](https://forum.klever.org/u/Duka)\ **Post date:** [October 2, 2025, 6:48pm UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/11 "2025-10-02T18:48:01Z")
Hello everyone, Docs updated accordingly! TY all! ---
**Author:** ![Jose\_Luis\_Latas](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/jose_luis_latas/32/30_2.png) [@Jose\_Luis\_Latas](https://forum.klever.org/u/Jose_Luis_Latas)\ **Post date:** [October 4, 2025, 7:26pm UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/12 "2025-10-04T19:26:44Z")
When I try to run the third step, I get errors when changing permissions. I run the commands: chown -R 999 $(pwd)/node chown -R 999 $(pwd)/node/config chown -R 999 $(pwd)/node/db chown -R 999 $(pwd)/node/logs And I get this error. ![image](https://europe1.discourse-cdn.com/flex013/uploads/klever/original/2X/e/e5697bc42c8735b6f5e9556532614ed961dc44c0.png) ---
**Author:** ![Maik](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/maik/32/33_2.png) [@Maik](https://forum.klever.org/u/Maik)\ **Post date:** [October 4, 2025, 7:32pm UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/13 "2025-10-04T19:32:16Z")
you might have to run it as sudo - depending on your user permissions `sudo chown -R 999 $(pwd)/node` `sudo chown -R 999 $(pwd)/node/config` `sudo chown -R 999 $(pwd)/node/db` `sudo chown -R 999 $(pwd)/node/logs` ---
**Author:** ![Jose\_Luis\_Latas](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/jose_luis_latas/32/30_2.png) [@Jose\_Luis\_Latas](https://forum.klever.org/u/Jose_Luis_Latas)\ **Post date:** [October 4, 2025, 7:48pm UTC](https://forum.klever.org/t/klever-blockchain-mainnet-upgrade-v-1-7-14-validators-it-s-time/4042/14 "2025-10-04T19:48:16Z")
> [@Duka](#): > > ```auto > docker run -it -d --restart unless-stopped \ > --user "999:999" \ > --name klever-node \ > -v $(pwd)/node/config:/opt/klever-blockchain/config/node \ > -v $(pwd)/node/db:/opt/klever-blockchain/db \ > -v $(pwd)/node/logs:/opt/klever-blockchain/logs \ > --network=host \ > --entrypoint=/usr/local/bin/validator \ > kleverapp/klever-go:v1.7.14-0-g22769b30 \ > '--log-save' '--use-log-view' '--rest-api-interface=0.0.0.0:8080' > > ``` Perfect… that’s it. I think it’s now updated. I’ve checked the latest node/logs files and it looks correct. Thanks