Aster

Aster review is a close reading of hidden-order execution

Aster review is an evaluation of the exchange's hidden-order control: a limit order with price, size, and presence kept off the public order book until execution. The feature reduces pre-trade information leakage while sharing the same matching environment as displayed liquidity. It does not promise a fill, eliminate price movement, or conceal the completed trade. Its value therefore rests on order placement, queue dynamics, and the difference between maker and taker execution.

A hidden quote may wait without filling

Set against that, Aster hidden orders fail at the most basic execution condition when the market never trades at the chosen limit price, leaving the concealed order open and unfilled.

Consider a BTC/USDT bid resting below the best ask. Aster removes the public view of its quoted price, size, and presence, yet the matching condition remains unchanged. Sellers must still reach the chosen price, and available counterflow must cover the requested quantity. If price turns early, the account holds an unfilled instruction rather than a position. A fast passage through the level may start execution without completing the intended size. The owner sees the order under Open orders, while the public depth display offers no clue the concealed quote exists.

This visibility gap also limits the owner's reading of the book. Other hidden interest remains absent, so displayed depth may understate matching liquidity at a level.

The assessment changes when opposing flow reaches the selected limit.

Fees follow maker or taker execution

Aster charges a hidden limit by its actual maker-or-taker outcome, so concealment carries no separate listed protocol fee and execution behavior determines the trading charge.

For USDT perpetuals, the published schedule sets maker execution at 0% and taker execution at 0.04%; USD1 perpetuals use 0% and 0.005%, respectively.

Concealment does not assign maker status. A buy limit posted below the best ask rests and adds liquidity; a buy limit at an executable ask removes liquidity immediately. The first outcome uses the maker schedule, while the second uses the taker schedule. Paying qualifying perps fees in ASTER applies a 5% discount. Fee equals nominal value multiplied by fee rate, with nominal value calculated from contract quantity and transaction price.

Post Only provides the maker guarantee by rejecting an order set to match immediately.

How does Aster conceal an order before execution?

On a practical level, Aster conceals a hidden order by withholding its price, size, and presence from the public book while retaining the instruction inside the same matching environment.

Before a match

A hidden instruction protects three public-book fields before execution: price, size, and order presence. After choosing a contract, leverage, amount, and limit price, the trader enables one Hidden Order control. The instruction remains visible in the owner's Open orders with a not-visible icon. Other participants do not see the quote as resting depth. It still shares the existing order-book liquidity rather than moving into a separate pool.

At execution

When matching occurs, the completed trade becomes public, and the account moves filled exposure into Positions. Aster therefore draws a two-stage boundary: concealed pre-trade intention followed by visible execution. The boundary protects an intended level while the order waits, yet it preserves completed trade records. Hidden Order describes public-book concealment before execution; Aster Chain's broader privacy design addresses encrypted orders and position data at the network layer.

Disclosure begins when matching produces an executed trade.

Partial fills start the disclosure boundary

At the other end, Aster reveals an executed trade after matching, so partial execution ends guaranteed pre-trade concealment before the trader's entire requested quantity has necessarily completed in full.

The public specification gives two firm endpoints: at 0% executed, the hidden quote stays outside the public book; at 100% filled, the order has become completed exposure. It does not define a separate disclosure rule for every intermediate state. Treat the first fill as the point where guaranteed pre-trade confidentiality ends. The execution report shows completed price and quantity, while normal limit-order state tracks any remainder. Final status changes when the residual fills, the trader cancels it, or its time-in-force removes it.

Time controls and large-order tools solve different problems

In the common configuration, Aster hidden orders remain limit orders, and their behavior should be separated from three time-in-force instructions and two scheduling tools serving different timing and disclosure needs.

Time-in-force choices

For context, Aster lists GTC, IOC, and FOK as three time-in-force modes. GTC rests until filled or canceled. IOC fills available quantity immediately and cancels the remainder. FOK requires 100% immediate execution or cancels the whole instruction. The hidden-order specification does not publish an all-combinations matrix, so the accepted controls shown in the order ticket determine the valid pairing.

TWAP and scaled execution

In day-to-day use, Aster's Time-Weighted Average Price strategy runs from a 1-minute minimum to a 7-day maximum and permits up to 30 simultaneous strategies per account. It divides size across time rather than making one resting quote invisible. Scaled Order divides size across prices, supports up to 110 sub-orders, and offers random size variance up to 10%. Those child limits appear separately on the book.

Post Only as a fee constraint

Post Only rejects immediate execution to preserve maker status. Hidden Order suppresses pre-trade display. The choice changes when fee certainty outranks concealment alone.

When does a hidden order improve execution quality?

Put another way, Aster hidden orders improve the execution decision when information leakage matters more than queue visibility, immediate completion, or the signaling value of displayed size to counterparties.

The order fits a strategy built around a fixed price, patient execution, and reduced displayed signaling. Apply this five-condition screen before selecting the control:

• The trade has one firm limit price.
• Displayed size would reveal meaningful intent.
• Immediate completion is not required.
• The account has enough margin for the full instruction.
• Maker or taker status is evaluated separately.

Consider a BTC hedge adjustment during a thin session. A displayed bid advertises both demand and size before sellers engage, while a hidden bid removes those cues and still waits at the same chosen level. This helps when the information cost of showing interest exceeds the value of attracting counterparties through visible depth. It helps less when an urgent exit requires immediate execution, because concealment does not create liquidity or move the order ahead of better-priced quotes.

Hidden execution earns its place when information control outweighs speed.

Aster beside Hyperliquid, dYdX Chain, and GMX

On the operational side, Aster differs from Hyperliquid, dYdX Chain, and GMX at the point where trade intent becomes visible, rather than merely at wallet connection or settlement time.

Hyperliquid's transparent queue

Hyperliquid runs fully on-chain perpetual and spot order books in HyperCore, with price-time priority for resting orders. Its model gives traders a public queue and consensus-level execution trail. Aster's hidden control instead removes the resting quote from public depth until matching, exchanging visible queue information for reduced pre-trade signaling.

dYdX Chain's validator order book

dYdX Chain routes an order to a validator, gossips it to other validators and full nodes, and matches it within the block proposal process. Its short-term order book lives in memory before committed fills reach chain state. That dissemination gives validators a synchronized matching view rather than a trader-selectable public concealment switch. Aster's differentiator is narrower: the public-facing book does not display the selected hidden instruction before execution.

GMX without an order book

GMX uses oracle-based pricing and liquidity pools rather than a central limit order book. Its limit instructions trigger against Chainlink Data Streams prices and execute through keepers, so displayed queue leakage is not the main decision variable. Venue choice turns on concealed intent, transparent priority, or pool-based execution.

The path from Aster Pro to Aster Chain

Alongside that, Aster introduced the optional hidden-order control in Aster Perpetuals during 2025, then placed broader encrypted-order privacy at the center of its Aster Chain network architecture.

The release record places the feature in the week beginning 16 June 2025, with mobile support following in the week beginning 7 July 2025. The established Aster Perpetuals workflow also spans four network connections: BNB Chain, Ethereum, Solana, and Arbitrum. These details locate Hidden Order as a concrete Pro trading control, not merely a privacy label attached to the ASTER token or the exchange's spot product.

Equally, Aster Chain expands the design boundary by encrypting orders before they reach the chain and decrypting them at execution. Its published architecture specifies more than 100,000 transactions per second and 50ms block latency. Those system claims address network-wide private execution, while the hidden-order workflow remains easy to evaluate through two observable account states: Open orders before a fill and Positions after it.

This Aster review separates those layers and judges the modifier at the transition from undisclosed order to published execution.