Web3Auth mainnet networks: mainnet, cyan, aqua, and celeste.
Please note that your keys change when you change your network. Make sure you’re on the correct network end to end across your Web3Auth integration.
Could someone confirm if these limits are still accurate? If there have been updates, I’d appreciate the latest figures.
Additionally, I’m interested in understanding how using a custom verifier (e.g., Auth0, Firebase, or a custom JWT provider) might affect these rate limits. Does implementing a custom verifier alter the key creation rate limits in any way?
These limits are no longer applicable. All the verifiers have been internally migrated to the sapphire networks. This means that even if you are using a cyan verifier, internally it is pointing to an instance of sapphire. Additionally, it is horizontally scalable, if you need more key generation it will scale automatically. If you have a special request for scalability you can contact our team directly and get it done as well.