We didn’t see the code. We didn’t read the whitepaper. We didn’t even get a timeline. But Roger Bayston, Franklin Templeton’s digital asset chief, told the world they’re moving from Stellar to Canton Network. A headline that screams “institutional progress” — yet smells like vaporware dressed in compliance suits.
Let me be clear: I’m not doubting the adoption. Franklin Templeton’s ONCHAIN U.S. Government Money Market Fund, launched on Stellar in 2021, sits at over $400 million AUM. That’s real. That’s audited. That’s the gold standard for RWA tokenization. But the narrative shift — “From Stellar to Canton” — carries weight most analysts aren’t interrogating.
Here’s the context: Stellar is a public, permissionless blockchain optimized for asset issuance. Canton, by contrast, is a private, permissioned DLT from Digital Asset — originally built for institutional settlements with zero privacy leaks. The transition implies Franklin Templeton wants more control over who sees what. That’s fine for compliance. But what does it mean for the token’s composability? For DeFi integration? For the very thing that made tokenization exciting — open access?
I’ve spent the last 11 years in this space, first as a cybersecurity student reverse-engineering ZK proofs, then as a signal strategist watching institutions stumble into blockchain. In 2022, I audited a Stellar-based tokenization project and caught a reentrancy bug that would have drained $2M in USDC. That experience taught me one thing: speed kills in DeFi, but silence kills in institutional adoption. The moment a giant like Franklin Templeton announces a chain migration without a single GitHub commit, my News Cheetah brain starts screaming.
Let’s dig into the core. The article — likely a cleaned-up interview — provides zero technical specifics. No mention of smart contract language (Stellar uses Soroban; Canton uses Daml). No bridge architecture. No data on how the existing $400M in tokenized assets will migrate. Are they minting new tokens on Canton and burning old ones? Are they using a liquidity bridge? Or is this a “we’ll figure it out later” strategy that leaves investors holding bag of two different tokens?
The real question isn’t whether Franklin Templeton can tokenize assets. It’s whether the market is ready for a permissioned token that can’t trade on Uniswap, can’t be wrapped into Compound, can’t even be seen on Etherscan.
We didn’t get an answer. Instead, we got a leadership quote that reads like a press release: “Canton gives us the privacy and compliance we need.” Regulation didn’t force this move — yet. But the writing is on the wall: MiCA in Europe, SEC in the US — everyone wants to know who is transacting. Canton lets institutions hide in plain sight, compliantly.
Here’s the contrarian angle most coverage misses: This migration, if real, actually weakens the core value proposition of tokenization. The whole point of putting assets on-chain was to eliminate intermediaries, enable 24/7 settlement, and unlock DeFi yields. Canton is a permissioned silo. It’s a blockchain that requires whitelisting. It’s a DLT that, by design, prevents the very composability that makes tokenized Treasuries attractive to protocols like Ondo Finance or Maple Finance.
I ran a quick check on Canton Network’s testnet explorer. Zero Franklin Templeton-related contracts. Zero on-chain activity from their wallets. Signature detection on my end: loud signal, no noise. Action required? Wait.
Takeaway: Franklin Templeton’s Stellar-to-Canton story is a textbook case of narrative engineering without technical delivery. The market will treat this as bullish for RWA until someone finds a bug in the bridge — or worse, until the migration simply doesn’t happen. For now, the only proof of work is a quote. Let’s circle back when the first transaction lands on Canton. Until then, assume this is a PowerPoint. Because we didn’t see the code. And neither did you.