TPWallet's Integration with Hardware Security Modules (HSMs)

Important distinction first: TPWallet does not natively connect to enterprise rack-mounted HSM appliances. What TPWallet integrates with are consumer hardware wallets (Ledger, and its own KeyPal hardware wallet) — pocket-sized signing devices that contain a certified secure element chip, functionally the consumer-grade equivalent of an HSM. True enterprise HSMs (FIPS 140-3 Level 3/4 rack appliances, PCIe cards with active zeroization) sit in custody platforms and multisig infrastructure; they are not paired directly with a mobile wallet app.

How the Integration Model Works

TPWallet acts only as the viewing and transaction-construction layer. The private key and seed phrase never enter the phone or browser:

1. TPWallet reads the public address and account list from the connected hardware device over USB, Bluetooth, or QR/bridge depending on the model.
2. When you initiate a transfer, token approval, DApp signature or swap, TPWallet sends the unsigned transaction payload to the hardware wallet.
3. The hardware device displays the recipient, amount, fee and contract details on its own screen.
4. You physically confirm and sign on the device; the signature returns to TPWallet, which broadcasts the signed transaction on-chain.
5. No seed phrase, no private key export, no key exposure to the app, DApp or phone OS.

Supported Connection Modes

USB / OTG: Ledger connected over cable on Android; supported on iOS, Android and the TPWallet browser extension per official docs. Bluetooth: wireless pairing for Bluetooth-capable Ledger models through the app or extension. QR / bridge-based: air-gapped or bridge devices communicate by scanning signed payload codes; KeyPal pairs through its desktop bridge tool with the extension wallet. Extension route: on desktop, the TPWallet Chrome/Firefox extension connects hardware devices through a bridge and mirrors the account for DApp interaction.

What You Can Do After Connecting

View balances and addresses for all accounts derived on the device. Send, receive, approve tokens and sign typed-data messages. Interact with DApps (swaps, staking, perps, NFT marketplaces) inside the TPWallet browser; the final confirmation always happens on the hardware screen. Manage multiple derived accounts under the same seed without importing keys into TPWallet.

Step-by-Step: Connect a Supported Hardware Wallet

1. Initialize the hardware device first on its own companion app: set PIN, back up the recovery seed offline, update firmware, and open the relevant chain app (e.g., Ethereum, TRON, Bitcoin) on the device.
2. Open TPWallet, go to the wallet selector, choose Add Hardware Wallet, and pick your device model.
3. Pair over USB/Bluetooth/QR as prompted; grant connection permission in TPWallet.
4. Select the derivation account you want to display; TPWallet shows the public address without ever importing the seed.
5. For any transaction, review details on the hardware screen, confirm with the device PIN/button, then the signed transaction broadcasts.
6. For DApp interaction, connect through the DApp browser and approve each signature directly on the hardware device.