fix byte padding issue temp (#347)

node/src/chains/common.rs

@@ -12,7 +12,7 @@ use kate::config::{MAX_BLOCK_COLUMNS, MAX_BLOCK_ROWS};
 use primitive_types::H160;
 use sc_telemetry::TelemetryEndpoints;
 use sp_core::sr25519::Public;
-use sp_runtime::{AccountId32, Perbill};
+use sp_runtime::AccountId32;
 
 pub const PROTOCOL_ID: Option<&str> = Some("Avail");
 pub const TELEMETRY_URL: &str = "ws://telemetry.avail.tools:8001/submit";

pallets/system/src/extensions/check_weight.rs

@@ -101,7 +101,11 @@ where
 
 		// Check padded len.
 		let dynamic_block_len = DynamicBlockLength::<T>::get();
-		let padded_added_len = kate::padded_len(len as u32, dynamic_block_len.chunk_size());
+		// TODO: Make the calculation correct and not pessimistic (See kate::gridgen::EvaluationGrid::from_extrinsics for reference)
+		// We waste some space but we account that there might be, at maximum, 1 byte for padding tail delimiter, 2 bytes for every appId, 4 bytes for encoding the transaction
+		let padded_added_len =
+			kate::padded_len(len as u32, dynamic_block_len.chunk_size()).saturating_add(7u32);
+
 		all_extrinsics_len.padded = all_extrinsics_len.padded.saturating_add(padded_added_len);
 
 		let max_padded_len = BlockDimensions::new(

runtime/src/version.rs

@@ -17,7 +17,7 @@ pub const VERSION: RuntimeVersion = RuntimeVersion {
 	/// Per convention: if the runtime behavior changes, increment spec_version
 	/// and set impl_version to 0. This paramenter is typically incremented when
 	/// there's an update to the transaction_version.
-	spec_version: 15,
+	spec_version: 16,
 	/// The version of the implementation of the specification. Nodes can ignore this. It is only
 	/// used to indicate that the code is different. As long as the authoring_version and the
 	/// spec_version are the same, the code itself might have changed, but the native and Wasm