If you were absolutely committed to:
- Bringing the global financial system onchain, linking all existing institutions into an interoperable network accessible to anyone
- Adding a fully decentralized crypto ecosystem inside that network, with atomic composability among traditional and crypto assets
- Allowing anyone in the world to personally own a piece of that network, with self-custody of that ownership stake
- Preserving privacy for everyone
What would you build?
If your understanding of Canton doesn’t fit this picture, let’s dig deeper.
Over the years, much of the crypto world has lost track of the importance of asymmetry in decentralization. @ShaulKfir reminds us of the importance.
Symmetric distribution means that one change impacts everyone; a burst of traffic impacts everyone; an error impacts everyone.
True decentralization requires autonomy, which means decentralized control: different control centers that can ignore each other when they disagree.
Canton is asymmetric: by separating ordering, distribution & confirmation from transaction validation, independent subnets can operate on different rules, with different bandwidths and costs, shielded from pressure on other subnets, without any compromise on composability, atomicity or cryptographic consistency proofs.
Fed research paper argues that digital money (stablecoins, MMFs, tokenized deposits) can be "fragile" even when perfectly backed, due to the properties of the chain. The core argument is that the rails can cause a "run on the bank."
@CantonNetwork prevents this risk
@LeilaniFarms Yuval is saying that continuous trading by the DTCC and its members / customers will go live on Canton in October. Several rounds of practices and process proveouts will happen before then, starting in July.
A series of practice DTCC <-> DTCC member trades will go through the Global Synchronizer in July. And around that time, various DTCC members will start regularly testing the new processes / procedures that they're building around Canton. Go live for continuous activity is slated for October.
It's actually pretty funny how few of the 800 active Validators are run by Wall Street / TradFi. But TradFi are capable of massive levels of activity, so it sort of balances out. Over time I'd expect the number of TradFi nodes to rise to a meaningful portion. But serious cypherpunks are also going to run their own Canton nodes (and their own subnets/havens) as well.
The pace is only going to increase, with better automation for the upgrades, we'll probably release more changes faster. And we're preparing ourselves to handle a steady rise in tps for the foreseeable future.
Impossible to predict exactly how adoption will go, but we've reached about 50% of Ethereum's daily active users, and we're still coming up on two years into this.
Frankly, it's been pretty intense.
It takes work to maintain a Validator on Canton. For starters, we upgrade every week, and have some sort of forking change about once a month. We have a lot of work to do, and the pace is not for everyone.
And you only earn rewards by either building & running an app, hosting an app and buying traffic for its users, or operating / staking a node on the backbone synchronizer. Not much room for casual players, but if you're up to it, you're welcome to join.
@thedevranjan@Param_eth For scaling reasons there's sometimes a delay of a week or two to get a validator slot, but if you want to run a node, you can. Not just institutions. Fill out the form here to be added to the queue:
https://t.co/xLuVWbiZ1N
@macjshiggins So true. AI is making systems engineering the default working mode for engineers now. Even better, you can afford to iteratively test all the way down the V, instead of just on the way back up.
Hey, guys, thanks for the questions.
Both are going to happen:
Validators on private subnets have to burn CC when they want to also compose transactions across the Global Synchronizer. That’s real now.
And you will see private synchronizers start to require CC burn for transactions on the private subnets.
You’ll know private subnet burn is close to reality when you see a CIP reach public discussion. I expect to see a CIP go public within a few months, but can’t be certain. There’s a lot of background work happening to move the network in this direction.
Hi, @akyra_0
An interesting and useful perspective in the memo. Thanks for taking the time to dig into the details.
The work to make it easier to route across the Global Synchronizer is a major focus for the Canton and Splice teams this year. You'll see significant improvements in the tooling for gSync routing in the Splice 1.0.x release line starting June - July, and further improvements throughout the rest of the year.
Also, as Yuval has already hinted, the community is considering whether to make CC burn a requireement for activity inside the subnets, independent of routing across the gSync. We'll see more analysis and discussion of the relevant tradeoffs in the second half of this year, along with some technical proposals for how it might happen.
One minor clarification: Most CC is now minted as App Provider rewards, not Validator rewards. The app reward portion is the largest now and its share will continue to rise.
A private subnet is a private synchronizer with some Validators linked to it. Those same Validators can also link to the Global Synchronizer. Making this easy and common is a big focus for the coming year. For example, you’ll see support for contract keys in multi-synchronizer apps, and (as Yuval mentions), CC burn on private synchronizers.
It is easier to do a series of micro hard forks, in comparison to one big one. But, the incentive for successful blockchains is to squeeze all the changes into one big hard fork, since the politics of activation is the difficult part.