mirror of
https://github.com/pezkuwichain/pezkuwi-fellows.git
synced 2026-10-30 15:39:51 +00:00
deploy: 99e179cbc1
This commit is contained in:
bkchr committed
1 parent
5f017216d9
commit
85e5acf766
4 files changed
+4
-4
No files matched your search
+1
-1
@@ -2623,7 +2623,7 @@ enum TypeRef {
|
||||
<p>Every <code>Type</code> is composed of multiple different types. Each of these "sub types" can reference either a full <code>Type</code> again or reference one of the primitive types. This is where <code>TypeRef</code> becomes relevant as the type referencing information. To reference a <code>Type</code> in the type information, a unique identifier is used. As primitive types can be represented using a single byte, they are not put as separate types into the type information. Instead the primitive types are directly part of <code>TypeRef</code> to not require the overhead of referencing them in an extra <code>Type</code>. The special primitive type <code>Void</code> represents a type that encodes to nothing and can be decoded from nothing. As FRAME doesn't support <code>Compact</code> as primitive type it requires a more involved implementation to convert a FRAME type to a <code>Compact</code> primitive type. SCALE only supports <code>u8</code>, <code>u16</code>, <code>u32</code>, <code>u64</code> and <code>u128</code> as <code>Compact</code> which maps onto the primitive type declaration in the RFC. One special case is a <code>Compact</code> that wraps an empty <code>Tuple</code> which is expressed as primitive type <code>Void</code>.</p>
|
||||
<p>The <code>TypeDef</code> variants have the following meaning:</p>
|
||||
<ul>
|
||||
<li><code>Composite</code>: A <code>struct</code> like type that is composed of multiple different fields. Each <code>Field</code> can have its own type. A <code>Composite</code> with no fields is expressed as primitive type <code>Void</code>.</li>
|
||||
<li><code>Composite</code>: A <code>struct</code> like type that is composed of multiple different fields. Each <code>Field</code> can have its own type. The order of the fields is significant. A <code>Composite</code> with no fields is expressed as primitive type <code>Void</code>.</li>
|
||||
<li><code>Enumeration</code>: Stores a <code>EnumerationVariant</code>. A <code>EnumerationVariant</code> is a struct that is described by a name, an index and a vector of <code>Field</code>s, each of which can have it's own type. Typically <code>Enumeration</code>s have more than just one variant, and in those cases <code>Enumeration</code> will appear multiple times, each time with a different variant, in the type information. <code>Enumeration</code>s can become quite large, yet usually for decoding a type only one variant is required, therefore this design brings optimizations and helps reduce the size of the proof. An <code>Enumeration</code> with no variants is expressed as primitive type <code>Void</code>.</li>
|
||||
<li><code>Sequence</code>: A <code>vector</code> like type wrapping the given type.</li>
|
||||
<li><code>BitSequence</code>: A <code>vector</code> storing bits. <code>num_bytes</code> represents the size in bytes of the internal storage. If <code>least_significant_bit_first</code> is <code>true</code> the least significant bit is first, otherwise the most significant bit is first.</li>
|
||||
|
||||
@@ -400,7 +400,7 @@ enum TypeRef {
|
||||
<p>Every <code>Type</code> is composed of multiple different types. Each of these "sub types" can reference either a full <code>Type</code> again or reference one of the primitive types. This is where <code>TypeRef</code> becomes relevant as the type referencing information. To reference a <code>Type</code> in the type information, a unique identifier is used. As primitive types can be represented using a single byte, they are not put as separate types into the type information. Instead the primitive types are directly part of <code>TypeRef</code> to not require the overhead of referencing them in an extra <code>Type</code>. The special primitive type <code>Void</code> represents a type that encodes to nothing and can be decoded from nothing. As FRAME doesn't support <code>Compact</code> as primitive type it requires a more involved implementation to convert a FRAME type to a <code>Compact</code> primitive type. SCALE only supports <code>u8</code>, <code>u16</code>, <code>u32</code>, <code>u64</code> and <code>u128</code> as <code>Compact</code> which maps onto the primitive type declaration in the RFC. One special case is a <code>Compact</code> that wraps an empty <code>Tuple</code> which is expressed as primitive type <code>Void</code>.</p>
|
||||
<p>The <code>TypeDef</code> variants have the following meaning:</p>
|
||||
<ul>
|
||||
<li><code>Composite</code>: A <code>struct</code> like type that is composed of multiple different fields. Each <code>Field</code> can have its own type. A <code>Composite</code> with no fields is expressed as primitive type <code>Void</code>.</li>
|
||||
<li><code>Composite</code>: A <code>struct</code> like type that is composed of multiple different fields. Each <code>Field</code> can have its own type. The order of the fields is significant. A <code>Composite</code> with no fields is expressed as primitive type <code>Void</code>.</li>
|
||||
<li><code>Enumeration</code>: Stores a <code>EnumerationVariant</code>. A <code>EnumerationVariant</code> is a struct that is described by a name, an index and a vector of <code>Field</code>s, each of which can have it's own type. Typically <code>Enumeration</code>s have more than just one variant, and in those cases <code>Enumeration</code> will appear multiple times, each time with a different variant, in the type information. <code>Enumeration</code>s can become quite large, yet usually for decoding a type only one variant is required, therefore this design brings optimizations and helps reduce the size of the proof. An <code>Enumeration</code> with no variants is expressed as primitive type <code>Void</code>.</li>
|
||||
<li><code>Sequence</code>: A <code>vector</code> like type wrapping the given type.</li>
|
||||
<li><code>BitSequence</code>: A <code>vector</code> storing bits. <code>num_bytes</code> represents the size in bytes of the internal storage. If <code>least_significant_bit_first</code> is <code>true</code> the least significant bit is first, otherwise the most significant bit is first.</li>
|
||||
|
||||
+1
-1
@@ -1 +1 @@
|
||||
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","proposed/0004-remove-unnecessary-allocator-usage.html#rfc-0004-remove-the-host-side-runtime-memory-allocator","proposed/0004-remove-unnecessary-allocator-usage.html#summary","proposed/0004-remove-unnecessary-allocator-usage.html#motivation","proposed/0004-remove-unnecessary-allocator-usage.html#stakeholders","proposed/0004-remove-unnecessary-allocator-usage.html#explanation","proposed/0004-remove-unnecessary-allocator-usage.html#new-host-functions","proposed/0004-remove-unnecessary-allocator-usage.html#other-changes","proposed/0004-remove-unnecessary-allocator-usage.html#drawbacks","proposed/0004-remove-unnecessary-allocator-usage.html#prior-art","proposed/0004-remove-unnecessary-allocator-usage.html#unresolved-questions","proposed/0004-remove-unnecessary-allocator-usage.html#future-possibilities","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#rfc-0013-prepare-core-runtime-api-for-mbms","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#summary","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#motivation","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#stakeholders","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#explanation","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#coreinitialize_block","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#drawbacks","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#testing-security-and-privacy","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#performance-ergonomics-and-compatibility","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#performance","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#ergonomics","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#compatibility","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#prior-art-and-references","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#unresolved-questions","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#future-directions-and-related-material","proposed/0045-nft-deposits-asset-hub.html#rfc-0045-lowering-nft-deposits-on-asset-hub","proposed/0045-nft-deposits-asset-hub.html#summary","proposed/0045-nft-deposits-asset-hub.html#motivation","proposed/0045-nft-deposits-asset-hub.html#requirements","proposed/0045-nft-deposits-asset-hub.html#stakeholders","proposed/0045-nft-deposits-asset-hub.html#explanation","proposed/0045-nft-deposits-asset-hub.html#enhanced-approach-to-further-lower-barriers-for-entry","proposed/0045-nft-deposits-asset-hub.html#short--and-long-term-plans","proposed/0045-nft-deposits-asset-hub.html#drawbacks","proposed/0045-nft-deposits-asset-hub.html#testing-security-and-privacy","proposed/0045-nft-deposits-asset-hub.html#security-concerns","proposed/0045-nft-deposits-asset-hub.html#performance-ergonomics-and-compatibility","proposed/0045-nft-deposits-asset-hub.html#performance","proposed/0045-nft-deposits-asset-hub.html#ergonomics","proposed/0045-nft-deposits-asset-hub.html#compatibility","proposed/0045-nft-deposits-asset-hub.html#unresolved-questions","proposed/0045-nft-deposits-asset-hub.html#addendum","proposed/0045-nft-deposits-asset-hub.html#enhanced-weak-governance-origin-model","proposed/0045-nft-deposits-asset-hub.html#function-based-pricing-model","proposed/0045-nft-deposits-asset-hub.html#linking-deposit-to-usdx-value","proposed/0046-metadata-for-offline-signers.html#rfc-0046-metadata-for-offline-signers","proposed/0046-metadata-for-offline-signers.html#summary","proposed/0046-metadata-for-offline-signers.html#motivation","proposed/0046-metadata-for-offline-signers.html#background","proposed/0046-metadata-for-offline-signers.html#solution-requirements","proposed/0046-metadata-for-offline-signers.html#stakeholders","proposed/0046-metadata-for-offline-signers.html#explanation","proposed/0046-metadata-for-offline-signers.html#definitions","proposed/0046-metadata-for-offline-signers.html#general-flow","proposed/0046-metadata-for-offline-signers.html#metadata-modularization","proposed/0046-metadata-for-offline-signers.html#merging-protocol","proposed/0046-metadata-for-offline-signers.html#complete-binary-merkle-tree-construction-protocol","proposed/0046-metadata-for-offline-signers.html#digest","proposed/0046-metadata-for-offline-signers.html#chain-verification","proposed/0046-metadata-for-offline-signers.html#drawbacks","proposed/0046-metadata-for-offline-signers.html#increased-transaction-size","proposed/0046-metadata-for-offline-signers.html#transition-overhead","proposed/0046-metadata-for-offline-signers.html#testing-security-and-privacy","proposed/0046-metadata-for-offline-signers.html#performance-ergonomics-and-compatibility","proposed/0046-metadata-for-offline-signers.html#peLine truncated
|
||||
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","proposed/0004-remove-unnecessary-allocator-usage.html#rfc-0004-remove-the-host-side-runtime-memory-allocator","proposed/0004-remove-unnecessary-allocator-usage.html#summary","proposed/0004-remove-unnecessary-allocator-usage.html#motivation","proposed/0004-remove-unnecessary-allocator-usage.html#stakeholders","proposed/0004-remove-unnecessary-allocator-usage.html#explanation","proposed/0004-remove-unnecessary-allocator-usage.html#new-host-functions","proposed/0004-remove-unnecessary-allocator-usage.html#other-changes","proposed/0004-remove-unnecessary-allocator-usage.html#drawbacks","proposed/0004-remove-unnecessary-allocator-usage.html#prior-art","proposed/0004-remove-unnecessary-allocator-usage.html#unresolved-questions","proposed/0004-remove-unnecessary-allocator-usage.html#future-possibilities","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#rfc-0013-prepare-core-runtime-api-for-mbms","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#summary","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#motivation","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#stakeholders","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#explanation","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#coreinitialize_block","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#drawbacks","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#testing-security-and-privacy","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#performance-ergonomics-and-compatibility","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#performance","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#ergonomics","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#compatibility","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#prior-art-and-references","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#unresolved-questions","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#future-directions-and-related-material","proposed/0045-nft-deposits-asset-hub.html#rfc-0045-lowering-nft-deposits-on-asset-hub","proposed/0045-nft-deposits-asset-hub.html#summary","proposed/0045-nft-deposits-asset-hub.html#motivation","proposed/0045-nft-deposits-asset-hub.html#requirements","proposed/0045-nft-deposits-asset-hub.html#stakeholders","proposed/0045-nft-deposits-asset-hub.html#explanation","proposed/0045-nft-deposits-asset-hub.html#enhanced-approach-to-further-lower-barriers-for-entry","proposed/0045-nft-deposits-asset-hub.html#short--and-long-term-plans","proposed/0045-nft-deposits-asset-hub.html#drawbacks","proposed/0045-nft-deposits-asset-hub.html#testing-security-and-privacy","proposed/0045-nft-deposits-asset-hub.html#security-concerns","proposed/0045-nft-deposits-asset-hub.html#performance-ergonomics-and-compatibility","proposed/0045-nft-deposits-asset-hub.html#performance","proposed/0045-nft-deposits-asset-hub.html#ergonomics","proposed/0045-nft-deposits-asset-hub.html#compatibility","proposed/0045-nft-deposits-asset-hub.html#unresolved-questions","proposed/0045-nft-deposits-asset-hub.html#addendum","proposed/0045-nft-deposits-asset-hub.html#enhanced-weak-governance-origin-model","proposed/0045-nft-deposits-asset-hub.html#function-based-pricing-model","proposed/0045-nft-deposits-asset-hub.html#linking-deposit-to-usdx-value","proposed/0046-metadata-for-offline-signers.html#rfc-0046-metadata-for-offline-signers","proposed/0046-metadata-for-offline-signers.html#summary","proposed/0046-metadata-for-offline-signers.html#motivation","proposed/0046-metadata-for-offline-signers.html#background","proposed/0046-metadata-for-offline-signers.html#solution-requirements","proposed/0046-metadata-for-offline-signers.html#stakeholders","proposed/0046-metadata-for-offline-signers.html#explanation","proposed/0046-metadata-for-offline-signers.html#definitions","proposed/0046-metadata-for-offline-signers.html#general-flow","proposed/0046-metadata-for-offline-signers.html#metadata-modularization","proposed/0046-metadata-for-offline-signers.html#merging-protocol","proposed/0046-metadata-for-offline-signers.html#complete-binary-merkle-tree-construction-protocol","proposed/0046-metadata-for-offline-signers.html#digest","proposed/0046-metadata-for-offline-signers.html#chain-verification","proposed/0046-metadata-for-offline-signers.html#drawbacks","proposed/0046-metadata-for-offline-signers.html#increased-transaction-size","proposed/0046-metadata-for-offline-signers.html#transition-overhead","proposed/0046-metadata-for-offline-signers.html#testing-security-and-privacy","proposed/0046-metadata-for-offline-signers.html#performance-ergonomics-and-compatibility","proposed/0046-metadata-for-offline-signers.html#peLine truncated
|
||||
+1
-1
@@ -1 +1 @@
|
||||
{"doc_urls":["introduction.html#introduction","proposed/0004-remove-unnecessary-allocator-usage.html#rfc-0004-remove-the-host-side-runtime-memory-allocator","proposed/0004-remove-unnecessary-allocator-usage.html#summary","proposed/0004-remove-unnecessary-allocator-usage.html#motivation","proposed/0004-remove-unnecessary-allocator-usage.html#stakeholders","proposed/0004-remove-unnecessary-allocator-usage.html#explanation","proposed/0004-remove-unnecessary-allocator-usage.html#new-host-functions","proposed/0004-remove-unnecessary-allocator-usage.html#other-changes","proposed/0004-remove-unnecessary-allocator-usage.html#drawbacks","proposed/0004-remove-unnecessary-allocator-usage.html#prior-art","proposed/0004-remove-unnecessary-allocator-usage.html#unresolved-questions","proposed/0004-remove-unnecessary-allocator-usage.html#future-possibilities","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#rfc-0013-prepare-core-runtime-api-for-mbms","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#summary","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#motivation","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#stakeholders","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#explanation","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#coreinitialize_block","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#drawbacks","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#testing-security-and-privacy","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#performance-ergonomics-and-compatibility","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#performance","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#ergonomics","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#compatibility","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#prior-art-and-references","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#unresolved-questions","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#future-directions-and-related-material","proposed/0045-nft-deposits-asset-hub.html#rfc-0045-lowering-nft-deposits-on-asset-hub","proposed/0045-nft-deposits-asset-hub.html#summary","proposed/0045-nft-deposits-asset-hub.html#motivation","proposed/0045-nft-deposits-asset-hub.html#requirements","proposed/0045-nft-deposits-asset-hub.html#stakeholders","proposed/0045-nft-deposits-asset-hub.html#explanation","proposed/0045-nft-deposits-asset-hub.html#enhanced-approach-to-further-lower-barriers-for-entry","proposed/0045-nft-deposits-asset-hub.html#short--and-long-term-plans","proposed/0045-nft-deposits-asset-hub.html#drawbacks","proposed/0045-nft-deposits-asset-hub.html#testing-security-and-privacy","proposed/0045-nft-deposits-asset-hub.html#security-concerns","proposed/0045-nft-deposits-asset-hub.html#performance-ergonomics-and-compatibility","proposed/0045-nft-deposits-asset-hub.html#performance","proposed/0045-nft-deposits-asset-hub.html#ergonomics","proposed/0045-nft-deposits-asset-hub.html#compatibility","proposed/0045-nft-deposits-asset-hub.html#unresolved-questions","proposed/0045-nft-deposits-asset-hub.html#addendum","proposed/0045-nft-deposits-asset-hub.html#enhanced-weak-governance-origin-model","proposed/0045-nft-deposits-asset-hub.html#function-based-pricing-model","proposed/0045-nft-deposits-asset-hub.html#linking-deposit-to-usdx-value","proposed/0046-metadata-for-offline-signers.html#rfc-0046-metadata-for-offline-signers","proposed/0046-metadata-for-offline-signers.html#summary","proposed/0046-metadata-for-offline-signers.html#motivation","proposed/0046-metadata-for-offline-signers.html#background","proposed/0046-metadata-for-offline-signers.html#solution-requirements","proposed/0046-metadata-for-offline-signers.html#stakeholders","proposed/0046-metadata-for-offline-signers.html#explanation","proposed/0046-metadata-for-offline-signers.html#definitions","proposed/0046-metadata-for-offline-signers.html#general-flow","proposed/0046-metadata-for-offline-signers.html#metadata-modularization","proposed/0046-metadata-for-offline-signers.html#merging-protocol","proposed/0046-metadata-for-offline-signers.html#complete-binary-merkle-tree-construction-protocol","proposed/0046-metadata-for-offline-signers.html#digest","proposed/0046-metadata-for-offline-signers.html#chain-verification","proposed/0046-metadata-for-offline-signers.html#drawbacks","proposed/0046-metadata-for-offline-signers.html#increased-transaction-size","proposed/0046-metadata-for-offline-signers.html#transition-overhead","proposed/0046-metadata-for-offline-signers.html#testing-security-and-privacy","proposed/0046-metadata-for-offline-signers.html#performance-ergonomics-and-compatibility","proposed/0046-metadata-for-offline-signers.html#performance","proposed/0046-metLine truncated
|
||||
{"doc_urls":["introduction.html#introduction","proposed/0004-remove-unnecessary-allocator-usage.html#rfc-0004-remove-the-host-side-runtime-memory-allocator","proposed/0004-remove-unnecessary-allocator-usage.html#summary","proposed/0004-remove-unnecessary-allocator-usage.html#motivation","proposed/0004-remove-unnecessary-allocator-usage.html#stakeholders","proposed/0004-remove-unnecessary-allocator-usage.html#explanation","proposed/0004-remove-unnecessary-allocator-usage.html#new-host-functions","proposed/0004-remove-unnecessary-allocator-usage.html#other-changes","proposed/0004-remove-unnecessary-allocator-usage.html#drawbacks","proposed/0004-remove-unnecessary-allocator-usage.html#prior-art","proposed/0004-remove-unnecessary-allocator-usage.html#unresolved-questions","proposed/0004-remove-unnecessary-allocator-usage.html#future-possibilities","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#rfc-0013-prepare-core-runtime-api-for-mbms","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#summary","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#motivation","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#stakeholders","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#explanation","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#coreinitialize_block","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#drawbacks","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#testing-security-and-privacy","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#performance-ergonomics-and-compatibility","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#performance","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#ergonomics","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#compatibility","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#prior-art-and-references","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#unresolved-questions","proposed/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html#future-directions-and-related-material","proposed/0045-nft-deposits-asset-hub.html#rfc-0045-lowering-nft-deposits-on-asset-hub","proposed/0045-nft-deposits-asset-hub.html#summary","proposed/0045-nft-deposits-asset-hub.html#motivation","proposed/0045-nft-deposits-asset-hub.html#requirements","proposed/0045-nft-deposits-asset-hub.html#stakeholders","proposed/0045-nft-deposits-asset-hub.html#explanation","proposed/0045-nft-deposits-asset-hub.html#enhanced-approach-to-further-lower-barriers-for-entry","proposed/0045-nft-deposits-asset-hub.html#short--and-long-term-plans","proposed/0045-nft-deposits-asset-hub.html#drawbacks","proposed/0045-nft-deposits-asset-hub.html#testing-security-and-privacy","proposed/0045-nft-deposits-asset-hub.html#security-concerns","proposed/0045-nft-deposits-asset-hub.html#performance-ergonomics-and-compatibility","proposed/0045-nft-deposits-asset-hub.html#performance","proposed/0045-nft-deposits-asset-hub.html#ergonomics","proposed/0045-nft-deposits-asset-hub.html#compatibility","proposed/0045-nft-deposits-asset-hub.html#unresolved-questions","proposed/0045-nft-deposits-asset-hub.html#addendum","proposed/0045-nft-deposits-asset-hub.html#enhanced-weak-governance-origin-model","proposed/0045-nft-deposits-asset-hub.html#function-based-pricing-model","proposed/0045-nft-deposits-asset-hub.html#linking-deposit-to-usdx-value","proposed/0046-metadata-for-offline-signers.html#rfc-0046-metadata-for-offline-signers","proposed/0046-metadata-for-offline-signers.html#summary","proposed/0046-metadata-for-offline-signers.html#motivation","proposed/0046-metadata-for-offline-signers.html#background","proposed/0046-metadata-for-offline-signers.html#solution-requirements","proposed/0046-metadata-for-offline-signers.html#stakeholders","proposed/0046-metadata-for-offline-signers.html#explanation","proposed/0046-metadata-for-offline-signers.html#definitions","proposed/0046-metadata-for-offline-signers.html#general-flow","proposed/0046-metadata-for-offline-signers.html#metadata-modularization","proposed/0046-metadata-for-offline-signers.html#merging-protocol","proposed/0046-metadata-for-offline-signers.html#complete-binary-merkle-tree-construction-protocol","proposed/0046-metadata-for-offline-signers.html#digest","proposed/0046-metadata-for-offline-signers.html#chain-verification","proposed/0046-metadata-for-offline-signers.html#drawbacks","proposed/0046-metadata-for-offline-signers.html#increased-transaction-size","proposed/0046-metadata-for-offline-signers.html#transition-overhead","proposed/0046-metadata-for-offline-signers.html#testing-security-and-privacy","proposed/0046-metadata-for-offline-signers.html#performance-ergonomics-and-compatibility","proposed/0046-metadata-for-offline-signers.html#performance","proposed/0046-metLine truncated
|
||||
Reference in new issue
Block a user