A self-custody wallet and an on-chain trading desk, inside your platform

Your users connect a wallet they already own — MetaMask, Rainbow, Coinbase Wallet, Trust, Phantom, TronLink, Tonkeeper, or anything that speaks WalletConnect — or create one inside the product, and trade on chain through aggregated DeFi liquidity across fifteen chains. You take a fee on every swap.

The platform holds nothing, and that is the point

No funds held. No contracts deployed. Nothing signed on a user’s behalf. A wallet created inside the product has its key generated and encrypted in the user’s own browser — PBKDF2-SHA512 into AES-256-GCM through WebCrypto, non-extractable. Your server stores an opaque envelope and the public addresses, so a locked wallet still renders a portfolio and there is nothing on your side to lose, to insure or to restore.

That is a build constraint rather than a promise: a scoped lint rule refuses key-derivation and cipher vocabulary anywhere in the addon’s server code, so the guarantee cannot quietly erode in a later release.

The in-product wallet announces itself over EIP-6963, which means every wallet surface you already have discovers it the way it discovers a browser extension — the swap terminal, wallet sign-in, the profile wallet tab and the NFT flows all use it with no special-casing.

Fifteen chains, four virtual machines

The distinction that matters to an operator is not the chain, it is the virtual machine — because that decides how a token is held, how an approval works, and what can go wrong with your fee address.

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 — jettons are per-owner contracts rather than balances, and the swap message is built server-side.

The Solana asymmetry is the likeliest misconfiguration in the whole product: a perfectly valid fee address can collect nothing, because the token account for that mint does not exist yet, and nothing about the address reveals it. The Wallets console goes and looks, per mint, and tells you.

The swap terminal

Markets rail, chart, and a ticket that compares quotes across the venues you enabled.
Approve-then-swap handled properly, including the USDT re-approve trap — an allowance that has to be zeroed before it can be raised — and a gas preflight before anything is sent.
A transaction machine that survives a page reload: a swap that was broadcast is still being tracked after a refresh.
A per-token risk verdict on the ticket, and a history view with the state of every swap.

One chokepoint, because after a quote the server can stop nothing

Geo restrictions, KYC level, chain enablement, the token allowlist and the slippage cap are all asserted server-side at the quote route. That is deliberate: once a quote is returned the user broadcasts to a public RPC, and nothing on your side can intervene. Everything you want enforced has to be enforced before that, and it is.

Revenue you can actually book

A fee on every aggregated swap, paid to your own fee address on chain by the router.
A separate accrual ledger. The addon records what the router paid you, and only a confirmed on-chain sweep books it as platform revenue — so your books never carry money the chain has not moved.
Direct liquidity pools for pairs no aggregator will quote. The addon calls a Uniswap V2/V3 factory and router already deployed on the chain — the factory deploys the pair, not us, so the zero-contract rule survives.
V3 collect() is bookable revenue and the collect is the sweep. V2 fees accrue into reserves and are structurally unbookable, because no on-chain fact separates fee from principal. Pick V3 if you want revenue that appears on a report.

What you run it from

Overview — quote outcomes, chain readiness, swaps needing attention, unswept fees.
Requirements — a per-chain probe that reports what actually answers, not what you configured. Those two disagree more often than you would expect.
Chains, Tokens (import, on-chain probe, screening, allowlist) and Pairs.
Providers and venue routing — who fills a swap, and who wins when both can.
Wallets — your fee addresses, checked per mint on Solana.
Quote log and Swap history, with the execution state machine spelled out.
Fees and revenue, Direct pools, Liquidity positions, a settings reference and a per-screen permission map.

Requirements — please read before buying

Web3 Wallet and On-Chain Trading is an addon for Bicrypto, a separate item sold separately. It does not run on its own — no standalone installer, no interface outside the Bicrypto panel, no database of its own. A working, licensed Bicrypto install is a hard prerequisite.

No other addon is required. In particular this is not the Ecosystem wallet and does not need it: Ecosystem creates and custodies wallets for your users and their balances live in your database, while this addon never holds a key. The two run side by side. ScyllaDB is not used.

You must bring your own vendor accounts, and they are not included

The addon talks to blockchains and to swap aggregators. It ships with no credentials of its own and cannot — the accounts have to be yours, and the rate limits, the terms and the bills are between you and those vendors. Nothing is metered or billed through this item.

A Reown / WalletConnect project id — required. Wallet connection and wallet sign-in. The free tier is enough to start. It is inlined into the frontend at build time, so it must be set before you build.
One RPC endpoint per chain you enable — required. Quotes, balances, approvals and receipt verification all read chain state. Public endpoints exist but rate-limit hard, so a paid provider is the normal choice. These resolve server-side and are never sent to a browser, because they often embed a provider key.
0x and 1inch API keys, if you enable those venues — their adapters cannot quote without one.
Jupiter and LI.FI keys are optional and only raise a rate limit. KyberSwap and Odos take no credential at all.
GoPlus for token screening, and the TRON and TON transport keys, are all optional.

Technical requirements

Linux — Ubuntu 24.04 LTS or newer, or another distribution shipping glibc 2.38+ (Debian 13+, RHEL / Rocky / Alma 10+). Ubuntu 22.04 will not run the platform. x86-64 or ARM64, glibc — not Alpine or musl. This is not shared PHP hosting.
Node.js 22, 24 or 26. No other major version boots — the platform’s HTTP server is a prebuilt native binary and ships those three ABIs only.
pnpm — the platform pins pnpm 10.28.0. npm and yarn cannot resolve the workspace.
MySQL 8.0+ or MariaDB 10.6+, reachable, with the mysql client on the application server. No existing schema is modified.
Redis, reachable and answering PING — a hard dependency of the platform, not a cache.
4 GB RAM minimum, 8 GB to build the frontend reliably. 2+ CPU cores. The platform’s cron process must be running — the confirmation sweep and four other scheduled jobs live there.
API dependencies: outbound HTTPS to your RPC endpoints and to whichever aggregators you enable. Swaps are executed by third-party aggregator routers already deployed on public blockchains; those routers are not operated or controlled by us and are governed by their own terms.

Non-custodial is a statement about custody, not a blanket exemption. This addon routes your users’ own funds through third-party DeFi routers and credits your fee address on each swap. Whether you may offer that, to whom, and with what disclosures, depends on your jurisdiction and on your terms of service. The addon gives you a geo gate, a KYC gate, per-chain enablement and a curated token allowlist, all asserted server-side, precisely so you can bound it — but establishing that you may offer it at all is your responsibility, and nothing here is legal advice. On-chain transactions are irreversible and are broadcast by the user from their own wallet: neither you nor we can reverse, recall or refund one.

It does not bridge between chains, does not custody funds, and deploys no contracts of its own. The documentation carries a page — What this does not do — written specifically so you do not promise a customer something that is not there.

Web3 Wallet & On-Chain Trading Addon for Bicrypto - Self-Custody Wallet, Multi-Chain DeFi Swaps