Web3 Wallet & On-Chain Trading
A self-custody wallet layer and an on-chain trading desk. Users connect their own wallet, keep their own keys, and trade aggregated DeFi liquidity across fifteen chains and four virtual machines — EVM, Solana, TRON and TON.
Your users connect a wallet they already own — MetaMask, Rainbow, Coinbase Wallet, Trust, Phantom, TronLink, Tonkeeper, or anything that speaks WalletConnect — and trade on chain through aggregated DeFi liquidity. You take a fee on every swap.
The platform holds no funds for this product, deploys no contracts, and never signs on a user's behalf.
Fifteen chains, four virtual machines
The addon started EVM-only. It is not any more, and the distinction that matters to you as an operator is not the chain — it is the virtual machine, because that is what decides how a token is held, how an approval works, and what can go wrong with your fee address.
| VM | Chains | What is different about it |
|---|---|---|
| EVM | Ethereum, Optimism, BNB Smart Chain, Polygon, Base, Arbitrum One, Avalanche, Linea, Cronos, Rootstock, Fantom Opera, Celo | Approve-then-swap. Any address receives any token with no setup. |
| SVM | Solana | A token lives in a token account, one per mint, and each must exist before anything can arrive. |
| TVM | TRON | TRC-20 approvals, priced from SunSwap. |
| TON | TON | Jettons are per-owner contracts, not balances. The swap message is built server-side. |
On EVM, setting a fee recipient is the whole job. On Solana it is not: a perfectly valid fee address can still collect nothing, because the token account for that mint does not exist yet — and nothing about the address itself reveals that.
Wallets goes and looks, per mint, and tells you.
What that means for you
Ecosystem creates and custodies wallets for your users, and their balances live in your database. This addon does the opposite: the key never exists on your server, so there is nothing to lose, nothing to insure, and nothing to restore. The two can run side by side.
Three consequences follow from non-custody, and they shape everything else in these pages:
- A swap is a transaction the user signs. You construct it; they broadcast it. If they close the tab after signing, the trade still settles.
- Your fee is collected on chain, by the aggregator, into an address you control. It does not pass through a platform wallet, so it is not in your profit report until you move it and record the move.
- You cannot reverse anything. There is no admin button that unwinds a settled swap, because the funds were never yours to move.
Where to start
The ordered path from a licensed install to your first swap. Step 10 is the one that catches the failure that costs money silently.
Which aggregators to enable, and the two questions to answer before you commit to one.
Where your money accrues, why it is not in the profit report yet, and how to collect it.
The five places "we never hold user funds" stops being true, and the terms clauses you have to write yourself.
Thirteen consoles in daily-use order, and what each one answers.
Every setting, its default, and which three only a Super Admin can change.
The one screen to open when a chain will not quote. It names the missing piece instead of making you guess.
Where the fee lands on each chain, and whether it can actually land there.