Securities and Blockchain Look Like Opposites. They're Not.

When you buy a share of Apple, you are not taking physical possession of anything. There is no certificate, no vault, no transfer of something tangible. What happens is simpler: a ledger is updated. Your account is credited. The seller's is debited. The security didn't move. The record changed.

When you transfer a token on a blockchain, the mechanics are remarkably similar. Two accounts on a ledger are updated — one on each side of the transaction. The token didn't travel anywhere. The record changed. At the transaction level, securities and crypto are much more similar than most people realize.

In a pickup poker game, the dealer's job is to confirm the pot — who's in, who folded — and then declare: pot's good. In a crypto transaction, that's the job of the miners. They validate that the transaction is legitimate and authorize the ledger to update — recording the change in ownership of the token. The blockchain is the record, and the miners are the dealers. It typically takes several confirmations before a transaction is considered final, but there is one unified system, one rail, one call.

In traditional securities settlement, you have two dealers. One confirms the payment leg — the money. Another confirms the asset transfer leg — the securities. Only then does DTCC update the ledger. Two separate pot's good calls, on two separate rails. And this is worth noting: that makes DVP the more complete system. A standard blockchain transaction is DF — Delivery of an asset on a single rail (setting aside DeFi protocols where the swap is atomic). Traditional securities settlement ties both sides together. Delivery versus Payment. The money and the securities, accounted for together.

It's called DVP. But shouldn't we really call it DVP+1?

Each confirmation takes time — the broker, the clearing firm, the DTCC ledger update. By the time both calls are made and reconciled, a day has passed. The architecture is sound. The clock is the problem.

That extra day is not merely an administrative inconvenience. It is also a float — capital committed but not yet settled, sitting in a gap between trade and finality. Settlement risk lives in that gap. After the move to T+1 in May 2024, the industry's CNS fail rate remained at approximately 2.12% — consistent with where it was under T+2. The window got shorter. The failures didn't disappear. Overnight funding has a rate. The infrastructure built to manage what can go wrong in the interval between agreement and finality has a cost. That cost is paid every day, by every participant, on every trade. It is a tax.

What if it didn't have to be?

What if delivery and payment happened on the same system — the same rail — at the moment of the transaction? One update. Both sides confirmed in the same hash, timestamped together. We could call that DXP: Delivery and Payment, simultaneously. What others call T-instant settlement, or atomic settlement — the trade either completes entirely or it doesn't happen at all. No float. No overnight exposure. No two dealers. One call: pot's good, on the asset and the payment, at once.

This is what we could be building now. The technology exists. The regulatory moment is as open as it has been in thirty years. What's missing is not the infrastructure. It's the will to build it.

DXP doesn't just eliminate the plus one. It changes what's possible downstream. When there is no delivery without payment — ever, by construction — a significant layer of compliance and reconciliation infrastructure built around the possibility of settlement failure has no failure to prepare for. The system is self-authenticating in a way that two-rail settlement can never be.

T+1 was progress. T+0 would be more progress. But until the two rails are consolidated, neither eliminates the structural gap. They only shrink it. DXP closes it.