pezkuwichain/pezkuwi-fellows
1
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-fellows.git synced 2026-10-30 07:29:51 +00:00
Code Releases Activity

deploy: db260ea2f9

Browse Source
This commit is contained in:
bkchr committed 2024-09-04 01:01:22 +00:00
1 parent b637db84e6
commit cbc0975f9f
4 files changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

print.html
+1 -1
View File
@@ -415,7 +415,7 @@ remains unchanged as we will store scale encoded <code>UMPSignal</code> messages
UMP queue by outputting them in <a href="https://github.com/paritytech/polkadot-sdk/blob/b5029eb4fd6c7ffd8164b2fe12b71bad0c59c9f2/polkadot/primitives/src/v7/mod.rs#L684">upward_messages</a>.</p>
<p>The UMP queue layout is changed to allow the relay chain to receive both the XCM messages and
<code>UMPSignal</code> messages. An empty message (empty <code>Vec&lt;u8&gt;</code>) is used to mark the end of XCM messages and
the start of <code>UMPSignal</code> messages.The <code>UMPSignal</code> is optional and can be omitted by parachains
the start of <code>UMPSignal</code> messages. The <code>UMPSignal</code> is optional and can be omitted by parachains
not using elastic scaling.</p>
<p>This way of representing the new messages has been chosen over introducing an enum wrapper to
minimize breaking changes of XCM message decoding in tools like Subscan for example.</p>
proposed/0103-introduce-core-index-commitment.html
+1 -1
View File
@@ -267,7 +267,7 @@ remains unchanged as we will store scale encoded <code>UMPSignal</code> messages
UMP queue by outputting them in <a href="https://github.com/paritytech/polkadot-sdk/blob/b5029eb4fd6c7ffd8164b2fe12b71bad0c59c9f2/polkadot/primitives/src/v7/mod.rs#L684">upward_messages</a>.</p>
<p>The UMP queue layout is changed to allow the relay chain to receive both the XCM messages and
<code>UMPSignal</code> messages. An empty message (empty <code>Vec&lt;u8&gt;</code>) is used to mark the end of XCM messages and
the start of <code>UMPSignal</code> messages.The <code>UMPSignal</code> is optional and can be omitted by parachains
the start of <code>UMPSignal</code> messages. The <code>UMPSignal</code> is optional and can be omitted by parachains
not using elastic scaling.</p>
<p>This way of representing the new messages has been chosen over introducing an enum wrapper to
minimize breaking changes of XCM message decoding in tools like Subscan for example.</p>
searchindex.js
+1 -1
View File
@@ -1 +1 @@
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","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/0103-introduce-core-index-commitment.html#rfc-0103--introduce-a-coreindex-commitment-and-a-sessionindex-field-in-candidate-receipts","proposed/0103-introduce-core-index-commitment.html#summary","proposed/0103-introduce-core-index-commitment.html#motivation","proposed/0103-introduce-core-index-commitment.html#stakeholders","proposed/0103-introduce-core-index-commitment.html#explanation","proposed/0103-introduce-core-index-commitment.html#reclaiming-unused-space-in-the-descriptor","proposed/0103-introduce-core-index-commitment.html#ump-transport","proposed/0103-introduce-core-index-commitment.html#polkadot-primitive-changes","proposed/0103-introduce-core-index-commitment.html#backwards-compatibility","proposed/0103-introduce-core-index-commitment.html#parachain-block-validation","proposed/0103-introduce-core-index-commitment.html#on-chain-backing","proposed/0103-introduce-core-index-commitment.html#drawbacks","proposed/0103-introduce-core-index-commitment.html#testing-security-and-privacy","proposed/0103-introduce-core-index-commitment.html#performance","proposed/0103-introduce-core-index-commitment.html#ergonomics","proposed/0103-introduce-core-index-commitment.html#compatibility","proposed/0103-introduce-core-index-commitment.html#relay-chain-runtime","proposed/0103-introduce-core-index-commitment.html#validators","proposed/0103-introduce-core-index-commitment.html#tooling","proposed/0103-introduce-core-index-commitment.html#prior-art-and-references","proposed/0103-introduce-core-index-commitment.html#unresolved-questions","proposed/0103-introduce-core-index-commitment.html#future-directions-and-related-material","proposed/0111-pure-proxy-replication.html#rfc-0111-pure-proxy-replication","proposed/0111-pure-proxy-replication.html#summary","proposed/0111-pure-proxy-replication.html#motivation","proposed/0111-pure-proxy-replication.html#stakeholders","proposed/0111-pure-proxy-replication.html#explanation","proposed/0111-pure-proxy-replication.html#drawbacks","proposed/0111-pure-proxy-replication.html#testing-security-and-privacy","proposed/0111-pure-proxy-replication.html#performance-ergonomics-and-compatibility","proposed/0111-pure-proxy-replication.html#performance","proposed/0111-pure-proxy-replication.html#ergonomics","proposed/0111-pure-proxy-replication.html#compatibility","proposed/0111-pure-proxy-replication.html#prior-art-and-references","proposed/0111-pure-proxy-replication.html#unresolved-questions","proposed/0111-pure-proxy-replication.html#future-directions-and-related-material","proposed/0112-compress-state-response-message-in-state-sync.html#rfc-0112-compress-the-state-response-message-in-state-sync","proposed/0112-compress-state-response-message-in-state-sync.html#summary","proposed/0112-compress-state-response-message-in-state-sync.html#motivation","proposed/0112-compress-state-response-message-in-state-sync.html#stakeholders","proposed/0112-compress-state-response-message-in-state-sync.html#explanation","proposed/0112-compress-state-response-message-in-state-sync.html#drawbacks","proposed/0112-compress-state-response-message-in-state-sync.html#testing-security-and-privacy","proposed/0112-compress-state-response-message-in-state-sync.html#performance-ergonomics-and-compatibility","proposed/0112-compress-state-response-message-in-state-sync.html#performance","proposed/0112-compress-state-response-message-in-state-sync.html#ergonomics","proposed/0112-compress-state-response-message-in-state-sync.html#compatibility","proposed/0112-compress-state-response-message-in-state-sync.html#prior-art-and-references","proposed/0112-compress-state-response-message-in-state-sync.html#unresolved-questions","proposed/0112-compress-state-response-mLine truncated
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","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/0103-introduce-core-index-commitment.html#rfc-0103--introduce-a-coreindex-commitment-and-a-sessionindex-field-in-candidate-receipts","proposed/0103-introduce-core-index-commitment.html#summary","proposed/0103-introduce-core-index-commitment.html#motivation","proposed/0103-introduce-core-index-commitment.html#stakeholders","proposed/0103-introduce-core-index-commitment.html#explanation","proposed/0103-introduce-core-index-commitment.html#reclaiming-unused-space-in-the-descriptor","proposed/0103-introduce-core-index-commitment.html#ump-transport","proposed/0103-introduce-core-index-commitment.html#polkadot-primitive-changes","proposed/0103-introduce-core-index-commitment.html#backwards-compatibility","proposed/0103-introduce-core-index-commitment.html#parachain-block-validation","proposed/0103-introduce-core-index-commitment.html#on-chain-backing","proposed/0103-introduce-core-index-commitment.html#drawbacks","proposed/0103-introduce-core-index-commitment.html#testing-security-and-privacy","proposed/0103-introduce-core-index-commitment.html#performance","proposed/0103-introduce-core-index-commitment.html#ergonomics","proposed/0103-introduce-core-index-commitment.html#compatibility","proposed/0103-introduce-core-index-commitment.html#relay-chain-runtime","proposed/0103-introduce-core-index-commitment.html#validators","proposed/0103-introduce-core-index-commitment.html#tooling","proposed/0103-introduce-core-index-commitment.html#prior-art-and-references","proposed/0103-introduce-core-index-commitment.html#unresolved-questions","proposed/0103-introduce-core-index-commitment.html#future-directions-and-related-material","proposed/0111-pure-proxy-replication.html#rfc-0111-pure-proxy-replication","proposed/0111-pure-proxy-replication.html#summary","proposed/0111-pure-proxy-replication.html#motivation","proposed/0111-pure-proxy-replication.html#stakeholders","proposed/0111-pure-proxy-replication.html#explanation","proposed/0111-pure-proxy-replication.html#drawbacks","proposed/0111-pure-proxy-replication.html#testing-security-and-privacy","proposed/0111-pure-proxy-replication.html#performance-ergonomics-and-compatibility","proposed/0111-pure-proxy-replication.html#performance","proposed/0111-pure-proxy-replication.html#ergonomics","proposed/0111-pure-proxy-replication.html#compatibility","proposed/0111-pure-proxy-replication.html#prior-art-and-references","proposed/0111-pure-proxy-replication.html#unresolved-questions","proposed/0111-pure-proxy-replication.html#future-directions-and-related-material","proposed/0112-compress-state-response-message-in-state-sync.html#rfc-0112-compress-the-state-response-message-in-state-sync","proposed/0112-compress-state-response-message-in-state-sync.html#summary","proposed/0112-compress-state-response-message-in-state-sync.html#motivation","proposed/0112-compress-state-response-message-in-state-sync.html#stakeholders","proposed/0112-compress-state-response-message-in-state-sync.html#explanation","proposed/0112-compress-state-response-message-in-state-sync.html#drawbacks","proposed/0112-compress-state-response-message-in-state-sync.html#testing-security-and-privacy","proposed/0112-compress-state-response-message-in-state-sync.html#performance-ergonomics-and-compatibility","proposed/0112-compress-state-response-message-in-state-sync.html#performance","proposed/0112-compress-state-response-message-in-state-sync.html#ergonomics","proposed/0112-compress-state-response-message-in-state-sync.html#compatibility","proposed/0112-compress-state-response-message-in-state-sync.html#prior-art-and-references","proposed/0112-compress-state-response-message-in-state-sync.html#unresolved-questions","proposed/0112-compress-state-response-mLine truncated
searchindex.json
+1 -1
View File
@@ -1 +1 @@
{"doc_urls":["introduction.html#introduction","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/0103-introduce-core-index-commitment.html#rfc-0103--introduce-a-coreindex-commitment-and-a-sessionindex-field-in-candidate-receipts","proposed/0103-introduce-core-index-commitment.html#summary","proposed/0103-introduce-core-index-commitment.html#motivation","proposed/0103-introduce-core-index-commitment.html#stakeholders","proposed/0103-introduce-core-index-commitment.html#explanation","proposed/0103-introduce-core-index-commitment.html#reclaiming-unused-space-in-the-descriptor","proposed/0103-introduce-core-index-commitment.html#ump-transport","proposed/0103-introduce-core-index-commitment.html#polkadot-primitive-changes","proposed/0103-introduce-core-index-commitment.html#backwards-compatibility","proposed/0103-introduce-core-index-commitment.html#parachain-block-validation","proposed/0103-introduce-core-index-commitment.html#on-chain-backing","proposed/0103-introduce-core-index-commitment.html#drawbacks","proposed/0103-introduce-core-index-commitment.html#testing-security-and-privacy","proposed/0103-introduce-core-index-commitment.html#performance","proposed/0103-introduce-core-index-commitment.html#ergonomics","proposed/0103-introduce-core-index-commitment.html#compatibility","proposed/0103-introduce-core-index-commitment.html#relay-chain-runtime","proposed/0103-introduce-core-index-commitment.html#validators","proposed/0103-introduce-core-index-commitment.html#tooling","proposed/0103-introduce-core-index-commitment.html#prior-art-and-references","proposed/0103-introduce-core-index-commitment.html#unresolved-questions","proposed/0103-introduce-core-index-commitment.html#future-directions-and-related-material","proposed/0111-pure-proxy-replication.html#rfc-0111-pure-proxy-replication","proposed/0111-pure-proxy-replication.html#summary","proposed/0111-pure-proxy-replication.html#motivation","proposed/0111-pure-proxy-replication.html#stakeholders","proposed/0111-pure-proxy-replication.html#explanation","proposed/0111-pure-proxy-replication.html#drawbacks","proposed/0111-pure-proxy-replication.html#testing-security-and-privacy","proposed/0111-pure-proxy-replication.html#performance-ergonomics-and-compatibility","proposed/0111-pure-proxy-replication.html#performance","proposed/0111-pure-proxy-replication.html#ergonomics","proposed/0111-pure-proxy-replication.html#compatibility","proposed/0111-pure-proxy-replication.html#prior-art-and-references","proposed/0111-pure-proxy-replication.html#unresolved-questions","proposed/0111-pure-proxy-replication.html#future-directions-and-related-material","proposed/0112-compress-state-response-message-in-state-sync.html#rfc-0112-compress-the-state-response-message-in-state-sync","proposed/0112-compress-state-response-message-in-state-sync.html#summary","proposed/0112-compress-state-response-message-in-state-sync.html#motivation","proposed/0112-compress-state-response-message-in-state-sync.html#stakeholders","proposed/0112-compress-state-response-message-in-state-sync.html#explanation","proposed/0112-compress-state-response-message-in-state-sync.html#drawbacks","proposed/0112-compress-state-response-message-in-state-sync.html#testing-security-and-privacy","proposed/0112-compress-state-response-message-in-state-sync.html#performance-ergonomics-and-compatibility","proposed/0112-compress-state-response-message-in-state-sync.html#performance","proposed/0112-compress-state-response-message-in-state-sync.html#ergonomics","proposed/0112-compress-state-response-message-in-state-sync.html#compatibility","proposed/0112-compress-state-response-message-in-state-sync.html#prior-art-and-references","proposed/0112-compress-state-response-message-in-state-sync.html#unresolved-questions","proposed/0112-compress-state-response-message-in-state-sync.html#futLine truncated
{"doc_urls":["introduction.html#introduction","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/0103-introduce-core-index-commitment.html#rfc-0103--introduce-a-coreindex-commitment-and-a-sessionindex-field-in-candidate-receipts","proposed/0103-introduce-core-index-commitment.html#summary","proposed/0103-introduce-core-index-commitment.html#motivation","proposed/0103-introduce-core-index-commitment.html#stakeholders","proposed/0103-introduce-core-index-commitment.html#explanation","proposed/0103-introduce-core-index-commitment.html#reclaiming-unused-space-in-the-descriptor","proposed/0103-introduce-core-index-commitment.html#ump-transport","proposed/0103-introduce-core-index-commitment.html#polkadot-primitive-changes","proposed/0103-introduce-core-index-commitment.html#backwards-compatibility","proposed/0103-introduce-core-index-commitment.html#parachain-block-validation","proposed/0103-introduce-core-index-commitment.html#on-chain-backing","proposed/0103-introduce-core-index-commitment.html#drawbacks","proposed/0103-introduce-core-index-commitment.html#testing-security-and-privacy","proposed/0103-introduce-core-index-commitment.html#performance","proposed/0103-introduce-core-index-commitment.html#ergonomics","proposed/0103-introduce-core-index-commitment.html#compatibility","proposed/0103-introduce-core-index-commitment.html#relay-chain-runtime","proposed/0103-introduce-core-index-commitment.html#validators","proposed/0103-introduce-core-index-commitment.html#tooling","proposed/0103-introduce-core-index-commitment.html#prior-art-and-references","proposed/0103-introduce-core-index-commitment.html#unresolved-questions","proposed/0103-introduce-core-index-commitment.html#future-directions-and-related-material","proposed/0111-pure-proxy-replication.html#rfc-0111-pure-proxy-replication","proposed/0111-pure-proxy-replication.html#summary","proposed/0111-pure-proxy-replication.html#motivation","proposed/0111-pure-proxy-replication.html#stakeholders","proposed/0111-pure-proxy-replication.html#explanation","proposed/0111-pure-proxy-replication.html#drawbacks","proposed/0111-pure-proxy-replication.html#testing-security-and-privacy","proposed/0111-pure-proxy-replication.html#performance-ergonomics-and-compatibility","proposed/0111-pure-proxy-replication.html#performance","proposed/0111-pure-proxy-replication.html#ergonomics","proposed/0111-pure-proxy-replication.html#compatibility","proposed/0111-pure-proxy-replication.html#prior-art-and-references","proposed/0111-pure-proxy-replication.html#unresolved-questions","proposed/0111-pure-proxy-replication.html#future-directions-and-related-material","proposed/0112-compress-state-response-message-in-state-sync.html#rfc-0112-compress-the-state-response-message-in-state-sync","proposed/0112-compress-state-response-message-in-state-sync.html#summary","proposed/0112-compress-state-response-message-in-state-sync.html#motivation","proposed/0112-compress-state-response-message-in-state-sync.html#stakeholders","proposed/0112-compress-state-response-message-in-state-sync.html#explanation","proposed/0112-compress-state-response-message-in-state-sync.html#drawbacks","proposed/0112-compress-state-response-message-in-state-sync.html#testing-security-and-privacy","proposed/0112-compress-state-response-message-in-state-sync.html#performance-ergonomics-and-compatibility","proposed/0112-compress-state-response-message-in-state-sync.html#performance","proposed/0112-compress-state-response-message-in-state-sync.html#ergonomics","proposed/0112-compress-state-response-message-in-state-sync.html#compatibility","proposed/0112-compress-state-response-message-in-state-sync.html#prior-art-and-references","proposed/0112-compress-state-response-message-in-state-sync.html#unresolved-questions","proposed/0112-compress-state-response-message-in-state-sync.html#futLine truncated