From e020237966a5127ed407a58537fc4a5222b0a8de Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Tue, 4 Jul 2023 15:16:45 +0200 Subject: [PATCH] Update RFC-0001-Agile Coretime.md Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com> --- RFC-0001-Agile Coretime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RFC-0001-Agile Coretime.md b/RFC-0001-Agile Coretime.md index 2a5e471..140defc 100644 --- a/RFC-0001-Agile Coretime.md +++ b/RFC-0001-Agile Coretime.md @@ -20,7 +20,7 @@ This proposes a periodic, sale-based method for assigning Polkadot Coretime. The The present system of allocating time for parachains on the cores of the Polkadot Ubiquitous Computer (aka "Polkadot") is through a process known as *slot auctions*. These are on-chain candle auctions which proceed for several days and result in a core being assigned to a single parachain for six months at a time up to 18 months in advance. Practically speaking, we only see two year periods being bid upon and leased. -Funds behind the bids made in the slot auctions are merely locked, not consumed or paid and become unlocked and returned to the bidder on expirt of the lease period. A means of sharing the deposit trustlessly known as a *crowdloan* is available allowing token holders to contribute to the overall deposit of a chain without any counterparty risk. +Funds behind the bids made in the slot auctions are merely locked, not consumed or paid and become unlocked and returned to the bidder on expiry of the lease period. A means of sharing the deposit trustlessly known as a *crowdloan* is available allowing token holders to contribute to the overall deposit of a chain without any counterparty risk. ### Problems