- Rating
- 2(+1)
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
The paper describes a method for autoregressive generation of Limit Order Book messages. It restructures the LOBS5 method so that the generated tokens will be guided to produce restricted messages within message-valid borders. The process is interesting, but also restrictive as it guarantees that the messages will not have anything "unexpected", something that is happening often in the market. Experiments are using Google and Intel stocks (2025 for training, and half of January 2026 for validation and the rest of January 2026 for testing). The method is compared only with the baseline LOBS5 (and a re-arranged version of it).
Critical strengths
- The method targets a practical problem in LOB message generation methods (specifically for the LOBS5 method).
- Results show that the design of the method works.
- Experiments include useful diagnostic tests.
Critical weaknesses
- A general comment here is the actual usefulness of message generation methods. Unlike text generation, the results of which are verified for their truthfulness and informativeness and are useful any time the same/similar semantic input is needed, stochastic message generation provides plausible scenarios which become obsolete once the scenario horizon is fulfilled.
- The claims of the paper regarding generative performance superiority require thorough comparison with directly related methods (including MarketGPT, MarS, TradeFM, LOBERT).
- The use of the term "replayability" is arbitrary as its actual meaning is not the meaning the authors intent to use it for.
- In Table 1, it is not clear why o[size] > 1 for "Cancel" while o[size] > 0 for "Delete".
- The experiments use only two US stocks with 500-message rollouts and for a very limited period (10 days from January 16 to January 30, 2026).
- The method does multiple changes in LOBS5 (it changes the token factorization, obtains direct access to the exact resting-order set, uses learned reference selection, and applies constrained decoding). Ablations for all the component-level changes would show which change contributes the most to the difference in the results between the method and its baseline.
Questions for authors
- Why use the term replayability instead of the term validity?
- Why is o[size]>1 used for Cancel and o[size]>0 for Delete?
- Why experiments do not include directly related methods MarketGPT, MarS, TradeFM, and LOBERT?
- Does ReLOBGen retain its advantage when LOBS5 and other baselines receive the same explicit order-level state information and use a validity mask?
- Can you report results for more equities, different liquidity and tick-size regimes, and longer rollouts?
3 comments
Response (2/2)
[W4, Q2] Size conditions for cancel and delete
As defined in the first paragraph of Section 3.1, cancel denotes partial cancellation, whereas delete denotes complete removal of an order. A partial cancellation must remove at least one share while leaving at least one share outstanding, so the referenced order must have at least two shares remaining (o[size] > 1), consistent with the cancel constraint 1 ≤ X_t[size] < R_t[size] in Table 1. A deletion removes the entire remaining quantity and therefore only requires a positive remaining size (o[size] > 0).
[W5, Q5] Experimental scope
We matched the experimental setup to the LOBS5 evaluation in LOB-Bench, including the S5 backbone and the 500-message rollout length. We will additionally report results for longer rollouts, as well as on an additional stock as described in our response to W2/Q3, once available.
[W6] Contribution of individual components
We have already evaluated each component according to its purpose, either ensuring replayability or improving rollout realism, as detailed below.
-
Token factorization. Section 5.4 analyzes this change through teacher-forced NLL (Table 5), and Table 2 shows that it alone leaves replayability violations largely unchanged. We introduced reference-first factorization to enable replayability and therefore did not originally report its rollout realism separately. We have now added LOBS5 (ref.-first) to Tables 3 and 4, showing that ReLOBGen improves rollout realism over this baseline despite using the same reference-first backbone.
-
Access to the exact resting-order set. Both methods use the exact resting-order set during rollout; the only difference is that ReLOBGen uses it during generation, whereas LOBS5 uses it during post-processing. Please see our response to Q4 for a detailed discussion.
-
Reference selection and inference-time masking. These two components jointly guarantee replayability: selecting the reference from the eligible set ensures reference eligibility, and inference-time masking ensures event-order compatibility. Since neither alone guarantees replayability, we evaluate them together rather than separately. Section 4.3 reports that inference-time masking excludes only a small fraction of the pretrained model’s probability mass.
-
Learned reference selection. To evaluate the contribution of learned reference selection to rollout realism, Section 5.4 compares learned and uniform selection under the same eligible set and inference-time masking. Both configurations guarantee replayability, but learned selection clearly improves realism (Tables 3 and 4).
[Q4] Comparison under matched information and validity constraints
Both existing methods and ReLOBGen access the exact resting-order set during closed-loop market simulation, as the LOB simulator maintains it to process messages and update the order book. The difference lies in when it is used: existing methods use it to post-process generated messages (Appendix A), whereas ReLOBGen uses it during generation. ReLOBGen’s core contribution is to enable the baseline to use this information during generation through eligible reference selection and inference-time masking, thereby guaranteeing replayability. Tables 2–4 evaluate this approach against LOBS5 (ref.-first), using the same pretrained reference-first backbone, and show that ReLOBGen improves replayability, rollout realism, and computational efficiency.
Additional experimental results
[W2, Q3] Extended evaluation across backbones and stocks
Our original evaluation matches the LOBS5 evaluation in LOB-Bench in the number of stocks (two: GOOG and INTC) and rollout length (500 messages). We now extend the evaluation to the MarketGPT Transformer backbone on GOOG and an additional stock, JPM, retaining its model size with minor modifications to the token ordering and context length. For each stock, we compare ReLOBGen with a reference-first baseline using the same pretrained backbone and report the results in Appendix F.
The gains observed with the LOBS5 state-space backbone extend to the MarketGPT Transformer. On both stocks, ReLOBGen achieves 100% replayability and improves rollout realism, with a 2.3–3.1× speedup per replayed message. ReLOBGen achieves lower unconditional point estimates than MarketGPT on 19 of 22 metrics for GOOG and 21 of 22 for JPM.
MarketGPT backbone results on GOOG and JPM. C / R denotes correction and rejection rates, respectively. Runtime is measured in milliseconds per replayed message. Event TV is the total variation distance between generated and observed event-type distributions, in percentage points. Columns from Overall to Trades report unconditional distances for the LOB-Bench metrics. Lower is better throughout. See Appendix F for detailed results.
| Stock | Method | Post-processing (C / R) | Runtime (ms) | Event TV (pp) | Overall | State | Times | Volumes | Depths | Levels | Trades |
|---|---|---|---|---|---|---|---|---|---|---|---|
| GOOG | MarketGPT (ref.-first) | 26.7% / 37.6% | 782 | 26.4 | 0.21 | 0.16 | 0.12 | 0.15 | 0.28 | 0.13 | 0.32 |
| GOOG | ReLOBGen | 0.0% / 0.0% | 254 | 1.8 | 0.09 | 0.05 | 0.11 | 0.08 | 0.11 | 0.09 | 0.09 |
| JPM | MarketGPT (ref.-first) | 38.5% / 37.9% | 514 | 48.4 | 0.35 | 0.31 | 0.40 | 0.21 | 0.47 | 0.23 | 0.45 |
| JPM | ReLOBGen | 0.0% / 0.0% | 225 | 2.5 | 0.09 | 0.10 | 0.13 | 0.13 | 0.08 | 0.09 | 0.06 |
[W5, Q5] Longer rollouts
We report 100 rollouts of 5,000 messages each from the GOOG test period in Appendix G. ReLOBGen maintains 100% replayability without correction or rejection throughout these rollouts, while realism metrics generally degrade as the horizon increases. To address the mismatch in mid-price displacement from the fixed anchor between training and longer rollouts, we also test updating the anchor to the current mid-price every 100 generated messages, which yields a modest improvement in rollout realism.
[W1] Use in interactive market simulation
We additionally report a market-order intervention experiment in Appendix H, demonstrating how ReLOBGen can be used to examine market responses to external orders while maintaining replayability. This provides a concrete example of its use as an interactive market simulation environment.
Response (1/2)
We thank the reviewer for the detailed feedback and address each point below. Changes in the revised manuscript are highlighted in blue. For the points that require additional experiments, namely a MarketGPT-style Transformer backbone on an additional stock and longer rollouts, we will provide the additional results in a follow-up response once they become available.
[Clarification] Distinguishing non-replayable messages from unexpected market events
We would like to clarify that all real LOB messages are replayable against the order book at the time they occur. Replayability concerns whether a message can be processed against that book state. Therefore, ensuring replayability only excludes messages that cannot be processed against the current book, such as cancelling a non-existent order or executing more shares than remain. It does not exclude unexpected market events.
[W1] Practical value of LOB message generation
Coupled with an LOB simulator in a closed loop, a message generator can serve as a market world model, simulating responses to an agent’s orders and providing an environment for developing and evaluating trading strategies. For example, MarS analyzes the market impact of injected TWAP orders and trains an order-execution agent in its generated environment, while M3 [1] demonstrates simulation-based stress testing and market-impact analysis. The value of these simulations for strategy development and evaluation does not expire when an individual rollout ends.
This research direction is also studied within the broader machine learning community. MarS (ICLR 2025) develops a market simulation engine based on generative modeling of order flow, while LOB-Bench (ICML 2025) provides a systematic framework for evaluating generative LOB models. TRADES (ECAI 2025) [2] generates order flows with a diffusion model and evaluates market responses to an external trading agent. Related work includes TradeFM, presented at the ICML 2026 Workshop on Foundation Models for Structured Data, and LOBERT [3], presented at the NeurIPS 2025 Workshop on Generative AI in Finance. MarketGPT and more recent work such as M3 [1] also explore generative modeling of market microstructure dynamics.
Within this active area of research, ReLOBGen generates replayable LOB messages by construction without post-processing. In our closed-loop simulation experiments, this approach improves rollout realism and achieves a 2.7–3.6× speedup per replayed message over the LOBS5 baseline.
[1] Zhang et al. (2026). M3: A State-Event Generative Foundation Model for Market Microstructure Dynamics. arXiv:2608.19227.
[2] Berti, Prenkaj, and Velardi (2025). TRADES: Generating Realistic Market Simulations with Diffusion Models. ECAI.
[3] Linna et al. (2025). LOBERT: Generative AI Foundation Model for Limit Order Book Messages. NeurIPS Workshop on Generative AI in Finance.
[W2, Q3] Comparison with related methods
ReLOBGen is a method applied to a field-wise autoregressive generator rather than a competing backbone, and its benefits are measured against existing post-processing on the same generator. To test generality, we are training a MarketGPT-style Transformer backbone on an additional stock and will report the results once they become available. The other methods cannot be compared under matched conditions: TradeFM has no public code, MarS releases inference code and small pretrained models but no training pipeline, and both MarS and LOBERT encode each order or message as a single token, so field-wise reference selection does not apply.
[W3, Q1] The term “replayability”
We follow prior LOB simulation work, where “replay” refers to processing messages through an LOB simulator: LOBS5 calls the component that processes generated messages a “replay simulator” [4], and Nagy et al. [5] use an ABIDES-based simulator to “replay NASDAQ price-time priority limit order book markets”. We prefer “replayability” over “validity” because it directly expresses whether a message can be applied to the current order book through the simulator’s state transition without modification, which we formalize in Definition 1.
[4] Nagy et al. (2023). Generative AI for End-to-End Limit Order Book Modelling: A Token-Level Autoregressive Generative Model of Message Flow Using a Deep State Space Network. ICAIF.
[5] Nagy, Calliess, and Zohren (2023). Asynchronous Deep Double Dueling Q-learning for trading-signal execution in limit order book markets. Frontiers in Artificial Intelligence.