You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Not a problem, but accounts would be more secure if they could opt-in to multi factor authentication. This is especially useful for stackers who either:
have a large balance
have attached wallets with large balances
own territories
have a well-known reputation
Describe the solution you'd like
I'd like to be able to configure MFA in the form of (at least) TOTP on my account. I think this could be used in the following ways:
Required on login after first factor is complete
Required when performing "high risk" actions like transferring a territory, or transacting over a certain (configurable?) threshold
I said ideally TOTP because MFA over SMS is bad, and email is only slightly better. It would be best to be able to use an open source authenticator app.
Describe alternatives you've considered
There's no real alternative that I can think of for things like territory ownership, but for balance concerns, you can link to an external wallet with budgets to help minimize risk.
Is your feature request related to a problem? Please describe.
Not a problem, but accounts would be more secure if they could opt-in to multi factor authentication. This is especially useful for stackers who either:
Describe the solution you'd like
I'd like to be able to configure MFA in the form of (at least) TOTP on my account. I think this could be used in the following ways:
I said ideally TOTP because MFA over SMS is bad, and email is only slightly better. It would be best to be able to use an open source authenticator app.
Describe alternatives you've considered
There's no real alternative that I can think of for things like territory ownership, but for balance concerns, you can link to an external wallet with budgets to help minimize risk.
Additional context
Discussed here
The text was updated successfully, but these errors were encountered: