Signature lifecycle tracker for Polymarket EOA makers. Know the moment a signed order becomes fillable at a bad price — before it gets picked off.
OrderbookTrade is the market-making infrastructure for prediction markets.
We start with observability (GhostGuard), expand to execution primitives (cancel registry, EIP-1271 adapters), and end with a full MM stack.
Today, we charge makers $299/mo to stop bleeding on stale signed orders.
Since the protocol removed fillOrder cancellation, an EOA-signed order can sit around, invisible and fillable, long after you meant to pull it.
The on-chain function you used to rely on for cancellation is gone. Signed orders now have no on-chain cancel path — only exchange-side best-effort removal.
The signed payload has no TTL and no sequence number. It stays cryptographically valid until the blockchain state itself changes — which is rarer than you think.
During volatile windows, a stale signed order can be picked off at catastrophic prices. Seen it? It's a 5-figure mistake per incident.
Webhook-based, language-agnostic — works with any stack. Drop us a POST endpoint, we do the rest.
POST /orders — raw signed payload + your maker ID. No SDK, no library lock-in.
We index the CLOB and chain; we know exactly when a signature moves between live, matched, stale, or at-risk.
Webhook fires when midpoint drifts past your threshold. Median latency: ~180ms. Ships with Discord, Slack, and raw JSON handlers.
GhostGuard detects. It doesn't prevent. If you're serious about MM'ing on Polymarket, you will eventually need both.
Monitoring layer. Buys you time.
EIP-1271 wallet + cancel registry.
Full features. Weekly feedback call required. Close cohort.
Webhook alerts, dashboard, Discord support. Production-ready.
Tailored setup against your infra. For larger books or non-standard signing.
4 years blockchain dev. Ex-NEO. Active in Polymarket #devs with the $POLY role. Shipped GhostGuard as a public Rust repo before writing this page. If it breaks, I'm the one on-call.