# Summary

Bifrost secured the lease for 16-23 through crowdloan paraid: 3356. Yet, Bifrost's current lease for para 2030 is for lease 15. Given there is no overlap between periods 15 and 16-23, an interruption in block production for para 2030 during the lease swap is inevitable. Even in the most ideal result, para 2030 will still face a pause in block production for approximately 4-8 hours.

In summary, we suggest executing in the Lease Admin governance track, clearing the lease of para 3356, and adding the corresponding lease period to para 2030.

# Regarding the Para Swap

Tests have shown that the para swap solution cannot effectively avoid the situation of block stopping (or the solution will lead to an increase in live slots and must be executed by root track governance and other problems)

# Suggested Solution

After testing, we suggest using the Lease Admin Track to clear Lease 16-23 for para 3356, and then add these Leases to para 2030. Here are the detailed steps:

Call data:

`0x1a020847011c0d00004700ee0700006d6f646c70792f6366756e64520000000000000000000000000000000000000072ee6b882837010000000000000000001000000008000000`

![Untitled](https://i.ibb.co/7kWgpNS/Untitled.png)

Construction Analysis:

- slots.clearAllLeases: Clear all leases held by Bifrost para 3356: lease16-23.
    - (This process will release the reserved DOT in the corresponding Crowdloan.)

- slots.forceLeases: Append the leases 16-23 cleared in the previous step to the Bifrost para 2030.
    - (This process will re-reserve the DOTs released in the previous Crowdloan.)

- After governance execution, the Bifrost parachain will obtain a complete and continuous renewal lease and no further operations are needed, while 3356 will be scrapped.

### Governance Track

The main parameters of Lease Admin Track are:

- Concurrent capacity: 10
- **Confirm Period: 3 hrs**
- **Prepare Period: 2 hrs**
- **Decision Period: 28 days**
- **Min Enact Period: 10 mins**
- **Decision Deposit: 5000 DOT**

This track has a larger capacity than the root track (which allows for immediate governance initiation to avoid not having enough time to complete governance), and requires less DOT to be locked up for initiating governance (5000 DOT).

### Governance Logic Analysis

This governance action will destroy the 3356 leasing rights of Bifrost and reissue them in 2030. The entire process only involves a reasonable transfer within the sovereignty of Bifrost, without generating extra relay chain resource consumption and waste. This operation is carried out to avoid the situation where the ecological parachain users encounter the suspension of service due to the parachain stop producing blocks, we believe that the initiation reason is in line with the interests of users and the community.

# Potential Risk Analysis

Due to the manual modification of the lease, it is uncertain whether it will affect the normal expiration and unlocking of the two crowdloans of 2030 & 3356. We preliminarily judge that the unlocking of the crowdloan is an independent logic, and after the expiration, the DOT of the corresponding fund can also be unlocked normally with the expiration of the Lease. Therefore, it is assessed that it will not affect the normal unlocking. However, further confirmation from Parity developers is still needed.

Transfer the Lease of Bifrost Parachain 3356 to Bifrost Parachain 2030 to avoid downtime

Governance

- **Problem Statement & Audience:** Bifrost faces a block production interruption during a lease swap from para 3356 to para 2030, affecting users and the community.
- **Significance:** The proposed solution aims to avoid block production pauses and ensure continuous service for Bifrost parachain users.
- **Proposed Solution:** Use the Lease Admin Track to clear and transfer leases from para 3356 to para 2030 to maintain uninterrupted block production.
- **Expected Outcomes:** Seamless transition of leases, continuous block production, and enhanced user experience for Bifrost parachain users.

#524 Transfer the Lease of Bifrost Parachain 3356 to Bifrost Parachain 2030 to avoid downtime

No Active Proposals