[PYNE live trading]

PYNE live trading

Deploy pyne-worker, register a strategy, give it R2 bars, and let the 1-minute cron re-run on new closes. StrategyEvent rows map to HOOX actions and hop to trade-worker over TRADE_SERVICE. This is the supported Pine → order path.

Abstract

pyne-worker vendors pynescript (hoox-pyne) and speaks the same evaluate contract as Flask POST /run (mode interpret | compile | auto). It is a tooling isolate: public /run uses X-API-Key (API_KEY), not mesh INTERNAL_KEY_BINDING. The mesh key is sent only on the trade hop.

Conceptual model

Event map (trade_forwarder.py)

Idempotency: pyne:{script}:{symbol}:{kind}:{direction}:{bar}:{time}:{action}.

Alert path (not orders)

alert() / alertcondition() → JSON type: pine_alert, source: pyne-worker to ALERT_WEBHOOK_URL or per-job webhook_url. HTTPS + public host only (SSRF fail-closed). Discord-style content is supported. Does not hit trade-worker unless you point the webhook at the gateway yourself.

Interface surface

Secrets

hoox secrets set pyne-worker API_KEY
hoox secrets set pyne-worker INTERNAL_KEY_BINDING   # live TRADE_SERVICE
hoox secrets set pyne-worker ALERT_WEBHOOK_URL      # optional
hoox secrets set pyne-worker DEFAULT_EXCHANGE       # optional
hoox secrets set dashboard PYNE_API_KEY             # match API_KEY

Deploy and health

hoox pyne deploy
hoox pyne health
# or: hoox deploy worker pyne-worker

Operator CLI

hoox pyne {health,run,scripts,cron,feed,ingest,sync-vendor,deploy}

Caps (isolate): 5 MB body, 100 KB script, 100 K bars, /run wall 30 s. Rate limit 100 req / 60 s per key.

Internals

KV: pyne dashboard.jsonc is secrets only (API_KEY, ALERT_WEBHOOK_URL). Cron and TRADE_SERVICE are wrangler, not CONFIG_KV.

Invariants

1. Same-symbol request.security may work; foreign / missing feed → na. The isolate will not invent bars to force a trade.
2. Unset API_KEY is open dev mode — do not ship that.
3. Without INTERNAL_KEY_BINDING, live forwards are rejected by requireInternalAuth.
4. Paid Workers is recommended for a 1-minute cron; free-tier limits apply.

Worked examples

1. hoox pyne deploy and hoox pyne health.
2. hoox pyne ingest (or /ingest) a testnet symbol.
3. hoox pyne scripts — register a strategy with tiny size.
4. hoox pyne cron — enable the job.
5. Confirm trade-worker test fills, then remove test: true.

Language-level event fields: PYNE strategy events. Alert frequency: PYNE alerts.

Failure modes

See also

• pyne-worker isolate
• trade-worker
• Test trading
• Ecosystem
• AXIS and HOOX
• Evaluate scripts