Idempotency in execution systems
In an execution system, a retry is a financial risk. Idempotency is the property that makes the same operation safe to repeat — so a dropped connection never doubles your position by accident.
Backtesting vs live trading: the gap where systems die
A backtest runs against a market that holds still. Live trading runs against one that fights back. Latency, slippage, partial fills, venue failure — the gap is where the promised edge quietly disappears.
Market data ingestion: the foundation nobody respects
Ingestion turns a stream of exchange messages into a consistent view of the market. Every signal and every risk decision reads from it. When it is silently wrong, everything downstream is wrong — and trusts it anyway.
The kill switch: building a system that can stop
The hard part is not stopping. It is being able to stop cleanly, fast, and from a state you can trust — on the worst day, which is the only day it matters.
Hot path, cold path
The hot path is fast and carries orders. The cold path is durable and records truth. Confuse the two and you get a system that is either too slow to compete or too fragile to trust.
Building a multi-exchange trading system
Connectors, a smart order router, a unified state store, and continuous reconciliation. The routing is the easy part — keeping one consistent position across venues that never coordinate is the system.
What financial infrastructure actually is
Settlement, custody, reconciliation, audit trail — the backend that moves capital without losing it. Invisible when it works, catastrophic when it does not, and underbuilt for exactly that reason.
On-chain settlement is harder than it looks
Finality is probabilistic, the chain is one ledger of several, and the real work lives at the boundary between on-chain truth and off-chain state. What tokenized settlement actually requires.
Why most trading systems fail
The signal is rarely the problem. Trading systems fail at the seams — where execution meets settlement, where state meets latency, where risk was treated as a check instead of a layer.
Execution is the real problem in crypto
Fragmented liquidity, inconsistent state, and venue failures turn every order into a distributed systems problem. The edge lives in execution architecture, not in models.
Risk management is a system, not a feature
A risk check runs once. A risk layer spans the whole system. The difference is the difference between catching a typo and preventing a blowup.
Ignacio Montoya is a systems architect specializing in algorithmic trading infrastructure, financial systems, and digital asset platforms. These essays reflect the architectural reasoning applied in engagement.