Allow Setting of EVM Address by EOA #1082
Conversation
Signed-off-by: Nana Essilfie-Conduah <[email protected]>
✅ Deploy Preview for hedera-hips ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Nana Essilfie-Conduah <[email protected]>
| utilize that to identify them in future. The cached address could dictate balance access or other privileged access. | ||
|
|
||
| As such, an EOA that has interacted with a smart contract using their long zero address and then sets an ECDSA derived | ||
| EVM address after will be responsible for any unexpected interactions with the smart contract |
There was a problem hiding this comment.
Maybe add a suggestion that such accounts should first transfer all contract assets to the EVM address, then update the account's EVM address ?
|
|
||
| ## User stories | ||
|
|
||
| 1. As an existing account with an ED key but no EVM address alias, I would like to set an ECDSA derived EVM address |
There was a problem hiding this comment.
In this user story, wouldn't the user have to update the ED key to the new ECDSA key that corresponds with the EVM address for 'ecrecover' to function? Maybe I'm misunderstanding the phrase 'correct ecrecover functionality', or is the implication that the key is being updated as well
| 2. As an existing account with an EC key but no EVM address alias, I would like to set an ECDSA derived EVM address | ||
| alias on my account that will identify my account on the EVM and allow for the correct `ecrecover` functionality. | ||
| 3. As an existing account with a complex key but no EVM address alias, I would like to set an ECDSA derived EVM address | ||
| alias on my account that will identify my account on the EVM and allow for the correct `ecrecover` functionality. |
There was a problem hiding this comment.
Same concern here as user story 1. Maybe we add the caveat to the stories, that the ECDSA signature that corresponds with the EVM address for ecrecover to function would need to be utilized on signatures for EVM of those transactions and not the key associated with the account on the hedera network.
| 4. As an account with an EVM address alias set after creation, I would like to set an evm address override to my | ||
| previous long zero address for a `ContractCreate` transaction. | ||
| 5. As an account with an EVM address alias set after creation, I would like to set an evm address override to my | ||
| previous long zero address for a `ContractCall` transaction. |
There was a problem hiding this comment.
Is this out of scope / too complex for this HIPs user story?
As an existing account with an ED key but no EVM address alias, I would like to update my key to an ECDSA key and set my EVM address to be derived from the new ECDSA key.
Description:
HIP 583 opened the doors for greater account compatibility with EVM flows by utilizing the account alias to encompass
the EVM address. However, given the static nature of the alias and concerns of complexity, existing accounts were not
allowed to update their alias and set one if it was null. This HIP aims to rectify this by allowing EOAs who have no
alias set to set it to an ECDSA key derived evm address value they own.
This HIP also replaces the need for HIP 631: Account Virtual Addresses as it
aimed to resolve this issue as well as provide even greater functionality. A form of HIP 631 could be revisited in the
future but not with the goal of providing address equivalence with the EVM.
Related issue(s):
Fixes #1070
Notes for reviewer:
1st draft, need to add a clarifying image and touch up
Checklist