- β’
Canton's enterprise model challenges crypto's permissionless ethos - developed by TradFi giant DRW, the system requires a business proposal and a two-thirds vote from existing members to become a validator, prioritizing institutional control over open access.
βIf you want to become a validator on Canton... you submit a business proposal to existing validators, and you get a two-thirds vote.β
- β’
Hidden state architecture separates Canton from public blockchains - unlike Ethereum where data is public, Cantonβs state is hidden from everyone but validators, creating a 'default no' environment that critics argue lacks necessary verifiability.
βThe validators know the state, but you cannot query an RPC node and see, here's the total supply of this asset, or here's the holders of this asset... the validators can see it, but nobody else can see it.β
- β’
MEV is being used as a marketing wedge for enterprise adoption - Canton leadership claims public chain front-running is a dealbreaker for institutions, though crypto natives point out that RFQ platforms already solve these privacy issues on-chain.
βHis point is like MEV is just, yeah, TradFi institutions are never gonna function with MEV. And to me, it's a bit strange because... those kinds of transactions are already possible on Ethereum and Solana. You can just use like RFQ platforms.β

