Ecosystem
Bicrypto's in-house matching engine and on-chain custody — your own markets on ScyllaDB, your own deposit addresses on fourteen-plus blockchains, and the operational weight that comes with holding customer coins.
Ecosystem turns Bicrypto from a front-end over somebody else's exchange into an exchange. It adds two things that the core does not have and cannot fake: a matching engine that runs in your own process against your own order book, and custody — every asset a customer holds sits at an address this install derived and signs for.
Both halves are consequential. The first means market data, fills and fees are yours rather than a passthrough of Binance or KuCoin. The second means that when a withdrawal fails, nobody else is going to fix it.
Without Ecosystem, a failed integration means charts stop updating. With Ecosystem, a lost passphrase means every private key on the install is permanently unreadable and no support process can recover them. Read Master wallets and the vault before you create a single wallet.
What it requires
Ecosystem is an addon. It needs a working Bicrypto install — the core platform, its database, its Redis, its processes — and adds two infrastructure dependencies of its own:
| Requirement | Needed for | If it is missing |
|---|---|---|
| Bicrypto core | Everything | The extension cannot be enabled |
| ScyllaDB | Orders, order book, candles, trade tape, stop orders | Trading endpoints answer 503. Wallets, deposits and withdrawals still work |
| Redis | Pending-deposit persistence, balance caches, address locks, the engine lease | Already mandatory for the core; Ecosystem leans on it harder |
| Blockchain RPC access | Deposits, withdrawals, balances, token deployment | Per chain — a chain with no RPC is simply an unusable chain |
Nothing else. It does not need an exchange provider, and it does not replace one: an install can run Binance-backed spot markets and its own Ecosystem markets side by side, and they use separate wallet types so the balances never mix.
Several other products in the catalogue require Ecosystem in turn — Futures Trading, NFT Marketplace, AI Market Maker and the Hummingbot Connector all trade against, or settle through, the engine this addon installs. So do the four blockchain addons (Solana, Tron, Monero, TON), which extend Ecosystem's custody to chains the base addon does not carry.
The custody model, stated plainly
The single most common misreading of this product is that the master wallet is a reserve — that customer coins pool in one address the platform controls. They do not.
- Every ECO wallet gets its own HD-derived deposit address per chain. That address is where the coins actually are. The derivation index is recorded per wallet, the key material is encrypted with the vault key, and the encrypted blob in the database is the only persisted copy.
- The master wallet is a gas tank. It pays the network fee when the platform moves a token on a customer's behalf, it deploys token contracts, and it deploys custodial contracts. Its balance is not backing anything.
- Custodial contracts exist for one narrow case. EVM tokens that cannot
delegate their own fee (
NO_PERMIT) deposit into a shared contract the platform deployed, because the user's own address has no gas to move them out. Every other combination — native coins, permit-capable tokens, UTXO chains, Solana, Tron, TON, Monero — deposits straight to the user's own address.
The consequence for an operator: coverage is a per-asset question, not a single balance you can look up. The admin overview computes it that way — what customers are owed against what the platform records itself as holding, minus what the withdrawal engine has already spoken for — and refuses to sum across currencies, because there is no price feed in that payload and adding BTC to USDT would be a confident wrong number on the one page that must not carry one.
What it adds to the platform
A wallet type. ECO wallets sit beside the core's FIAT and SPOT wallets. They are the only wallets that can withdraw on-chain through this addon, and the only ones the engine will trade.
Markets you define. A market is a pair of two active Ecosystem tokens, with
your own precision, limits and maker/taker fees. Users reach them from the
market list at /ecosystem and trade them at
/trade?symbol=BTC-USDT&type=spot-eco.
An order book in ScyllaDB. Limit and market orders go through the matching
engine; stop-limit and stop-market orders rest outside it until their trigger
price is crossed. Orders, candles, the aggregated book, the trade tape, the
open-order index and stop orders all live in the trading keyspace.
Deposits and withdrawals on your chains. Twelve built-in EVM chains, four UTXO chains, four licensed non-EVM chains, plus any number of operator-defined EVM chains added from the admin panel without a code change.
An admin console at /admin/ecosystem — chain diagnostics, master and
custodial wallets, the private ledger, unspent outputs, markets and tokens.
Where to start
ScyllaDB, Redis, the vault key, and enabling the extension. Do this before anything else on this page.
The three chain families, how to enable one, and the diagnostics console that
tells you which .env key is missing.
Key custody, the passphrase trade-off, and what the master wallet actually pays for.
Per-user addresses, custodial contracts, token contract types, and how a deposit becomes a balance.
Deploying or importing a token, then turning two of them into a tradable pair.
Every screen in the addon's nav, what it is for, and the permission each one needs.
Where the engine runs, the cron jobs it registers, the repair scripts, and what your backups do not cover.
Every variable the addon reads, what breaks without it, and the ones that are dead.
Before you commit to running this
Three facts worth knowing on day zero rather than day ninety.
ScyllaDB is not in your backup. The built-in database backup covers MySQL
only, and so does mysqldump. Orders, candles and the trade tape are not in
either. If you run Ecosystem, you own Scylla's backups.
Provider instances are cached at module load. Changing any chain variable in
.env requires a backend restart. There is no reload button, and a chain that
looks misconfigured after an edit is usually a chain that has not been restarted.
A chain's diagnostics can pass while the flow is broken. The requirements console probes RPC endpoints, explorers and provider keys individually and reports readiness per platform flow — deposits, withdrawals, tx history — precisely because "the RPC answered" is not the same as "a customer can get their money out". Use it, and read the readiness rows rather than the green ticks.