So once the code has been released to enable XCM in the runtime in version 0.9.19, it still needs to move through Polkadot's governance before the upgrade will be applied. This should take a few weeks, depending on whether the technical committee chooses to accelerate the upgrade
Channels are fully safe, secure bridges between parachains. Unlike other bridging protocols, which introduce a 'weakest-link' problem, messages across XCMP channels are secured at the same level as the relay chain. Mr. Vitalik describes it well:
Parachains open channels to other parachains by sending an XCM message to the relay-chain instructing it to open the channel (and inform the remote chain of the request). Since the relay-chain hasn't had XCM processing enabled, no channels have been opened until now.
XCM support for Polkadot was enabled in PR github.com , but it's been on Kusama much longer. After being battle-tested among Kusama's chaotic community, it's proven ready to deploy to the Polkadot network.
So what does this mean for the trends within the developer community on Polkadot?
Another factor is market participation: the thing that's slowly blowing everyone's minds in the blockchain space is asynchrony. Arbitrage bots, MEV, and "international trade" between blockchains are going to be altered forever by the impending asynchronous paradigm.
There's going to be a combinatorial explosion in both the amount and kinds of opportunities in the Polkadot and Kusama ecosystems. This is really what XCM unlocks: cross-chain value. Further down the line, this'll teach the next generation of devs what chains & products to build
Loading suggestions...