Two new proposals on the Network Nervous System are moving through the voting process for the Internet Computer, adding another round of upgrades to the protocol’s registry and governance systems.
The first proposal, numbered 141243, upgrades the Registry Canister and introduces stricter rules around Cloud Engine subnet architecture. Under the change, Cloud Engine subnets will only be allowed to contain type4 reward nodes, while non Cloud Engine subnets will be prevented from using those nodes entirely.
Supporters say that change matters because Cloud Engine infrastructure is expected to expand across the Internet Computer network. Separating node types by subnet role could help avoid configuration issues as the system becomes larger and more complex.
The second proposal, 141242, upgrades the NNS Governance Canister and adds a set of new governance tools. Among them is support for DeleteSubnet proposals, which will initially apply to Cloud Engine subnets. The proposal also introduces new data visibility for neurons with an eight-year dissolve delay through the eight_year_gang_bonus_base_e8s metric, alongside additional infrastructure tied to Mission 70 voting rewards.
Taken together, the changes point to a broader effort by the Internet Computer to tighten the connection between infrastructure, governance and token economics.
For long-term participants, the recognition of eight-year neuron commitments could be especially important. Those users have often argued that longer lock-up periods should carry greater weight inside the governance system, both through voting influence and reward design.
The timing is also notable because it arrives during a period when blockchain security has become a larger talking point across the industry.
Last week, Solana-based Drift Protocol suffered an exploit estimated at roughly $285 million, making it one of the largest crypto hacks of the year so far. Reports suggest the attacker gained access through compromised administrative controls rather than a direct flaw in smart contract code. The incident prompted renewed debate about multisig governance, operational security and how much responsibility should sit at the protocol layer versus the application layer.
Following the attack, the Solana Foundation and security firm Asymmetric Research introduced a new STRIDE security programme aimed at DeFi protocols. The programme includes around-the-clock monitoring for projects with more than $10 million in total value locked, formal verification for larger protocols, structured threat reviews and a real-time incident response network.
That response has highlighted a wider divide in how blockchain ecosystems approach security.
Many networks continue to rely heavily on external audits, monitoring systems and emergency response teams. Those tools are useful, particularly after an exploit has already happened, but critics argue they often remain reactive by nature.
The Internet Computer has long presented its security model differently. Features such as chain-key cryptography, threshold signing and native cross-chain functionality are designed to reduce the need for exposed private keys, bridges and fragmented infrastructure. Supporters argue that approach can remove some of the attack surfaces that have repeatedly appeared across other ecosystems.
Even so, no blockchain system is immune from risk. Governance frameworks, validator incentives and software updates all introduce their own pressures over time. What matters is whether networks can keep adapting before weaknesses turn into larger failures.
For the Internet Computer, the latest proposals suggest that the focus remains on reinforcing the foundations while the network expands. Registry controls, subnet management and long-term governance incentives may not generate the same headlines as token prices, but they often shape how resilient a blockchain becomes over time.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion