# Guarded on Day 1

**URL:** <https://agora.multiversx.com/t/guarded-on-day-1/479>\
**Category:** General\
**Created:** [March 20, 2025, 7:46pm UTC](https://agora.multiversx.com/t/guarded-on-day-1/479 "2025-03-20T19:46:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![joaquim](https://dub1.discourse-cdn.com/flex005/user_avatar/agora.multiversx.com/joaquim/32/86_2.png) [@joaquim](https://agora.multiversx.com/u/joaquim)\
**Post date:** [March 20, 2025, 7:46pm UTC](https://agora.multiversx.com/t/guarded-on-day-1/479/1 "2025-03-20T19:46:13Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![bubu](https://dub1.discourse-cdn.com/flex005/user_avatar/agora.multiversx.com/bubu/32/87_2.png) [@bubu](https://agora.multiversx.com/u/bubu)\
**Post date:** [March 20, 2025, 8:13pm UTC](https://agora.multiversx.com/t/guarded-on-day-1/479/2 "2025-03-20T20:13:01Z")

</div>

Great idea!  
Having a freshly created wallet in a “ready to guard” state would be a great addition.

---

<div class="post-metadata">

**Author:** ![elpulpo](https://dub1.discourse-cdn.com/flex005/user_avatar/agora.multiversx.com/elpulpo/32/88_2.png) [@elpulpo](https://agora.multiversx.com/u/elpulpo)\
**Post date:** [March 21, 2025, 12:27am UTC](https://agora.multiversx.com/t/guarded-on-day-1/479/3 "2025-03-21T00:27:34Z")

</div>

It’s a great idea indeed!

---

<div class="post-metadata">

**Author:** ![chessucation](https://dub1.discourse-cdn.com/flex005/user_avatar/agora.multiversx.com/chessucation/32/74_2.png) [@chessucation](https://agora.multiversx.com/u/chessucation)\
**Post date:** [March 21, 2025, 9:03am UTC](https://agora.multiversx.com/t/guarded-on-day-1/479/4 "2025-03-21T09:03:45Z")

</div>

Sounds great!

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?

---

<div class="post-metadata">

**Author:** ![joaquim](https://dub1.discourse-cdn.com/flex005/user_avatar/agora.multiversx.com/joaquim/32/86_2.png) [@joaquim](https://agora.multiversx.com/u/joaquim)\
**Post date:** [March 21, 2025, 1:11pm UTC](https://agora.multiversx.com/t/guarded-on-day-1/479/6 "2025-03-21T13:11:33Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![janniksam](https://avatars.discourse-cdn.com/v4/letter/j/edb3f5/32.png) [@janniksam](https://agora.multiversx.com/u/janniksam)\
**Post date:** [April 2, 2025, 8:25pm UTC](https://agora.multiversx.com/t/guarded-on-day-1/479/7 "2025-04-02T20:25:31Z")

</div>

Similar discussion about fresh wallets and how to make guardians more visible for anyone was going on here:

> [@Improving guardians by embedding them in the wallet creation workflow](https://agora.multiversx.com/t/improving-guardians-by-embedding-them-in-the-wallet-creation-workflow/211/5):
>
> One think I would like to add. Not sure, how you think about this: If the guardian is activated on a “clean” account, there shouldn’t be any activation period for the guardian. I define a clean account as: balance = 0 EGLD no esdts / sfts / nfts… This can only work, if we have the foundation (or someone else) to pay the gas fees in the future, as mentioned in the original post.
