Overview
WaaS React SDK
Wallet as a Service (WaaS)
- Overview
- Quickstart
- Errors
- Pagination
- Wallet Creation APIs
- Wallet Experience APIs
- NFT APIs
- Web3 APIs
- SDK
Integrations
- Get Started
- Authentication
- Connectors
- FAQ
- Partners
FAQ
Here are answers to the questions we get asked most often.
Bitski wallet natively supports:
- Ethereum mainnet
- Ethereum Goerli
- Polygon mainnet
- Polygon Mumbai
- Optimism mainnet
- Arbitrum One mainnet
If you’d like to use low-level RPC calls, we support any EVM chain. See our Web3 docs for more information.
Secure key storage is very challenging. One other possible option besides Bitski is a siloed approach. However, this approach, will be inconvenient for your users. Users will have to fund this wallet separately, and can then only manage their assets through your interface.
A great place to start is via our connectors! We support many wallet list ecosystems like RainbowKit, BlockNative Onboard, and Web3Modal. Check out our RainbowKit connector for an example.
We designed the Bitski SDK to be compatible with other wallets and dapp browsers, while still providing a great experience for users who don’t already have a wallet. Learn more about integrating our JS SDK here.
Our keys are both created and stored on our HSMs (Hardware Security Modules). Approved transactions are passed to the HSM to sign. The keys never leave the hardware.
Not at the moment, but that is definitely on our roadmap!
Currently for ETH, users can sign into our web wallet and click Get ETH to purchase via credit card. However, if you’re working with digital assets, we suggest using a backend with App Wallet to send assets to users directly. This prevents the need for the user to purchase ETH, while allowing them to have decentralized ownership.
Feel free to reach out to us.