2008 Proved Wall Street Had No Map of Its Own Risks. Sui Was Built to Draw One.

On the weekend of September 13, 2008, the heads of Wall Street’s biggest banks filed into the New York Fed to try to save Lehman Brothers. By Monday morning, Lehman had filed the largest bankruptcy in U.S. history.
The problem that weekend wasn’t intelligence or effort. Nobody could answer the questions that mattered fast enough.
Lehman had **900,000+ derivatives contracts with 6,000+ counterparties**, about $35 trillion in notional value. A month before the collapse, Fed officials were *still* trying to get information on those contracts. The failure splintered into 75+ separate bankruptcy proceedings, and about 1,000 contracts were still unsettled four years later. Days after Lehman, AIG nearly went down holding $440B+ in credit-default swaps its own regulator later said he barely understood.
**Wall Street had mountains of records. What it didn’t have was a map.**
I just published a long piece on this. Here’s the short version.
**1. Finance records things. It doesn’t record how things connect.**
Every bank, custodian, servicer and clearinghouse keeps its own ledger. What’s never existed is a shared, authoritative record of the *relationships* between them.
Follow a 2008 mortgage: pooled into a mortgage-backed security, sliced into tranches, bundled into a CDO, sliced again, insured by credit-default swaps, pledged as collateral. Every step creates a new entity with its own books, each seeing only its own layer.
That’s not a speed problem. It’s an architecture problem. And it’s about to get worse:
>The financial system of 2008 was too interconnected for anyone to understand. The financial system of tomorrow will be too interconnected for humans to operate.
Fixing the first requires making financial relationships machine-readable. Fixing the second requires making them programmable.
**2. Rebuild the chain as objects.**
On Sui, every asset can be an object with a permanent identity, an owner and a version history, and objects can own other objects. So the 2008 chain stops being disconnected ledgers and becomes a structure. The mortgage keeps its identity when it’s pooled. The pool, the tranches and the CDO are distinct objects, each with a traceable link to what’s beneath it.
Once assets live onchain as objects, much of this map draws itself. The protocol records every ownership link and every transaction in a form software can read, and applications record the rest, like a swap pointing to the CDO it insures. Call it an **economic dependency graph**.
And this is *not* the same as “tokenizing securities.” Tokenize a 2008-style CDO as one opaque token and nothing changes. **Putting opaque securities on a blockchain just makes opaque securities easier to transfer.**
**3. Visibility, intelligence, action.**
* **Visibility:** a mortgage defaults, and software traces the damage outward through the security, the tranche, the CDO, the funds holding it and the insurer behind it. What took weeks of phone calls in 2008 becomes a query. * **Intelligence:** regulators stop asking banks to self-report exposures weeks later and ask the system directly: *“If commercial real estate drops 25%, who takes losses and where does it spread?”* * **Action:** this is the big one.
**4. PTBs make financial relationships executable, and anyone can compose them.**
Atomic transactions aren’t new. Bank-focused networks like Canton settle multi-party deals all-or-nothing and can chain complex workflows. **The difference is who gets to compose.** On those networks, composing happens among members who were sponsored in and have authorized each other. On Sui, *anyone* (a company treasury, a startup, an AI agent) can assemble a brand-new financial action on the spot from up to 1,024 steps across any public application, each step feeding the next, without joining anything or asking permission.
Institutional networks give finance a private club. Sui gives it a public set of building blocks.
Three examples from the piece:
* **Capital that goes where it’s needed:** collateral verified, pledged and substituted automatically, even at 2 a.m. on a Sunday. Less capital sitting idle just because the system is slow. * **Agreements that coordinate themselves:** a hospital financed by ten lenders across three countries. When a milestone is certified, one transaction checks insurance and permits, releases every lender’s share and updates every position. If any condition fails, no money moves. * **An economy that can improvise:** a manufacturer’s AI agent needs $2M of materials by Friday. Because every piece lives onchain, it sells tokenized Treasuries, borrows against receivables, converts currency, pays the supplier and insures the shipment in one transaction no one ever designed, simulated first and all-or-nothing.
That last one is the core of it. With just 100 financial apps, there are nearly **162,000** ways to combine three of them. Nobody will pre-build all of those. **An autonomous economy can’t wait for developers.** An AI agent can’t wait to be sponsored into a network or approved by every counterparty before it acts.
That’s why Sui’s architecture matters beyond any single DeFi app. The value isn’t just a better lending protocol or exchange. It’s that every app on Sui becomes a building block for financial arrangements nobody has invented yet.
**5. Why Sui over Canton?**
Canton is serious, and the piece treats it that way. But the starting points differ:
>**Canton is private by default and shares by exception. Sui is verifiable by default and private by exception.**
On Canton, a system-wide picture has to be assembled from private views, institution by institution. On Sui, the shared, verifiable state is the starting point, and confidentiality is added where it’s needed: Seal for data, confidential transfers for amounts, Nautilus for private computation, and Spheres for relationships that are sensitive in themselves.
Canton is bringing programmability to the institutional system as it exists today. Sui is trying to make institutional finance part of an open programmable economy. The question isn’t which network can modernize Wall Street. **It’s which architecture can connect Wall Street to everything else.**
**The honest part:** faster finance can spread contagion faster. A partial map can mislead. 2008’s worst exposures lived offchain. Spheres and confidential transfers aren’t production-ready yet. The piece covers all of it. But speed with sight is different from speed without it, and private-by-default networks risk making contagion faster while the full picture stays behind institutional walls.
**The bottom line:** the object model gives finance a vocabulary. The relationships give it a map. Programmable transactions give it the ability to act.
**The old financial system recorded what happened. The next one could understand what is happening, and act on it.**
Full article (Lehman details, the Canton comparison, the hard problems and sources): [https://medium.com/@jakewinters32/the-financial-system-has-never-had-a-map-of-itself-edf8b379b2f8](https://medium.com/@jakewinters32/the-financial-system-has-never-had-a-map-of-itself-edf8b379b2f8)
So here’s my question: if the next financial system needs to be machine-readable, globally composable and usable by autonomous agents, is an institution-first architecture really the right foundation? Or does an open, object-based system like Sui have the stronger long-term design? Especially interested in hearing from people working in TradFi, Canton or Daml.
*Not financial advice.*
On the weekend of September 13, 2008, the heads of Wall Street’s biggest banks filed into the New York Fed to try to save Lehman Brothers. By Monday morning, Lehman had filed the largest bankruptcy in U.S. history.
The problem that weekend wasn’t intelligence or effort. Nobody could answer the questions that mattered fast enough.
Lehman had **900,000+ derivatives contracts with 6,000+ counterparties**, about $35 trillion in notional value. A month before the collapse, Fed officials were *still* trying to get information on those contracts. The failure splintered into 75+ separate bankruptcy proceedings, and about 1,000 contracts were still unsettled four years later. Days after Lehman, AIG nearly went down holding $440B+ in credit-default swaps its own regulator later said he barely understood.
**Wall Street had mountains of records. What it didn’t have was a map.**
I just [published a long piece on this](https://medium.com/@jakewinters32/the-financial-system-has-never-had-a-map-of-itself-edf8b379b2f8?postPublishedType=repub). Here’s the short version.
**1. Finance records things. It doesn’t record how things connect.**
Every bank, custodian, servicer and clearinghouse keeps its own ledger. What’s never existed is a shared, authoritative record of the *relationships* between them.
Follow a 2008 mortgage: pooled into a mortgage-backed security, sliced into tranches, bundled into a CDO, sliced again, insured by credit-default swaps, pledged as collateral. Every step creates a new entity with its own books, each seeing only its own layer.
That’s not a speed problem. It’s an architecture problem. And it’s about to get worse:
>The financial system of 2008 was too interconnected for anyone to understand. The financial system of tomorrow will be too interconnected for humans to operate.
Fixing the first requires making financial relationships machine-readable. Fixing the second requires making them programmable.
**2. Rebuild the chain as objects.**
On Sui, every asset can be an object with a permanent identity, an owner and a version history, and objects can own other objects. So the 2008 chain stops being disconnected ledgers and becomes a structure. The mortgage keeps its identity when it’s pooled. The pool, the tranches and the CDO are distinct objects, each with a traceable link to what’s beneath it.
Once assets live onchain as objects, much of this map draws itself: the protocol records every ownership link and every transaction in a form software can read. Call it an **economic dependency graph**.