Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

General transactions in extrinsic format #84

Merged
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add table for extrinsic type bit repr
Signed-off-by: georgepisaltu <[email protected]>
  • Loading branch information
georgepisaltu committed Mar 13, 2024
commit f03607ab3b958cf01573fe173c27b23ca381d7c3
9 changes: 8 additions & 1 deletion text/0084-general-transaction-extrinsic-format.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,14 @@ An extrinsic is currently encoded as one byte to identify the extrinsic type and

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 |

## Drawbacks

Expand Down