Overview
Welcome to the developer documentation for BitTap Wallet.
Last updated
Welcome to the developer documentation for BitTap Wallet.
Last updated
Tapd is the official implementation of, but with an issue that end users must deploy an own Tapd and LND locally to master their wallet keys; otherwise, they have to escrow their wallet keys to the service provider who is running and locally.
BitTap solves this issue by introducing another layer, which Bittapd stands for. Bittapd is a service deployed on the Tapd side, working like an Taproot Assets Protocol's agent to help facilitate the interactions between Tapd and end users which have their self-custodial keys.
The architecture of BitTap Wallet shows below. End users aka. Browser Extension Wallet don't communicate with Tapd directly, instead they call Bittapd's API for everything except that they will generate their own private/public keys for BTC and Taproot Assets.
End users generate and manage the keys, and Bittapd don't need private keys to work. When private keys are needed to sign a transaction, Bittapd will ask for it to be conducted on the wallet side by the end user. In this way, BitTap wallet is a truly non-custodial wallet for Taproot Assets.
While BitTap team has developed the first non-custodial browser extension wallet for Taproot Assets in the world, we would like to open the capability to our partners to build truly decentralized web3 together so that in our partners' products, end users can truly own their Taproot Assets as well.
