Goose

DTCC starts production trades on Canton Network in july. ondo and layerzero are listed as native supported assets on the network. DTCC settles $2.5 quadrillion annually in securities. when those tokenized treasuries need to bridge into public defi markets, ondo is already embedded in the plumbing. 66% of tokenized stocks market, $800m TVL, $15b cumulative volume, and now sitting inside the settlement layer that JPMorgan, Goldman, and BlackRock are building on. the $300T addressable market doesn't come to ethereum mainnet. it comes through permissioned rails with compliance controls baked in. ondo is the two-way valve between those rails and public yield markets. july is 60 days out.

DTCC tokenized securities go live for partial trading july 2026 with full production october. USDC is the settlement currency. if 1% of daily US equity volume routes through tokenized rails that's $29B daily in USDC settlement demand. current USDC transfer volume across all use cases is ~$280B monthly. one use case would 3x total USDC velocity. circle, chainlink, securitize, backpack all confirmed in the working group alongside blackrock, JPM, goldman, citadel. securitize got FINRA approval for atomic settlement may 4. chainlink provides proof of reserve and data feeds across the entire asset lifecycle. the value accrues to the settlement layer and oracle layer, not to platform tokens with no fee capture. already posted about ondo's 108x P/S disconnect. apply that lens to every RWA token. the chokepoints are USDC and LINK. every tokenized equity trade must settle in one and price through the other.

There are two aspects to this LayerZero incident: One is the very design of the protocol itself, and the other is what appears to be LayerZero's own DVN being exploited. LayerZero's security model uses a X of K of N model, where each application gets to choose their own security. N is the total number of DVNs that exist for an application to choose from. K is how many you actually choose to use from the total pool. X is how many of the K you chose that you need sign off from in order to execute a transaction. Furthermore, a "DVN" can be anything from a single node ran by a single entity (like Layerzero Lab's own DVN in this instance) or you can plug an entire network of nodes in as a single DVN ( such as Axelar's entire network or Chainlink's entire CCIP of three seperate networks of independent nodes can be a single DVN in a config). However, what this means is that this means there is no security floor. A configuration can be a 1/1 DVN and the DVN you chose can be a single node ran by a single entity. I personally think this is a flawed design. Modular security is a worthwhile design space, however, the range of security should have a native security floor that is quite strong, and then allow *additional* layering of security on top of that for more high-value use-cases. Therefore, your security model range should be strong -> very strong -> obscenely strong; not zero to obscenely strong. The blockchain equivalent of LayerZero's design would be if Ethereum allowed an application building on its own to hand-select a single Ethereum validator to verify and execute all of its its own onchain code. Would anyone consider that safe? That's literally what LayerZero's security model as a protocol. Zero security floor. Anything goes. As a real-world analogy, imagine if a roller coaster manufacturer allowed amusement parks to individually decide what the minimum safety specs were for each roller coaster, rather than having the manufacturer themselves impose a minimum safety level on the roller coaster. Would you ride on roller coasters where amusement parks get to decide what is the minimum safety rather than the actual manufacturers of the roller coaster? The second part to this story is the fact that in this particular 1/1 DVN configuration, the DVN ran and operated by the LayerZero Labs team was the sole node responsible for the entirety of the security. So, to sum it up, there is both a philosophical question around the protocol's design itself, along with operational security around how LayerZero Labs secures its own DVN for use. I have attached some more tweets from various people for additional interesting points and discussion.