Don't generate the consensusEngine field in chain specs (#10303)

paritytech · Nov 19, 2021 · 34bc246 · 34bc246
1 parent 439af98
commit 34bc246
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 2 deletions.
diff --git a/substrate/client/chain-spec/res/chain_spec.json b/substrate/client/chain-spec/res/chain_spec.json
@@ -19,7 +19,6 @@
 		["wss://telemetry.polkadot.io/submit/", 0]
 	],
 	"protocolId": "fir",
-	"consensusEngine": null,
 	"genesis": {
 		"raw": [
 			{

diff --git a/substrate/client/chain-spec/res/chain_spec2.json b/substrate/client/chain-spec/res/chain_spec2.json
@@ -19,7 +19,6 @@
 		["wss://telemetry.polkadot.io/submit/", 0]
 	],
 	"protocolId": "fir",
-	"consensusEngine": null,
 	"myProperty": "Test Extension",
 	"genesis": {
 		"raw": [

diff --git a/substrate/client/chain-spec/src/chain_spec.rs b/substrate/client/chain-spec/src/chain_spec.rs
@@ -168,6 +168,7 @@ struct ClientSpec<E> {
 	#[serde(flatten)]
 	extensions: E,
 	// Never used, left only for backward compatibility.
+	#[serde(default, skip_serializing)]
 	consensus_engine: (),
 	#[serde(skip_serializing)]
 	#[allow(unused)]