Skip to content

Commit a095801

Browse files
committed
wip: Unlock parachain
1 parent f4d07b0 commit a095801

File tree

3 files changed

+57
-15
lines changed

3 files changed

+57
-15
lines changed

develop/parachains/maintenance/.pages

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,3 +5,4 @@ nav:
55
- 'Storage Migrations': storage-migrations.md
66
# - 'Debug Production Issues': debug-prod-issues.md
77
- 'Runtime Metrics and Monitoring': runtime-metrics-monitoring.md
8+
- 'Unlock Parachain': unlock-parachain.md
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
title: Unlock Parachain
3+
description: TODO
4+
---
5+
6+
# Unlock Parachain
7+
8+
## Introduction
9+
10+
Parachain locks are designed in such way to ensure the decentralization of parachains. If parachains are not locked when it should be, it could introduce centralization risk for new parachains.
11+
12+
A parachain can be locked only with following conditions:
13+
14+
- Relaychain governance MUST be able to lock any parachain.
15+
- A parachain MUST be able to lock its own lock.
16+
- A parachain manager SHOULD be able to lock the parachain.
17+
- A parachain SHOULD be locked when it successfully produced a block for the first time.
18+
19+
A parachain can be unlocked only with following conditions:
20+
- Relaychain governance MUST be able to unlock any parachain.
21+
- A parachain MUST be able to unlock its own lock.
22+
23+
## Check if a Parachain is Locked
24+
25+
To check if a parachain is locked,

llms.txt

Lines changed: 31 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,7 @@ Doc-Page: https://docs.polkadot.com/develop/parachains/maintenance/
3030
Doc-Page: https://docs.polkadot.com/develop/parachains/maintenance/runtime-metrics-monitoring/
3131
Doc-Page: https://docs.polkadot.com/develop/parachains/maintenance/runtime-upgrades/
3232
Doc-Page: https://docs.polkadot.com/develop/parachains/maintenance/storage-migrations/
33+
Doc-Page: https://docs.polkadot.com/develop/parachains/maintenance/unlock-parachain/
3334
Doc-Page: https://docs.polkadot.com/develop/parachains/testing/benchmarking/
3435
Doc-Page: https://docs.polkadot.com/develop/parachains/testing/
3536
Doc-Page: https://docs.polkadot.com/develop/parachains/testing/mock-runtime/
@@ -692,21 +693,7 @@ decl_test_parachains! {
692693
- [**`decl_test_networks`**](https://github.com/paritytech/polkadot-sdk/blob/{{dependencies.repositories.polkadot_sdk.version}}/cumulus/xcm/xcm-emulator/src/lib.rs#L916){target=\_blank} - defines a testing network with relay chains, parachains, and bridges, implementing message transport and processing logic. Example:
693694

694695
```rust
695-
decl_test_networks! {
696-
pub struct WestendMockNet {
697-
relay_chain = Westend,
698-
parachains = vec![
699-
AssetHubWestend,
700-
BridgeHubWestend,
701-
CollectivesWestend,
702-
CoretimeWestend,
703-
PeopleWestend,
704-
PenpalA,
705-
PenpalB,
706-
],
707-
bridge = ()
708-
},
709-
}
696+
Failed to fetch snippet after 3 attempts
710697
```
711698

712699
By leveraging these macros, developers can customize their testing networks by defining relay chains and parachains tailored to their needs. For guidance on implementing a mock runtime for a Polkadot SDK-based chain, refer to the [Pallet Testing](/develop/parachains/testing/pallet-testing/){target=\_blank} article.
@@ -5610,6 +5597,35 @@ The primary trade-off is increased implementation complexity, as you must manage
56105597
For a complete implementation example of multi-block migrations, refer to the [official example](https://github.com/paritytech/polkadot-sdk/tree/{{dependencies.repositories.polkadot_sdk.version}}/substrate/frame/examples/multi-block-migrations){target=\_blank} in the Polkadot SDK.
56115598
--- END CONTENT ---
56125599

5600+
Doc-Content: https://docs.polkadot.com/develop/parachains/maintenance/unlock-parachain/
5601+
--- BEGIN CONTENT ---
5602+
---
5603+
title: Unlock Parachain
5604+
description: TODO
5605+
---
5606+
5607+
# Unlock Parachain
5608+
5609+
## Introduction
5610+
5611+
Parachain locks are designed in such way to ensure the decentralization of parachains. If parachains are not locked when it should be, it could introduce centralization risk for new parachains.
5612+
5613+
A parachain can be locked only with following conditions:
5614+
5615+
- Relaychain governance MUST be able to lock any parachain.
5616+
- A parachain MUST be able to lock its own lock.
5617+
- A parachain manager SHOULD be able to lock the parachain.
5618+
- A parachain SHOULD be locked when it successfully produced a block for the first time.
5619+
5620+
A parachain can be unlocked only with following conditions:
5621+
- Relaychain governance MUST be able to unlock any parachain.
5622+
- A parachain MUST be able to unlock its own lock.
5623+
5624+
## Check if a Parachain is Locked
5625+
5626+
To check if a parachain is locked,
5627+
--- END CONTENT ---
5628+
56135629
Doc-Content: https://docs.polkadot.com/develop/parachains/testing/benchmarking/
56145630
--- BEGIN CONTENT ---
56155631
---

0 commit comments

Comments
 (0)