What must be given
The settings carry how much to show at a time and the price the order rests at. Both must be above zero.
The shown amount cannot be larger than the whole. Checks that it clears the sizes the venue trades in are written beside that one and unreached: the place admitting a request passes no venue rules, and the sizes are weighed on the way out against the whole amount.
When nothing is hidden
Where the amount to show equals the whole, nothing is held back and no shown amount is named. What goes out is a plain limit order, so asking to show everything is not an error.
What Praxis does and does not do
The sending path sends that one order and reports it. It sends no portion after portion, and waits for none to fill before the next.
Praxis hands the figure over and does nothing further with it. What the venue displays, and when, is past what this code can show.
Naming a shown amount also settles how long the order rests. The builder carrying it refuses the amount on anything but a limit order, and refuses again where it is not below the whole. Two kinds of send miss that builder entirely: a market order sized in money, and a linked pair.
Left alone, the order keeps one name and one record. Changing it does not: the old order is cancelled and the replacement gets a name of its own.
Related
Source evidence
---
row: P2-22
baseline: 49aa659
created: 2026-09-28 07:18 UTC
modified: 2026-10-12 05:34 UTC
evidence:
- claim: "The settings carry a shown amount and a price to rest at, both above zero"
source: "`iceberg_params.py` 30-31, required positive at 37-41"
- claim: "The shown amount cannot be above the whole"
source: "`validate_trade_command.py` 353-355"
- claim: "The checks against the venue's smallest size, step and value are written but unreached, the one caller passing no venue rules"
source: "`validate_trade_command.py` 429-432, reached only past 143, called without rules at `execution_manager.py` 3479"
- claim: "One limit order for the whole amount is sent, at that price, with the shown amount named on it"
source: "`execution_manager.py` 5322-5331, the figure chosen at 5296"
- claim: "Where the shown amount equals the whole, nothing is named"
source: "`execution_manager.py` 5296"
- claim: "The shown amount reaches the venue as a field of its own"
source: "`binance_adapter.py` 825"
- claim: "Naming one also sets how long the order rests"
source: "`binance_adapter.py` 826"
- claim: "The builder that carries it refuses it on anything but a limit order"
source: "`binance_adapter.py` 771-773"
- claim: "Two kinds of send reach the venue without passing that builder"
source: "either `binance_adapter.py` 1505-1512 or 1522-1536, against the ordinary path at 1542-1548"
- claim: "That builder refuses again where the shown amount is not below the whole"
source: "`binance_adapter.py` 821-823"
- claim: "The sending path does not send successive portions, nor wait for one to fill before the next"
source: "`execution_manager.py` 5322-5404, which sends once and goes on to report"
- claim: "Changing the order gives it a new name and cancels the old"
source: "`execution_manager.py` 8695-8716, the replacement sent at 10324-10352"
---