Users won't use they keyboards to input password for setup password, they would just choose the utf-8 character elegantly from our list of utf-8 chars with fitlerns based on language , emojis and so on.

- WE don't need 2FA to sign Txs, this is what we do:

We have very strongly held backend wallet that will never be hacked.

Users empty their aptos account to our system wallet post registration of 1P (2FA protocol) ,session state.

We should ideally have in sidebar :

1. Import wallet or generate a new wallet
2. ANd Faucet to claim funds
3. Bind the wallet to session

To register (Should have imported or generated new wallet with sufficient balance):

0. EMpty the balance of the account (min 1 APT) to the 1p system account (process.env.APTOS_ACCOUNT)
1. 1 Letter password (any utf-8 character)
2. Choose the direction mapping for colors.
3. Never remmber the password in the frontend, but the setup , directions would be binded to tthe cache

Now what next...

Sidebar another page - Authenticate

- to authenticate 1P after importing wallet

Sidebar another page - Manage wallet (only if 1P autheticated)

Send tx flow and the transfer actually happens via the backend through process.env.APTOS_PRIVATE_KEY (our system wallet) - to the input address ...