What Happens When I Create a Devnet or Legacy Testnet Project for My Production Application?

:classical_building: Content from Web3Auth Community

This topic was originally posted by shahbaz on 3/3/2025.
This content has been migrated from our previous community forum to preserve valuable discussions.


When you create a Devnet or Legacy Testnet project for a production application, you expose your users to potential risks and limitations.

Key Considerations:

  1. Testnets Are Not Stable – Devnets and legacy testnets are designed for testing purposes only. The infrastructure and keys may change over time due to ongoing updates. For example, Ethereum testnets have transitioned from Rinkeby → Goerli → Sepolia, affecting dependent systems.

  2. User Accounts at Risk – Since testnets are not meant for production use, any accounts created using a verifier on these networks could become inaccessible or invalid due to changes in dependencies.

  3. No Migration Support – If you create a verifier on Devnet or Legacy Testnet for production applications, we cannot assist with migrating it to Mainnet, Cyan, Aqua, or Sapphire Mainnet projects.

Recommendation:

Always use a Mainnet-supported project for production applications to ensure stability and long-term usability for your users.