

On July 2, the International Monetary Fund published a blog under the name of Tobias Adrian, the institution's Financial Counsellor and the man who runs its Monetary and Capital Markets Department. The title was measured in the way IMF titles always are: Tokenization Can Change the World's Financial Architecture. The argument underneath it was not measured at all.
Adrian's point, stripped of the diplomatic phrasing, is that tokenization does something deeper than speed up settlement. When assets and liabilities move onto shared ledgers, risk stops living on the balance sheets of banks and funds and starts living inside the platforms and the code that govern the transactions. His words, not mine: oversight must extend beyond institutions to the code itself, and critical smart contracts could become too important to fail, the way systemically important banks are today.
I have been making a version of that argument since 2016, back when saying it in a finance meeting earned you a polite silence. The difference now is who is saying it. When the most conservative financial institution on the planet writes that the locus of risk is migrating into software, the debate about whether this is real is over. What remains is the question the IMF raised and did not fully answer: which settlement asset, and whose code.
Most of the coverage filed this piece under crypto validation and moved on. That misses the interesting part. Adrian is not cheerleading. He is describing, with some alarm, a structural shift that removes the buffers the current system relies on.
His logic runs like this. Today's plumbing is slow on purpose. Trades are matched, settlement is delayed, reconciliation follows. Those frictions cost time and money, but they also buy something valuable: room to intervene when something breaks. Tokenization collapses that room. When ownership and transfer are embedded in the asset itself, a trade can execute, settle, and move payment in the same instant. The frictions disappear, and so do the buffers. Liquidity calls arrive in real time, collateral triggers fire automatically, and a failure can propagate faster than any supervisor can react.
That is not a technology upgrade. It is a redistribution of where trust has to sit. In the old system, you trusted the institution behind the transaction. In the tokenized system, you increasingly trust the code that executes it. The IMF has now said this in writing.
This is the shift Deal Box was built around. From the start we treated tokenization as a change in where risk concentrates rather than a faster database, which meant the code could not be an afterthought bolted onto the asset. It had to be the thing you engineered first.
The sharpest section of Adrian's piece is about money itself. Every financial system rests on a core settlement asset, and traditionally that role belonged to central bank reserves, the risk free claim that sits underneath everything else. Tokenization reopens the question, because several forms of digital money can now circulate on the same ledgers.
The IMF lays out three candidates. Tokenized bank deposits, which inherit the existing regulatory framework but strip banks of the reaction time that delayed settlement used to give them. Stablecoins, which offer reach and programmability but rest on a promise of par convertibility that has cracked under stress before. And tokenized central bank reserves, which remove credit risk from the settlement asset but force central banks to operate programmable infrastructure far beyond anything they run today.
Each of those has a common feature worth naming plainly: every one of them is a liability of somebody. A bank, an issuer, or a state. Each carries the credit and governance risk of the institution standing behind it. The IMF is honest about this. It notes that even fully backed stablecoins have failed under pressure, and that tokenized reserves demand central banks take on an operational role most of them do not want.
There is a fourth option the piece does not sit with, and it is the one I have spent a decade building toward. A settlement asset that is nobody's liability, that carries no issuer credit risk, that no single central bank governs, and that has never been successfully attacked across seventeen years of operation. That asset is Bitcoin. If the entire concern is that risk now concentrates in the settlement layer, then the settlement layer you want underneath a global tokenized system is the one with the fewest points of failure and the least discretionary control. Neutrality is not a slogan here. It is a risk property.
The IMF's most consequential line is the one about the code. If financial logic moves into smart contracts, then oversight has to reach the contracts, and the critical ones start to look systemically important. Legal foundations, Adrian writes, matter just as much. Market participants need to know whether a tokenized record is definitive ownership, whether settlement is legally final, and which jurisdiction's law applies. Without that clarity, he says, tokenization stays fragmented and peripheral.
I agree with every word, and I would go further. You cannot supervise code you were not allowed to see the design of, and you cannot make a tokenized asset legible to a regulator if identity and compliance were never part of the asset in the first place. The lesson the industry keeps relearning is that compliance bolted on after issuance does not hold. It has to be compliance first, engineered into the instrument before the first token exists.
That conviction is why our tokenization work is Bitcoin native rather than a wrapper stretched across a dozen chains. Through OroBit, we built a contract language designed for institutional tokenization on Bitcoin, one that anchors the critical record to Bitcoin's base layer while carrying the transfer restrictions and compliance logic an institution actually needs. But a contract language is not enough on its own. An allocator will not move into a tokenized asset if it cannot prove who stands on the other side of a transfer. So we built the identity and naming layer underneath the asset, through True I/O and UCID, with BTCNames handling the naming. That is what makes the code auditable rather than opaque, which is the property the IMF is now telling policymakers they will need.
I started Deal Box in 2016 and tokenized a real world asset before there was a tidy category to file it under. People sometimes read that as foresight. It was not. It came from watching, over a long enough stretch, how markets actually behave. Capital migrates toward whatever rails make it easier to access, cheaper to move, and faster to settle. It did this when the DTC pulled paper certificates into a vault in the 1970s and let ownership change hands by book entry. Tokenization is that same instinct applied one more time, with the ownership record moving off a closed ledger and onto a programmable one.
For most of the last decade the idea ran well ahead of the machinery. The instruments existed, but the settlement layer, the compliance tooling, and the institutional identity did not, so serious capital waited. The thesis never needed revising. The rails simply had to catch up, and the institutions had to arrive at the same conclusion on their own terms. This week the IMF arrived. When the fund writes that risk is moving into the code and that the code now needs the kind of oversight we reserve for the most important banks, it is describing the exact problem we chose to engineer for at the start.
Adrian closes his piece by saying the outcome will be decided by policy choices still to be made: the balance of public and private money, the degree of interoperability, the legal frameworks, and the governance of the code. He is right that those choices are open. He is also, I think, describing the seams where the next decade of infrastructure gets built.
The best outcome he can imagine is a system that supplies the public goods a financial system needs, a risk free settlement asset chief among them, while leaving room for the private innovation that makes it useful. I would put it more directly. The risk free settlement asset already exists, it is not the liability of any government, and the work now is building compliant, identity backed, institution ready rails on top of it. We have been doing that work since before the IMF had the vocabulary for the problem.
Infrastructure cycles reward the people stubborn enough to hold the fundamentals while the plumbing takes its time. It is taking its time no longer, and the establishment is writing our thesis back to us in its own careful language. Whether this happens stopped being the live question a while ago. What matters now is which layer it settles on, and whether the code underneath can be trusted to carry it. We made our call on both in 2016. Nothing the IMF published this month has given me a reason to revise it.


