Source Notes & Caveats
This industry is largely opaque and lacks objective, independently audited performance measurements. Most figures below originate from vendor press releases or self-reported surveys. Treat all numbers as indicative rather than definitive, and verify against your own benchmarking before committing to a platform.
[1] Fabric throughput ~3,500 TPS — Sourced from Hyperledger Caliper benchmark test suite v2.5 (LF Decentralized Trust). Caliper is the project's own benchmarking framework; results are hardware- and configuration-dependent and should be reproduced on representative production hardware. The figure reflects Raft ordering under controlled conditions and may not hold at scale or under adversarial load.
[2] Fabric finality ~2–3 s — Reflects typical Raft ordering block time in enterprise configurations with default settings. Actual finality is configurable (blockperiodseconds) and varies with network size, transaction complexity, and validator count. No independently published production latency data is available for large-scale deployments.
[3] Fabric-X 100,000+ TPS target — IBM Research contribution to LF Decentralized Trust (2025). This is a research-track contribution, not a production release. The figure is a stated design target for the Arma BFT ordering service under parallel microservice execution; it has not been independently reproduced in a multi-party production environment.
[4] Besu QBFT ~1,000 TPS — Cited by LF Decentralized Trust project page (2025) and corroborated by academic performance analysis using the Hyperledger Caliper tool (ResearchGate, 2022). Throughput is highly sensitive to block time configuration (blockperiodseconds), node count, and transaction complexity; the ~1,000 TPS figure reflects a representative enterprise configuration, not a maximum ceiling.
[5] Besu QBFT block time ~2 s / fault tolerance 2-of-3 — Per Hyperledger Besu documentation (besu.hyperledger.org). Block period is operator-configurable; the 2 s default is common in enterprise deployments but not fixed. The 2f+1 fault tolerance requirement (minimum 4 validators for f=1) is a protocol property documented in the QBFT specification.
[6] Tessera deprecation June 2026 — Confirmed in Besu release notes and project documentation. Any Besu deployment using private transactions via Tessera must complete migration to an alternative private transaction manager before this date.
[7] Corda >$10B tokenized RWAs — R3 press release, February 2025 (GlobeNewswire). The figure was subsequently updated to $17B by September 2025 (R3 Labs launch announcement). Both figures originate from R3 itself; the methodology for calculating "on-chain RWAs" (e.g. notional value vs. settlement value, active vs. cumulative) is not publicly disclosed. The number should be read as a directional indicator of ecosystem scale, not an audited balance sheet figure.
[8] Corda ~2,500 Kotlin/CorDapp developers globally — No independently verified census exists. This estimate is derived from job-market proxies (freelance platform listings, Stack Overflow survey data on Kotlin for enterprise DLT) and is widely cited in analyst commentary. The true figure could be materially higher or lower; R3 has not published a developer count. Kotlin itself has a larger global developer base; the constraint is Corda-specific CorDapp expertise.
[9] Corda commercial license 20–25% TCO premium — Indicative estimate based on publicly available Corda Enterprise vs. open-source feature comparison and typical enterprise software licensing patterns. R3 does not publish list pricing; actual cost uplift depends on node count, support tier, and negotiated terms. This figure should be modelled with your procurement team, not taken as a fixed rate.
[10] Corda on Solana / R3 Labs strategic direction — R3's strategic pivot to Solana was announced May 2025 (R3 / Solana Foundation press release); R3 Labs, the division executing this strategy, was formally launched September 2025. R3 Labs targets public-chain RWA distribution via Solana. The long-term implications for the permissioned Corda roadmap are not yet clear; R3 states both tracks will be maintained, but resource allocation between them is not disclosed.
[11] Canton / Digital Asset $135M raised, investor list — Per Digital Asset public funding announcements and Crunchbase. Note: Fnality International (a related but legally separate entity whose £FnPS runs on Ethereum/Besu, not Canton) raised $136M in a separate Series C round (September 2025). These are distinct companies; the $135M figure applies to Digital Asset / Canton only.
[12] DTCC/DTC U.S. Treasury tokenisation MVP H1 2026 — Based on DTCC Digital Launchpad programme announcements and reported timelines. The broader rollout timeline is subject to regulatory clearance and operational readiness. No independently audited throughput or economics for this deployment have been published as of the knowledge cutoff for this tool.
[13] Canton Daml developer pool <1,000 — No verified census exists. This is a rough market estimate based on Daml certification programme participation, GitHub contributor counts, and CorDapp developer community signals. Digital Asset has not published an official developer count. Given the niche language (Haskell-influenced functional syntax), the pool is widely considered the smallest of the four platforms evaluated here.
[14] Canton TCO ~$150K/node/yr — Indicative internal modelling estimate. Digital Asset does not publish pricing. Actual TCO is highly dependent on deployment model (cloud vs. on-premise), Canton Enterprise vs. open-source, support tier, and integration complexity. This figure should be treated as a high-end planning assumption requiring validation via direct vendor engagement.
[15] Fnality BoE settlement finality designation — The Sterling Fnality Payment System (£FnPS) was recognised by HM Treasury in August 2022 and commenced controlled live payments in December 2023. It received Settlement Finality designation from the Bank of England (announced December 2024). Fnality runs on Ethereum/Besu, not Canton. The reference in this tool is to Canton's association with Fnality's shareholders (Goldman Sachs, DTCC, BNP Paribas), not to the underlying technology stack of £FnPS.