mirror of
https://github.com/pezkuwichain/pezkuwi-fellows.git
synced 2026-10-29 23:19:52 +00:00
deploy: 91b31618c4
This commit is contained in:
bkchr committed
1 parent
e187c0d242
commit
6dcdbb1104
4 files changed
+26
-18
No files matched your search
+12
-8
@@ -989,23 +989,27 @@ of the paras, the locked/unlocked state, and the manager info.</p>
|
||||
<p>The version 1 of these functions has been taken as a base rather than the version 2, as a <a href="https://github.com/w3f/PPPs/pull/6">PPP#6</a> deprecating the version 2 of these functions has previously been accepted.</p>
|
||||
<pre><code class="language-wat">(func $ext_storage_clear_prefix_version_3
|
||||
(param $maybe_prefix i64) (param $maybe_limit i64)
|
||||
(param $maybe_cursor_in_out i64) (param $backend_out i32)
|
||||
(param $unique_out i32) (param $loops_out i32) (return i32))
|
||||
(param $maybe_cursor_in i64) (param $removal_results_out i32))
|
||||
(func $ext_default_child_storage_clear_prefix_version_3
|
||||
(param $child_storage_key i64) (param $prefix i64) (param $maybe_limit i64)
|
||||
(param $maybe_cursor_in_out i64) (param $backend_out i32)
|
||||
(param $unique_out i32) (param $loops_out i32) (return i32))
|
||||
(param $maybe_cursor_in i64) (param $removal_results_out i32))
|
||||
(func $ext_default_child_storage_kill_version_4
|
||||
(param $child_storage_key i64) (param $maybe_limit i64)
|
||||
(param $maybe_cursor_in_out i64) (param $backend_out i32)
|
||||
(param $unique_out i32) (param $loops_out i32) (return i32))
|
||||
(param $maybe_cursor_in i64) (param $removal_results_out i32))
|
||||
</code></pre>
|
||||
<p>These functions amend already implemented but still unused functions introduced by <a href="https://github.com/w3f/PPPs/pull/7">PPP#7</a>, hence there's no version number change. <code>maybe_limit</code> defines the limit of backend deletions, not counting keys in the current overlay. <code>maybe_cursor_in_out</code> may be used to pass a continuation cursor. The cursor is written into the same field if the limit was reached and not all the keys were cleared; otherwise, <code>None</code> is written. (CAVEAT: It's impossible to determine appropriate buffer size; the approach is discussible). <code>backend_out</code>, <code>unique_out</code> and <code>loops_out</code> parameters contain the memory location where the output is written (respectively, the number of items removed from the backend DB; the number of unique keys removes, including overlay; the number of iterations done). Any of the output parameters may be <code>-1</code>, in which case no output is written. The functions return <code>0</code> to indicate success, or <code>1</code> if <code>maybe_cursor_in_out</code> buffer length was not enough to write the new cursor; in the latter case, <code>None</code> is written to the buffer.</p>
|
||||
<p>These functions amend already implemented but still unused functions introduced by <a href="https://github.com/w3f/PPPs/pull/7">PPP#7</a>, hence there's no version number change. <code>maybe_limit</code> defines the limit of backend deletions, not counting keys in the current overlay. <code>maybe_cursor_in</code> may be used to pass a continuation cursor. After the operation is completed, a SCALE-encoded <a href="https://spec.polkadot.network/id-cryptography-encoding#defn-varrying-data-type">varying data</a> are written to the provided output buffer. The varying data consists from the following fields, in order:</p>
|
||||
<ul>
|
||||
<li><a href="https://spec.polkadot.network/id-cryptography-encoding#defn-option-type">Optional</a> continuation cursor. Absence of the cursor denotes the end of the operation;</li>
|
||||
<li>32-bit unsigned integer representing the number of items removed from the backend DB;</li>
|
||||
<li>32-bit unsigned integer representing the number of unique keys removes, including overlay;</li>
|
||||
<li>32-bit unsigned integer representing the number of iterations done.</li>
|
||||
</ul>
|
||||
<p>The size of the output buffer must be determined at the compile time. If the SCALE-encoded data do not fit into the buffer, the data are silently trucated. The caller may determine the truncation by checking the value length data contained in the SCALE-encoded data header.</p>
|
||||
<pre><code class="language-wat">(func $ext_crypto_ed25519_sign_version_2
|
||||
(param $key_type_id i32) (param $key i32) (param $msg i64) (param $out i32) (return i32))
|
||||
(func $ext_crypto_sr25519_sign_version_2
|
||||
(param $key_type_id i32) (param $key i32) (param $msg i64) (param $out i32) (return i32))
|
||||
func $ext_crypto_ecdsa_sign_version_2
|
||||
(func $ext_crypto_ecdsa_sign_version_2
|
||||
(param $key_type_id i32) (param $key i32) (param $msg i64) (param $out i32) (return i32))
|
||||
(func $ext_crypto_ecdsa_sign_prehashed_version_2
|
||||
(param $key_type_id i32) (param $key i32) (param $msg i64) (param $out i32) (return i64))
|
||||
|
||||
@@ -292,23 +292,27 @@
|
||||
<p>The version 1 of these functions has been taken as a base rather than the version 2, as a <a href="https://github.com/w3f/PPPs/pull/6">PPP#6</a> deprecating the version 2 of these functions has previously been accepted.</p>
|
||||
<pre><code class="language-wat">(func $ext_storage_clear_prefix_version_3
|
||||
(param $maybe_prefix i64) (param $maybe_limit i64)
|
||||
(param $maybe_cursor_in_out i64) (param $backend_out i32)
|
||||
(param $unique_out i32) (param $loops_out i32) (return i32))
|
||||
(param $maybe_cursor_in i64) (param $removal_results_out i32))
|
||||
(func $ext_default_child_storage_clear_prefix_version_3
|
||||
(param $child_storage_key i64) (param $prefix i64) (param $maybe_limit i64)
|
||||
(param $maybe_cursor_in_out i64) (param $backend_out i32)
|
||||
(param $unique_out i32) (param $loops_out i32) (return i32))
|
||||
(param $maybe_cursor_in i64) (param $removal_results_out i32))
|
||||
(func $ext_default_child_storage_kill_version_4
|
||||
(param $child_storage_key i64) (param $maybe_limit i64)
|
||||
(param $maybe_cursor_in_out i64) (param $backend_out i32)
|
||||
(param $unique_out i32) (param $loops_out i32) (return i32))
|
||||
(param $maybe_cursor_in i64) (param $removal_results_out i32))
|
||||
</code></pre>
|
||||
<p>These functions amend already implemented but still unused functions introduced by <a href="https://github.com/w3f/PPPs/pull/7">PPP#7</a>, hence there's no version number change. <code>maybe_limit</code> defines the limit of backend deletions, not counting keys in the current overlay. <code>maybe_cursor_in_out</code> may be used to pass a continuation cursor. The cursor is written into the same field if the limit was reached and not all the keys were cleared; otherwise, <code>None</code> is written. (CAVEAT: It's impossible to determine appropriate buffer size; the approach is discussible). <code>backend_out</code>, <code>unique_out</code> and <code>loops_out</code> parameters contain the memory location where the output is written (respectively, the number of items removed from the backend DB; the number of unique keys removes, including overlay; the number of iterations done). Any of the output parameters may be <code>-1</code>, in which case no output is written. The functions return <code>0</code> to indicate success, or <code>1</code> if <code>maybe_cursor_in_out</code> buffer length was not enough to write the new cursor; in the latter case, <code>None</code> is written to the buffer.</p>
|
||||
<p>These functions amend already implemented but still unused functions introduced by <a href="https://github.com/w3f/PPPs/pull/7">PPP#7</a>, hence there's no version number change. <code>maybe_limit</code> defines the limit of backend deletions, not counting keys in the current overlay. <code>maybe_cursor_in</code> may be used to pass a continuation cursor. After the operation is completed, a SCALE-encoded <a href="https://spec.polkadot.network/id-cryptography-encoding#defn-varrying-data-type">varying data</a> are written to the provided output buffer. The varying data consists from the following fields, in order:</p>
|
||||
<ul>
|
||||
<li><a href="https://spec.polkadot.network/id-cryptography-encoding#defn-option-type">Optional</a> continuation cursor. Absence of the cursor denotes the end of the operation;</li>
|
||||
<li>32-bit unsigned integer representing the number of items removed from the backend DB;</li>
|
||||
<li>32-bit unsigned integer representing the number of unique keys removes, including overlay;</li>
|
||||
<li>32-bit unsigned integer representing the number of iterations done.</li>
|
||||
</ul>
|
||||
<p>The size of the output buffer must be determined at the compile time. If the SCALE-encoded data do not fit into the buffer, the data are silently trucated. The caller may determine the truncation by checking the value length data contained in the SCALE-encoded data header.</p>
|
||||
<pre><code class="language-wat">(func $ext_crypto_ed25519_sign_version_2
|
||||
(param $key_type_id i32) (param $key i32) (param $msg i64) (param $out i32) (return i32))
|
||||
(func $ext_crypto_sr25519_sign_version_2
|
||||
(param $key_type_id i32) (param $key i32) (param $msg i64) (param $out i32) (return i32))
|
||||
func $ext_crypto_ecdsa_sign_version_2
|
||||
(func $ext_crypto_ecdsa_sign_version_2
|
||||
(param $key_type_id i32) (param $key i32) (param $msg i64) (param $out i32) (return i32))
|
||||
(func $ext_crypto_ecdsa_sign_prehashed_version_2
|
||||
(param $key_type_id i32) (param $key i32) (param $msg i64) (param $out i32) (return i64))
|
||||
|
||||
+1
-1
@@ -1 +1 @@
|
||||
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","new/0149-rfc-1-renewal-adjustment.html#rfc-0149-renewal-adjustment","new/0149-rfc-1-renewal-adjustment.html#summary","new/0149-rfc-1-renewal-adjustment.html#motivation","new/0149-rfc-1-renewal-adjustment.html#stakeholders","new/0149-rfc-1-renewal-adjustment.html#explanation","new/0149-rfc-1-renewal-adjustment.html#drawbacks","new/0149-rfc-1-renewal-adjustment.html#testing-security-and-privacy","new/0149-rfc-1-renewal-adjustment.html#performance-ergonomics-and-compatibility","new/0149-rfc-1-renewal-adjustment.html#prior-art-and-references","new/0149-rfc-1-renewal-adjustment.html#future-directions-and-related-material","new/xxxx-improve-the-security-of-proof-of-possession.html#rfc-xxxx-adding-customized-mandatory-context-to-proof-of-possession-statement","new/xxxx-improve-the-security-of-proof-of-possession.html#summary","new/xxxx-improve-the-security-of-proof-of-possession.html#motivation","new/xxxx-improve-the-security-of-proof-of-possession.html#explanation","new/xxxx-improve-the-security-of-proof-of-possession.html#drawbacks","new/xxxx-improve-the-security-of-proof-of-possession.html#testing-security-and-privacy","new/xxxx-improve-the-security-of-proof-of-possession.html#performance-ergonomics-and-compatibility","new/xxxx-improve-the-security-of-proof-of-possession.html#performance","new/xxxx-improve-the-security-of-proof-of-possession.html#ergonomics","new/xxxx-improve-the-security-of-proof-of-possession.html#compatibility","new/xxxx-improve-the-security-of-proof-of-possession.html#prior-art-and-references","new/xxxx-improve-the-security-of-proof-of-possession.html#unresolved-questions","new/xxxx-improve-the-security-of-proof-of-possession.html#future-directions-and-related-material","proposed/0000-pre-elves_soft.html#rfc-0000-pre-elves-soft-concensus","proposed/0000-pre-elves_soft.html#summary","proposed/0000-pre-elves_soft.html#motivation","proposed/0000-pre-elves_soft.html#stakeholders","proposed/0000-pre-elves_soft.html#explanation","proposed/0000-pre-elves_soft.html#availability-voting","proposed/0000-pre-elves_soft.html#fork-choice","proposed/0000-pre-elves_soft.html#elves","proposed/0000-pre-elves_soft.html#fast-prunning","proposed/0000-pre-elves_soft.html#concerns-drawbacks-testing-security-and-privacy","proposed/0000-pre-elves_soft.html#performance-ergonomics-and-compatibility","proposed/0000-pre-elves_soft.html#compatibility","proposed/0000-pre-elves_soft.html#prior-art-and-references","proposed/0000-pre-elves_soft.html#unresolved-questions","proposed/0000-pre-elves_soft.html#future-directions-and-related-material","proposed/0000-pre-elves_soft.html#sassafras","proposed/0000-pre-elves_soft.html#thresahold-randomness","proposed/0000-pre-elves_soft.html#mid-strenght-concensus","proposed/0000-pre-elves_soft.html#avoid-wall-clock-time","proposed/0000-pre-elves_soft.html#partial-relay-chain-blocks","proposed/0017-coretime-market-redesign.html#rfc-0017-coretime-market-redesign","proposed/0017-coretime-market-redesign.html#summary","proposed/0017-coretime-market-redesign.html#motivation","proposed/0017-coretime-market-redesign.html#stakeholders","proposed/0017-coretime-market-redesign.html#explanation","proposed/0017-coretime-market-redesign.html#overview","proposed/0017-coretime-market-redesign.html#market-period-14-days","proposed/0017-coretime-market-redesign.html#renewal-period-7-days","proposed/0017-coretime-market-redesign.html#reserve-price-adjustment","proposed/0017-coretime-market-redesign.html#settlement-period--secondary-market-7-days","proposed/0017-coretime-market-redesign.html#additional-considerations","proposed/0017-coretime-market-redesign.html#new-track-coretime-admin","proposed/0017-coretime-market-redesign.html#transition-to-the-new-model","proposed/0017-coretime-market-redesign.html#details-on-some-mechanics","proposed/0017-coretime-market-redesign.html#implications","proposed/0017-coretime-market-redesign.html#appendix","proposed/0017-coretime-market-redesign.html#further-discussion-points","proposed/0017-coretime-market-redesign.html#insights-clearing-price-dutch-auctions","proposed/0017-coretime-market-redesign.html#prior-art-and-references","proposed/0117-unbrick-collective.html#rfc-0117-the-unbrick-collective","proposed/0117-unbrick-collective.html#summary","proposed/0117-unbrick-collective.html#motivation","proposed/0117-unbrick-collective.html#stakeholders","proposed/0117-unbrick-collective.html#explanation","proposed/0117-unbrick-collective.html#the-collective","proposed/0117-unbrick-collective.html#the-unbrick-process","proposed/0117-unbrick-collective.html#belonging-to-the-collective","proposed/0117-unbrick-collective.html#drawbacks","proposed/0117-unbrick-collective.html#testing-security-and-privacy","proposed/0117-unbrick-collective.html#performance-ergonomics-and-compatibility","proposed/0117-unbrick-collective.html#performance","proposed/0117-unbrick-collective.html#ergonomics","proposed/011Line truncated
|
||||
Object.assign(window.search, {"doc_urls":["introduction.html#introduction","new/0149-rfc-1-renewal-adjustment.html#rfc-0149-renewal-adjustment","new/0149-rfc-1-renewal-adjustment.html#summary","new/0149-rfc-1-renewal-adjustment.html#motivation","new/0149-rfc-1-renewal-adjustment.html#stakeholders","new/0149-rfc-1-renewal-adjustment.html#explanation","new/0149-rfc-1-renewal-adjustment.html#drawbacks","new/0149-rfc-1-renewal-adjustment.html#testing-security-and-privacy","new/0149-rfc-1-renewal-adjustment.html#performance-ergonomics-and-compatibility","new/0149-rfc-1-renewal-adjustment.html#prior-art-and-references","new/0149-rfc-1-renewal-adjustment.html#future-directions-and-related-material","new/xxxx-improve-the-security-of-proof-of-possession.html#rfc-xxxx-adding-customized-mandatory-context-to-proof-of-possession-statement","new/xxxx-improve-the-security-of-proof-of-possession.html#summary","new/xxxx-improve-the-security-of-proof-of-possession.html#motivation","new/xxxx-improve-the-security-of-proof-of-possession.html#explanation","new/xxxx-improve-the-security-of-proof-of-possession.html#drawbacks","new/xxxx-improve-the-security-of-proof-of-possession.html#testing-security-and-privacy","new/xxxx-improve-the-security-of-proof-of-possession.html#performance-ergonomics-and-compatibility","new/xxxx-improve-the-security-of-proof-of-possession.html#performance","new/xxxx-improve-the-security-of-proof-of-possession.html#ergonomics","new/xxxx-improve-the-security-of-proof-of-possession.html#compatibility","new/xxxx-improve-the-security-of-proof-of-possession.html#prior-art-and-references","new/xxxx-improve-the-security-of-proof-of-possession.html#unresolved-questions","new/xxxx-improve-the-security-of-proof-of-possession.html#future-directions-and-related-material","proposed/0000-pre-elves_soft.html#rfc-0000-pre-elves-soft-concensus","proposed/0000-pre-elves_soft.html#summary","proposed/0000-pre-elves_soft.html#motivation","proposed/0000-pre-elves_soft.html#stakeholders","proposed/0000-pre-elves_soft.html#explanation","proposed/0000-pre-elves_soft.html#availability-voting","proposed/0000-pre-elves_soft.html#fork-choice","proposed/0000-pre-elves_soft.html#elves","proposed/0000-pre-elves_soft.html#fast-prunning","proposed/0000-pre-elves_soft.html#concerns-drawbacks-testing-security-and-privacy","proposed/0000-pre-elves_soft.html#performance-ergonomics-and-compatibility","proposed/0000-pre-elves_soft.html#compatibility","proposed/0000-pre-elves_soft.html#prior-art-and-references","proposed/0000-pre-elves_soft.html#unresolved-questions","proposed/0000-pre-elves_soft.html#future-directions-and-related-material","proposed/0000-pre-elves_soft.html#sassafras","proposed/0000-pre-elves_soft.html#thresahold-randomness","proposed/0000-pre-elves_soft.html#mid-strenght-concensus","proposed/0000-pre-elves_soft.html#avoid-wall-clock-time","proposed/0000-pre-elves_soft.html#partial-relay-chain-blocks","proposed/0017-coretime-market-redesign.html#rfc-0017-coretime-market-redesign","proposed/0017-coretime-market-redesign.html#summary","proposed/0017-coretime-market-redesign.html#motivation","proposed/0017-coretime-market-redesign.html#stakeholders","proposed/0017-coretime-market-redesign.html#explanation","proposed/0017-coretime-market-redesign.html#overview","proposed/0017-coretime-market-redesign.html#market-period-14-days","proposed/0017-coretime-market-redesign.html#renewal-period-7-days","proposed/0017-coretime-market-redesign.html#reserve-price-adjustment","proposed/0017-coretime-market-redesign.html#settlement-period--secondary-market-7-days","proposed/0017-coretime-market-redesign.html#additional-considerations","proposed/0017-coretime-market-redesign.html#new-track-coretime-admin","proposed/0017-coretime-market-redesign.html#transition-to-the-new-model","proposed/0017-coretime-market-redesign.html#details-on-some-mechanics","proposed/0017-coretime-market-redesign.html#implications","proposed/0017-coretime-market-redesign.html#appendix","proposed/0017-coretime-market-redesign.html#further-discussion-points","proposed/0017-coretime-market-redesign.html#insights-clearing-price-dutch-auctions","proposed/0017-coretime-market-redesign.html#prior-art-and-references","proposed/0117-unbrick-collective.html#rfc-0117-the-unbrick-collective","proposed/0117-unbrick-collective.html#summary","proposed/0117-unbrick-collective.html#motivation","proposed/0117-unbrick-collective.html#stakeholders","proposed/0117-unbrick-collective.html#explanation","proposed/0117-unbrick-collective.html#the-collective","proposed/0117-unbrick-collective.html#the-unbrick-process","proposed/0117-unbrick-collective.html#belonging-to-the-collective","proposed/0117-unbrick-collective.html#drawbacks","proposed/0117-unbrick-collective.html#testing-security-and-privacy","proposed/0117-unbrick-collective.html#performance-ergonomics-and-compatibility","proposed/0117-unbrick-collective.html#performance","proposed/0117-unbrick-collective.html#ergonomics","proposed/011Line truncated
|
||||
+1
-1
@@ -1 +1 @@
|
||||
{"doc_urls":["introduction.html#introduction","new/0149-rfc-1-renewal-adjustment.html#rfc-0149-renewal-adjustment","new/0149-rfc-1-renewal-adjustment.html#summary","new/0149-rfc-1-renewal-adjustment.html#motivation","new/0149-rfc-1-renewal-adjustment.html#stakeholders","new/0149-rfc-1-renewal-adjustment.html#explanation","new/0149-rfc-1-renewal-adjustment.html#drawbacks","new/0149-rfc-1-renewal-adjustment.html#testing-security-and-privacy","new/0149-rfc-1-renewal-adjustment.html#performance-ergonomics-and-compatibility","new/0149-rfc-1-renewal-adjustment.html#prior-art-and-references","new/0149-rfc-1-renewal-adjustment.html#future-directions-and-related-material","new/xxxx-improve-the-security-of-proof-of-possession.html#rfc-xxxx-adding-customized-mandatory-context-to-proof-of-possession-statement","new/xxxx-improve-the-security-of-proof-of-possession.html#summary","new/xxxx-improve-the-security-of-proof-of-possession.html#motivation","new/xxxx-improve-the-security-of-proof-of-possession.html#explanation","new/xxxx-improve-the-security-of-proof-of-possession.html#drawbacks","new/xxxx-improve-the-security-of-proof-of-possession.html#testing-security-and-privacy","new/xxxx-improve-the-security-of-proof-of-possession.html#performance-ergonomics-and-compatibility","new/xxxx-improve-the-security-of-proof-of-possession.html#performance","new/xxxx-improve-the-security-of-proof-of-possession.html#ergonomics","new/xxxx-improve-the-security-of-proof-of-possession.html#compatibility","new/xxxx-improve-the-security-of-proof-of-possession.html#prior-art-and-references","new/xxxx-improve-the-security-of-proof-of-possession.html#unresolved-questions","new/xxxx-improve-the-security-of-proof-of-possession.html#future-directions-and-related-material","proposed/0000-pre-elves_soft.html#rfc-0000-pre-elves-soft-concensus","proposed/0000-pre-elves_soft.html#summary","proposed/0000-pre-elves_soft.html#motivation","proposed/0000-pre-elves_soft.html#stakeholders","proposed/0000-pre-elves_soft.html#explanation","proposed/0000-pre-elves_soft.html#availability-voting","proposed/0000-pre-elves_soft.html#fork-choice","proposed/0000-pre-elves_soft.html#elves","proposed/0000-pre-elves_soft.html#fast-prunning","proposed/0000-pre-elves_soft.html#concerns-drawbacks-testing-security-and-privacy","proposed/0000-pre-elves_soft.html#performance-ergonomics-and-compatibility","proposed/0000-pre-elves_soft.html#compatibility","proposed/0000-pre-elves_soft.html#prior-art-and-references","proposed/0000-pre-elves_soft.html#unresolved-questions","proposed/0000-pre-elves_soft.html#future-directions-and-related-material","proposed/0000-pre-elves_soft.html#sassafras","proposed/0000-pre-elves_soft.html#thresahold-randomness","proposed/0000-pre-elves_soft.html#mid-strenght-concensus","proposed/0000-pre-elves_soft.html#avoid-wall-clock-time","proposed/0000-pre-elves_soft.html#partial-relay-chain-blocks","proposed/0017-coretime-market-redesign.html#rfc-0017-coretime-market-redesign","proposed/0017-coretime-market-redesign.html#summary","proposed/0017-coretime-market-redesign.html#motivation","proposed/0017-coretime-market-redesign.html#stakeholders","proposed/0017-coretime-market-redesign.html#explanation","proposed/0017-coretime-market-redesign.html#overview","proposed/0017-coretime-market-redesign.html#market-period-14-days","proposed/0017-coretime-market-redesign.html#renewal-period-7-days","proposed/0017-coretime-market-redesign.html#reserve-price-adjustment","proposed/0017-coretime-market-redesign.html#settlement-period--secondary-market-7-days","proposed/0017-coretime-market-redesign.html#additional-considerations","proposed/0017-coretime-market-redesign.html#new-track-coretime-admin","proposed/0017-coretime-market-redesign.html#transition-to-the-new-model","proposed/0017-coretime-market-redesign.html#details-on-some-mechanics","proposed/0017-coretime-market-redesign.html#implications","proposed/0017-coretime-market-redesign.html#appendix","proposed/0017-coretime-market-redesign.html#further-discussion-points","proposed/0017-coretime-market-redesign.html#insights-clearing-price-dutch-auctions","proposed/0017-coretime-market-redesign.html#prior-art-and-references","proposed/0117-unbrick-collective.html#rfc-0117-the-unbrick-collective","proposed/0117-unbrick-collective.html#summary","proposed/0117-unbrick-collective.html#motivation","proposed/0117-unbrick-collective.html#stakeholders","proposed/0117-unbrick-collective.html#explanation","proposed/0117-unbrick-collective.html#the-collective","proposed/0117-unbrick-collective.html#the-unbrick-process","proposed/0117-unbrick-collective.html#belonging-to-the-collective","proposed/0117-unbrick-collective.html#drawbacks","proposed/0117-unbrick-collective.html#testing-security-and-privacy","proposed/0117-unbrick-collective.html#performance-ergonomics-and-compatibility","proposed/0117-unbrick-collective.html#performance","proposed/0117-unbrick-collective.html#ergonomics","proposed/0117-unbrick-collective.html#comLine truncated
|
||||
{"doc_urls":["introduction.html#introduction","new/0149-rfc-1-renewal-adjustment.html#rfc-0149-renewal-adjustment","new/0149-rfc-1-renewal-adjustment.html#summary","new/0149-rfc-1-renewal-adjustment.html#motivation","new/0149-rfc-1-renewal-adjustment.html#stakeholders","new/0149-rfc-1-renewal-adjustment.html#explanation","new/0149-rfc-1-renewal-adjustment.html#drawbacks","new/0149-rfc-1-renewal-adjustment.html#testing-security-and-privacy","new/0149-rfc-1-renewal-adjustment.html#performance-ergonomics-and-compatibility","new/0149-rfc-1-renewal-adjustment.html#prior-art-and-references","new/0149-rfc-1-renewal-adjustment.html#future-directions-and-related-material","new/xxxx-improve-the-security-of-proof-of-possession.html#rfc-xxxx-adding-customized-mandatory-context-to-proof-of-possession-statement","new/xxxx-improve-the-security-of-proof-of-possession.html#summary","new/xxxx-improve-the-security-of-proof-of-possession.html#motivation","new/xxxx-improve-the-security-of-proof-of-possession.html#explanation","new/xxxx-improve-the-security-of-proof-of-possession.html#drawbacks","new/xxxx-improve-the-security-of-proof-of-possession.html#testing-security-and-privacy","new/xxxx-improve-the-security-of-proof-of-possession.html#performance-ergonomics-and-compatibility","new/xxxx-improve-the-security-of-proof-of-possession.html#performance","new/xxxx-improve-the-security-of-proof-of-possession.html#ergonomics","new/xxxx-improve-the-security-of-proof-of-possession.html#compatibility","new/xxxx-improve-the-security-of-proof-of-possession.html#prior-art-and-references","new/xxxx-improve-the-security-of-proof-of-possession.html#unresolved-questions","new/xxxx-improve-the-security-of-proof-of-possession.html#future-directions-and-related-material","proposed/0000-pre-elves_soft.html#rfc-0000-pre-elves-soft-concensus","proposed/0000-pre-elves_soft.html#summary","proposed/0000-pre-elves_soft.html#motivation","proposed/0000-pre-elves_soft.html#stakeholders","proposed/0000-pre-elves_soft.html#explanation","proposed/0000-pre-elves_soft.html#availability-voting","proposed/0000-pre-elves_soft.html#fork-choice","proposed/0000-pre-elves_soft.html#elves","proposed/0000-pre-elves_soft.html#fast-prunning","proposed/0000-pre-elves_soft.html#concerns-drawbacks-testing-security-and-privacy","proposed/0000-pre-elves_soft.html#performance-ergonomics-and-compatibility","proposed/0000-pre-elves_soft.html#compatibility","proposed/0000-pre-elves_soft.html#prior-art-and-references","proposed/0000-pre-elves_soft.html#unresolved-questions","proposed/0000-pre-elves_soft.html#future-directions-and-related-material","proposed/0000-pre-elves_soft.html#sassafras","proposed/0000-pre-elves_soft.html#thresahold-randomness","proposed/0000-pre-elves_soft.html#mid-strenght-concensus","proposed/0000-pre-elves_soft.html#avoid-wall-clock-time","proposed/0000-pre-elves_soft.html#partial-relay-chain-blocks","proposed/0017-coretime-market-redesign.html#rfc-0017-coretime-market-redesign","proposed/0017-coretime-market-redesign.html#summary","proposed/0017-coretime-market-redesign.html#motivation","proposed/0017-coretime-market-redesign.html#stakeholders","proposed/0017-coretime-market-redesign.html#explanation","proposed/0017-coretime-market-redesign.html#overview","proposed/0017-coretime-market-redesign.html#market-period-14-days","proposed/0017-coretime-market-redesign.html#renewal-period-7-days","proposed/0017-coretime-market-redesign.html#reserve-price-adjustment","proposed/0017-coretime-market-redesign.html#settlement-period--secondary-market-7-days","proposed/0017-coretime-market-redesign.html#additional-considerations","proposed/0017-coretime-market-redesign.html#new-track-coretime-admin","proposed/0017-coretime-market-redesign.html#transition-to-the-new-model","proposed/0017-coretime-market-redesign.html#details-on-some-mechanics","proposed/0017-coretime-market-redesign.html#implications","proposed/0017-coretime-market-redesign.html#appendix","proposed/0017-coretime-market-redesign.html#further-discussion-points","proposed/0017-coretime-market-redesign.html#insights-clearing-price-dutch-auctions","proposed/0017-coretime-market-redesign.html#prior-art-and-references","proposed/0117-unbrick-collective.html#rfc-0117-the-unbrick-collective","proposed/0117-unbrick-collective.html#summary","proposed/0117-unbrick-collective.html#motivation","proposed/0117-unbrick-collective.html#stakeholders","proposed/0117-unbrick-collective.html#explanation","proposed/0117-unbrick-collective.html#the-collective","proposed/0117-unbrick-collective.html#the-unbrick-process","proposed/0117-unbrick-collective.html#belonging-to-the-collective","proposed/0117-unbrick-collective.html#drawbacks","proposed/0117-unbrick-collective.html#testing-security-and-privacy","proposed/0117-unbrick-collective.html#performance-ergonomics-and-compatibility","proposed/0117-unbrick-collective.html#performance","proposed/0117-unbrick-collective.html#ergonomics","proposed/0117-unbrick-collective.html#comLine truncated
|
||||
Reference in new issue
Block a user