We're excited to announce support for Ledger and Trezor hardware wallets in the Zabo API!
Hardware wallets are an important tool that enable you to take complete control of your cryptocurrency. Today there are millions of hardware wallets being used across the world to help people securely store their crypto. It's no surprise that hardware wallets were one of our most requested features!
One of the attractive elements of hardware wallets is that they hold assets offline in a physical device, away from potential hackers and other attackers. However, one downside to this approach is that hardware wallets are disconnected (by design) from your other financial services.
Historically this disconnect has made it difficult for users to track their assets within a hardware wallet, especially in other financial services tools. This difficulty is compounded by the fact that the various hardware wallets have unique technical architectures that require dedicated engineering resources to integrate. Creating a Trezor integration doesn't also get you a Ledger integration.
With Zabo, developers can let their users connect Ledger and Trezor wallets to their app with the exact same, few lines code.
Even better, the data that is returned from all connected wallets (balances, transaction history, other account data) is exactly the same format. This standardization saves time for the user, saves resources required for connecting wallets and saves resources on integrating the wallet data into your app!
How it works
Zabo gives your app the ability to connect to hundreds of cryptocurrency wallets in completely whitelabeled, native way. This is done by embedding a widget into your app with just a few lines of code.
Here's what it would look like from your users' perspective:
After your users have authenticated their wallet, the data will be accessible to your application.
Importantly: Zabo does not change the underlying security model of the connecting wallet. Users with hardware wallets need to authenticate like they normally would. In other words, it's just as secure as normal usage.
xPub (Extended Public Key) functionality
Hardware wallets are unique in that they typically create a new public address each time cryptocurrency is received. Since public addresses are viewable by anyone on the network, creating new addresses for each incoming transaction provides some privacy.
However, the creation of new addresses for each transaction received renders searching via a single public wallet address ineffective for hardware wallets.
To access the entire balance and history of a hardware wallet, you must must have a users' xPub (extended public key) address. By letting your users extract their xPub addresses directly from hardware wallets, Zabo is able to provide a complete picture of assets held on the device.
Zabo also supports direct entry of xPub addresses beyond hardware wallets. If you're a developer or wallet that is using xPub outside hardware wallets - reach out!
We aren't stopping here though.
We plan to integrate other hardware wallets and wallets that leverage xPub functionality and have many more connections on the way! Stay tuned.