Universal Compatibility
Support all custody models without vendor lock-in:Self-Custody
Hardware wallets, software wallets, or browser extensions under your control
Institutional Custody
Fireblocks, Copper, Coinbase Prime, or any licensed custodian
MPC Solutions
Multi-party computation providers like Dfns, Zengo, or Qredo
Smart Contract Wallets
Safe (formerly Gnosis Safe), Argent, or custom account abstraction implementations
Network-Specific Integration
Custody requirements vary by blockchain - Ethereum wallets differ fundamentally from Solana wallets. Trusset handles these differences automatically:- Automatic Detection: API calls, White Label apps, and the Issuer Platform detect the target network and integrate appropriate wallet providers.
- Native Support: Each blockchain’s native wallet standards work out-of-the-box - MetaMask for EVM chains, Phantom for Solana, and so on.
- Unified Interface: Despite underlying differences, you interact with all networks through identical API endpoints and dashboard interfaces.
Relayer Integration
The Relayer eliminates manual signing for backend operations. Instead of signing every transaction through your custody provider, configure a relayer with a vault-stored private key and execute operations through API calls. The relayer complements traditional custody by handling routine automated tasks while you maintain custody control over high-value operations and admin functions.Custody Provider Examples
Common integrations across different custody models:| Provider Type | Examples | Integration Method |
|---|---|---|
| Hardware Wallets | Ledger, Trezor | Direct browser connection |
| Browser Extensions | MetaMask, Phantom, Rabby | Web3 provider injection |
| Institutional Custody | Fireblocks, Copper, Anchorage | API-based signing |
| MPC Providers | Dfns, Zengo, Qredo | SDK integration |
| Smart Contract Wallets | Safe, Argent | Contract interaction |
Relayer
Automated transaction relay for backend operations
Instances
Instance-level wallet configuration