Docs
ZeroTrade docs that reduce friction after purchase
Move from purchase to a confident paper-mode deployment without ambiguity, hype, or hidden steps.
Quickstart path
Go from purchase to a working node with hardware guidance, setup, activation, and first paper-mode validation in one sequence.
License and activation
Understand how no-login purchase, transaction verification, local activation, handshake signing, and grace windows fit together.
Risk and mode policy
See exactly how demo, replay, paper, and live are separated, and what deterministic checks stand between signals and execution.
SSH and local panel path
Understand the real access model in plain language: SSH into your machine with its domain or server IP, then open the local panel through an SSH tunnel from your home PC.
Oracle and replay
Learn how local Gemma and BYOK OpenAI power explanations, briefings, and anomaly triage without becoming an unsafe execution authority.
Quant and ZeroTrade Quantum
Understand the deterministic factor model, optional IonQ-compatible research probes, prepared-only defaults, and why quantum output remains advisory.
Documentation Map
What these docs cover
Operator Manual
Install, upgrade, backups, health checks, and service lifecycle guidance for serious long-running nodes.
Mode Policy
Clear separation between demo, replay, paper, and live so nobody confuses simulation with production behavior.
License Handbook
How keys, account ids, node handshakes, update channels, and grace behavior interact.
Risk Guide
What the risk-core checks, why it rejects drafts, and how tiny-wallet constraints behave.
Research Standards
How ZeroTrade talks about methodology and proof
Replay and paper are part of the research loop
ZeroTrade is designed to prove behavior through replay, anomaly review, and live-paper posture before deeper trust is earned.
Historical claims need assumptions
If the product ever publishes strategy research, date ranges, fees, slippage, limitations, and the difference between simulation and live operation should be clear.
Public credibility should stay evidence-bound
The site is stronger when it avoids invented biographies, anonymous-expert theatre, and unsupported historical-performance boasting.
Operations complete the math
Research is only useful if the runtime can survive stale data, venue degradation, drawdown limits, and deterministic trade gating in production.
Journey
The path from purchase to live-ready confidence
SSH Tunnel In Plain English
Explain the remote panel path the way a normal customer expects
The private panel is not running on the public website. It lives on the machine where the node is installed.
The normal login pattern is ssh ubuntu@example.com or ssh ubuntu@serverIP, depending on whether you use a hostname or a raw IP.
Once the tunnel is open, http://127.0.0.1:8010/panel works on your home PC because SSH forwards your own port 8010 to the server's local panel port.
If you type http://127.0.0.1:8010/panel before opening the SSH tunnel, your Windows desktop is only checking itself. That is why the tunnel step matters.
Command Examples
The three commands that matter most for a first remote session
Use your own hostname if you have one.
A raw IP is fine if you do not want a dedicated hostname yet.
Keep that SSH session open, then load the browser panel on your own PC.
CLI Surface
Real commands you can use immediately
Bring the node bundle onto a clean Ubuntu host, home lab box, or mini PC.
Provision the local Ollama runtime and pull the default Gemma 4 E2B model for 16 GB class hosts.
Use the larger Gemma 4 E4B model when you want stronger local reasoning and can tolerate slower inference.
Bind the purchased credentials to the runtime.
Open the local ZeroTrade control surface in the terminal after install.
Show the first-session operator path for SSH, doctor checks, and the private panel.
Show the SSH and browser-tunnel path for the local web panel, including the plain-English home-PC flow.
Inspect deterministic paper execution, recent fills, and open positions.
Install an encrypted strategy preset into the local strategy vault.
Run the sealed daily strategy review so non-live nodes can adapt without exposing raw playbooks.
Confirm health, heartbeat, and mode posture before operating.