Spent the last few days adding Canton Network support to Spraay Protocol's batch payment infrastructure. It's chain 16 for Spraay, and the most interesting one we've integrated to date — for reasons that have less to do with us and more to do with where Canton is going.
The Canton context
If you've been heads-down in crypto Twitter, Canton is easy to miss. While most of the EVM ecosystem has been arguing about L2 fragmentation, Canton has quietly become the rail of choice for serious institutional tokenization. The numbers are real:
- DTCC — which clears the vast majority of U.S. securities and custodies $114T in assets — partnered with Digital Asset in December 2025 to tokenize DTC-custodied U.S. Treasuries on Canton, with broader rollout through 2H 2026
- JPMorgan's Kinexys is deploying JPM Coin natively on Canton in phases throughout 2026
- Broadridge's distributed ledger repo platform, running on Canton rails, already processes $4 trillion monthly in overnight Treasury financing
- Goldman Sachs, BNY Mellon, BNP Paribas, HSBC, Euroclear, S&P Global, Nasdaq are all participants
- Network-wide: ~$6T in tokenized real-world assets across 600+ institutions, ~500K daily transactions
This is a network built for the financial plumbing layer most crypto-native builders don't think about every day. And it's already running.
Where batch payments fit
Most of Spraay's chains are payment-rail-first: send USDC to N recipients, take a 0.3% protocol fee, optimize gas. That story translates cleanly to retail and to agent-driven commerce (we've leaned hard into x402-style agent payments).
Canton is different. Holdings are UTXO-style. Transfers go through Splice's Token Standard via a TransferFactory_Transfer choice on the global synchronizer. Instruments are admin-scoped — the DSO party admins Canton Coin, but any institution issuing on Canton (a tokenized Treasury, a deposit token, a fund share) can be its own instrument admin.
So a batch payment primitive that works against Token Standard isn't "competing with DTCC." It's a small piece of utility infra that any app building on Canton can compose with — programmatic disbursements, fund flows between sub-accounts, payroll, agent-driven micropayments — whether the instrument is Canton Coin today or a tokenized money-market fund share tomorrow.
What's live
github.com/plagtech/spraay-canton runs against the cn-quickstart LocalNet. It exposes a REST API for batch payments, queries holdings via the Token Standard Holding interface, fetches the TransferFactory from the Scan-hosted registry, executes one TransferFactory_Transfer per recipient, and collects the protocol fee through a second transfer to the operator party. Same shape as every other Spraay chain — just spoken in Daml.
The repo is open, the integration is small, and the door's open if anyone building on Canton wants payment primitives or just wants to compare notes.
Spraay now spans 16 chains. The interesting part isn't the count — it's that the span now goes from retail-facing chains all the way to the network where institutional tokenization is being built. That's a different kind of map than it was last year.
Top comments (0)