1st draft of EVM based address aliasing specification #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Arbitrum and Optimism use an offset of |
- removed superfluous file - updated `offsetAlias` definition based on 9/21 WG meeting - added 3 new requirements based on 9/21 WG meeting - minor editorial updates such as links
- added requirement on the order of `offsetAlias`es to form an `addressAlias` - minor editorial update
`chainId` must be of uniform length to enable systematic treamtment of addressalia by developers. - Modified R4 to give the length constraints in bytes - added a new R5 for `chainId` padding with zeros - updated requirements numbering - updated examples with new zero padding
1. Reduce chainId size encoded to 8 bytes 2. Add another figure to visually exemplify multi-chain inheritance from l1 -> L2 -> L3
- Added security considerations for EOA and Smart contract addresses used in aliasing as discussed during the last two WG meetings - Added definition of externally owned account into the glossary - Updated participant list (please, add yourself if you were missed)
|
I would recommend including the checksum protections of the standard address across the aliases. The address is compared against the raw binary keccak-256 hash of the address bytes, and where there are letters in the same corresponding place as a “1” bit, the letter is capitalized. This helps with random RAM errors and with human readability. Full spec: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-55.md |
- Incorporated comment by @realcodywburns - added reference - fixed a reference link
…nternationalization recommendation per PGB requirement for a full Draft Standard
|
@Therecanbeonlyone1969 approved |
Therecanbeonlyone1969
requested review from
tasdienes
and removed request for
kthomas
tasdienes
approved these changes
Feb 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See issue #24