The Lens

cBNB is BNB on Canton, issued by Nuxaris and backed one for one by BNB locked on BNB Chain. This episode asks who actually holds that BNB, and what happens when a holder hands the token back.

Who holds it? The cBNB docs say each token in circulation is matched by one BNB in a vault contract on BNB Chain. Nethermind's security review of that vault and its router says both are operated by three Safe multisigs, and the Admin Safe holds the admin role on both. A Safe multisig is a shared account where a set number of owners must sign before anything moves. The review does not say who the owners are or what the thresholds are. Open.

The way in. New cBNB is issued only after the BNB deposit is final on BNB Chain. Holding and sending need no allowlist. In the audit, Nuxaris says only addresses it controls deposit into the vault.

The way out. cBNB goes to a redemption party and the registrar burns it. Then two owners of the Relayer Safe sign the release of the BNB from the vault. Burn first, then pay.

The harder read. The audit's known-limitation tests include one named admin safe can drain the vault, and one named relayer safe releases without on-chain proof of burn. They are not findings. They describe a vault that trusts its operators. The vault address is shared with integration partners on request, so the backing cannot yet be checked in public.

Scale and status. The Digital Asset registry reported a total supply of 1.5 cBNB on 13 October 2026. Nuxaris has locked 25 million CC through Cashen and applied for Featured App status for cBNB. Applied, not approved. Canal lists a BNB-backed cBNB in its own plans.

Super Validators, the operators that jointly run and govern Canton's shared network, must lock part of the rewards they earn to keep their weight (CIP-0105). Featured Apps, the apps the network rewards for their activity, must lock 5 million CC per party, or 25 million for an asset issuer (CIP-0116). Is that lock held by the ledger, or by a promise?

Today the answer is split. CIP-0105 calls the lock "a visible, on-chain commitment," but its own Phase 1 has Super Validators disclose a segregated party holding the locked coin to the Foundation. Phase 2 "Activates upon deployment of CC locking contracts to MainNet." The Dev Fund proposal to build it says Phase 1 runs on "spreadsheets and off-chain disclosures."

The penalty is on-chain. Revoking a featured app right and changing a Super Validator's reward weight are voted actions that execute on the ledger. On the public Scan feed, 60 vote requests cite CIP-0116 and 56 were accepted; 9 cite CIP-0105 and 5 were accepted.

The locks in contracts are announced, not live: CIP-0127 is an open draft, and its migration plan waits for the first increment on MainNet. Until then, it says, the Foundation's dashboards track "good-faith locked CC" beside on-chain locks.

My read is that it's more than a promise and less than a contract.

On Canton, a synchronizer is the service that orders transactions between nodes. The Canton Network's own primer says synchronizers can be deployed privately by application operators, or run as shared infrastructure. The shared one is the Global Synchronizer, run by the Super Validators, the operators that jointly run and govern the network.

So the software and the shared network come apart. This episode reads which is which, issuance by issuance.

Digital Asset's own bond table puts the EIB's euro bond of November 2022 on Goldman Sachs DAP, and the EIB's sterling bond of January 2023 and the Hong Kong government's green bonds of February 2024 on HSBC Orion. The issuers' own pages say private: "private blockchain-based technology" (EIB, 2022) and "Private permissioned blockchain under the HSBC Orion platform" (EIB, 2023). The HKMA names "HSBC Orion as the digital assets platform."

On the other side, Circle's USDCx is minted on Canton against USDC deposited in xReserve, and Franklin Templeton's Benji platform expanded to the Canton Network itself.

My read: a bond on a bank's private platform is a Digital Asset software story, not shared network activity. Whether any of those platforms has since connected to the Global Synchronizer is open.

Fairmint has opened a discussion draft for an NFT profile on Canton's token standard: pull request 276 in the Canton Foundation's CIP repository, opened 6 October 2026. A CIP is a Canton Improvement Proposal, a written change the network can adopt. This one is a draft. It is not adopted.

The mechanism, from the draft: a conforming item is a holding with an amount of exactly 1.0, one instrument per item. A holding is the contract that says a party owns some of an asset. It adds no transfer protocol. Transferable items use the existing CIP-0112 transfer and allocation flows, and a soulbound mode means the registry must not offer a transfer at all. My read: a profile, not a new token.

