Will Hyperliquid introduce KYC by September 30, 2026?
Probability
5¢
1h
+0.0pp
24h
+0.0pp
24h Vol
$0.00
Liquidity
$4.7K
Canonical status
confidence: highSource status (Polymarket)
Derived status (Orrery)
Reason
Active market, expiry beyond the near-expiry window.
Resolution & Risk
LOW risk- End date
- Oct 1, 2026
- UMA status
- n/a
- Resolution source
- Market type
- Binary
- No obvious resolution-risk signals in metadata.
Probability (last 7 days)
+0.0pp 7dWhy did it move?
Structured · 1 factor- 01Liquidity
Thin liquidity
Only $4.7k of visible book — small orders can move the line. Treat the probability as a soft estimate.
What to track next
- Set an alert at the next ±5pp probability move so you find out before the next leg.
- Add to your watchlist — Home will show probability deltas since your last visit.
- Compare against sibling markets in the same event below — divergent pricing across related contracts is the cleanest tell.
Verification actions only — never trade recommendations.
Each factor is grounded in a single named metric you can verify on this page — probability, volume, liquidity, signal, resolution state. No predictions, no prose hallucinations.
Resolution & Risk
LOW risk- End date
- Oct 1, 2026
- UMA status
- n/a
- Resolution source
- Market type
- Binary
- No obvious resolution-risk signals in metadata.
Verification Brief
A guided checklist for what must be proven before this market is treated as reliable context.
The market is live. Track source, liquidity, and wording before escalating it to a resolution-sensitive task.
Create trust-state alertVerification goal
Map resolution-relevant sources to the exact criteria needed to avoid misreading price as settlement.
What needs proof
Primary source
requiredConfirm the primary source and whether it directly answers the market's resolution question.
Current evidence: x.com
Contract wording
requiredExtract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule.
Orrery verification task Will Hyperliquid introduce KYC by September 30, 2026? State: Live — live monitoring Need sources for: 1. Primary source: Confirm the primary source and whether it directly answers the market's resolution question. 2. Contract wording: Extract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule. 3. Liquidity context: Check whether the move is supported by enough liquidity and volume to treat it as meaningful context. Drop only durable links that map to one criterion. Research only. Not trade advice.
Orrery verification brief Will Hyperliquid introduce KYC by September 30, 2026? State: live monitoring Verify: Primary source + Contract wording Price is not settlement. Research only. Not trade advice.
Market link goes in reply
A controlled loop for durable sources. Every source must answer one criterion from this Verification Brief.
Sources
0
Criteria covered
0
Reviewed
0
Awaiting review
0
Submit a source mapped to a criterion
Recent source checks
Pilot audit summary
Research only · Not trade advice · Every source maps to one criterion
Timeline
critical · price · trade flowCritical
- Oct 1, 04:00 UTCScheduled resolutionLOW
Market resolves in 1891.8h
Price movement
+0.0pp over the last 24h, now 5¢.
Recent Trades
No recent trades visible from the Data API for this market. That usually means liquidity is thin or this market is between event windows.
Related Markets
5- 23¢-4.5
Will Hyperliquid introduce KYC by March 31, 2027?
Other · Vol $0.00
- 34¢-1.0
Will Hyperliquid introduce KYC by September 30, 2027?
Other · Vol $0.00
- 8¢0.0
Will Hyperliquid introduce KYC by December 31, 2026?
Other · Vol $0.00
- 30¢0.0
Will Hyperliquid introduce KYC by June 30, 2027?
Other · Vol $0.00
- 37¢0.0
Will Hyperliquid introduce KYC by December 31, 2027?
Other · Vol $0.00
Market Description
This market will resolve to "Yes" if Hyperliquid officially implements KYC requirements for users by 11:59 PM ET on the date specified in the title. Otherwise, this market will resolve to "No". KYC is defined as a mandatory identity verification process — including but not limited to submission of legal name, government-issued ID, proof of address, or biometric verification — required for users to access core trading functionality on Hyperliquid (spot, perpetuals, or HyperCore). The requirement must be implemented by Hyperliquid itself, by the Hyperliquid Foundation, by Hyperliquid Labs, or via the official Hyperliquid frontend (app.hyperliquid.xyz) or any official successor frontend. Frontend-level KYC at app.hyperliquid.xyz qualifies regardless of whether the underlying Hyperliquid protocol remains permissionlessly accessible via direct contract interaction or third-party frontends. KYC enforced solely by third-party frontends, wallets, or fiat on-ramp partners does not qualify. Geofencing or IP-based restrictions alone do not qualify — the requirement must involve identity collection. Optional KYC offered in exchange for enhanced features (higher limits, lower fees, access to additional assets) does not qualify if base trading functionality remains accessible without verification. A pilot, beta, or rollout limited to a specific jurisdiction (e.g. US users only) does qualify, provided KYC is live and enforced for the targeted user group and the rollout is officially confirmed by Hyperliquid. An announcement, policy proposal, or governance vote without live enforcement does not qualify. Once KYC is live and enforced for at least one qualifying user cohort, this market will resolve to "Yes" — a subsequent reversal or rollback does not change resolution. If Hyperliquid announces KYC but does not enforce it on at least one live user cohort by the resolution date, this market will resolve to "No". The resolution source is official communications from Hyperliquid (https://x.com/HyperliquidX), the Hyperliquid Foundation, or the Hyperliquid Policy Center, corroborated by credible news sources.
Why this category?
confidence: lowCategory
Source
Reason
No override, sports marker, rule, or upstream hint matched. Market is unclassified — the keyword rules need an entry for this topic.
Categories come from a deterministic engine: manual overrides (highest priority) → sports hard markers → event-tag rules → keyword rules → Gamma category hint → default. The engine is versioned in category-overrides.ts; methodology lives at /methodology.
FAQ — questions readers actually ask
What is the current Polymarket probability for "Will Hyperliquid introduce KYC by September 30, 2026?"?
As of Tue, 14 Jul 2026 08:13:45 GMT, YES is priced at 5% implied probability on Polymarket. The price changed +0.0pp in the last 24 hours, +0.0pp in the last hour, and +0.0pp in the last 7 days.
When does this market resolve?
This market resolves by Oct 1, 2026 (2026-10-01T04:00:00.000Z). Resolution is determined from the market description on Polymarket.
What source determines the outcome?
Resolution is sourced from the market description on Polymarket. Polymarket's UMA optimistic oracle is the final settlement layer; if the published source is ambiguous, UMA tokenholders adjudicate. Source-extraction confidence is shown in the Resolution & Risk block above.
How much is being traded on this market?
$0.00 of trading volume in the last 24 hours. Lifetime volume on Polymarket: $1.5K. Open liquidity in the YES/NO orderbooks: $4.7K. Spread between best bid and best ask: 1.9¢.
Is this a trade recommendation?
No. Orrery describes — never predicts. Every signal on this market carries explicit Evidence, Backtest, and Action tiers. The Action is always one of: Watch only, Inspect timeline, Create alert, Verify source, or Ignore — never Buy or Sell. The probability above is the market's collective implied probability, not a forecast Orrery is publishing.
How fresh is this data and where does it come from?
This page revalidates from the public Polymarket APIs every 30 seconds. Probability and 24h-change come from Gamma; the chart series comes from the CLOB orderbook history; trade and holder data come from the Data API. The fetched-at timestamp on each block tells you exactly how old the underlying upstream pull was.
Alerts
In-app banners fire as soon as a rule is satisfied. Email digests are wired to a server-side cron and continue while your tabs are closed. Telegram and Discord are planned — every existing rule will keep working as channels light up.