The next wave of Polkadot: 06 Major Parachain developments coming in 2024
Tags: polkadotparachains, appchains
Published: 2024-02-14 09:09:37

<p>Parachains are Polkadot’s ground-breaking innovation that has been enabling a wide range of enterprises to develop advanced, future-proof Layer-1 blockchains that are easily customizable for application-specific use cases. Speaking about 2023, it was a cherishing year for <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachain</a> and the monthly active addresses saw notable growth from <a href="https://messari.io/report/state-of-polkadot-q4-2023">104,000 to 2,00,000</a>, and this growth was seen across all the leading <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachains</a>. Plus, a range of interesting upgrades were rolled out for the Parachain ecosystem, such as the introduction of Polkadot-SDK. Now that we are in 2024, let’s talk about the major <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Polkadot Parachin</a> developments of 2024 and understand how they drive benefits to the entire Parachain ecosystem.&nbsp;</p>
<figure class="wp-block-image aligncenter size-large"><a href="https://www.zeeve.io/appchains/polkadot-parachains/"><img src="https://www.zeeve.io/wp-content/uploads/2024/02/Deploy-custom-Parachains-on-Zeeves-Sandbox-in-few-clicks.-1-1024x130.jpg" alt="Polkadot Parachains developments" class="wp-image-58796"/></a></figure>
<h2 id="h-06-major-polkadot-parachain-developments-coming-in-2024">06 Major Polkadot Parachain developments coming in 2024</h2>
<p>Based on Polkadot’s official announcements and as described by Gavin Wood in his <a href="https://medium.com/polkadot-network/polkadot-2023-roundup-7fe77d88f022">annual diary</a> that he published in December, 2023, below are the 06 major upgrades coming to Parachains in 2024:</p>
<h3 id="h-1-agile-coretime">1. Agile Coretime:&nbsp;</h3>
<p>Let’s discuss Agile Coretime as the first major <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Polkadot Parachain</a> developments in 2024. Agile Coretime is a novel idea of Parachain coretime (Duration on Parachain–Polkadot’s key resource) allocation which has been introduced after RFC-1– the first “Request for Comments' ' and an intense development period. Agile Coretime mechanism replaces the traditional auction-based allocation with a unique sale-based approach in which chunks of Coretime are represented as XCM NFTs and are offered to buyers at a more predictable price via monthly sale, ahead of the usage.</p>
<p>Earlier, projects could only lease the <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachain</a> space which included challenges like hard-to-predict deposit, no estimated time of slot allocation. Now, Agile Coretime is eliminating all the previous challenges of auction-based space allocation systems like&nbsp; 2-year contract, high-fluctuation in allocation estimation, and meanwhile making Coretime allocation more predictable, flexible, user-friendly, and economical. For trading of Coretime, marketplaces like <strong>Lastic</strong> have already been developed, providing ease to the buyers.</p>
<h4>What new things Agile Coretime enables?</h4>
<p><strong>Coretime-chain:</strong></p>
<p>Coretime-chain is designed to monitor and track record of all the coretime transactions. It’s a sort of specialized ledger which aggregates the activity details for every coretime like who owns how much space, what core has been renowned, which core is sold on bulk, whose ownership is shifting, and many more.&nbsp;</p>
<p><strong>Great Flexibility:</strong></p>
<p>As Agile Coretime replaces the traditional auction-system, users will no longer be forced to lease <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachain</a> blockspace for 6 months to 2 years. Rather, they can instantly specify and get the space they actually need. This situation will save cost, time, and waste of valuable resources.</p>
<p><strong>No need to lock DOT Tokens:</strong></p>
<p>Unlike the old Parachain slot allocation method, Agile Coretime does not require buyers to lock in DOT, which created huge uncertainty and was also discouraging for small projects. Now, they can get the space on-demand with no advance capital investment.</p>
<p><strong>Guarantee of space allocation:</strong></p>
<p>Agile Coretime guarantees space allocation for buyers. Earlier, even when a project successfully gets their desired coretime, the cost of slots after their lease expiry can highly fluctuate due to high demand of <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachains</a>.</p>
<p>Additionally, Agile Coretime offers the following two unique formats for projects through which they can buy Parachain space:</p>
<p><strong>Bulk core time: </strong>Exactly what the name suggests, bulk coretime explains the process of buying Coretime in bulk and in advance for future use.</p>
<p><strong>Instantaneous coretime:</strong><strong> </strong>This format is like SaaS products’ pay-as-you go plan. Projects can buy Coretime and continue paying for its subscription. Plus, this type of Coretime is available for instant needs.</p>
<h3 id="h-2-on-demand-parachains">2. On-demand Parachains:</h3>
<p>The next big Parachain development in Polkadot’s 2024 bucket is&nbsp; ‘On-Demand Parachains’, which was previously known as Parathread among Polkadot veterans. On-demand <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachains</a> now work with Agile Coretime mechanism and thus represent a highly dynamic acquisition method for Polkadot block space. As we can understand from its name, on-demand Parachains allow projects to buy coretime immediately whenever there’s a requirement for transactions. The need of opting for longtime “rented” blockspace will no longer be relevant. Instead, On-demand Parachain model will be applicable where buyers contribute Coretime into a shared pool and from that pool anyone can buy required Coretime in an instance. Besides Agile Coretime, On-demand Parachains will set a new standard for Polkadot’s space utilization process. As discussed, On-demand Parachains are backed with Agile Coretime mechanism. Therefore, the same two space selling formats– Bulk core time and Instantaneous coretime will work for ODPs as well.</p>
<h4>What Problem On-Demand Parachains aim to solve?</h4>
<p>Before On-demand Parachains (ODPs), projects had the only option to secure block space for a certain period; e.g one 2 years. Plus, they are required to author a new block every 12 seconds throughout the duration you own the slot. While this guaranteed ability or requirement to author block in 12 seconds is an essential feature for high-traction applications, the same can also result in wastage of computational resources from the perspective of new projects that do not see very high volumes of transactions as they are just starting out. On-demand <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachains</a> puts an end to this 12-seconds block authoring method and instead allows collator-based ordering of Core when there’s a demand.</p>
<h3 id="h-3-elastic-scaling">3. Elastic Scaling:</h3>
<p>Elastic scaling, which can also be called on-demand scaling, is a feature that will allow Parachains to occupy multiple cores simultaneously, enabling them to achieve scalability beyond one single core. Simply put, Elastic scaling optimizes <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachain network’s</a> performance by adjusting its resource allocation in line with the scaling demand. As we know, the demand for blockspace in applications will peak and fall. The peak demand here can be catered by acquiring additional coretime with instantaneous coretime of Elastic Scaling. However, for more predictable demand, applications should ideally acquire blockspace in bulk.&nbsp;</p>
<h4>How Elastic Scaling works?</h4>
<p>The main technology powering Elastic scaling is Agile Coretime that we have discussed already. With Agile Coretime, Parachains get the flexibility to scale dynamically– be it up or down based on needs.&nbsp; For example, if your application needs higher scalability, you can add more cores. Whereas, if the traffic volume goes down, you can exclude core to reduce scalability, thus preventing the situation of ‘Empty Blocks’ which is a major challenge for <a href="https://www.zeeve.io/blockchain-protocols/">blockchains</a> nowadays.</p>
<h3>4. Asynchronous Backing:</h3>
<p>Asynchronous Backing is a very crucial upgrade on Parachain’s consensus protocol, for which the announcement was made by <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Polkadot</a> developers at the sub0 developer conference held in Lisbon. Async backing is essentially designed to split the existing Parachain block time from 12 to now 6 seconds and meanwhile expand the block space on each block by at least 5 to 10 times. As of now, asynchronous Backing is live on <a href="https://www.zeeve.io/blockchain-protocols/deploy-kusama-node/">Kusama</a>, plus it’s supported on Rococo testnet and will soon be pushed on to production.&nbsp;</p>
<p>Elastic scaling and instantaneous coretime are the two main technologies that powers asynchronous backing, enabling greater flexibility into Parachains for future scaling. Parity’s lead engineer, Sophia Gold earlier made a statement saying that the <a href="https://www.zeeve.io/blockchain-protocols/deploy-polkadot-node/">Polkadot</a> team has created a credible roadmap to scale Parachains for massive scalability. Launching the asynchronous Backing feature is one such effort that we have made to enable endless scalability in Parachains and expand our ecosystem to 1,000 Parachains by the end of 2024.&nbsp;</p>
<h4>Key advantages of Asynchronous Backing:</h4>
<li>2x higher throughput or 2x lower latency for all the <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachains</a>.</li>
<li>Allows 4x more data for a parablock</li>
<li>Enable all the Collators to submit parablocks in advance for backing desired groups.</li>
<li>Ease for Collators as they have the flexibility to build parablocks in advance.</li>
<li>Greater efficiency and notable boost in scalability.</li>
<li>Less or almost zero wastage of empty (unused) blockspace.</li>
<h3>5. Ethereum Snowbridge:</h3>
<p>Addition of Snowbride into <a href="https://www.zeeve.io/blockchain-protocols/deploy-polkadot-node/">Polkadot</a> is making waves across the Parachain community. On 16th of January, Snowbridge developer– Clara announced on X Platform that their team has deployed&nbsp; Snowbridge successfully on Rococo public testnet. Hence, users can test the usability of the bridge by performing <a href="https://www.zeeve.io/blog/what-are-cross-chain-bridges-a-detailed-guide/">cross-chain</a> transfer of tokens back and forth from Ethereum Sepolia to AssetHub Rococo.&nbsp;</p>
<p>Snowbridge is a general-purpose, fully decentralized, and trustless bridge between <a href="https://www.zeeve.io/blockchain-protocols/deploy-polkadot-node/">Polkadot</a> and <a href="https://www.zeeve.io/blockchain-protocols/deploy-ethereum-blockchain/">Ethereum</a> designed for enabling cross-chain asset transfer and compatibility.&nbsp; Further, Snowbridge eventually aims to be a common-good bridge launched on BridgeHub Parachain.&nbsp;</p>
<h4>Components upholding Snowbridge:</h4>
<p><strong>BridgeHub</strong></p>
<p>The Parity team, in alliance with Web3 Foundation and Snowfork has launched their common-good BridgeHub on <a href="https://www.zeeve.io/blockchain-protocols/deploy-kusama-node/">Kusama</a>. This bridge hub hosts several bridges between other chains, including <a href="https://www.zeeve.io/blockchain-protocols/deploy-ethereum-blockchain/">Ethereum</a> &amp; Kusama. Bridge hub implements multiple unique pallets to be able to work and allow cross-chain asset transfer, which are:</p>
<ul><!-- wp:list-item -->
<li><strong>InboundQueue-</strong> Pallet designed for accepting all the inbound messages from the <a href="https://www.zeeve.io/blockchain-protocols/deploy-ethereum-blockchain/">Ethereum blockchain</a>.</li>
<!-- /wp:list-item -->

