mirror of
https://github.com/pezkuwichain/pezkuwi-fellows.git
synced 2026-11-02 00:41:08 +00:00
deploy: ccbe03ed54
This commit is contained in:
bkchr committed
1 parent
5088ae880f
commit
6a71d56ae8
4 files changed
+42
-8
No files matched your search
+20
-3
@@ -868,6 +868,7 @@ Such conversion attempts will explicitly fail.</p>
|
||||
<li><a href="proposed/0103-introduce-core-index-commitment.html#ump-transport">UMP transport</a></li>
|
||||
<li><a href="proposed/0103-introduce-core-index-commitment.html#polkadot-primitive-changes">Polkadot Primitive changes</a></li>
|
||||
<li><a href="proposed/0103-introduce-core-index-commitment.html#parachain-block-validation">Parachain block validation</a></li>
|
||||
<li><a href="proposed/0103-introduce-core-index-commitment.html#on-chain-backing">On-chain backing</a></li>
|
||||
<li><a href="proposed/0103-introduce-core-index-commitment.html#backwards-compatibility">Backwards compatibility</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -1044,13 +1045,29 @@ and rename to <code>reserved1</code> and <code>reserved2</code> fields.</li>
|
||||
additional information in the descriptor.</p>
|
||||
<h3 id="parachain-block-validation"><a class="header" href="#parachain-block-validation">Parachain block validation</a></h3>
|
||||
<p>If the candidate descriptor is version 1, there are no changes.</p>
|
||||
<p>For version 2, backers and the runtime must check the validity of <code>core_index</code> and <code>session_index</code> fields.
|
||||
<p>Backers must check the validity of <code>core_index</code> and <code>session_index</code> fields.
|
||||
A candidate must not be backed if any of the following are true:</p>
|
||||
<ul>
|
||||
<li>the <code>core_index</code> in the descriptor does not match the core the backing group is assigned to</li>
|
||||
<li>the <code>core_index</code> in the descriptor does not match the core the backer is assigned to</li>
|
||||
<li>the <code>session_index</code> is not equal to the session of the <code>relay_parent</code> in the descriptor</li>
|
||||
<li>the <code>core_index</code> in the descriptor does not match the one determined by the <code>UMPSignal::SelectCore</code> message</li>
|
||||
<li>the <code>core_index</code> in the descriptor does not match the one determined by the
|
||||
<code>UMPSignal::SelectCore</code> message</li>
|
||||
</ul>
|
||||
<h3 id="on-chain-backing"><a class="header" href="#on-chain-backing">On-chain backing</a></h3>
|
||||
<p>If the candidate descriptor is version 1, there are no changes.</p>
|
||||
<p>For version 2 descriptors the runtime will determine the <code>core_index</code> similarly to backers but
|
||||
will always ignore the committed claim queue offset and use <code>0</code>, as it only cares
|
||||
about what candidates can be backed at current block. </p>
|
||||
<p>As the chain advances the claims also advance to the top of the queue. The runtime will only back<br />
|
||||
a candidate if the claimed core selected by it's claim queue offset has reached the top of the queue
|
||||
at the current relay chain block: <code>current_block_num - relay_parent_num - 1 == claim_queue_offset</code>.</p>
|
||||
<p>The impact of this change is that candidates built into the future (<code>claim queue offset > 0</code>)
|
||||
can no longer be backed earlier even if the core is free and the core is assigned to the
|
||||
parachain. </p>
|
||||
<p>Introducing this additional check is required to ensure the runtime computes the core index
|
||||
determinstically. For example, some collator has missed his slot and the core is now used
|
||||
to back a candidate with a higher claim queue offset. The number of assigned cores can
|
||||
be different at these two queue offsets and the committed core indices would be different. </p>
|
||||
<h3 id="backwards-compatibility"><a class="header" href="#backwards-compatibility">Backwards compatibility</a></h3>
|
||||
<p>There are two flavors of candidate receipts that are used in network protocols, runtime and node
|
||||
implementation:</p>
|
||||
|
||||
@@ -188,6 +188,7 @@
|
||||
<li><a href="#ump-transport">UMP transport</a></li>
|
||||
<li><a href="#polkadot-primitive-changes">Polkadot Primitive changes</a></li>
|
||||
<li><a href="#parachain-block-validation">Parachain block validation</a></li>
|
||||
<li><a href="#on-chain-backing">On-chain backing</a></li>
|
||||
<li><a href="#backwards-compatibility">Backwards compatibility</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -364,13 +365,29 @@ and rename to <code>reserved1</code> and <code>reserved2</code> fields.</li>
|
||||
additional information in the descriptor.</p>
|
||||
<h3 id="parachain-block-validation"><a class="header" href="#parachain-block-validation">Parachain block validation</a></h3>
|
||||
<p>If the candidate descriptor is version 1, there are no changes.</p>
|
||||
<p>For version 2, backers and the runtime must check the validity of <code>core_index</code> and <code>session_index</code> fields.
|
||||
<p>Backers must check the validity of <code>core_index</code> and <code>session_index</code> fields.
|
||||
A candidate must not be backed if any of the following are true:</p>
|
||||
<ul>
|
||||
<li>the <code>core_index</code> in the descriptor does not match the core the backing group is assigned to</li>
|
||||
<li>the <code>core_index</code> in the descriptor does not match the core the backer is assigned to</li>
|
||||
<li>the <code>session_index</code> is not equal to the session of the <code>relay_parent</code> in the descriptor</li>
|
||||
<li>the <code>core_index</code> in the descriptor does not match the one determined by the <code>UMPSignal::SelectCore</code> message</li>
|
||||
<li>the <code>core_index</code> in the descriptor does not match the one determined by the
|
||||
<code>UMPSignal::SelectCore</code> message</li>
|
||||
</ul>
|
||||
<h3 id="on-chain-backing"><a class="header" href="#on-chain-backing">On-chain backing</a></h3>
|
||||
<p>If the candidate descriptor is version 1, there are no changes.</p>
|
||||
<p>For version 2 descriptors the runtime will determine the <code>core_index</code> similarly to backers but
|
||||
will always ignore the committed claim queue offset and use <code>0</code>, as it only cares
|
||||
about what candidates can be backed at current block. </p>
|
||||
<p>As the chain advances the claims also advance to the top of the queue. The runtime will only back<br />
|
||||
a candidate if the claimed core selected by it's claim queue offset has reached the top of the queue
|
||||
at the current relay chain block: <code>current_block_num - relay_parent_num - 1 == claim_queue_offset</code>.</p>
|
||||
<p>The impact of this change is that candidates built into the future (<code>claim queue offset > 0</code>)
|
||||
can no longer be backed earlier even if the core is free and the core is assigned to the
|
||||
parachain. </p>
|
||||
<p>Introducing this additional check is required to ensure the runtime computes the core index
|
||||
determinstically. For example, some collator has missed his slot and the core is now used
|
||||
to back a candidate with a higher claim queue offset. The number of assigned cores can
|
||||
be different at these two queue offsets and the committed core indices would be different. </p>
|
||||
<h3 id="backwards-compatibility"><a class="header" href="#backwards-compatibility">Backwards compatibility</a></h3>
|
||||
<p>There are two flavors of candidate receipts that are used in network protocols, runtime and node
|
||||
implementation:</p>
|
||||
|
||||
+1
-1
@@ -1 +1 @@
|
||||
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","new/0112-compress-state-response-message-in-state-sync.html#rfc-0112-compress-the-state-response-message-in-state-sync","new/0112-compress-state-response-message-in-state-sync.html#summary","new/0112-compress-state-response-message-in-state-sync.html#motivation","new/0112-compress-state-response-message-in-state-sync.html#stakeholders","new/0112-compress-state-response-message-in-state-sync.html#explanation","new/0112-compress-state-response-message-in-state-sync.html#drawbacks","new/0112-compress-state-response-message-in-state-sync.html#testing-security-and-privacy","new/0112-compress-state-response-message-in-state-sync.html#performance-ergonomics-and-compatibility","new/0112-compress-state-response-message-in-state-sync.html#performance","new/0112-compress-state-response-message-in-state-sync.html#ergonomics","new/0112-compress-state-response-message-in-state-sync.html#compatibility","new/0112-compress-state-response-message-in-state-sync.html#prior-art-and-references","new/0112-compress-state-response-message-in-state-sync.html#unresolved-questions","new/0112-compress-state-response-message-in-state-sync.html#future-directions-and-related-material","new/0114-secp256r1-hostfunction.html#rfc-0114-introduce-secp256r1_ecdsa_verify_prehashed-host-function-to-verify-nist-p256-elliptic-curve-signatures","new/0114-secp256r1-hostfunction.html#summary","new/0114-secp256r1-hostfunction.html#motivation","new/0114-secp256r1-hostfunction.html#stakeholders","new/0114-secp256r1-hostfunction.html#explanation","new/0114-secp256r1-hostfunction.html#drawbacks","new/0114-secp256r1-hostfunction.html#testing-security-and-privacy","new/0114-secp256r1-hostfunction.html#security","new/0114-secp256r1-hostfunction.html#performance-ergonomics-and-compatibility","new/0114-secp256r1-hostfunction.html#performance","new/0114-secp256r1-hostfunction.html#ergonomics","new/0114-secp256r1-hostfunction.html#compatibility","new/0114-secp256r1-hostfunction.html#prior-art-and-references","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#rfc-114-adjust-tipper-track-confirmation-periods","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#summary","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#motivation","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#stakeholders","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#explanation","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#drawbacks","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#testing-security-and-privacy","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#performance-ergonomics-and-compatibility","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#performance","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#ergonomics--compatibility","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#prior-art-and-references","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#unresolved-questions","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#future-directions-and-related-material","proposed/00xx-smart-contracts-coretime-chain.html#rfc-0002-smart-contracts-on-the-coretime-chain","proposed/00xx-smart-contracts-coretime-chain.html#summary","proposed/00xx-smart-contracts-coretime-chain.html#motivation","proposed/00xx-smart-contracts-coretime-chain.html#stakeholders","proposed/00xx-smart-contracts-coretime-chain.html#explanation","proposed/00xx-smart-contracts-coretime-chain.html#drawbacks","proposed/00xx-smart-contracts-coretime-chain.html#testing-security-and-privacy","proposed/00xx-smart-contracts-coretime-chain.html#testing","proposed/00xx-smart-contracts-coretime-chain.html#security","proposed/00xx-smart-contracts-coretime-chain.html#privacy","proposed/00xx-smart-contracts-coretime-chain.html#performance-ergonomics-and-compatibility","proposed/00xx-smart-contracts-coretime-chain.html#performance","proposed/00xx-smart-contracts-coretime-chain.html#ergonomics","proposed/00xx-smart-contracts-coretime-chain.html#compatibility","proposed/00xx-smart-contracts-coretime-chain.html#prior-art-and-references","proposed/00xx-smart-contracts-coretime-chain.html#unresolved-questions","proposed/00xx-smart-contracts-coretime-chain.html#future-directions-and-related-material","proposed/0100-xcm-multi-type-asset-transfer.html#rfc-0100-new-xcm-instruction-initiateassetstransfer","proposed/0100-xcm-multi-type-asset-transfer.html#summary","proposed/0100-xcm-multi-type-asset-transfer.html#motivation","proposed/0100-xcm-multi-type-asset-transfer.html#stakeholders","proposed/0100-xcm-multi-type-asset-transfer.html#explanation","proposed/0100-xcm-multi-type-asset-transfer.html#example-usage-transferring-2-different-asset-types-across-3-chains","proposed/0100-xcm-multi-type-asset-transfer.html#drawbacks","proposed/0100-xcm-multi-type-asset-transfer.html#testing-security-and-privacy","proposed/0100-xcm-multi-type-asset-transfer.htmlLine truncated
|
||||
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","new/0112-compress-state-response-message-in-state-sync.html#rfc-0112-compress-the-state-response-message-in-state-sync","new/0112-compress-state-response-message-in-state-sync.html#summary","new/0112-compress-state-response-message-in-state-sync.html#motivation","new/0112-compress-state-response-message-in-state-sync.html#stakeholders","new/0112-compress-state-response-message-in-state-sync.html#explanation","new/0112-compress-state-response-message-in-state-sync.html#drawbacks","new/0112-compress-state-response-message-in-state-sync.html#testing-security-and-privacy","new/0112-compress-state-response-message-in-state-sync.html#performance-ergonomics-and-compatibility","new/0112-compress-state-response-message-in-state-sync.html#performance","new/0112-compress-state-response-message-in-state-sync.html#ergonomics","new/0112-compress-state-response-message-in-state-sync.html#compatibility","new/0112-compress-state-response-message-in-state-sync.html#prior-art-and-references","new/0112-compress-state-response-message-in-state-sync.html#unresolved-questions","new/0112-compress-state-response-message-in-state-sync.html#future-directions-and-related-material","new/0114-secp256r1-hostfunction.html#rfc-0114-introduce-secp256r1_ecdsa_verify_prehashed-host-function-to-verify-nist-p256-elliptic-curve-signatures","new/0114-secp256r1-hostfunction.html#summary","new/0114-secp256r1-hostfunction.html#motivation","new/0114-secp256r1-hostfunction.html#stakeholders","new/0114-secp256r1-hostfunction.html#explanation","new/0114-secp256r1-hostfunction.html#drawbacks","new/0114-secp256r1-hostfunction.html#testing-security-and-privacy","new/0114-secp256r1-hostfunction.html#security","new/0114-secp256r1-hostfunction.html#performance-ergonomics-and-compatibility","new/0114-secp256r1-hostfunction.html#performance","new/0114-secp256r1-hostfunction.html#ergonomics","new/0114-secp256r1-hostfunction.html#compatibility","new/0114-secp256r1-hostfunction.html#prior-art-and-references","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#rfc-114-adjust-tipper-track-confirmation-periods","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#summary","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#motivation","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#stakeholders","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#explanation","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#drawbacks","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#testing-security-and-privacy","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#performance-ergonomics-and-compatibility","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#performance","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#ergonomics--compatibility","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#prior-art-and-references","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#unresolved-questions","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#future-directions-and-related-material","proposed/00xx-smart-contracts-coretime-chain.html#rfc-0002-smart-contracts-on-the-coretime-chain","proposed/00xx-smart-contracts-coretime-chain.html#summary","proposed/00xx-smart-contracts-coretime-chain.html#motivation","proposed/00xx-smart-contracts-coretime-chain.html#stakeholders","proposed/00xx-smart-contracts-coretime-chain.html#explanation","proposed/00xx-smart-contracts-coretime-chain.html#drawbacks","proposed/00xx-smart-contracts-coretime-chain.html#testing-security-and-privacy","proposed/00xx-smart-contracts-coretime-chain.html#testing","proposed/00xx-smart-contracts-coretime-chain.html#security","proposed/00xx-smart-contracts-coretime-chain.html#privacy","proposed/00xx-smart-contracts-coretime-chain.html#performance-ergonomics-and-compatibility","proposed/00xx-smart-contracts-coretime-chain.html#performance","proposed/00xx-smart-contracts-coretime-chain.html#ergonomics","proposed/00xx-smart-contracts-coretime-chain.html#compatibility","proposed/00xx-smart-contracts-coretime-chain.html#prior-art-and-references","proposed/00xx-smart-contracts-coretime-chain.html#unresolved-questions","proposed/00xx-smart-contracts-coretime-chain.html#future-directions-and-related-material","proposed/0100-xcm-multi-type-asset-transfer.html#rfc-0100-new-xcm-instruction-initiateassetstransfer","proposed/0100-xcm-multi-type-asset-transfer.html#summary","proposed/0100-xcm-multi-type-asset-transfer.html#motivation","proposed/0100-xcm-multi-type-asset-transfer.html#stakeholders","proposed/0100-xcm-multi-type-asset-transfer.html#explanation","proposed/0100-xcm-multi-type-asset-transfer.html#example-usage-transferring-2-different-asset-types-across-3-chains","proposed/0100-xcm-multi-type-asset-transfer.html#drawbacks","proposed/0100-xcm-multi-type-asset-transfer.html#testing-security-and-privacy","proposed/0100-xcm-multi-type-asset-transfer.htmlLine truncated
|
||||
+1
-1
@@ -1 +1 @@
|
||||
{"doc_urls":["introduction.html#introduction","new/0112-compress-state-response-message-in-state-sync.html#rfc-0112-compress-the-state-response-message-in-state-sync","new/0112-compress-state-response-message-in-state-sync.html#summary","new/0112-compress-state-response-message-in-state-sync.html#motivation","new/0112-compress-state-response-message-in-state-sync.html#stakeholders","new/0112-compress-state-response-message-in-state-sync.html#explanation","new/0112-compress-state-response-message-in-state-sync.html#drawbacks","new/0112-compress-state-response-message-in-state-sync.html#testing-security-and-privacy","new/0112-compress-state-response-message-in-state-sync.html#performance-ergonomics-and-compatibility","new/0112-compress-state-response-message-in-state-sync.html#performance","new/0112-compress-state-response-message-in-state-sync.html#ergonomics","new/0112-compress-state-response-message-in-state-sync.html#compatibility","new/0112-compress-state-response-message-in-state-sync.html#prior-art-and-references","new/0112-compress-state-response-message-in-state-sync.html#unresolved-questions","new/0112-compress-state-response-message-in-state-sync.html#future-directions-and-related-material","new/0114-secp256r1-hostfunction.html#rfc-0114-introduce-secp256r1_ecdsa_verify_prehashed-host-function-to-verify-nist-p256-elliptic-curve-signatures","new/0114-secp256r1-hostfunction.html#summary","new/0114-secp256r1-hostfunction.html#motivation","new/0114-secp256r1-hostfunction.html#stakeholders","new/0114-secp256r1-hostfunction.html#explanation","new/0114-secp256r1-hostfunction.html#drawbacks","new/0114-secp256r1-hostfunction.html#testing-security-and-privacy","new/0114-secp256r1-hostfunction.html#security","new/0114-secp256r1-hostfunction.html#performance-ergonomics-and-compatibility","new/0114-secp256r1-hostfunction.html#performance","new/0114-secp256r1-hostfunction.html#ergonomics","new/0114-secp256r1-hostfunction.html#compatibility","new/0114-secp256r1-hostfunction.html#prior-art-and-references","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#rfc-114-adjust-tipper-track-confirmation-periods","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#summary","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#motivation","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#stakeholders","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#explanation","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#drawbacks","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#testing-security-and-privacy","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#performance-ergonomics-and-compatibility","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#performance","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#ergonomics--compatibility","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#prior-art-and-references","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#unresolved-questions","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#future-directions-and-related-material","proposed/00xx-smart-contracts-coretime-chain.html#rfc-0002-smart-contracts-on-the-coretime-chain","proposed/00xx-smart-contracts-coretime-chain.html#summary","proposed/00xx-smart-contracts-coretime-chain.html#motivation","proposed/00xx-smart-contracts-coretime-chain.html#stakeholders","proposed/00xx-smart-contracts-coretime-chain.html#explanation","proposed/00xx-smart-contracts-coretime-chain.html#drawbacks","proposed/00xx-smart-contracts-coretime-chain.html#testing-security-and-privacy","proposed/00xx-smart-contracts-coretime-chain.html#testing","proposed/00xx-smart-contracts-coretime-chain.html#security","proposed/00xx-smart-contracts-coretime-chain.html#privacy","proposed/00xx-smart-contracts-coretime-chain.html#performance-ergonomics-and-compatibility","proposed/00xx-smart-contracts-coretime-chain.html#performance","proposed/00xx-smart-contracts-coretime-chain.html#ergonomics","proposed/00xx-smart-contracts-coretime-chain.html#compatibility","proposed/00xx-smart-contracts-coretime-chain.html#prior-art-and-references","proposed/00xx-smart-contracts-coretime-chain.html#unresolved-questions","proposed/00xx-smart-contracts-coretime-chain.html#future-directions-and-related-material","proposed/0100-xcm-multi-type-asset-transfer.html#rfc-0100-new-xcm-instruction-initiateassetstransfer","proposed/0100-xcm-multi-type-asset-transfer.html#summary","proposed/0100-xcm-multi-type-asset-transfer.html#motivation","proposed/0100-xcm-multi-type-asset-transfer.html#stakeholders","proposed/0100-xcm-multi-type-asset-transfer.html#explanation","proposed/0100-xcm-multi-type-asset-transfer.html#example-usage-transferring-2-different-asset-types-across-3-chains","proposed/0100-xcm-multi-type-asset-transfer.html#drawbacks","proposed/0100-xcm-multi-type-asset-transfer.html#testing-security-and-privacy","proposed/0100-xcm-multi-type-asset-transfer.html#performance-ergonomics-and-cLine truncated
|
||||
{"doc_urls":["introduction.html#introduction","new/0112-compress-state-response-message-in-state-sync.html#rfc-0112-compress-the-state-response-message-in-state-sync","new/0112-compress-state-response-message-in-state-sync.html#summary","new/0112-compress-state-response-message-in-state-sync.html#motivation","new/0112-compress-state-response-message-in-state-sync.html#stakeholders","new/0112-compress-state-response-message-in-state-sync.html#explanation","new/0112-compress-state-response-message-in-state-sync.html#drawbacks","new/0112-compress-state-response-message-in-state-sync.html#testing-security-and-privacy","new/0112-compress-state-response-message-in-state-sync.html#performance-ergonomics-and-compatibility","new/0112-compress-state-response-message-in-state-sync.html#performance","new/0112-compress-state-response-message-in-state-sync.html#ergonomics","new/0112-compress-state-response-message-in-state-sync.html#compatibility","new/0112-compress-state-response-message-in-state-sync.html#prior-art-and-references","new/0112-compress-state-response-message-in-state-sync.html#unresolved-questions","new/0112-compress-state-response-message-in-state-sync.html#future-directions-and-related-material","new/0114-secp256r1-hostfunction.html#rfc-0114-introduce-secp256r1_ecdsa_verify_prehashed-host-function-to-verify-nist-p256-elliptic-curve-signatures","new/0114-secp256r1-hostfunction.html#summary","new/0114-secp256r1-hostfunction.html#motivation","new/0114-secp256r1-hostfunction.html#stakeholders","new/0114-secp256r1-hostfunction.html#explanation","new/0114-secp256r1-hostfunction.html#drawbacks","new/0114-secp256r1-hostfunction.html#testing-security-and-privacy","new/0114-secp256r1-hostfunction.html#security","new/0114-secp256r1-hostfunction.html#performance-ergonomics-and-compatibility","new/0114-secp256r1-hostfunction.html#performance","new/0114-secp256r1-hostfunction.html#ergonomics","new/0114-secp256r1-hostfunction.html#compatibility","new/0114-secp256r1-hostfunction.html#prior-art-and-references","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#rfc-114-adjust-tipper-track-confirmation-periods","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#summary","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#motivation","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#stakeholders","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#explanation","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#drawbacks","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#testing-security-and-privacy","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#performance-ergonomics-and-compatibility","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#performance","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#ergonomics--compatibility","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#prior-art-and-references","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#unresolved-questions","new/RFC-114 Adjust Tipper Track Confirmation Periods.html#future-directions-and-related-material","proposed/00xx-smart-contracts-coretime-chain.html#rfc-0002-smart-contracts-on-the-coretime-chain","proposed/00xx-smart-contracts-coretime-chain.html#summary","proposed/00xx-smart-contracts-coretime-chain.html#motivation","proposed/00xx-smart-contracts-coretime-chain.html#stakeholders","proposed/00xx-smart-contracts-coretime-chain.html#explanation","proposed/00xx-smart-contracts-coretime-chain.html#drawbacks","proposed/00xx-smart-contracts-coretime-chain.html#testing-security-and-privacy","proposed/00xx-smart-contracts-coretime-chain.html#testing","proposed/00xx-smart-contracts-coretime-chain.html#security","proposed/00xx-smart-contracts-coretime-chain.html#privacy","proposed/00xx-smart-contracts-coretime-chain.html#performance-ergonomics-and-compatibility","proposed/00xx-smart-contracts-coretime-chain.html#performance","proposed/00xx-smart-contracts-coretime-chain.html#ergonomics","proposed/00xx-smart-contracts-coretime-chain.html#compatibility","proposed/00xx-smart-contracts-coretime-chain.html#prior-art-and-references","proposed/00xx-smart-contracts-coretime-chain.html#unresolved-questions","proposed/00xx-smart-contracts-coretime-chain.html#future-directions-and-related-material","proposed/0100-xcm-multi-type-asset-transfer.html#rfc-0100-new-xcm-instruction-initiateassetstransfer","proposed/0100-xcm-multi-type-asset-transfer.html#summary","proposed/0100-xcm-multi-type-asset-transfer.html#motivation","proposed/0100-xcm-multi-type-asset-transfer.html#stakeholders","proposed/0100-xcm-multi-type-asset-transfer.html#explanation","proposed/0100-xcm-multi-type-asset-transfer.html#example-usage-transferring-2-different-asset-types-across-3-chains","proposed/0100-xcm-multi-type-asset-transfer.html#drawbacks","proposed/0100-xcm-multi-type-asset-transfer.html#testing-security-and-privacy","proposed/0100-xcm-multi-type-asset-transfer.html#performance-ergonomics-and-cLine truncated
|
||||
Reference in new issue
Block a user