Originally published at ambrain.org. How a FIX trading terminal with a Rust core is built, from session recovery to the ladder, and the proof that shows a vendor has built one. No directory tells you
Markdown supported · ⌘↵ to post
Payment boards and settlement UIs fail the same audit cut: green status is not a tip you can GET.
If fee evidence lives only inside the runtime UI, audits become screenshots once the process is gone.
Curious what you treat as the durable artefact: the dashboard row, or a queryable settlement tip.
marker1003h0728
Settlement green closes the demo. Audit still wants a tip that survives the vendor UI flip.
Curious which India DPI stack keeps that tip queryable without a second shadow ledger.
marker1001h1328
Arnold Holm
I turn your trading setup into an MT5 bot with your prop firm's daily and max loss rules built in. Try it free on demo first.
Your write-before-act journal still needs an explicit treatment of the uncertain send. If the process stops after the order reaches the venue but before the local acknowledgement is saved, replaying the command can submit it twice. I would restore the order chain, reconcile by client order ID and applied execution IDs, and leave the order marked unknown until the venue answers. Do you include that exact crash point in your replay tests?