<!-- wp:list-item -->
<li><strong>OutboundQueue</strong>- Pallet designed for accepting all the outbound messages to the Ethereum blockchain.</li>
<!-- /wp:list-item -->

<!-- wp:list-item -->
<li><strong>EthereumBeaconClient-</strong> This pallet works with a Light Client that is responsible for tracking Ethereum’s Beacon chain and verifying all the inbound messages submitted on InboundQueue pallet.</li>
<!-- /wp:list-item -->

<!-- wp:list-item -->
<li><strong>System</strong>- Pallet that takes overall responsibility of the bridge, plus it provides basic system functionality to ensure its seamless operation.</li>
<!-- /wp:list-item --></ul>
<h4>Ethereum-side components</h4>
<p><strong>Gateway- </strong>The <a href="https://www.zeeve.io/blockchain-protocols/deploy-ethereum-blockchain/">Ethereum</a>-side of the bridge hub is organized with a central gateway which is responsible for receiving, verification, and dispatch of inbound Polkadot’s messages. Plus, it accepts outbound messages to deliver to Polkadot as well as implement high–level features; e.g. token transfer.</p>
<p><strong>Agent- </strong>&nbsp;Agent contract’s instances work as proxies for the consensus systems of <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Polkadot</a>. Developers can initiate creation of agents in a permissionless way by calling the extrinsic: <em>EthereumSystem::create_agent</em> on the Parachain’s BridgeHub.</p>
<p><strong>BeefyClient- </strong>Verifies Polkadot Consensus by implementing a light client.&nbsp;</p>
<h3>6. Kusama Bridge:</h3>
<p>Last but very important <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Polkaot Parachain</a> development in 2024 is the upcoming Kusama→Polkadot bridge. Since the start, Kusama has been optimized to receive messages from non-Parachain or external chains using Substrate pallets. This same <a href="https://www.zeeve.io/appchains/substrate-chains/">Substrate</a> instance will be utilized in the <a href="https://www.zeeve.io/blockchain-protocols/deploy-kusama-node/">Kusama</a> to Polkadot bridge, which will be implemented either as a system-level Pararchain or as the community-operated Parachains.</p>
<p>Based on the most recent update, the Kusama bridge is live and is bridging Rococo &lt;&gt; Westend testnets. The bridge is deployed on the Rococo Bridge Hub and Westend Bridge Hub chains, and is configured to bridge XCM messages between Rococo Asset Hub and Westend Asset Hub. This means you can use XCM to transfer ROC and WND tokens across both chains seamlessly.</p>
<p>With these same capabilities, the bridge will be deployed on <a href="https://www.zeeve.io/blockchain-protocols/deploy-polkadot-node/">Polkadot</a> and <a href="https://www.zeeve.io/blockchain-protocols/deploy-kusama-node/">Kusama</a> as soon as the on-chain runtimes get upgraded to release Runtimes 1.1.2. The estimate for the bridge being live is within the first half of March, 2024 (as confirmed by Polkadot’s officials).</p>
<p>Apart from these six major developments, Polkadot is expecting a few more upgrades in 2024 and beyond. This may include expansion of XCM and DAO primitives, multi-asset sub-treasuries, an innovative consensus for block production– Sassafras, and a different recent RFC, known as CoreJam.&nbsp;</p>

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7ifw411oing6p6o4jhf2.png)
<h2>Launch your own Parachains with Zeeve’s Open-source tools, Low-code tools in minutes</h2>
<p><a href="https://www.zeeve.io/">Zeeve</a> is committed to simplifying blockchain deployment for everyone. For <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachains</a>, <a href="https://www.zeeve.io/rollups/">Zeeve Rollups-as-a-service (RaaS)</a> stack mainly offers two open-source tools— Wrench and Larch, complete with an abstraction layer over the complex method of testing and <a href="https://www.zeeve.io/appchains/polkadot-parachains/">deploying custom Parachains</a>.</p>
<p>Wrench is an intuitive and easy-to-use tool designed to launch a production-grade Parachain on the rococo-local. Wrench offers a comprehensive toolkit for setting up all kinds of <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Parachains</a>– be it a multi-node, managed, or distributed Parachain Testnet, integrated with analytics, monitoring capabilities, and real-time alerts.</p>
<p><a href="https://www.zeeve.io/blog/zeeves-larch-polkadot-substrate-zombienet-automation-and-monitoring-with-an-intuitive-gui-tool"><strong>Larch</strong></a><strong> </strong>is focused on Parachain testing. It’s an innovative GUI frontend that automates the creation, management, and testing approach of the <a href="https://www.zeeve.io/blog/testing-a-polkadot-parachain-with-zombienet">Zombienet</a>. Using Larch’s comprehensive dashboard, developers can quickly set up relay chains and parachains just in a few clicks, with no need to manually write command lines or create .toml or .yaml files.&nbsp;</p>
<p>For more information about <a href="https://www.zeeve.io/appchains/polkadot-parachains/">Zeeve’s Parachain-related services</a> or Zeeve RaaS, <a href="https://www.zeeve.io/talk-to-an-expert/">connect with our experts</a>. You can simply drop your queries via mail on this page or for a detailed discussion, there’s an option for scheduling one-to-one calls.</p>