We’re excited to share that the vetKeys feature is now code complete and ready to be enabled on mainnet for testing purposes! 
In line with the release process used for previous cryptographic features like threshold ECDSA and Schnorr signatures, we are proposing to create a test vetKD master key on a 13-node application subnet. This will allow us to:
-
Conduct extended testing of vetKeys functionality on mainnet.
-
Build confidence with operational procedures, including key backup and recovery workflows.
-
Enable developers to experiment with the full vetKeys derivation functionality in their dApps.
-
Identify edge cases and gather insights into performance and system behavior.
Important Note: The test vetKey is strictly intended for testing purposes and should not be used in production environments. The vetKeys feature is still undergoing internal security reviews and audits, and as such, we strongly recommend limiting its use to non-critical testing scenarios only.
Next steps
If this proposal is approved, we will submit follow-up proposals to:
-
Back up the test key on an additional application subnet.
-
Enable vetKeys derivation functionality to support end-to-end testing.
Following a successful testing phase—and assuming everything proceeds smoothly—we plan to propose the creation of the production key in later governance proposals. The earliest expected timeline for this would be mid-June.