This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Use Extensible Multiaddress in all Polkadot Runtimes #2126
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a breaking change for the transaction version. cc @s3krit @joepetrowski
This PR introduces the
Multiaddress
type into the Polkadot, Kusama, Westend, Cumulus, and "Test" runtimes.You can learn more about the
Multiaddress
type here: paritytech/substrate#7380With this PR, all of the Polkadot runtimes are now able to more easily adopt future address formats like those provided by pallet-evm or even a future name-service pallet, or those we have not even thought of.