Limitations and Known Issues
This page is not a disclaimer. It inventories what the production build does not do, what will not be built, and where this documentation can still be wrong.
Not enabled in this production build
Section titled “Not enabled in this production build”| Status | |
|---|---|
| Wallet sign-in | Not configured. The interface states this. There is no session to recover |
| Launch submit | Every venue in the Deploy form is listed and disabled. No token is created from this build |
| Trade / swap submit | Order panel and quote interface render. Nothing is constructed or broadcast |
| Volume Bot / Batch Send | Forms visible. Plans are not accepted |
| Snipe | Not available |
| Trackers | Empty. That feed is not available |
| Platform token / access gate | No token has been issued. No gate is in force |
| Platform fee collection | No treasury address is published. When no recipient is configured, no fee is charged — see Fees |
| Messaging bot | Not available |
| Browser extension | Not available |
| Condition-triggered automation | Not built. Volume plans, when they run, are clock-based, not condition-based |
| Custodial unattended trading | Not planned; see below |
| Dedicated reporting address | Not published. See Contact |
No venue accepts a launch from this build.
Easy to misread
Section titled “Easy to misread”The terminal shows boards, order panels, and deploy fields that resemble a live trading product. They are the intended layout. A control labelled as a buy, a Deploy submit, or a volume-plan start does not move funds.
If documentation and the screen disagree, the screen’s disabled state is authoritative, and this page should be corrected.
Not planned
Section titled “Not planned”Custodial unattended trading. It conflicts with Custody & Security. The usability advantage is real. It does not justify holding decryptable keys.
Investment advice, return projections, or return commitments. The platform is a set of tools, not a recommendation.
Paywalled security. Confirmation states and slippage bounds are properties of the product working. They are not a paid tier.
Operating requirements
Section titled “Operating requirements”| Browser | A current desktop browser |
| Wallet | Not required to read. Required to sign, once sign-in is configured |
| Automation | Will require the page to remain open. The server does not sign |
| Network | If a feed cannot be reached, the interface should empty or degrade, not invent |
Trading crypto-assets carries the risk of total loss of principal.
The platform is a set of tools. It provides no investment advice, makes no commitment regarding trading outcomes, and does not guarantee that any transaction will be confirmed on-chain or executed at a particular price.
You bear full responsibility for every transaction you initiate. The platform does not hold user assets and therefore cannot reverse, freeze, or recover any transaction once submitted.
You are solely responsible for ensuring that use of the platform complies with the laws of your jurisdiction.
Reporting issues
Section titled “Reporting issues”If this documentation diverges from actual behaviour, report it through Contact once a channel is published. Where documentation and the running product disagree, the product is authoritative, and the discrepancy is a defect in the documentation.