How is Web3Auth prepared against bots? One, or even Web3Auth itself, if wanted could easily use bots to surpass the Monthly Active Wallets (MAWs) and create a big billing for the web3auth user.
I read in the legacy forum that setting up an MFA is an option, but wondering what other measures are in place. We are not looking to force users to set up MFA in our dApp + we want to enable wallet connect as well.
With both Core Kit and Plug and Play SDKs, you have the choice to use multiple types of multi-factor flows according to your needs to better enhance security. You can read more at the below links:
Please connect with our business team for a demo call to discuss your project requirements and find out which Web3Auth product is the best fit for you.