# Auctions/Slots to Coretime ## Terminology - **Overlapping Slots**. A set of slots that have one or more common Lease Periods. | paraID/LP | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | |-----------|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:--:|:--:|:--:|:--:| | paraID 1 | x | x | x | x | x | x | x | x | | | | | | | paraID 2 | | | | | | x | x | x | x | x | x | x | x | - **Future concurrent Slot**. A slot that has as a first LP the last LP of another slot + 1. | paraID/LP | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | |-----------|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:--:|:--:|:--:|:--:|:--:|:--:|:--:| | paraID 1 | x | x | x | x | x | x | x | x | | | | | | | | | | paraID 2 | | | | | | | | | x | x | x | x | x | x | x | x | - **Future non concurrent Slot**. A slot that has as a first LP the last LP of another slot + anything more than 1. | paraID/LP | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | |-----------|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:--:|:--:|:--:|:--:|:--:|:--:|:--:|:--:| | paraID 1 | x | x | x | x | x | x | x | x | | | | | | | | | | | paraID 2 | | | | | | | | | | x | x | x | x | x | x | x | x | - **Existing team, same paraID**. This is a team that uses the same paraID that it currently has to bid for a new auction. This happens if the team does not do a crowdloan to renew their slot or did not do a crowdloan to get a slot on the first place. - **Existing team, new paraID**. This is a team that registers a new paraID to bid for a new auction. This happens if the team wants to go for overlapping slots or if they are opening a crowdloan to renew their slot when they already did to get a slot on the first place. - **New team, new paraID**. A new team competing on the auction mechanism. ## Potential cases | | Overlapping Slots (1) | Future concurrent slot (2) | Future non-concurrent slot (3) | |----------------------------|-------------------|------------------------|----------------------------------| | Existing team, same paraID (a) | Not possible | No problem | Not common (would mean downtime) - Decision needed | | Existing team, new paraID (b) | Swap needed | Swap needed | Swap needed - Not common (would mean downtime) - Decision Needed | | New team, new paraID \(c) | NA | No problem | Decision needed | - **[a-1]**. The same paraID can't bid for overlapping slots, so this is not possible. [Ref](https://github.com/paritytech/polkadot-sdk/blob/eefd5fe4499515da66d088505093f75b5aa22550/polkadot/runtime/common/src/auctions.rs#L449). - **[a-2]**. A team can extend their lease by getting the lease periods of a slot that it does not have currently. This wouldn't be an issue as it would result in their current slot allocation being bigger and migration would be automatic. Would migrate automatically with coretime assuming the auction is won before coretime is enacted. - **[a-3]**. It is possible yet not probable that a team get's a slot that starts in the future, as this would mean downtime between the end of their current slot and the beginning of the next. This could happen because of a mistake or an oversight. - **[b-1]**. Very common case when teams see an opportunity of low turnout to an auction or because they are recurring to a new crowdloan as a funding mechanism. Proposal is two-fold: communicate to teams to swap before coretime is enacted and/or allow for re-assingment of migrated cores. - **[b-2]**. Very common case when teams recurr to a crowdloan as a funding mechanism to renew. Proposal is two-fold: communicate to teams to swap before coretime is enacted (if possible, might be that coretime is enacted before team can swap) and/or allow for re-assingment of migrated cores. - **[b-3]**. Similar to [a-3], however it would require a swap as well. - **[c-1]**. Overlapping slots as a concept does not apply for a new team. - **[c-2]**. Would migrate automatically with coretime assuming the auction is won before coretime is enacted. - **[c-3]**. Similar to [a-3] but with a new team so there's no risk of downtime. This also applies for an auction that's splitted between teams and teams have their first paraID sometime in the future. ### Considerations - Swap is not something that exists in coretime anymore. We should be thinking about re-assingment of tasks. - Giving future slots a core today might result in heavier load for the relay chain.