I did some research on @CantonNetwork, which raised a lot of money before. I think there’s a lot worth discussing about its design. I haven’t tested it myself, just summarized some points from the literature. First of all, aside from the privacy aspect that everyone’s talking about, its network design is based on sync domains, with a concept of 'domains.' It’s somewhat similar to L2/subchains but not entirely independent, allowing atomic collaboration. Comparing it to Ethereum’s structure makes it easier to understand: Ethereum is a typical global shared ledger where all nodes synchronize and share the same state. Under this overarching logic, Canton splits into multiple partitions, with each partition executing tasks in parallel. Sorting and forwarding are done within these partitions, which are the 'domains.' Its biggest advantages are: 1. As long as the participating parties share at least one 'domain,' contracts from different applications can be processed together atomically. When necessary, sorting rights can even be migrated to another 'domain.' In contrast, in Ethereum’s traditional structure, L2s must rely on bridges, which significantly reduces system complexity and attack surfaces. 2. Canton’s sync domains only see encrypted data, whereas traditional sorters process plaintext. This is the main narrative being pushed in the market for this project. Sync domains don’t know what information they’re sorting, so naturally, there’s no MEV. The validity of the information is verified locally by each stakeholder for their part of the transaction and endorsed with a signature. To some extent, this sacrifices complete trustlessness and shifts to limited trust. From this, it’s easier to draw conclusions. Canton’s design assumes limited trust in sync domain operators. It doesn’t aim for Ethereum’s strong trustlessness of 'permissionless global synchronization,' so its target customers are likely institutional-level use cases like stock tokenization, cross-border payments, etc. The advantages it offers are 'efficiency' and 'privacy' within a compliant environment.