This page is a high‑level intro. For full docs, see the Trails documentation and site.
What you get
- One confirmation from any EOA or smart wallet (embedded or external).
- Unified liquidity: check balances across chains/tokens; propose viable routes.
- Automatic orchestration: swap/bridge as needed, then execute the final target call on the destination chain.
- Non‑custodial: users sign; Trails never holds funds.
Typical uses
- Pay: mints, purchases, subscriptions, in‑app currency top‑ups.
- Fund: deposits to protocols, on‑chain account funding.
- Swap: low‑latency cross‑chain swaps in‑app.
- Earn: deposit into vaults/strategies.
How it works (high level)
1
Define intent
Your app declares the destination chain, target contract/call, and desired amount/currency.
2
Inspect & route
Trails inspects the user’s balances. If passthrough is possible, it uses it; otherwise it proposes cross‑chain/token routes.
3
Orchestrate & execute
Trails bundles required swaps/bridges and submits the final transaction for the user to confirm — one signature.
Get started
- Install:
pnpm add 0xtrails - Docs & examples: docs.trails.build/home
- Use with Sequence: launch Trails from your app UI alongside Web SDK, or combine with Checkout SDK for card paths.
Trails targets EVM chains and works with any wallet. See official Trails docs for supported chains and configuration.