Who it is for: Fairmint's post to the cip-discuss mailing list says that, as an SEC-registered transfer agent, it will use the profile for equity certificates on Canton. Announced, not live. A transfer agent keeps the official record of who owns a company's shares.

What it rests on: CIP-0056 is final. CIP-0112, Token Standard V2, was approved on 12 June 2026, and on 28 July 2026 the Super Validators accepted a MainNet vote, 13 for and none against, to enable the models that carry V2 support. Super Validators are the group of operators that jointly run and govern Canton's shared network.

What is not there yet: no CIP number, a discussion link still to be added, no comments or reviews when read, and a reference implementation that the draft says will ship once reworked onto V2. Open.

The harder read: the draft says its uniqueness, revocation and replacement declarations state what the registry undertakes and are not ledger proof, and that a revocable item can be burned without the owner's signature. The public instrument list shows every item, though not who holds it. Fairmint's CEO was elected General Director of the Canton Foundation in December 2025.

On Canton, "weight" means two things. Every Super Validator node carries the same voting weight, the Foundation's included, and a vote passes with two thirds of the nodes. Reward weight is separate: it sets an operator's share of Super Validator rewards, and changing it takes a vote.

LSEG was approved as a Super Validator with a maximum weight of 10 under CIP-0124, a programme that "contains confidential commitments to the ecosystem," with milestones checked by an accountability committee. The Goldman Sachs proposal uses the same template and has not been voted on.

LSEG does not run its own node, so its weight has to be hosted. A request by the Global Synchronizer Foundation to add it was rejected, 2 for and 10 against. A second request, from MPC Holding, would lift that node from 45 to 55 and was still open on 7 October.

What the ledger shows: hosted weights are "combined and represented on-ledger under the name of the SV Node Operator." The split by owner lives in a configuration file in a public GitHub repository. Read on 7 October, that file listed MPC Holding at 35 and named neither LSEG, Marex nor Goldman Sachs. Canton Strategic Holdings is one of the names under the MPC Holding entry.

A draft proposal dated 30 September would move owners, weights and beneficiaries onto the ledger and show them in Scan. Nothing changes until a migration is voted on and executed. My read: it would show who holds the weight, not the confidential milestones behind it.

Zenith is building an EVM execution layer on Canton. EVM means the Ethereum-style machine those contracts run on. Its primitive, external call, lets a Daml contract call a Solidity contract inside one Canton transaction. Daml is the language Canton contracts are written in. Solidity is the language Ethereum contracts are written in. An external call is a step where Canton reaches that other system and still finishes as one transaction. Zenith's testnet post (28 Sep 2026) says that in a single transaction, either all succeed or the whole transaction aborts. That is atomic settlement: both sides finish together, or neither side does.

The mechanism, from the Canton 3.6.1 release notes: the submitting participant runs the call and records the result. A participant is the node that holds a party's contracts. Confirming participants independently re-validate that result against their own copy of the extension service before approving. A confirmer has to say yes before the step counts. The merged Canton code rejects the request on behalf of all hosted confirming parties on any disagreement. My read: a guarantee of agreement, not of truth, and it binds only the participants running the service.

What is live: Canton 3.6.1 was released on 5 October 2026 with external call as a released feature, requiring Daml-LF 2.4 and protocol version 36 or later. A protocol version is the numbered set of rules the network is running. Zenith's testnet runs a development Canton protocol version. The testnet synchronizer, the service that orders transactions, is on that development version. Read on 6 October, its explorer showed 520,676 indexed EVM transactions and a 4.4s average for linked transactions. Kaiko's oracle is live on the testnet, with production set for Zenith's mainnet launch. An oracle is a feed that brings an outside fact, such as a price, onto the ledger.

What slipped: MainNet was expected in Q2 2026 (5 Mar), then early Q3 2026 (19 Mar), and is now framed as after the Canton 3.6 rollout in Q4 2026 (28 Sep). Announced, not confirmed. I have not found a primary dating the MainNet upgrade to protocol version 36. Open.

