Node System Upgrade 2nd Reminder 🛠️ Bluwhale is transitioning Master and Common Nodes to our new zkChain, Oceanum. The migration is still ongoing until September. Once deployment is complete, you will be able to run your own nodes. During this period: ⏳ Node Token claims remain temporarily unavailable until September 30. ✅ Your Node rewards will continue to accumulate ✅ No rewards will be lost ✅ Claims will resume once the migration is complete Thank you for your patience and continued support while we complete this transition. 🐳

Node manager v0.2.3 released: ▸ Rebuilt miner architecture, CPU annealing ~5x per core ▸ CUDA utilization from 55% to 94% ▸ Metal up ~43% on an M4 Max ▸ Any executable can act as a miner ▸ Self-repairing stack, readable logs ▸ And more... →

Node operator checklist before 25 August. 🔸 Upgrade to v1.7.7 🔸 Remove [Eth] EnableBAL from config.toml first, or the node will not start 🔸 Everything else is a binary swap Full list of deprecated flags 👇

Node.js 20 has reached end-of-life and no longer receives important security updates. Projects on v20 will still run on Vercel. After October 1, new builds will be rejected. Upgrade your projects to Node.js 24 in one click.

Node Upgrade ⚙️ A big thank you to all node operators helping secure the peaq network, including @Telekom, @Lufthansa Innovation Hub, @TU_Muenchen, and many others Please update your nodes to peaq-v0.0.112 ahead of the runtime upgrade and follow the instructions below Docker image: Branch tag (if building from source): peaq-v0.0.112 WASM override for EVM tracing enabled nodes (peaq.v0.0.112-evm.wasm):

Nodes hold the rules of the network. Any changes made to nodes are done by the core developers which in return requires users to accept their change by adopting their updates. Inform yourself about all future updates by joining the Kaspa Core R&D