Advertisement. Remove ads.
Blockchains were born open, but most real-world apps need some data to stay closed. That tension has sidelined countless projects - until now.
With the Niobium upgrade, the Internet Computer (ICP) introduced vetKeys, a feature that manufactures user-specific secret keys inside the protocol itself. Keys are generated by all nodes in a subnet, immediately sharded, and shipped to the rightful owner in an encrypted bundle.
No node, hacker, or rogue admin ever sees the full private key; only the user can reconstruct it locally.
Why is that such a big deal? Because the moment you can encrypt data without introducing a centralized key server, entire classes of GDPR-sensitive or enterprise workloads become block-chain-viable.
Picture a medical-records dApp where doctors decrypt files on-demand, or a payroll system that stores salary figures on-chain yet keeps them invisible to everyone except HR and the employee.
The vetKeys flow is pure cryptography: the user supplies a one-off “transport” public key; each validator derives an encrypted key share; the canister bundles those shares; and the user decrypts the final secret on their own device, verifying the package wasn’t tampered with along the way.
Developer possibilities explode:
Projects are already integrating the toolkit. OpenChat will let users regenerate lost encryption keys; Diode is building fully private storage canisters where even node operators can’t peek.
Looking ahead, Trusted Execution Environments will allow data to be decrypted inside secure enclaves, enabling complex computations without ever exposing raw information.
vetKeys don’t merely bolt privacy onto ICP - they make confidentiality a native, first-class feature of the chain. If you shelved a Web3 idea because “everything is public,” it may be time to dust off that roadmap.
Also See: Quant Says Middleware Will Rule the Stack
For updates and corrections, email newsroom[at]stocktwits[dot]com.