| Start Date | 12 March 2024 |
| Description | Support more extrinsic types by updating the extrinsic format |
@@ -221,7 +221,14 @@ detailing proposed changes to the technical implementation of the Polkadot netwo
An extrinsic is currently encoded as one byte to identify the extrinsic type and version. This RFC aims to change the interpretation of this byte regarding the reserved bits for the extrinsic type and version. In the following explanation, bits represented using T make up the extrinsic type and bits represented using V make up the extrinsic version.
Currently, the bit allocation within the leading encoded byte is 0bTVVV_VVVV. In practice in the Polkadot ecosystem, the leading byte would be 0bT000_0100 as the version has been equal to 4 for a long time.
-This RFC proposes for the bit allocation to change to 0bTTVV_VVVV.
+This RFC proposes for the bit allocation to change to 0bTTVV_VVVV. As a result, the extrinsic type bit representation would change as follows:
+| bits | type |
+| 00 | unsigned |
+| 10 | signed |
+| 01 | reserved |
+| 11 | reserved |
+
+
This change would reduce the maximum possible transaction version from the current 127 to 63. In order to bypass the new, lower limit, the extrinsic format would have to change again.
diff --git a/proposed/0004-remove-unnecessary-allocator-usage.html b/proposed/0004-remove-unnecessary-allocator-usage.html
index 7ed5498..53e49d4 100644
--- a/proposed/0004-remove-unnecessary-allocator-usage.html
+++ b/proposed/0004-remove-unnecessary-allocator-usage.html
@@ -90,7 +90,7 @@
@@ -443,7 +443,7 @@ This would remove the possibility to synchronize older blocks, which is probably