Auto-Trade
Virae includes auto-trade surfaces for tightly scoped strategy workflows.
Auto-trade is different from manual trading. A manual trade is a single user-confirmed action. An auto-trade task is a configured strategy that can evaluate markets over time and submit or manage orders when its rules allow.
Current user-facing strategies
The Auto Trade overview currently includes:
| Strategy | Market context | User-facing mode |
|---|---|---|
| BTC 15m Tail | BTC 15-minute recurring prediction markets | Live task when account and backend gates allow; simulations are also available |
| ETH 15m Tail | ETH 15-minute recurring prediction markets | Live task when account and backend gates allow; simulations are also available |
| Musk Tweet Count | Elon Musk post-count range markets | Configuration-gated live task and simulations |
| Weather Temperature | Temperature-market model runs | Simulation only |
The presence of a strategy card does not guarantee that live trading is enabled for every account or environment. Check the status and task controls shown in the product.
The overview and strategy pages can show:
- task configuration
- task enablement state
- current round context
- order and settlement history
- diagnostics for why the strategy is waiting, blocked, or eligible
- recent decisions and execution outcomes
- simulation summaries that are separate from user live orders
How it differs from recurring crypto trading
Recurring crypto pages are market pages where the user can trade a round manually.
Auto-trade pages are strategy control surfaces. They are for configuring and monitoring a recurring decision process. Users should not treat them as ordinary market pages.
What strategies watch
Inputs differ by strategy.
BTC and ETH Tail can depend on:
- the current 15-minute market round
- Chainlink price distance and freshness
- orderbook prices, depth, spread, and liquidity
- account and task risk limits
- settlement and redemption after the round
Musk Tweet Count can depend on:
- discovery of the current post-count market
- XTracker counter data and freshness
- available outcome ranges and orderbooks
- configuration, account, and risk gates
Weather Temperature is a simulation-only strategy. Its displayed runs should not be interpreted as user live orders.
If any required input is missing or stale, the page may show a waiting or blocked state instead of submitting an order.
Task controls
Auto-trade task controls can include entry sizing, spread limits, minimum or maximum acceptable ask prices, and risk settings such as take-profit and stop-loss behavior.
The exact visible fields can vary by strategy version. Users should review the task summary before enabling a task.
Task lifecycle controls use the same meaning across Virae automation:
- Pause temporarily disables new automated entries and can be resumed with the existing configuration.
- Risk paused means a task-level loss limit, bankroll floor, or other configured exit condition paused the task. Review the task and its risk settings before resuming it.
- Delete task permanently removes the automation from the task list and cannot be undone. Existing orders and positions are not cancelled or closed, and historical activity is retained.
Only deletion is a terminal task state. Risk and exit controls pause automation rather than deleting the task.
Simulations versus live orders
Simulation and shadow results are strategy observations produced without using them as proof of a user fill.
Keep these states separate:
- a simulation decision
- a live task decision
- an order submission
- an order fill
- an order cancellation or failure
- market settlement and redemption
A healthy simulation does not prove that a live task was allowed to place an order. A submitted order does not prove it filled.
Sharing and copying a task
The Auto Trade web surface can create a share link for a task configuration. A recipient should review the copied strategy, sizing, risk limits, and account-specific readiness before creating their own task.
Sharing does not transfer ownership of the original task, wallet, position, or performance history.
Telegram entry
The Polymarket Bot opens Auto Trade in the Telegram Mini App. Current task configuration is handled in the richer Mini App or web interface rather than an in-chat setup wizard.
Settlement and history
Auto-trade history is most useful when read in three phases:
- the strategy decision that made the order eligible or skipped it
- the order state after submission
- the settlement or redemption result after the market resolves
This is why the auto-trade page can show both order data and settlement data.
User rule
Only enable an auto-trade task when you understand the product, the entry rules, and the maximum exposure you are allowing the strategy to take.