When a user signs up on Authereum, a new contract-based account is deployed. Each account contract requires keys to manage it, so when you signed up a new key pair was also generated on your browser client-side. This key is encrypted with a password derived key (PBKDF2). Keys are stored in browse local storage and the encrypted keystore is stored on Authereum so that you can login in different devices.
A more detailed explanation can be read in the Authereum Key Architecture Explained article.
Yes! Authereum is offered as a web3 provider so the user on the dapp can generate a signature given a challenge string provided by the dapp and then verify the signatures on the backend using EIP1271. A number of dapps that have integrated Authereum are doing signature based authentication. Read the Verifying Signatures section for examples on using EIP1271 for verifying contract-based account signatures and check out the section on signing message using the web3 provider.
The Authereum provider is meant to be used on the browser because it relies on iframe communication to access sandboxed local storage. If running with node directly then it won't work but we are working on a provider that would work with node for backends.
Only you, the owner of the account, has access to the contract-based account (CBA). The relayer, or anyone else for that matter, does not have access to your CBA. The relayer takes your signed transaction and attaches the gas fee. The CBA meta-transaction method is responsible for refunding the relayer after the user's transaction has been processed.
Not yet, but we are working on adding support for this.
Yes! Authereum support WalletConnect. Simply scan a WalletConnect-enabled QRCode to setup the connection.
Yes! Reach out to us on Telegram or email.
No, this doesn't happen because each testnet is a separate chain and account creating involves deployment a smart contract to that testnet.
It's not possible at the moment but we are currently working on ways to use local RPCs. It's more challenging than anticipated because of different moving parts so we can't give a definite time when we'll have something ready but it's in the works.
For more FAQs, please visit the help center to view Frequently Asked Questions: https://support.authereum.org