Algo Trading Bots for Bicrypto

Server-side automated trading for your platform. A user picks a strategy family, tunes it against the live price, sets a risk envelope, allocates capital and starts the bot. From then on a server-side engine evaluates that bot every few seconds and places real orders on its owner’s behalf.

Nothing runs in the browser. Closing the tab, logging out or losing the connection does not stop a bot — only stopping it does, or one of the limits it was created with.

Please read first: this is an add-on, and it needs two other products

Algo Trading Bots is an extension for Bicrypto. It does not run on its own, and Bicrypto alone is not enough. It has no standalone installer, no interface of its own outside the Bicrypto panel and no database of its own — it uses core’s wallets, KYC, notifications, permissions and cron manager. Two products are hard prerequisites, and both are sold separately:

Bicrypto (core) — wallets, KYC, notifications, permissions, the cron manager.
Ecosystem add-on — the markets bots trade, the candles they price off, and the ECO wallet their orders hold from.
Algo Trading Bots — this item.

It is ecosystem-only end to end. Bots trade ecosystem markets, price off ecosystem candles, and their orders are backed by the ECO wallet. Nothing in it can reach an exchange spot or futures book.

With Ecosystem disabled, no bot runs anywhere in the deployment — not even a paper bot, because a paper bot still needs a price feed. The platform raises a standing warning saying exactly that. There is no configuration that makes the combination work.

Please read: your users are placing real orders

A live bot places real orders on its owner’s behalf, with their own money, on your platform. Whether you may offer that, to whom, and with what disclosures depends on your jurisdiction and on what your terms of service say. The product ships a risk envelope on every bot, a platform-wide kill switch and KYC-gated selling in the marketplace precisely so you can bound it — but establishing that you may offer it at all is your responsibility, and nothing here is legal advice.

Nothing in this add-on influences a market price or a trade outcome. Bots are strategies your users configure and run against your own order book; the engine places the orders those rules ask for and nothing else. There is no mechanism anywhere in it for steering a fill, a price or a result.

Five strategy families

DCA — accumulate on a schedule or on a drawdown, with averaging-down rules and a take-profit on the averaged entry.
Grid — rest a ladder of buys and sells across a range and harvest the oscillation. The ladder rests; it does not cross the spread.
Indicator — entries and exits from technical conditions, built in the visual rule builder.
Trailing stop — follow the price up and exit on a defined retracement.
Custom rules — combine conditions and actions into your own strategy and, if you choose, publish it.

The Strategy Builder

A visual rule builder: conditions (indicator, number or percentage, with comparison and crossing operators), combined with AND/OR, driving actions (buy, sell, close position) with their own size, amount type and order type. No code, and the same engine evaluates whatever it produces.

Paper trading, then live

Every bot can run in paper mode against the same live prices and the same strategy logic, with simulated fills and a separate paper account — so a user can watch a strategy behave for a week before a single real order is placed. Live and paper can each be switched off platform-wide.

The risk envelope, and the kill switch

A bot is created with limits and cannot exceed them: a capital allocation, a maximum loss, a take-profit target, a maximum number of trades and a maximum run time. When one is reached the bot stops itself and says which limit did it. On your side there is a platform-wide kill switch that stops every running bot at once and records who pressed it and why.

An allocation does not move money. Funds stay in the user’s Ecosystem wallet and are held by the matching engine only against a real order.

The strategy marketplace

Users who build a strategy can sell it. Listings are moderated — you approve, reject, feature or unlist — selling is gated behind KYC at a level you set, reviews are moderated too, and you take a commission you configure on every purchase. A bot deployed from a purchased strategy runs the configuration the buyer paid for, pinned at the moment of purchase.

The admin console

Dashboard — fleet totals, running bots, engine health and the kill switch.
Bots — every bot on the platform with its owner, mode, allocation, trades, win rate and last error, and a force-stop on any of them.
Marketplace and Reviews — moderation queues for both, with purchases, refunds and disputes.
Settings — engine interval, per-user bot caps, risk floors and ceilings, trading modes, order types and marketplace commission.
Audit logs — who changed what, from which address.

Technical requirements

All of this is what the stack underneath already requires. The add-on itself introduces no new npm dependency, so installing it does not change the dependency tree of your installation.

Platform

Bicrypto core and the Ecosystem add-on, both installed, licensed and enabled, with at least one active ecosystem market — bot creation is refused outright on any pair that is not one.
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.
Not shared PHP hosting. A running install is long-lived Node.js processes behind a reverse proxy.

Runtime

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.
4 GB RAM minimum, 8 GB to build the frontend reliably. 2+ CPU cores. Shell access, and the ability to restart the backend.
A backend process holding the ecosystem matching lease — the evaluation engine runs there and nowhere else.

Database and services

MySQL 8.0+ or MariaDB 10.6+, reachable, with the mysql client available on the application server. The add-on’s tables are created by the platform’s update command; no existing schema is modified.
Redis — the settings cache and cron scheduling.
ScyllaDB — required by Ecosystem underneath this add-on. The candles every indicator strategy and the price fallback read live there.

API dependencies: none

The add-on calls no external service and reads no API key. It has no environment variable of its own — every setting lives in the database and is edited on an admin screen.
Prices come from the Ecosystem candles your own platform already publishes; orders go to your own order book; funds move through the ECO wallet core already manages.
There is no hosted AI service, no metering and no per-use cost of any kind attached to this item.

What is in the download

Full source code. The backend as TypeScript (97 files) and the user surface plus the admin console as TypeScript and React (59 files). No compiled-only code and no obfuscation.
Documentation — 24 pages of offline HTML covering installation, the five strategy families, the Strategy Builder, running and monitoring bots, risk management and the kill switch, the marketplace and its money, the admin console, every setting, the API reference and troubleshooting, plus five customer-facing help pages. Open documentation/index.html in any browser.
A commented .env.example which states plainly that the add-on reads no environment variable, and what does need to be in place instead.
A project manifest, a changelog covering every release, a licence file, and a small script that compiles the shipped source into a production installation.

Support

Documentation: mashdiv.com/docs/trading-bot
Support: mashdiv.com/support

Algo Trading Bots for Bicrypto - DCA, Grid & Indicator Strategies, Marketplace & Paper Trading