Is Daml Hub Quietly Becoming Canton’s Weakest Trust Layer?

If Canton is designed as a privacy-preserving, decentralized multi-domain network for institutions, how do you justify relying on Daml Hub as a managed infrastructure layer without creating a hidden centralization point where participant control, Ledger API visibility, operational metadata, and institutional dependency quietly shift trust back to the platform provider rather than the protocol itself?

@adhexzzz

Daml Hub has been decommissioned and is not part of the Canton Network stack at all.

Encourage you to have a read through the latest Canton Network docs, potentially this section on Trust Model may be helpful :

Trust Model Overview - Canton Network Docs

Understanding who you trust and what you trust them for in Canton Network

Thanks for clarifying — I was referencing older architecture assumptions. I’ll read through the Trust Model section and revisit my understanding of how visibility and coordination work in the current Canton stack.