Enterprise
What should a capital markets desk ask before adopting blockchain settlement infrastructure?
The interesting engineering in this sector sits behind the price, not in front of it.
The answer
Ask what the desk must be able to prove about a position, to whom, and how quickly — that proof obligation, not the throughput figure on the vendor’s slide, is what should decide the architecture. Most desks discover their actual proof obligation during a first audit rather than a design review, and by then the system is already built around the wrong answer.
The instruction feed is the product, not the exchange screen
Order handling and matching are the visible part of a venue or desk build. The settlement instruction feed, the reconciliation against a transfer agent, and the versioned transfer-restriction rules underneath the register are the part that determines whether the system survives its first regulatory review — and the part most vendor demos do not show.
Checklist
What must be proven, to whom, and in how long?
A position statement produced in an afternoon and one produced in three weeks are different systems. Get the real requirement before the design.
Where does the register live if the vendor’s platform is decommissioned?
A register of holders is the product in this sector. A vendor exit plan that does not name the export format and the escrow arrangement is not a plan.
How is a transfer-agent disagreement resolved, and by which system?
State it before launch. Discovering it during a dispute is an audit finding, not a bug.
Talk to the practice
Tell us what you are trying to build and what has to be true for it to work.
Contact