pezkuwichain/pezkuwi-subxt
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-05-31 08:41:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix polkadot-sdk CI failures (#2901)

Browse Source 
* taplo

* markdown

* publish = false

* feature propagation
This commit is contained in:
Serban Iorga
2024-03-27 17:05:13 +01:00
committed by Bastian Köcher
parent aeb3438322
commit de37ffd531
11 changed files with 40 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bridges/relays/parachains/Cargo.toml
+1
View File
@@ -4,6 +4,7 @@ version = "0.1.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2018"
license = "GPL-3.0-or-later WITH Classpath-exception-2.0"
publish = false
[lints]
workspace = true
bridges/relays/parachains/README.md
+7 -6
View File
@@ -1,7 +1,7 @@
# Parachains Finality Relay
The parachains finality relay works with two chains - source relay chain and target chain (which may be standalone
chain, relay chain or a parachain). The source chain must have the
chain, relay chain or a parachain). The source chain must have the
[`paras` pallet](https://github.com/paritytech/polkadot/tree/master/runtime/parachains/src/paras) deployed at its
runtime. The target chain must have the [bridge parachains pallet](../../modules/parachains/) deployed at its runtime.
@@ -39,11 +39,12 @@ Rococo (source relay chain) to BridgeHubWestend (target chain) parachains finali
change chain names. So the metrics are:
- `Rococo_to_BridgeHubWestend_Parachains_best_parachain_block_number_at_source` - returns best known parachain block
number, registered in the `paras` pallet at the source relay chain (Rococo in our example);
number, registered in the `paras` pallet at the source relay chain (Rococo in our example);
- `Rococo_to_BridgeHubWestend_Parachains_best_parachain_block_number_at_target` - returns best known parachain block
number, registered in the bridge parachains pallet at the target chain (BridgeHubWestend in our example).
number, registered in the bridge parachains pallet at the target chain (BridgeHubWestend in our example).
If relay operates properly, you should see that the `Rococo_to_BridgeHubWestend_Parachains_best_parachain_block_number_at_target`
tries to reach the `Rococo_to_BridgeHubWestend_Parachains_best_parachain_block_number_at_source`. And the latter one
always increases.
If relay operates properly, you should see that
the `Rococo_to_BridgeHubWestend_Parachains_best_parachain_block_number_at_target` tries to reach
the `Rococo_to_BridgeHubWestend_Parachains_best_parachain_block_number_at_source`.
And the latter one always increases.