Since
0xtrails@0.16.0, Trails uses its own built-in EVM runtime by default — wagmi is no longer required. The patterns below still work for apps that share an existing wagmi session, via the @0xtrails/adapter-wagmi package. See the 0.16 release notes for the migration.How It Works
Trails detects and uses connected wallets through its built-in runtime, or through wagmi connectors when you install the wagmi adapter. For apps that already use wagmi, wrap your app with a wagmi provider, include the desired wallet connectors in your config, and passwagmiAdapter({ wagmiConfig }) to TrailsProvider.
Basic Wagmi Setup
Sequence Wallet Integration
Integrate Sequence smart contract wallets for enhanced security and user experience:Privy Embedded Wallets
Integrate Privy for seamless embedded wallet experiences. You can try live demos below:Multiple Wallet Support
Combine multiple wallet connectors to give users choice:Supported Wallet Types
Trails works with all wagmi-compatible wallets including:- Injected Wallets: MetaMask, Coinbase Wallet, Brave Wallet
- WalletConnect: Any wallet supporting WalletConnect protocol
- Smart Contract Wallets: Sequence, Safe, Biconomy
- Embedded Wallets: Privy, Dynamic, Magic
- Mobile Wallets: Rainbow, Trust Wallet, Phantom
- Hardware Wallets: Ledger, Trezor (via connectors)
Key Benefits
- Universal Compatibility: Works with any wagmi connector
- No Wallet Modifications: Wallets don’t need ERC-7702, 4337, or other external dependencies
- Cross-Chain Transactions: Complex multi-chain operations in 1-click
- Flexible Integration: Use existing wallet infrastructure
- Future-Proof: Automatically supports new wagmi connectors