⚠ INTERNAL — Operator UX mock · Design preview of V2 development path · demo-wired ≠ production-live · back to dev guide
Polygon · pUSD 10
📓 Developer Guide 📋 Reason Codes 📈 Shadow Mode
JD John Doe · Admin

Liquidity-Pulse

strat.liquidity-pulse
Strategy planned Spec started frozen

Liquidity-Pulse is a market-analytics tool that monitors emerging Polymarket markets for early liquidity opportunities.

What it does

Liquidity-Pulse is a market-analytics tool that monitors emerging Polymarket markets for early liquidity opportunities. When a market's volume and attention signal crosses configured thresholds, the bot emits an OrderIntent for user-controlled maker quote placement. All execution decisions remain with the user; this bot provides structured analytics and sizing recommendations only.

Pipeline placement

runs after: Market scanner / Observation bus Liquidity-Pulse runs before: Risk guardrail pipeline

Applies to: Polymarket binary markets that are gaining attention but currently have wide spreads and thin depth, offering attractive

Why it matters

If this failsConsequence
Quote placed before sufficient volume confirmationEarly quotes on unproven markets may sit unmatched or attract adverse selection from informed traders who discovered the market first.
Spread tightening faster than quote updatesQuotes placed at the initial wide spread become the worst price on the book as other makers tighten, leading to adverse selection.
Market resolves before position unwindsShort-lived markets may reach resolution before an early maker position can be exited, forcing settlement at a potentially unfavorable resolution price.

Inputs

Polymarket inputs

InputSourceRequiredUse
CLOB book depth, spread, and volumews_marketrequiredMeasure current spread width and depth; detect volume pickup above tighten_at_volume_usd.
Market metadata (creation time, category, status)gammarequiredCompute market age; verify event_lead_time_h; confirm market is open.
Market status (open/closed)clob_publicrequiredSkip closed or resolved markets.

Internal inputs

InputSourceRequiredUse
KillSwitch active flagKillSwitchrequiredAbort all intent emission if KillSwitch active.
Attention signal (volume trend, social mention rate)internal (market scanner)requiredGate quote entry on attention signal exceeding threshold.
Builder code bytes32internal configrequiredInjected into builder field on every signed V2 OrderIntent.

Authority

What this bot is permitted to do

Trade

State

Readiness

Spec started

Status

planned

Class

Alpha Strategy

Default mode

shadow_only

Developer owner

Polytraders core — Strategy pod

Capital impact

Direct

Reason codes emitted

CodeSeverityMeaningAction
LP_QUOTE_EMITTEDINFOAttention signal fired, spread viable, hours_to_event OK. GTC post-only maker OrderIntent emitted.Emit GTC maker OrderIntent.
LP_TOO_CLOSE_TO_RESOLUTIONHARD_REJECThours_to_event < 1h hard floor. Resolution risk too high for new maker positions.Skip; no OrderIntent.
LP_TIGHT_SPREADWARNRecommended spread between 100 and 200 bps; adverse selection risk elevated.Emit with lower confidence; log warning.
LP_SPREAD_BELOW_FLOORHARD_REJECTComputed spread < 50 bps hard floor.Skip; no OrderIntent.
KILL_SWITCH_ACTIVEHARD_REJECTGlobal kill switch is active.Skip all markets; no OrderIntents emitted.

Used by

Reverse index — strategies that currently reference strat.liquidity-pulse. If you change this bot's authority or reason codes, these strategies must re-pass shadow.

StrategyStateActivity
AI Frontier — release-day takerfrozenlast triggered 38m ago
NBA props — line-shopdemo-wiredlast triggered 45m ago

Showing 2 of 2 · demo-wired ≠ production-live

Why this matters

Strategy bots does NOT sign, route, or directly submit orders to the chain. Understanding the authority boundary prevents misuse and makes promotion-gate reviews faster and more reliable. View raw spec JSON →
Polytraders Operator UX Mock · INTERNAL · demo-wired ≠ production-live · the plan · reason codes · shadow-mode pipeline
⚙ Page Configuration
Current page settings
Loading configuration…