In referendum 1161, the Coretime Chain was configured and the sales started. Unfortunately the wrong units were used in the call to start the sales. This means that the sale base price is 1 nanoDOT, instead of 10 DOT.
This referendum simply sets the state for the <code>sale_info</code> to change both the <code>end_price</code> and <code>sellout_price</code> from 10 to 100,000,000,000 via an XCM Transact. By this referendum passing before the interlude ends, the current sale will be unaffected.
This is a high priority which must pass within 6.5 days to ensure the 5 cores on the open market are not sold at this unintended low price. Therefore tidying up the other incorrect values in state is put off to another referendum.

- Problem Statement: Incorrect units used in the call to start sales in Coretime Chain, affecting the sale base price.
- Significance: High priority to prevent 5 cores from being sold at an unintended low price.
- Proposed Solution: Change end_price and sellout_price from 10 to 100,000,000,000 via an XCM Transact.
- Expected Outcomes: Prevent unintended low-price sales, ensuring the correct pricing for the 5 cores on the open market.

#1172 [Whitelisted Caller] Fix incorrect price for first coretime sale

No Active Proposals