Since the launch of guardians, a novel concept in web3 with protocol level 2FA, there is a waiting time of 20 epochs before you can activate the guardian.
I’m supposing the reason is to protect a compromised wallet from locking out the true owner so they can still fight to try to retrieve staked funds that have an unbonding period.
I would like to discuss and suggest that guardians can be enabled on Day 1 if it’s the very first transaction of said wallet (nonce 0).
This would allow new wallets to have 2FA enabled from the start which would be very beneficial for products like xPortal which can then have it active as soon as the user is onboarded.
We also see this need in Gaupa Login with wallet abstraction where we would like to use the benefits of guardian (2FA) as soon as a user creates an account.
Let me know your thoughts and I’ll convert it into a proposal!
On UI end, you see this as an “opt in to wallet security” type of prompt or something the user needs to know about beforehand to take the action themselves?
Similar to many Web2 platforms that handle financial or sensitive data, you’ll be prompted to enable two-factor authentication during onboarding. If you skip it at first and later decide to activate it after conducting some transactions, you’ll face a 20-day waiting period. Nonetheless, this approach ensures that new users have their wallets protected right from the start.