Quietly but confidently, the Internet Computer Protocol (ICP) is getting a serious security boost. Behind the scenes, engineers are shaping up support for AMD’s Secure Encrypted Virtualisation (SEV), marking a bold move in how ICP handles replica upgrades and state encryption. The work is technical, time-consuming, and anything but cosmetic.
SEV is designed to protect the confidentiality of data in use, offering encryption at the virtual machine level. For ICP, adopting SEV means anchoring a node’s encryption keys to the very code it’s running. That makes keys tamper-resistant and unrecoverable outside their intended environment — a smart choice, but one that doesn’t come without some hefty structural consequences.
The team has confirmed that early tests of SEV support are scheduled to begin this summer. While that may sound straightforward, it’s hiding a complex web of engineering challenges. Rolling out SEV on ICP calls for a deep rethink of the upgrade and release machinery that sits under the hood of the protocol.
One of the biggest shifts comes in how encryption keys are generated and protected. Under this new approach, each replica’s keys are derived from a cryptographic hash of the running code. These keys don’t leave the virtual machine, and crucially, the hash changes with every release. That means an upgraded replica won’t be able to read the encrypted state left behind by an older one — unless the system finds a way to securely hand off those keys between versions.
To make that handoff safe and community-approved, the upgrade process itself is being overhauled. The new method will have to enable trusted key-sharing between consecutive replica versions, all while ensuring that no unauthorised or tampered replicas get access to the encrypted state. That’s a major shift from the current system and has knock-on effects across several moving parts.
The process of releasing new code will also need to adapt. Each release must now have its SEV hash calculated and stored, so the NNS Registry — the Internet Computer’s source of truth for node configuration — needs an upgrade of its own. It will have to record and distribute these hashes alongside the usual information, so that nodes know which versions are approved and which are off-limits.
Booting the operating system becomes more complicated, too. The bootloader — responsible for starting up the node and loading the correct software — must now verify that the OS matches the expected hash before anything else can run. That means redesigning the OS boot process from the ground up, with a strong focus on cryptographic assurance.
Beyond the internal mechanics, the way nodes interact is also changing. With SEV in place, nodes will be able to check if their peers are running SEV-enabled replicas — and if they’re not, the connection stops there. By default, data won’t be shared with nodes that don’t meet the new standard, cutting off any unapproved or potentially insecure participants from the network. That raises the bar for trust and integrity, but it also adds complexity to connection and verification protocols.
This isn’t a cosmetic polish or a mild performance tweak. The switch to SEV touches nearly every part of the infrastructure, and getting it right demands careful planning, testing, and coordination. Stability is a top priority, and no one wants to introduce security at the cost of uptime or user data. To that end, the team is taking a methodical approach, building out the necessary support structures and keeping a close eye on performance and safety throughout the rollout.
The upside is a system that can promise higher security guarantees, tighter control over upgrades, and an architecture that’s more resistant to tampering. It also sets the stage for a more fine-grained trust model across the network, where replicas can make smart decisions about who to trust — and who to avoid.
This move may not be loud or flashy, but it reflects a deliberate step towards strengthening the Internet Computer’s foundations. It’s a technical challenge with very real consequences, and one that will shape how secure, reliable, and flexible the network is in the years to come.
More updates are expected as testing begins in earnest. For now, SEV support remains a work-in-progress — a carefully engineered shift in how the Internet Computer handles itself behind the scenes.