The harder read: Zenith's docs say one transaction routes need your own extension, service and block builder, plus contracts only the operator can disclose, and the testnet gateway is run by Zenith. CIP-0091 made Zenith a Super Validator of weight 10, most of it reachable only through growth targets that run within 12 months of the MainNet upgrade carrying external call. A CIP is a Canton Improvement Proposal, a written change the network can adopt. A Super Validator is a validator the network has weighted to help run the shared ordering.

On 25 September 2026 the SEC's Division of Corporation Finance published FAQs that define a "receipt": an instrument certifying that a stated amount of an asset has been deposited with a custodian, and that the depositor owns it. Two tests sit inside that answer. A receipt does not provide the holder with any additional financial incentives or benefits. And the issuer cannot transfer, lend, pledge, rehypothecate, or otherwise use the deposited asset for any reason. These are staff views, not a rule of the Commission.

This episode reads three Canton assets against those two sentences.

CBTC (BitSafe): a 1:1 wrapped bitcoin, with the bitcoin held under FROST threshold signatures across independent operators so no single party can move reserves alone. My read: the custody side is built the way the second test describes. A holder lending CBTC in a Canton lending market is a different act from the custodian lending the deposit.

The Canton part: under the token standard CIP-0056, holdings are private, so total supply published on the ledger cannot be independently verified. The registry reports it. Read on 5 October, CBTC's registry figure was about 38 coins, the issuer's own number. BitSafe's answer is Chainlink Proof of Reserve.

cLTC (Greywick Digital): announced, expected on Canton by the end of 2026 against a published, independently attested reserve. The Litecoin Foundation memorandum names cLTC for "institutional trading, yield bearing, and other institutional-grade vehicles." My read: that wording collides with the first test only if the yield lives inside the token. The announcement does not say which. Open.

iSOL (Canal): a SOL backed asset, redeemed by removing iSOL and releasing SOL on Solana, with a controlled MainNet pilot of at least 14 days described in its Featured App application. A product carrying SOL staking yield is listed as a separate future line. Open: whether the deposited SOL itself is staked.

Chainlink shipped CCIP 2.0 on 28 September 2026. If your asset lives on Canton, what actually changes the day it needs to leave?

This episode reads Chainlink through a data governance lens. Every large organisation fights the same four problems with data: agreeing what a thing is called, naming who owns the record, keeping every copy fresh and consistent, and moving it between systems without re-keying. Under other names, that is what Chainlink sells. Data Streams is distribution with a freshness guarantee, SmartData is master data about an asset, CCIP is the integration layer with a token standard, and Chainlink's own Canton proposal wrote the data access step down: acquire the rights to view private data, standardise it, publish it.

The 2.0 change: the default is one Committee Verifier of sixteen operators, an issuer can add its own verifier and require its signature on every transfer, and Chainlink's docs say the Risk Management Network's automated role is no longer active in current deployments. My read is that security became a setting, and the reconciliation step moved from the platform to the data owner. April's $292 million Kelp exploit ran through a bridge with a single verifier and no second source to reconcile against.

Canton set up its own bridge race in 2025 (CIP-0065: Chainlink, LayerZero and Wormhole at weight three each, a bonus for the first to move $10 million for an independent third party, the plain asset name for the first to move $50 million of one asset). All three delivered between June and August 2026 and were paid in Canton Coin by unanimous votes. Chainlink's directory lists Canton Mainnet with one lane, to Ethereum, already on the 2.0 contracts, fees quoted in Canton Coin, and zero tokens.

Who on Canton already reads Chainlink data: Temple (Data Streams for private spot markets), CBTC by BitSafe (Proof of Reserve on the bitcoin backing, over two million transactions a month), Alpend and Raven Market (Data Streams for collateral pricing and options settlement), T-RIZE (Data Streams for proof of insurance, with the insurer as the source of truth). Edel reads Data Streams on Ethereum and Base today, with Edel Markets on Canton still to launch.

My read, up front. Most of real-world finance isn't fungible. A building, a loan, a fund commitment, each one is its own thing. So the record that matters is a deed, not a balance. Jubilee wants to build deeds for Canton, starting with art. And it filed the plan under the network's RWA standards track.

