An article to understand the Polkadot parallel thread: "pay as you use" parachain
PolkaWorld
2020-08-18 07:02
本文约1898字,阅读全文需要约8分钟
A way to access Polkadot with a lower threshold.

Editor's Note: This article comes fromPolkaWorld(ID:gh_6c4c2038ddba), reproduced by Odaily with authorization.

Editor's Note: This article comes from

), reproduced by Odaily with authorization.

Dedicated parachain slots provide high throughput but require a relatively large security deposit of up to two years. So why do you need to do this? Because shared security is not free security, parachains are the link between this security and the throughput of Polkadot. Parathreads have exactly the same API and functions as parachains, but are based on a "pay-as-you-go" approach.

If you imagine Polkadot as a huge computer, parachains are like applications in physical memory and are highly available. Parathreads are like applications on disk, which can be copied into memory when needed. For those already familiar with how bitcoin and ethereum work, users bid to include a parathread block into the relay chain, similar to how users bid to include transactions in bitcoin or ethereum blocks.

secondary title

  • pthread application

  • Parathreads are suitable for the following three applications:

  • Applications seeking access to Polkadot

Applications concerned about losing parachain slot bits

Applications that read more than write

For some applications, it makes more sense to be a parathread than a parachain. That is, those applications that do not have frequent state updates. Take domain name services as an example. The number of read requests is high, but updating the registry every hour is normal. DNS does not require Polkadot's six-second block time. Oracles are also good candidates for parathreading, such as daily weather or Bitcoin block oracles.

Parathread Economics

secondary title

Parathread Economics

In each relay chain block, a parathread will issue its willingness to execute a block by participating in an auction. The parathread collator will tell the validators assigned to the pool how many DOTs they are willing to pay to execute and complete their blocks. The pay-per-block model differs from parachains, which have the right to execute one block per relay chain block through their dedicated slots.

Parathreads can fund block execution in a number of ways. For example, they could raise funds and have a DOT account for their chain, and let collators use that account to finalize blocks when needed. Alternatively, parathreads can have an inflation model that gives collators more native tokens while the relay chain is running. Once the value of the native token exceeds the value of the DOT required to win the auction, the collator will accept the block reward.

secondary title

Polkadot allocation

Parathreads are a powerful complement to Polkadot. Since parathreads have the same interface as parachains, they are all protected by Polkadot shared security and can send and receive messages via XCMP.

Polkadot will be able to support around 100 parachains. Parallel threads allow applications to share parachain slots, increasing the number of applications that can run on Polkadot. This will allow more infrastructure chains to exist and improve composability.

One of the set of parachains will be the system level chain. One of our goals with Polkadot is to have a relay chain with no transactions. The proof of validity is the only information that enters the relay chain block. This means there will be a parachain for DOT transfers, one for governance, one for staking, one for smart contracts, etc.

Another set of parachains will be applications that lease dedicated parachain slots. These will be heavily used chains like decentralized exchanges or stablecoin chains. For these chains, bonding to fully utilize the Relay Chain can be more economical than paying per block.

The third category will be parathreads, which are most applications that need Polkadot's security and connectivity, but not the full throughput.https://substrate.dev/

Parathreads are an important step towards making Polkadot more accessible and optimizing the resources available on the relay chain. With Polkadot such a strong entry-level capability, any team can start developing applications, prepare for Polkadot's launch, and confidently believe that they can connect to the relay chain and fully benefit from interoperability.

https://wiki.polkadot.network/

PolkaWorld
作者文库