Case study
G3 Trade
How the command bot turns a desk instruction into a fill you can inspect.
G3 Trade accepts allocated capital and trades authorized accounts on your behalf. Direct books if you want involvement. Specialist-run books if you want the desk on the session. The command bot is how the operator works the ticket: account, symbol, quantity, then confirm. Reporting on the website shows the fill.
Updated · Written by G3 Trade · Published by G3 Trade
Paper walkthrough
Propose, confirm, then a sample fill
This page is a scripted walkthrough of how the desk works a ticket: propose, confirm, then a sample fill. It is educational only — not live trading, and not a public desk.
Paper execution starts off. The bot stays idle.
Investor book
Book A
Sim101
Book B
Sim204
| Account | Side | Qty | Fill |
|---|---|---|---|
| Waiting for a confirmed paper ticket. | |||
Command bot
Simulated sample. These results are based on simulated or hypothetical performance results that have certain inherent limitations. Unlike the results shown in an actual performance record, these results do not represent actual trading. Also, because these trades have not actually been executed, these results may have under-or over-compensated for the impact, if any, of certain market factors, such as lack of liquidity. Simulated or hypothetical trading programs in general are also subject to the fact that they are designed with the benefit of hindsight. No representation is being made that any account will or is likely to achieve profits or losses similar to these being shown. Disclosures.
Two surfaces
What you see, and what the desk does
Investor
A scoped login on the website
After onboarding, G3 Trade issues a login for your allocation. You inspect fills reported by the venue, statements, and equity. Drill from account to ticket.
Desk
The operator works the bot
Account, symbol, and quantity sit on the ticket. The bot proposes. The desk confirms. Paper fills stay paper. Live never auto-confirms, and quantity is never guessed.
Education
Alpha and survival are different engines
G3 Trade is the desk. The command bot works the ticket: account, symbol, quantity, then confirm. The edge lives outside this software — in NinjaTrader, TradingView, or the operator. Survival rails on the desk run independently of that edge.
Generating the edge
A book makes money only if the signal has an edge. Typical families: trend following in sustained moves, mean reversion in ranges, statistical arbitrage across related prices, market making around a spread. Those methods are not built into the command bot. The bot restates a ticket. It does not pick a market regime or invent size.
Watching for losses
Profit on a ticket is irrelevant if one session takes the book out. Survival is separate from the signal. On this desk that means a kill switch the operator confirms, a daily drawdown flatten the operator sets, a heartbeat flatten if the hub goes silent, and quantity ceilings. Paper execution on this website starts off.
Illustrative arithmetic
Suppose a $10,000 starting balance and a rule that a single stop may not cost more than 2% ($200). A 15% drop from that start is $8,500 — a pause level some desks use while they inspect the process. Those figures are hypothetical. They do not size a G3 ticket and they are not a track record.
Hypothetical figures. These results are based on simulated or hypothetical performance results that have certain inherent limitations. Unlike the results shown in an actual performance record, these results do not represent actual trading. Also, because these trades have not actually been executed, these results may have under-or over-compensated for the impact, if any, of certain market factors, such as lack of liquidity. Simulated or hypothetical trading programs in general are also subject to the fact that they are designed with the benefit of hindsight. No representation is being made that any account will or is likely to achieve profits or losses similar to these being shown.
What this desk actually has
- Kill switch: flatten and cancel across connected accounts after the operator confirms.
- Daily drawdown: flatten when loss versus day-start equity hits the operator threshold (software default 5%, not the 15% example above).
- Heartbeat: if the hub or NT8 socket goes silent past the timeout, the process flattens locally.
- Quantity ceilings and proportional copy sizing — allocation math, not stop-distance risk.
- BOT_EXECUTION off, paper, or live. Live never auto-confirms. Quantity is never guessed.
Educational only. Not investment, trading, legal, or tax advice. Not a recommendation to trade any instrument or to use any size, stop, or drawdown figure. Risk disclosures.
The path
Four steps on every ticket
01
Set the ticket
Account focus, symbol, and an explicit quantity. Incomplete tickets stop. The bot does not invent size.
02
Propose
The command bot restates the side, size, symbol, and account. Nothing has filled.
03
Confirm on the desk
The operator confirms. Live never auto-confirms. Paper on this website is a sample only.
04
Inspect the fill
The book shows account, side, quantity, and price. That same tape is what reporting is built to show.
Next step
Talk to G3 Trade
Request access when you want a program conversation. After onboarding, investors inspect fills on the website — they do not receive the desk.