FAQs

Looking for answers? Check out the most frequently asked questions about the Suku Wallet below.

How does the Suku Wallet safeguard my funds?

The keys of your Suku Wallet are powered by Hardware Security Modules (HSM) managed by AWS. These devices are specifically designed so no one, including Suku and AWS employees, can retrieve your plaintext keys from the service. The key never leaves the device. Suku does not have access to the key. Our hardware security modules (HSMs) have been validated under FIPS 140-2, military-grade security.

Additionally, Suku Wallet is migrating to Account Abstraction (AA) based on EIP-4337. This will increase Suku Wallet's security even further and allow each user to add more than one Multi-Sig signer to their smart contract-based Multi-Sig, thereby improving not only the overall security level of our wallet but also providing more flexibility for non-custodial wallet recovery options.

The SukuWallet is an experimental project. Please use it at your own risk.

Can I send crypto to any X user?

You can send crypto to any X @handle using Suku Wallet. When recipients want to access their funds, they can simply log into their Suku Wallet with their Twitter account. This is made possible by Suku's protocol.

Can I use the SukuWallet with any other web3 app?

Absolutely! Suku Wallet seamlessly connects to web3 utilizing the well-established and audited WalletConnect technology, empowering you to use and interact with almost every Web3 app.

How does my X @handle relate to my SukuWallet?

Your TX@handle is directly linked to your Suku Wallet. It serves as the identifier for your wallet and controls your funds.

​What happens if I change my X handle?

If you change your X handle, your funds will still be associated with your previous @handle. If another user claims it, they will gain control over the related assets. It's important to remember to ensure you don't lose access to your funds.