Where infrastructure earns its place

Most conversations about new financial infrastructure are conversations about speed. How fast it settles, how fast it scales, how fast it can be shipped. Speed is easy to describe and easy to compare, which is probably why it gets the attention.

The institutions that actually move money ask a duller question first. Will this behave the same way tomorrow as it did today. Predictability is harder to market than speed, because there is nothing to show. It only becomes visible when it is missing.

Why we build on Canton

This is part of why we build on Canton. Privacy there is not a feature layered on afterwards to satisfy a requirement. It is part of how the network is arranged, so that parties can transact without publishing their business to everyone else who happens to be connected. For anyone who has worked inside a regulated institution, that distinction is not academic.

A network like that only works if somebody actually runs it. Validators, nodes, monitoring, the unglamorous business of being available when nothing interesting is happening. This is the part of the work that nobody writes about, and it is the part that decides whether the rest of it is real.

The cost of moving too fast

Moving too fast has a cost that arrives late. A shortcut taken to make a launch date tends to come back as an incident, and an incident in payments is not a technical event. It is a person who no longer knows whether their money is where they left it.

So we try to keep our own work quiet in the same way. Fewer announcements, more time spent on the parts that have to hold. Our products sit on top of this network, and they inherit whatever it does well and whatever it does badly, which makes the health of the network our problem rather than someone else’s.

Infrastructure earns trust slowly. Canton is being built on foundations we think are the right ones, and we intend to keep building on top of it.