The Internet Computer is nudging another piece of cryptographic machinery into the wild. The vetKeys rollout is moving from test mode to production, and while it’s a quiet operation by most standards, it comes with a blink-and-miss-it pause for Internet Identity (II) users. Mark your calendar for 8:00 AM UTC on 26 June. That’s when the II subnet is scheduled to snooze for just five to ten minutes while a production vetKey gets backed up. Existing sessions will continue as usual, so no one’s getting booted out mid-click—but no new sessions will kick off during that brief window.
This key shuffle isn’t just a tidy backend upgrade. It’s the next official step in getting vetKeys into regular canister hands. The key itself, technically identified as Bls12_381_G2:key_1, is set to be backed up from the fiduciary subnet pzp6e to a second subnet uzr34. Once it’s safely tucked away, a proposal will be floated to the Network Nervous System (NNS) to enable public access. At that point, canisters will be able to use it via the vetKD API.
Getting here hasn’t been rushed. For several weeks, the DFINITY team has been running through the motions on subnets 2fq7c and fuqsr, exercising key lifecycle tasks like generation, backup, and end-to-end derivation workflows. Those test environments laid the groundwork for this upcoming production release. The team didn’t just check boxes—they validated the real-life steps that ensure a secure, retrievable, and usable vetKey.
The decision to pause the subnet hosting Internet Identity may raise some eyebrows, but there’s good reason behind it. The resharing operation needed for backup isn’t yet fully automated. It takes a trio of NNS proposals submitted and executed in sequence, and that comes with unavoidable subnet downtime. It’s the same process that was recently used to backup the test vetKD key, so the playbook is familiar.
During the brief downtime, you won’t be able to start new Internet Identity sessions. That means if you’re trying to log in to a dapp via II during those few minutes, you might be politely told to wait. However, if you’re already logged in, you won’t notice much at all. Sessions remain active, and dapps continue humming along. From a user’s point of view, the change is so minor it could pass completely unnoticed—unless you were planning a login right then.
The broader picture here is a slow and steady rollout that builds trust in the system. vetKeys (short for verifiable encryption and threshold key derivation) offer a more secure way for canisters to manage secrets and cryptographic operations. Getting these keys into production isn’t just a technical milestone; it’s a commitment to better infrastructure for decentralised applications on the Internet Computer.
The move toward production was formally kicked off with a proposal on 20 June to generate the key on subnet pzp6e. That subnet already holds the production-grade ECDSA and Schnorr keys, making it the natural home for the vetKey as well. By placing the key here, DFINITY is ensuring parity in the treatment of vetKey alongside other critical cryptographic keys.
After the key’s generation and backup, the enabling step is scheduled for 27 June. Once enabled, developers will be able to integrate vetKey functionality into their applications. It’s another piece in the growing puzzle of tools that allow canisters to act independently and securely. The vetKD API will be the public-facing channel for this interaction, offering developers the ability to request key derivations securely and verifiably.
While the technology moves forward, communication remains open. DFINITY has committed to sharing updates at each milestone. That includes progress on proposals, timing of operations, and expected impacts. They’re also encouraging feedback and open discussion along the way, recognising that protocol upgrades are as much about the community as they are about the code.
This production rollout is the result of careful planning, successful testing, and coordinated action. It reflects a focus on resilience—every step has a backup, every key has a safeguard, and every interruption is announced with precision. Rather than rushing automation, DFINITY is keeping things transparent and intentional, making sure each piece lands properly before moving on to the next.
For users, the most noticeable part of all this will likely be the short II downtime. It’s a gentle reminder that even the most seamless systems occasionally take a breath. And for developers, it’s a green light to start exploring what vetKeys can unlock. With the API soon available, the kinds of apps that can be built on the Internet Computer just got a lot more interesting.
vetKeys bring threshold cryptography into the developer toolkit, enabling a new way to think about key usage, secret management, and verifiable workflows. While the actual cryptographic functions may sit behind APIs, their implications ripple outward—opening paths for multi-user apps, cross-canister coordination, and more robust privacy models.
There’s still more work ahead. Full automation of backup processes, expanded key support, and broader adoption are all likely in the pipeline. But for now, this production rollout stands as a careful, necessary step that brings the network closer to being self-sustaining, resilient, and developer-friendly.
As 26 June approaches, developers and users alike are encouraged to plan accordingly. Don’t schedule a login-heavy onboarding campaign during that five-minute slot. But once it’s over, the road ahead for vetKeys will be wide open. Keep an eye on the NNS proposals. The key story is just beginning.
And if you’re someone who skipped ahead, here’s the bit you need to know: Internet Identity will take a short nap on 26 June at 8AM UTC. It won’t forget anything—it just won’t let new people in for a few minutes. Logged-in users stay logged in. Dapps keep running. The real action is behind the scenes, as vetKeys take their place in production. For developers, it’s a fresh tool; for users, a tiny pause. For the Internet Computer, it’s progress by precision.
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
🪙 BTC Wallet: bc1pp5kuez9r2atdmrp4jmu6fxersny4uhnaxyrxau4dg7365je8sy2q9zff6p
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
