# DAML leger is not blockchain **URL:** \ **Category:** App Development\ **Tags:** daml, json-api, rps-security, ledger-api, canton, damlhub\ **Created:** [April 26, 2023, 3:21pm UTC](https://forum.canton.network/t/daml-leger-is-not-blockchain/6485 "2023-04-26T15:21:53Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Iqra\_Mustafa1](https://avatars.discourse-cdn.com/v4/letter/i/ec9cab/32.png) [@Iqra\_Mustafa1](https://forum.canton.network/u/Iqra_Mustafa1)\ **Post date:** [April 26, 2023, 3:21pm UTC](https://forum.canton.network/t/daml-leger-is-not-blockchain/6485/1 "2023-04-26T15:21:53Z")
The DAML ledger is not a blockchain. But when we run DAML contracts on some other supported platforms, i.e., Fabric or Corda, they inherit the properties of the underlying persistent layer. For instance, their consensus mechanism? ---
**Author:** ![Remy](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/remy/32/595_2.png) [@Remy](https://forum.canton.network/u/Remy)\ **Post date:** [April 27, 2023, 1:12pm UTC](https://forum.canton.network/t/daml-leger-is-not-blockchain/6485/2 "2023-04-27T13:12:16Z")
The basic answer is yes. Note that as explain in this thread, we are working on enabling the Canton Synchronization and Consensus layer over Byzantine Fault Tolerant (BFT). Once done we plane to remove the dependency on any external blockchain layer for consensus ---
**Author:** ![jvelasco.intellecteu](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/jvelasco.intellecteu/32/7305_2.png) [@jvelasco.intellecteu](https://forum.canton.network/u/jvelasco.intellecteu)\ **Post date:** [May 14, 2023, 9:31am UTC](https://forum.canton.network/t/daml-leger-is-not-blockchain/6485/3 "2023-05-14T09:31:42Z")
Hi @Remy could you please share the thread you mention? Thanks Jose ---
**Author:** ![cocreature](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/cocreature/32/36_2.png) [@cocreature](https://forum.canton.network/u/cocreature)\ **Post date:** [May 15, 2023, 6:47am UTC](https://forum.canton.network/t/daml-leger-is-not-blockchain/6485/4 "2023-05-15T06:47:28Z")
@jvelasco.intellecteu I believe Remy was referring to [Canton Decentralized Domain - #2 by Wayne\_Collier](https://discuss.daml.com/t/canton-decentralized-domain/6476/2) ---
**Author:** ![Wayne\_Collier](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/wayne_collier/32/4156_2.png) [@Wayne\_Collier](https://forum.canton.network/u/Wayne_Collier)\ **Post date:** [May 15, 2023, 12:10pm UTC](https://forum.canton.network/t/daml-leger-is-not-blockchain/6485/5 "2023-05-15T12:10:03Z")
To take this one step further, you could argue that a blockchain provides at least: - Guarantee of ordering, and - Guarantee of consistent and immutable state among other guarantees. Canton 2.x gets its ordering guarantees from the sync domain, which in turn relies on a source of ordering that can either be a simple relational database, or a decentralized ordering service. If you need your ordering service to be decentralized, then for Canton 2.x you can use Hyperledger Besu or some alternative. It might be helpful to think of the Canton sync domain as a “router with guarantees”, rather than thinking of it as the underlying persistence layer. Instead, the state maintained on the participant nodes is closer to being a root persistence layer; the sync domain is there to deliver guarantees of ordering, delivery and readiness to commit a transaction, not to serve as the root source of persistent data. The sync domain does persist the transaction log to get that job done, but I’d argue that the state maintained in the contracts stored in the participant nodes is the root persistence layer. Which gets us to the second major property: consistent and immutable state. That is provided by the hashes that Canton records with each change to the contract data, and the proofs (“commitments”) sent among the stakeholders to verify that the resulting contract creation and update/archive actions have produced the same state for every stakeholder. So Canton splits its blockchain into two concerns: a chain of validated hashes and proofs between UTXO states on the Canton participant nodes, and an ordering and routing service with strong guarantees, provided by the synchronization domain. The missing piece in the Canton protocol is to make the synchronization domain fully decentralized within the Canton protocol itself. That’s the work we’re doing now, and we plan to announce more details about it over the coming months.