We will be launching HYPE-USD tomorrow, 07/08 at 7 pm UTC.
Rewards will start counting for this asset at launch.
Rewards will start counting for this asset at launch.
We are experiencing an unexpected downtime. Trading might not be available at the moment.
All exchange operations are back to normal. Apologies for the inconvenience.
We are experiencing an unexpected downtime. Trading might not be available at the moment.
All exchange operations are back to normal. Apologies for the inconvenience.
We will be performing scheduled maintenance on Thursday, 9 July from 8:00 AM to 8:30 AM UTC. Trading functionality may be temporarily unavailable during this time.
Scheduled maintenance have started. Expect up to 30m of downtime.
The maintenance has been completed. All exchange operations are back to normal.
We will be launching MU-USD tomorrow, 07/10 at 6pm UTC.
Rewards will start counting for this asset at launch.
Rewards will start counting for this asset at launch.
❤2
We will be performing scheduled maintenance on Monday, 13 July from 8:00 AM to 9:00 AM UTC. Trading functionality may be temporarily unavailable during this time.
We are experiencing an unexpected downtime. Trading might not be available at the moment.
All exchange operations are back to normal. Apologies for the inconvenience.
Scheduled maintenance have started. Expect up to 1h of downtime.
The maintenance has been completed. All exchange operations are back to normal.
We will be performing scheduled maintenance on Wednesday, 15 July from 8:00 AM to 9:00 AM UTC. Trading functionality may be temporarily unavailable during this time.
Scheduled maintenance have started. Expect up to 1h of downtime.
The maintenance has been completed. All exchange operations are back to normal.
Perps v0.0.55 — What's new
Order Handling & API
More reliable order acknowledgements near expiry. Orders submitted with a short expiration could occasionally come back as
Upfront validation for bracket orders. Bracket submissions with a take-profit or stop-loss trigger that could never arm (e.g. a TP at or below a long entry) are now rejected as a whole with a clear 400 before anything is placed. Previously the parent order could go live while the invalid trigger leg was dropped, with the rejection visible only in the per-leg ack. If you use brackets, you may want to verify your trigger prices are set correctly relative to entry.
New isolated_only field on instruments. Instrument payloads now include a boolean isolated_only, indicating whether an instrument supports only isolated account margin (when false, both cross and isolated are supported). Note: the field is required in the schema, so clients with strict codegen from our OpenAPI definitions should regenerate.
Faster proxy registration with clearer errors. POST /v1/account/proxy latency is significantly reduced. Malformed expiry timestamps (e.g. seconds instead of milliseconds) now fail immediately with a descriptive 400, while a genuinely expired proxy consistently returns the documented 422 proxy_expired.
Margin & Risk Consistency
Tighter margin accounting for rapid order submission. When multiple orders for the same account arrive in quick succession, in-flight (not-yet-resolved) orders are now consistently counted toward margin usage. Margin availability is now deterministic regardless of submission timing — as a side effect, bursts of orders that collectively exceed available margin will see the excess orders rejected for insufficient margin rather than intermittently accepted.
Margin mode and leverage changes now account for pending orders. Switching margin mode or raising leverage is rejected while you have orders still in the risk pipeline (previously only resting orders were considered). This guarantees every order is margined under the settings it was evaluated with — simply retry the change once pending orders resolve.
Price-bounded liquidations. Liquidation orders are now submitted as reduce-only IOC limit orders priced at the position's fee-aware bankruptcy level, rather than unbounded market orders. This bounds liquidation execution at the price where the account reaches zero equity, making liquidation flow on the book more predictable for everyone providing liquidity around it.
Platform Reliability
Automatic recovery from transient infrastructure events. Internal stream connections now reconnect automatically with retry, and service readiness is restored on its own once a stalled sequence stream recovers. Combined with bounded timeouts on internal messaging clients, the platform self-heals after failovers instead of requiring operator intervention — meaning shorter and less frequent degraded windows.
Improved monitoring. New and refined alerting on data freshness, consumer lag, and connectivity gives us earlier detection of degradation, before it becomes client-visible.
Order Handling & API
More reliable order acknowledgements near expiry. Orders submitted with a short expiration could occasionally come back as
internal_error even though the order had been accepted and was live — the acknowledgement simply arrived a moment after the expiry cutoff. The response path now allows a short grace window for that acknowledgement to land, so the response you get reflects what actually happened to the order. No client changes needed — the response contract is unchanged. It's also the start of a broader push on engine ergonomics and reliability, with more improvements landing over the next few releases.Upfront validation for bracket orders. Bracket submissions with a take-profit or stop-loss trigger that could never arm (e.g. a TP at or below a long entry) are now rejected as a whole with a clear 400 before anything is placed. Previously the parent order could go live while the invalid trigger leg was dropped, with the rejection visible only in the per-leg ack. If you use brackets, you may want to verify your trigger prices are set correctly relative to entry.
New isolated_only field on instruments. Instrument payloads now include a boolean isolated_only, indicating whether an instrument supports only isolated account margin (when false, both cross and isolated are supported). Note: the field is required in the schema, so clients with strict codegen from our OpenAPI definitions should regenerate.
Faster proxy registration with clearer errors. POST /v1/account/proxy latency is significantly reduced. Malformed expiry timestamps (e.g. seconds instead of milliseconds) now fail immediately with a descriptive 400, while a genuinely expired proxy consistently returns the documented 422 proxy_expired.
Margin & Risk Consistency
Tighter margin accounting for rapid order submission. When multiple orders for the same account arrive in quick succession, in-flight (not-yet-resolved) orders are now consistently counted toward margin usage. Margin availability is now deterministic regardless of submission timing — as a side effect, bursts of orders that collectively exceed available margin will see the excess orders rejected for insufficient margin rather than intermittently accepted.
Margin mode and leverage changes now account for pending orders. Switching margin mode or raising leverage is rejected while you have orders still in the risk pipeline (previously only resting orders were considered). This guarantees every order is margined under the settings it was evaluated with — simply retry the change once pending orders resolve.
Price-bounded liquidations. Liquidation orders are now submitted as reduce-only IOC limit orders priced at the position's fee-aware bankruptcy level, rather than unbounded market orders. This bounds liquidation execution at the price where the account reaches zero equity, making liquidation flow on the book more predictable for everyone providing liquidity around it.
Platform Reliability
Automatic recovery from transient infrastructure events. Internal stream connections now reconnect automatically with retry, and service readiness is restored on its own once a stalled sequence stream recovers. Combined with bounded timeouts on internal messaging clients, the platform self-heals after failovers instead of requiring operator intervention — meaning shorter and less frequent degraded windows.
Improved monitoring. New and refined alerting on data freshness, consumer lag, and connectivity gives us earlier detection of degradation, before it becomes client-visible.
❤2
We will be launching SKHYNIX-USD and SKHY-USD on 07/15 at 7pm UTC.
Rewards will start counting for these assets at launch.
Rewards will start counting for these assets at launch.
SKHYNIX is LIVE for trading https://polymarket.com/asset/skhynix
SKHY is LIVE for trading https://polymarket.com/asset/SKHY
SKHY is LIVE for trading https://polymarket.com/asset/SKHY
Polymarket
$1,306.7 | SKHYNIX-USD | Polymarket
Trade SKHYNIX (SKHYNIX) perps on Polymarket.