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: 73c98535fc

Browse Source
This commit is contained in:
bkchr committed 2024-12-12 01:12:18 +00:00
1 parent 2496bc1a56
commit 7b58e0fb70
4 files changed
+12 -12
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

print.html
+5 -5
View File
@@ -686,7 +686,7 @@ The weight limit is the maximum weight allowed for the query execution.</li>
<li><code>metadata</code>: Return metadata of supported extensions (introduced in later section) and methods, serving as a feature discovery functionality.
The representation and encoding mechanism is similar to the <a href="https://github.com/paritytech/frame-metadata/"><code>frame-metadata</code></a>, using <code>scale-info</code>.</li>
</ul>
<p><strong>Example XCQ Runtime API</strong>:</p>
<h4 id="example-xcq-runtime-api"><a class="header" href="#example-xcq-runtime-api">Example XCQ Runtime API</a></h4>
<pre><pre class="playground"><code class="language-rust"><span class="boring">#![allow(unused)]
</span><span class="boring">fn main() {
</span>decl_runtime_apis! {
@@ -701,7 +701,7 @@ enum XcqError {
Custom(String),
}
<span class="boring">}</span></code></pre></pre>
<p><strong>Example Metadata (before SCALE-encoded)</strong></p>
<h4 id="example-metadata-before-scale-encoded"><a class="header" href="#example-metadata-before-scale-encoded">Example Metadata (before SCALE-encoded)</a></h4>
<pre><pre class="playground"><code class="language-rust"><span class="boring">#![allow(unused)]
</span><span class="boring">fn main() {
</span>pub struct Metadata {
@@ -890,7 +890,7 @@ extern &quot;C&quot; {
</li>
</ol>
<h3 id="xcm-integration"><a class="header" href="#xcm-integration">XCM integration</a></h3>
<p>The integration of XCQ into XCM is acheived by adding a new instruction to XCM, as well as a new variant of the <code>Response</code> type in <code>QueryResponse</code> message.:</p>
<p>The integration of XCQ into XCM is achieved by adding a new instruction to XCM, as well as a new variant of the <code>Response</code> type in <code>QueryResponse</code> message.:</p>
<ul>
<li>A new <code>ReportQuery</code> instruction</li>
</ul>
@@ -898,7 +898,7 @@ extern &quot;C&quot; {
</span><span class="boring">fn main() {
</span>ReportQuery {
query: SizeLimitedXcq,
weight_limit: Option&lt;Weight&gt;,
weight_limit: WeightLimit,
info: QueryResponseInfo,
}
<span class="boring">}</span></code></pre></pre>
@@ -962,7 +962,7 @@ extern &quot;C&quot; {
<li>XCQ Query Program Size: The size of XCQ query programs should be optimized to ensure efficient storage and transmission via XCMP/HRMP.
Some strategies to address this issue include:
<ul>
<li>Exploring modular program structures that allow for separate storage and transmission of core logic and supporting elements. PolkaVM supports spliting the program into multiple modules.</li>
<li>Exploring modular program structures that allow for separate storage and transmission of core logic and supporting elements. PolkaVM supports splitting the program into multiple modules.</li>
<li>Establishing guidelines for optimizing dynamic memory usage within query programs</li>
</ul>
</li>
proposed/0126-introduce-xcq.html
+5 -5
View File
@@ -273,7 +273,7 @@ The weight limit is the maximum weight allowed for the query execution.</li>
<li><code>metadata</code>: Return metadata of supported extensions (introduced in later section) and methods, serving as a feature discovery functionality.
The representation and encoding mechanism is similar to the <a href="https://github.com/paritytech/frame-metadata/"><code>frame-metadata</code></a>, using <code>scale-info</code>.</li>
</ul>
<p><strong>Example XCQ Runtime API</strong>:</p>
<h4 id="example-xcq-runtime-api"><a class="header" href="#example-xcq-runtime-api">Example XCQ Runtime API</a></h4>
<pre><pre class="playground"><code class="language-rust"><span class="boring">#![allow(unused)]
</span><span class="boring">fn main() {
</span>decl_runtime_apis! {
@@ -288,7 +288,7 @@ enum XcqError {
Custom(String),
}
<span class="boring">}</span></code></pre></pre>
<p><strong>Example Metadata (before SCALE-encoded)</strong></p>
<h4 id="example-metadata-before-scale-encoded"><a class="header" href="#example-metadata-before-scale-encoded">Example Metadata (before SCALE-encoded)</a></h4>
<pre><pre class="playground"><code class="language-rust"><span class="boring">#![allow(unused)]
</span><span class="boring">fn main() {
</span>pub struct Metadata {
@@ -477,7 +477,7 @@ extern &quot;C&quot; {
</li>
</ol>
<h3 id="xcm-integration"><a class="header" href="#xcm-integration">XCM integration</a></h3>
<p>The integration of XCQ into XCM is acheived by adding a new instruction to XCM, as well as a new variant of the <code>Response</code> type in <code>QueryResponse</code> message.:</p>
<p>The integration of XCQ into XCM is achieved by adding a new instruction to XCM, as well as a new variant of the <code>Response</code> type in <code>QueryResponse</code> message.:</p>
<ul>
<li>A new <code>ReportQuery</code> instruction</li>
</ul>
@@ -485,7 +485,7 @@ extern &quot;C&quot; {
</span><span class="boring">fn main() {
</span>ReportQuery {
query: SizeLimitedXcq,
weight_limit: Option&lt;Weight&gt;,
weight_limit: WeightLimit,
info: QueryResponseInfo,
}
<span class="boring">}</span></code></pre></pre>
@@ -549,7 +549,7 @@ extern &quot;C&quot; {
<li>XCQ Query Program Size: The size of XCQ query programs should be optimized to ensure efficient storage and transmission via XCMP/HRMP.
Some strategies to address this issue include:
<ul>
<li>Exploring modular program structures that allow for separate storage and transmission of core logic and supporting elements. PolkaVM supports spliting the program into multiple modules.</li>
<li>Exploring modular program structures that allow for separate storage and transmission of core logic and supporting elements. PolkaVM supports splitting the program into multiple modules.</li>
<li>Establishing guidelines for optimizing dynamic memory usage within query programs</li>
</ul>
</li>
searchindex.js
+1 -1
View File
@@ -1 +1 @@
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","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/0123-pending-code-as-storage-location-for-runtime-upgrades.html#rfc-0123-introduce-pending_code-as-intermediate-storage-key-for-the-runtime-code","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#summary","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#motivation","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#stakeholders","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#explanation","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#drawbacks","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#testing-security-and-privacy","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#performance-ergonomics-and-compatibility","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#performance","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#ergonomics","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#compatibility","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#prior-art-and-references","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#unresolved-questions","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#future-directions-and-related-material","proposed/0125-xcm-asset-metadata.html#rfc-0125-xcm-asset-metadata","proposed/0125-xcm-asset-metadata.html#summary","proposed/0125-xcm-asset-metadata.html#motivation","proposed/0125-xcm-asset-metadata.html#stakeholders","proposed/0125-xcm-asset-metadata.html#explanation","proposed/0125-xcm-asset-metadata.html#new-instructions","proposed/0125-xcm-asset-metadata.html#repurposing-assetinstanceundefined","proposed/0125-xcm-asset-metadata.html#drawbacks","proposed/0125-xcm-asset-metadata.html#testing-security-and-privacy","proposed/0125-xcm-asset-metadata.html#performance-ergonomics-and-compatibility","proposed/0125-xcm-asset-metadata.html#performance","proposed/0125-xcm-asset-metadata.html#ergonomics","proposed/0125-xcm-asset-metadata.html#compatibility","proposed/0125-xcm-asset-metadata.html#prior-art-and-references","proposed/0125-xcm-asset-metadata.html#unresolved-questions","proposed/0125-xcm-asset-metadata.html#future-directions-and-related-material","proposed/0126-introduce-xcq.html#rfc-0126-introduce-xcqcross-consensus-query","proposed/0126-introduce-xcq.html#summary","proposed/0126-introduce-xcq.html#motivation","proposed/0126-introduce-xcq.html#stakeholders","proposed/0126-introduce-xcq.html#explanation","proposed/0126-introduce-xcq.html#xcq-runtime-api","proposed/0126-introduce-xcq.html#xcq-executor","proposed/0126-introduce-xcq.html#xcq-extension","proposed/0126-introduce-xcq.html#xcq-program-structure","proposed/0126-introduce-xcq.html#xcq-program-execution-flow","proposed/0126-introduce-xcq.html#xcm-integration","proposed/0126-introduce-xcq.html#drawbacks","proposed/0126-introduce-xcq.html#performance-issues","proposed/0126-introduce-xcq.html#user-experience-issues","proposed/0126-introduce-xcq.html#testing-security-and-privacy","proposed/0126-introduce-xcq.html#performance-ergonomics-and-compatibility","proposed/0126-introduce-xcq.html#performance","proposed/0126-introduce-xcq.html#ergonomics","proposed/0126-introduce-xcq.html#compatibility","proposed/0126-introduce-xcq.html#prior-art-and-references","proposed/0126-introduce-xcq.html#unresolved-questions","proposed/0126-introduce-xcq.html#future-directions-and-related-material","approved/0001-agile-coretime.html#rfc-1-agile-coretime","approved/0001-agile-coretime.html#summary","approved/0001-agile-coretime.html#motivation","approved/0001-agile-coretime.html#present-system","approved/0001-agile-coretime.html#problems","approved/0001-agile-coretime.html#requirements","approved/0001-agile-coretime.html#stakeholders","approved/0001-agile-coretime.html#explanation","approved/0001-agile-coretime.html#overview","approved/0001-agile-coretime.html#detail"Line truncated
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","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/0123-pending-code-as-storage-location-for-runtime-upgrades.html#rfc-0123-introduce-pending_code-as-intermediate-storage-key-for-the-runtime-code","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#summary","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#motivation","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#stakeholders","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#explanation","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#drawbacks","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#testing-security-and-privacy","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#performance-ergonomics-and-compatibility","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#performance","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#ergonomics","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#compatibility","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#prior-art-and-references","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#unresolved-questions","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#future-directions-and-related-material","proposed/0125-xcm-asset-metadata.html#rfc-0125-xcm-asset-metadata","proposed/0125-xcm-asset-metadata.html#summary","proposed/0125-xcm-asset-metadata.html#motivation","proposed/0125-xcm-asset-metadata.html#stakeholders","proposed/0125-xcm-asset-metadata.html#explanation","proposed/0125-xcm-asset-metadata.html#new-instructions","proposed/0125-xcm-asset-metadata.html#repurposing-assetinstanceundefined","proposed/0125-xcm-asset-metadata.html#drawbacks","proposed/0125-xcm-asset-metadata.html#testing-security-and-privacy","proposed/0125-xcm-asset-metadata.html#performance-ergonomics-and-compatibility","proposed/0125-xcm-asset-metadata.html#performance","proposed/0125-xcm-asset-metadata.html#ergonomics","proposed/0125-xcm-asset-metadata.html#compatibility","proposed/0125-xcm-asset-metadata.html#prior-art-and-references","proposed/0125-xcm-asset-metadata.html#unresolved-questions","proposed/0125-xcm-asset-metadata.html#future-directions-and-related-material","proposed/0126-introduce-xcq.html#rfc-0126-introduce-xcqcross-consensus-query","proposed/0126-introduce-xcq.html#summary","proposed/0126-introduce-xcq.html#motivation","proposed/0126-introduce-xcq.html#stakeholders","proposed/0126-introduce-xcq.html#explanation","proposed/0126-introduce-xcq.html#xcq-runtime-api","proposed/0126-introduce-xcq.html#xcq-executor","proposed/0126-introduce-xcq.html#xcq-extension","proposed/0126-introduce-xcq.html#xcq-program-structure","proposed/0126-introduce-xcq.html#xcq-program-execution-flow","proposed/0126-introduce-xcq.html#xcm-integration","proposed/0126-introduce-xcq.html#drawbacks","proposed/0126-introduce-xcq.html#performance-issues","proposed/0126-introduce-xcq.html#user-experience-issues","proposed/0126-introduce-xcq.html#testing-security-and-privacy","proposed/0126-introduce-xcq.html#performance-ergonomics-and-compatibility","proposed/0126-introduce-xcq.html#performance","proposed/0126-introduce-xcq.html#ergonomics","proposed/0126-introduce-xcq.html#compatibility","proposed/0126-introduce-xcq.html#prior-art-and-references","proposed/0126-introduce-xcq.html#unresolved-questions","proposed/0126-introduce-xcq.html#future-directions-and-related-material","approved/0001-agile-coretime.html#rfc-1-agile-coretime","approved/0001-agile-coretime.html#summary","approved/0001-agile-coretime.html#motivation","approved/0001-agile-coretime.html#present-system","approved/0001-agile-coretime.html#problems","approved/0001-agile-coretime.html#requirements","approved/0001-agile-coretime.html#stakeholders","approved/0001-agile-coretime.html#explanation","approved/0001-agile-coretime.html#overview","approved/0001-agile-coretime.html#detail"Line truncated
searchindex.json
+1 -1
View File
@@ -1 +1 @@
{"doc_urls":["introduction.html#introduction","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/0123-pending-code-as-storage-location-for-runtime-upgrades.html#rfc-0123-introduce-pending_code-as-intermediate-storage-key-for-the-runtime-code","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#summary","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#motivation","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#stakeholders","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#explanation","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#drawbacks","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#testing-security-and-privacy","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#performance-ergonomics-and-compatibility","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#performance","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#ergonomics","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#compatibility","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#prior-art-and-references","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#unresolved-questions","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#future-directions-and-related-material","proposed/0125-xcm-asset-metadata.html#rfc-0125-xcm-asset-metadata","proposed/0125-xcm-asset-metadata.html#summary","proposed/0125-xcm-asset-metadata.html#motivation","proposed/0125-xcm-asset-metadata.html#stakeholders","proposed/0125-xcm-asset-metadata.html#explanation","proposed/0125-xcm-asset-metadata.html#new-instructions","proposed/0125-xcm-asset-metadata.html#repurposing-assetinstanceundefined","proposed/0125-xcm-asset-metadata.html#drawbacks","proposed/0125-xcm-asset-metadata.html#testing-security-and-privacy","proposed/0125-xcm-asset-metadata.html#performance-ergonomics-and-compatibility","proposed/0125-xcm-asset-metadata.html#performance","proposed/0125-xcm-asset-metadata.html#ergonomics","proposed/0125-xcm-asset-metadata.html#compatibility","proposed/0125-xcm-asset-metadata.html#prior-art-and-references","proposed/0125-xcm-asset-metadata.html#unresolved-questions","proposed/0125-xcm-asset-metadata.html#future-directions-and-related-material","proposed/0126-introduce-xcq.html#rfc-0126-introduce-xcqcross-consensus-query","proposed/0126-introduce-xcq.html#summary","proposed/0126-introduce-xcq.html#motivation","proposed/0126-introduce-xcq.html#stakeholders","proposed/0126-introduce-xcq.html#explanation","proposed/0126-introduce-xcq.html#xcq-runtime-api","proposed/0126-introduce-xcq.html#xcq-executor","proposed/0126-introduce-xcq.html#xcq-extension","proposed/0126-introduce-xcq.html#xcq-program-structure","proposed/0126-introduce-xcq.html#xcq-program-execution-flow","proposed/0126-introduce-xcq.html#xcm-integration","proposed/0126-introduce-xcq.html#drawbacks","proposed/0126-introduce-xcq.html#performance-issues","proposed/0126-introduce-xcq.html#user-experience-issues","proposed/0126-introduce-xcq.html#testing-security-and-privacy","proposed/0126-introduce-xcq.html#performance-ergonomics-and-compatibility","proposed/0126-introduce-xcq.html#performance","proposed/0126-introduce-xcq.html#ergonomics","proposed/0126-introduce-xcq.html#compatibility","proposed/0126-introduce-xcq.html#prior-art-and-references","proposed/0126-introduce-xcq.html#unresolved-questions","proposed/0126-introduce-xcq.html#future-directions-and-related-material","approved/0001-agile-coretime.html#rfc-1-agile-coretime","approved/0001-agile-coretime.html#summary","approved/0001-agile-coretime.html#motivation","approved/0001-agile-coretime.html#present-system","approved/0001-agile-coretime.html#problems","approved/0001-agile-coretime.html#requirements","approved/0001-agile-coretime.html#stakeholders","approved/0001-agile-coretime.html#explanation","approved/0001-agile-coretime.html#overview","approved/0001-agile-coretime.html#detail","approved/0001-agile-coretimLine truncated
{"doc_urls":["introduction.html#introduction","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/0123-pending-code-as-storage-location-for-runtime-upgrades.html#rfc-0123-introduce-pending_code-as-intermediate-storage-key-for-the-runtime-code","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#summary","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#motivation","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#stakeholders","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#explanation","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#drawbacks","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#testing-security-and-privacy","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#performance-ergonomics-and-compatibility","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#performance","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#ergonomics","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#compatibility","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#prior-art-and-references","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#unresolved-questions","proposed/0123-pending-code-as-storage-location-for-runtime-upgrades.html#future-directions-and-related-material","proposed/0125-xcm-asset-metadata.html#rfc-0125-xcm-asset-metadata","proposed/0125-xcm-asset-metadata.html#summary","proposed/0125-xcm-asset-metadata.html#motivation","proposed/0125-xcm-asset-metadata.html#stakeholders","proposed/0125-xcm-asset-metadata.html#explanation","proposed/0125-xcm-asset-metadata.html#new-instructions","proposed/0125-xcm-asset-metadata.html#repurposing-assetinstanceundefined","proposed/0125-xcm-asset-metadata.html#drawbacks","proposed/0125-xcm-asset-metadata.html#testing-security-and-privacy","proposed/0125-xcm-asset-metadata.html#performance-ergonomics-and-compatibility","proposed/0125-xcm-asset-metadata.html#performance","proposed/0125-xcm-asset-metadata.html#ergonomics","proposed/0125-xcm-asset-metadata.html#compatibility","proposed/0125-xcm-asset-metadata.html#prior-art-and-references","proposed/0125-xcm-asset-metadata.html#unresolved-questions","proposed/0125-xcm-asset-metadata.html#future-directions-and-related-material","proposed/0126-introduce-xcq.html#rfc-0126-introduce-xcqcross-consensus-query","proposed/0126-introduce-xcq.html#summary","proposed/0126-introduce-xcq.html#motivation","proposed/0126-introduce-xcq.html#stakeholders","proposed/0126-introduce-xcq.html#explanation","proposed/0126-introduce-xcq.html#xcq-runtime-api","proposed/0126-introduce-xcq.html#xcq-executor","proposed/0126-introduce-xcq.html#xcq-extension","proposed/0126-introduce-xcq.html#xcq-program-structure","proposed/0126-introduce-xcq.html#xcq-program-execution-flow","proposed/0126-introduce-xcq.html#xcm-integration","proposed/0126-introduce-xcq.html#drawbacks","proposed/0126-introduce-xcq.html#performance-issues","proposed/0126-introduce-xcq.html#user-experience-issues","proposed/0126-introduce-xcq.html#testing-security-and-privacy","proposed/0126-introduce-xcq.html#performance-ergonomics-and-compatibility","proposed/0126-introduce-xcq.html#performance","proposed/0126-introduce-xcq.html#ergonomics","proposed/0126-introduce-xcq.html#compatibility","proposed/0126-introduce-xcq.html#prior-art-and-references","proposed/0126-introduce-xcq.html#unresolved-questions","proposed/0126-introduce-xcq.html#future-directions-and-related-material","approved/0001-agile-coretime.html#rfc-1-agile-coretime","approved/0001-agile-coretime.html#summary","approved/0001-agile-coretime.html#motivation","approved/0001-agile-coretime.html#present-system","approved/0001-agile-coretime.html#problems","approved/0001-agile-coretime.html#requirements","approved/0001-agile-coretime.html#stakeholders","approved/0001-agile-coretime.html#explanation","approved/0001-agile-coretime.html#overview","approved/0001-agile-coretime.html#detail","approved/0001-agile-coretimLine truncated