What It Takes to Bring Institutional Finance On-Chain
summary
Secured Finance actually connects a UBS tokenized money market fund on Ethereum (mainnet, transfer‑restricted) and reports two concrete JGB designs: wrapper vs native book-entry. Execution stays on existing venues, custody stays with custodians, and allocation DVP happens on the shared ledger; the prototype exposes hidden intraday liquidity gaps, credit‑line needs and who pays settlement costs. Builders must define the legal asset, reuse the GMA repo contract where possible, map participant responsibilities, and design permissioned visibility before coding.
AI-written summary · about
chapters (18)
- 0:00Introduction and JGB Repo Working Group
- 1:07Mapping TradFi Functions to DeFi
- 2:31The Full Financial Protocol Lifecycle
- 3:08UBS Tokenized Fund on Ethereum
- 4:15What Is an Onchain Japanese Bond?
- 4:36Wrapper Versus Native Book-Entry Models
- 6:39Responsibilities Around a Repo Trade
- 7:30Operations Approval Before Settlement
- 8:20Where Blockchain Fits Institutional Markets
- 9:31Connecting Existing Execution Venues
- 10:10Credit, Liquidity, and Balance Sheets
- 11:16Finding Hidden Settlement Costs
- 12:19Delivery Versus Payment Economics
- 13:00Privacy as Institutional Information Control
- 14:17Permissioned Visibility for Ethereum
- 15:07Reusing Legal Agreements and Data Models
- 17:25Five Questions Before Building
- 19:10Asset, Constraints, Boundaries, and Control
