Activation notice: block 7,400,000
This page records what changed on chain 114514 at block 7,400,000.
In effect since block 7,400,000 (chain 114514). Everything on this page is in force. The page records what changed at that boundary, because a client written against the older behavior breaks on the rows below.
{"type":"account_state","address":"0x…"} returns the current height. Use it to check where the chain is.
One release moves twenty behaviors at one height, so the chain gains one boundary. The rows below are the ones a caller can observe. The rest of the release is internal. It changes no request, response or rejection that you can see.
New rejections
| Surface | Behaviour |
|---|---|
submit_order on a perp | An order whose leverage cannot survive its own MAINTENANCE margin is refused with InsufficientMargin. See below. |
activate_pair (governance) | A spot pair with no price/size grid is refused. A zero tick or zero lot IS "no grid". |
listing (governance) | A market symbol outside the accepted bound is refused. |
An account under quarantine_user | Its orders are refused at admission. Below this height the flag was recorded but never enforced. |
The admission maintenance floor
This row is the most likely to change what your client sees. Below 7,400,000, admission reserves INITIAL margin, but the liquidation engine demands MAINTENANCE margin. A market can have high base leverage against a low maintenance ratio. BTC and ETH both qualify. On such a market, the system can admit an order, and the position is under water the moment it fills.
At and above the height, the maintenance ratio clamps the admission divisor. The system now refuses that order with InsufficientMargin. No oid is burned and nothing rests on the book, so the rejection is clean.
If you size positions to survive maintenance, you need to do nothing. If you place orders at the leverage ceiling, expect a rejection that did not happen before. Size down. Do not retry.
Changed behavior
| Surface | Below | At and above |
|---|---|---|
delisting (governance) | Halts admission only. A resting order SURVIVES the delist. | The delist cancels resting orders on that market. |
| A spot match's taker rate | Can resolve more than once; a relist is admitted with no taker override. | Resolved once, and a relist requires the override. |
vault_withdraw refused for a leader | The reject text does not say what to use instead. | The text names vault_transfer as the lane. |
priority_bid outcome text | Carries the word (stub). The fee itself was always real. | The word is gone. |
The last two rows change an outcome string. A client that matches on outcome text, not on the status of the action, breaks at this height. Match on status.
New lanes
These lanes are new capability, not fixes. Each one is unreachable below the height.
A contract may call CoreWriter
Below 7,400,000, only a top-level transaction to 0x3333…3333 reaches L1. A call from inside a contract emits nothing. CoreWriter never reverts on an L1-side failure, so the call looks as if it worked. At and above the height, the contract lane is active. See Core ↔ EVM transfers.
Permissionless spot deployment
A deployer may register a token, register a pair, set its parameters and set its genesis distribution without a governance vote. This lane can create spot supply, so it is the most consequential row on this page. The spot surface documents the actions and their bounds.
Randomized TWAP slices
A twap_order may ask for a randomized slice schedule. The begin-block executor draws each slice size and each inter-slice delay from a digest over committed inputs. The draw is deterministic: every validator draws the same numbers. It makes a TWAP harder to front-run. A twap_order that does not ask for it keeps the fixed schedule, byte for byte.
Governance-only changes
At and above this height, mb_configure_chain writes the deposit-scan policy as consensus data. Below it, the chain discards the voted policy and each node reads its own file. If you operate a validator, restate the scan-policy flags on every rotation. See the bridge rotation procedure.
listing also registers the base token in total_supply. This is the registration test that gov_adjust_spot_balance reads. A listing below this height leaves that key unwritten.
Unchanged
No field is renamed, removed or re-typed. No endpoint changes availability. No signing domain moves. A client that only reads and places ordinary orders needs no change. The exception is a client that places orders at the leverage ceiling, which is the one row above.