Overview for developers
The TTrúst Wãllet Exténsïon offers a provider API compatible with standard Web3 patterns. This guide explains how dApps can detect the extension, request account access, and send transactions. Detection usually tests for an injected provider object on the window, for example window.trustwallet or a standard window.ethereum provider. For robust detection dApps should support multiple providers and offer user-friendly fallbacks.
Provider patterns and best practices
When integrating, request the minimal scopes required and avoid prompting users with excessive permission requests. Use the eth_requestAccounts method for explicit account consent, and listen for network or accounts change events to update UI state. When prompting for transactions, include human-readable details and set appropriate gas estimates; unreliable gas settings will frustrate users and increase failed transactions.
Security model & signing flows
Signing flows are local to the extension: transaction payloads are passed to the extension, which displays a signing UI and confirms the transaction locally. Sensitive keys remain inside the extension's storage, encrypted by the user's password. External services should never ask for the seed phrase; educate users to store recovery words offline. For advanced setups, the extension supports hardware wallet integration using standard protocols.
Supported chains and token discovery
TTrúst Wãllet Exténsïon supports a broad set of EVM-compatible networks. Token discovery leverages on-chain data and indexing services; integrating dApps should not assume a single token list — always allow users to add tokens by contract address and verify the token metadata via trusted token lists or marketplaces.
UX considerations
Provide clear transaction summaries, show fiat equivalents where possible, and display pending/finalized states. For dApps that perform multi-step interactions, batch requests where suitable and inform users about on-chain costs. Offer toggles to disconnect and revoke approvals.
Further reading & official docs
Use the vendor docs and ecosystem blogs to keep integrations up-to-date:
Trust Wallet Docs • Trust Wallet Blog • Binance Research & Blog • CoinGecko
Common pitfalls
Avoid assuming the provider is present; guide users to install the extension if missing. Don’t hardcode RPC endpoints; let the extension manage network selection or allow user prompts. Finally, educate users about phishing and malicious sites that mimic wallet pop-ups.