On July 2, the International Monetary Fund published a blog under the name of Tobias Adrian, the institution's Financial Counsellor and the man who runs its Monetary and Capital Markets Department. The title was measured in the way IMF titles always are: Tokenization Can Change the World's Financial Architecture. The argument underneath it was not measured at all.
Adrian's point, stripped of the diplomatic phrasing, is that tokenization does something deeper than speed up settlement. When assets and liabilities move onto shared ledgers, risk stops living on the balance sheets of banks and funds and starts living inside the platforms and the code that govern the transactions. His words, not mine: oversight must extend beyond institutions to the code itself, and critical smart contracts could become too important to fail, the way systemically important banks are today.
I have been making a version of that argument since 2016, back when saying it in a finance meeting earned you a polite silence. The difference now is who is saying it. When the most conservative financial institution on the planet writes that the locus of risk is migrating into software, the debate about whether this is real is over. What remains is the question the IMF raised and did not fully answer: which settlement asset, and whose code.
Most of the coverage filed this piece under crypto validation and moved on. That misses the interesting part. Adrian is not cheerleading. He is describing, with some alarm, a structural shift that removes the buffers the current system relies on.
His logic runs like this. Today's plumbing is slow on purpose. Trades are matched, settlement is delayed, reconciliation follows. Those frictions cost time and money, but they also buy something valuable: room to intervene when something breaks. Tokenization collapses that room. When ownership and transfer are embedded in the asset itself, a trade can execute, settle, and move payment in the same instant. The frictions disappear, and so do the buffers. Liquidity calls arrive in real time, collateral triggers fire automatically, and a failure can propagate faster than any supervisor can react.
That is not a technology upgrade. It is a redistribution of where trust has to sit. In the old system, you trusted the institution behind the transaction. In the tokenized system, you increasingly trust the code that executes it. The IMF has now said this in writing.
This is the shift Deal Box was built around. From the start we treated tokenization as a change in where risk concentrates rather than a faster database, which meant the code could not be an afterthought bolted onto the asset. It had to be the thing you engineered first.
The sharpest section of Adrian's piece is about money itself. Every financial system rests on a core settlement asset, and traditionally that role belonged to central bank reserves, the risk free claim that sits underneath everything else. Tokenization reopens the question, because several forms of digital money can now circulate on the same ledgers.
The IMF lays out three candidates. Tokenized bank deposits, which inherit the existing regulatory framework but strip banks of the reaction time that delayed settlement used to give them. Stablecoins, which offer reach and programmability but rest on a promise of par convertibility that has cracked under stress before. And tokenized central bank reserves, which remove credit risk from the settlement asset but force central banks to operate programmable infrastructure far beyond anything they run today.
Each of those has a common feature worth naming plainly: every one of them is a liability of somebody. A bank, an issuer, or a state. Each carries the credit and governance risk of the institution standing behind it. The IMF is honest about this. It notes that even fully backed stablecoins have failed under pressure, and that tokenized reserves demand central banks take on an operational role most of them do not want.
There is a fourth option the piece does not sit with, and it is the one I have spent a decade building toward. A settlement asset that is nobody's liability, that carries no issuer credit risk, that no single central bank governs, and that has never been successfully attacked across seventeen years of operation. That asset is Bitcoin. If the entire concern is that risk now concentrates in the settlement layer, then the settlement layer you want underneath a global tokenized system is the one with the fewest points of failure and the least discretionary control. Neutrality is not a slogan here. It is a risk property.
The IMF's most consequential line is the one about the code. If financial logic moves into smart contracts, then oversight has to reach the contracts, and the critical ones start to look systemically important. Legal foundations, Adrian writes, matter just as much. Market participants need to know whether a tokenized record is definitive ownership, whether settlement is legally final, and which jurisdiction's law applies. Without that clarity, he says, tokenization stays fragmented and peripheral.
I agree with every word, and I would go further. You cannot supervise code you were not allowed to see the design of, and you cannot make a tokenized asset legible to a regulator if identity and compliance were never part of the asset in the first place. The lesson the industry keeps relearning is that compliance bolted on after issuance does not hold. It has to be compliance first, engineered into the instrument before the first token exists.
That conviction is why our tokenization work is Bitcoin native rather than a wrapper stretched across a dozen chains. Through OroBit, we built a contract language designed for institutional tokenization on Bitcoin, one that anchors the critical record to Bitcoin's base layer while carrying the transfer restrictions and compliance logic an institution actually needs. But a contract language is not enough on its own. An allocator will not move into a tokenized asset if it cannot prove who stands on the other side of a transfer. So we built the identity and naming layer underneath the asset, through True I/O and UCID, with BTCNames handling the naming. That is what makes the code auditable rather than opaque, which is the property the IMF is now telling policymakers they will need.
I started Deal Box in 2016 and tokenized a real world asset before there was a tidy category to file it under. People sometimes read that as foresight. It was not. It came from watching, over a long enough stretch, how markets actually behave. Capital migrates toward whatever rails make it easier to access, cheaper to move, and faster to settle. It did this when the DTC pulled paper certificates into a vault in the 1970s and let ownership change hands by book entry. Tokenization is that same instinct applied one more time, with the ownership record moving off a closed ledger and onto a programmable one.
For most of the last decade the idea ran well ahead of the machinery. The instruments existed, but the settlement layer, the compliance tooling, and the institutional identity did not, so serious capital waited. The thesis never needed revising. The rails simply had to catch up, and the institutions had to arrive at the same conclusion on their own terms. This week the IMF arrived. When the fund writes that risk is moving into the code and that the code now needs the kind of oversight we reserve for the most important banks, it is describing the exact problem we chose to engineer for at the start.
Adrian closes his piece by saying the outcome will be decided by policy choices still to be made: the balance of public and private money, the degree of interoperability, the legal frameworks, and the governance of the code. He is right that those choices are open. He is also, I think, describing the seams where the next decade of infrastructure gets built.
The best outcome he can imagine is a system that supplies the public goods a financial system needs, a risk free settlement asset chief among them, while leaving room for the private innovation that makes it useful. I would put it more directly. The risk free settlement asset already exists, it is not the liability of any government, and the work now is building compliant, identity backed, institution ready rails on top of it. We have been doing that work since before the IMF had the vocabulary for the problem.
Infrastructure cycles reward the people stubborn enough to hold the fundamentals while the plumbing takes its time. It is taking its time no longer, and the establishment is writing our thesis back to us in its own careful language. Whether this happens stopped being the live question a while ago. What matters now is which layer it settles on, and whether the code underneath can be trusted to carry it. We made our call on both in 2016. Nothing the IMF published this month has given me a reason to revise it.