So, precisely. Confirmed, a filed proposal for six hundred thousand Canton Coin, a committee champion, and open-source infrastructure with two audits scoped. Announced, a private MainNet review, atomic settlement, backed offers and flat fees. Open, the approval, the audits, an independent check on the numbers, and whether independent users turn up.

So the test for Jubilee isn't whether art on Canton finds buyers. It's whether its parts get picked up by a team that isn't Jubilee, for something that isn't art. Its own fourth milestone asks for a worked example outside collectibles. If you'd build on it, which one-of-one asset goes first?

Canton was built for banks. This summer X Money made paying a handle ordinary, and two apps on Canton, HandlPay and Send, are building the private version. So can Canton handle everyday payments, and when you get paid on it, who else gets paid?

The stack is live at small scale. There are three ways to name who you're paying: the network's own name service, Send's Sendtags, and HandlPay's social handles. There are two dollars. Circle's USDCx is about 7.2 million on Canton at today's read, and Send's CUSD routes its reserve yield to Canton Coin buybacks. Money gets in and out through Kraken and the bridges, and there's a card you can fund from a Canton wallet.

Who else gets paid is mostly the float and the mint. Featured apps earn newly minted Canton Coin for the activity they drive, which is how a payments app can charge you nothing. The switch to traffic-based rewards didn't go live on 18 August, and validators now vote on each featured app's weight. That vote is the biggest variable in a Canton payments business.

Tokenization is moving into real estate, private credit and structured products. Someone has to structure and issue those assets on Canton and price the risk on them, and this issue asks whether T-RIZE is that layer yet.

A real seat on Canton. A Montreal tokenization firm, welcomed to Canton's Global Synchronizer Foundation in April 2025, running a validator and issuing on regulated-market rails. That's on Canton's own pages, not self-declared. confirmed

One company, several rails. Its own chain, Rizenet, is an Avalanche L1, and Canton is the regulated-rails venue. Partners include Texture Capital, a FINRA broker-dealer, plus Fireblocks and ERC-3643. confirmed

The edge is the AI, not the token. Rizemind is a federated-learning layer deployed on Circle's Arc, where data stays inside each institution and only model updates move. It's backed by a Mitacs and NSERC funded tokenization chair at ETS. confirmed

Two stories, read at their tier. T-RIZE and Chainlink are reported to have anchored proof of insurance on Canton for Kairos Digital Loan Notes, a $500M bond on UK litigation-finance receivables, sourced from trade press. With Republic and Canton it announced the first new-construction real estate equity tokenization on Canton, phase one of a stated $200M plan called Vision 60. announced

The token is moving upmarket. Listed on Revolut and Kraken, it's delisting from both on a set deadline given to holders and consolidating onto native Canton and Arc, with a 30M Canton Coin lock underneath. announced Edel wants to be the venue. T-RIZE sits earlier and wider, issuing the assets and building the layer that prices their risk, and nothing trades until it's issued. my read

DTCC is settling tokenized Treasuries on Canton and the SEC just opened a lane for tokenized stocks. Someone has to build the venue where those assets trade, and this issue asks whether Edel is that venue yet.

Runway is live. That part is real. Edel's Canton participation platform is in private beta, with thousands of beta users, a Cantex partnership and three rounds of Canton Coin rewards. The figures are Edel's own. announced

Markets is the ambition. It isn't live. A Canton-native venue for perpetual futures on tokenized equities and commodities, with positions kept private, targeting Q3 2026. On 22 September Edel's own site still showed the waitlist. open

A bad month, handled like adults. A wrapped-stock rate was gamed on Edel's Ethereum lender, about 78x inflation and roughly $403K of bad debt. The oracle was right, the wrapper wasn't, and Edel absorbed the loss. confirmed

Two things moved, and both point at Canton. DTCC ran live tokenized-asset trades with Canton among the rails, with a full service due in October. confirmed The SEC's lane is spot stock through automated pools with full shareholder rights, while Edel Markets is perps on an orderbook plus commodities. A tailwind, not a green light. my read

