-
Notifications
You must be signed in to change notification settings - Fork 22
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
1st draft of EVM based address aliasing specification #29
Conversation
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 |
See issue #24