From f939d757a8732be4726b9f1bd517d9f2fb9f7cc9 Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Tue, 25 Jul 2023 11:49:18 +0100 Subject: [PATCH] Update text/0001-agile-coretime.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Bastian Köcher --- text/0001-agile-coretime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0001-agile-coretime.md b/text/0001-agile-coretime.md index 81e7332..a99a521 100644 --- a/text/0001-agile-coretime.md +++ b/text/0001-agile-coretime.md @@ -340,7 +340,7 @@ FACTOR(T) := 2 - T #### Instantaneous Price Progression -This proposal assumes the existence of a Relay-chain-based price-setting mechanism for the Instantaneous Coretime Market which alters from block to block, taking into account several parameters: the last price, the size of the Instantaneous Coretime Pool (in terms of cores per block) and the amount of Instantaneous Coretime waiting for processing (in terms of Core-blocks queued). +This proposal assumes the existence of a Relay-chain-based price-setting mechanism for the Instantaneous Coretime Market which alters from block to block, taking into account several parameters: the last price, the size of the Instantaneous Coretime Pool (in terms of cores per Relay-chain block) and the amount of Instantaneous Coretime waiting for processing (in terms of Core-blocks queued). The ideal situation is to have the size of the Instantaneous Coretime Pool be equal to some factor of the Instantaneous Coretime waiting. This allows all Instantaneous Coretime sales to be processed with some limited latency while giving limited flexibility over ordering to the Relay-chain apparatus which is needed for efficient operation.