Phase Two is a real map, mostly arrows. Edel joined the DTCC working group as one of 100-plus members, which is a seat at the table, not a deal with DTCC. Its roadmap takes Markets to open beta and then mainnet, adds a stocks product it says has SPY and QQQ live on Canton, plus staking and fee-funded buybacks. announced

Congress stalled. The regulator moved anyway. The CLARITY Act failed to advance in the Senate, and the next day, 17 September, the SEC issued a five-year exemption to let tokenized stock trade onchain. confirmed, SEC release

Read the order, not the story. Real shares only, with dividends and votes and no synthetics. The issuer gets 30 days to object to tokenization. The contracts have to be public and auditable, on a public, permissionless ledger. Volume caps, halts with the stock, US persons, five years. confirmed

One line decides who gets in. A public, permissionless ledger points the whole exemption at open, retail-facing trading, the world of automated pools. my read Public, permissionless rails carry retail equity trading and permissioned, private rails carry institutional settlement. Canton's built for the second, so this lane isn't Canton's. my read

The rail Canton actually runs doesn't need it. DTCC's tokenization service is lining up to go live in October. announced Its first phase is US Treasuries custodied at DTC, Marex, BNP Paribas and SocGen have run live pilots on it, and the order doesn't touch it. confirmed

The rules aren't written yet. That's the opening. The exemption is temporary and open for comment, and the permanent shape of US tokenization law is still being drafted, lane by lane. announced

Canton Strategic Holdings ($CNTN) is the first public company built entirely on a Canton Coin treasury. Q2 2026 is the first quarter that treasury earned anything, and read closely it is two companies on one ticker, running on two different clocks. confirmed, from the release

Company one is the holding. 3.7 billion Canton Coin, marked to market. That mark swung 23.7 million dollars against them and drove a 19.3 million dollar net loss, and the coin is carried at 523 million against 584 million paid, underwater about 11 percent on cost. Its clock is the CC price, which nobody controls. confirmed

Company two is the operating business, and this is the quarter it switched on. 1.5 million dollars of revenue from two Canton native jobs, locking Canton Coin to back other operators and running a Super Validator. Yield from holding the position, not from its price. confirmed

The catch is that the business is metered. Earning power on the network is measured as weight, and only 0.5 of an approved 15 units is live today. The other 14.5 unlocks in tranches through Q1 2028, and only as the company meets deliverables and the Canton Foundation's Accountability Committee signs each one off. announced, not earned So the market prices $CNTN as the coin it holds, and the thesis is whether the metered business compounds into what the coin alone cannot, before the unlocks stall. Not a price call, a cadence call. my read

The Canton Coin mint curve stepped down this year, out of its 20 billion a year phase and into the 10 billion phase, on the published schedule. So the question from issue one, does the burn beat what the schedule mints, has a moving bar. confirmed, white paper and FDV post

Pulled from the network's own scan data, the most recent tracked day minted 21.9 million coins and burned 16.4 million, a burn to mint ratio of 0.75, and across 30 days that ratio never once crossed one. Annualized, mint runs about 7.9 billion a year, below the paper's ceiling for this phase; burn runs about 5.6 billion, more than double the steady-state target but still short of today's mint. Supply is still growing. confirmed

One line stayed open. Cumulative reward-minting and the reported circulating supply do not reconcile against recorded burn, off by about 2 billion coins. Reward minting is not the whole supply story, and that gap is stated on screen rather than smoothed over. open

The question institutions actually ask is whether the thing that makes the network valuable also makes the token valuable, or whether those are two assets sharing a name. On Canton the mechanism is written down. Every network fee is burned in full by the person paying it, so the token's claim on activity is the burn. confirmed, white paper

New coins are minted on a published curve, and in the current phase they go to application providers, validators and Super Validators. Holders are not on that list. So the token captures value through the burn and nothing through the mint, and both are published facts. The bar the burn has to clear is about 10 billion coins a year in this phase, 2.5 billion at steady state. confirmed

What today's burn actually is could not be sourced from a primary that week, so it was marked open on screen, and it is the first thing issue two closes. open