-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat: use f4 eth addresses wherever possible #9532
Conversation
Builds on #9531, merge that first. |
id, err := address.IDFromAddress(addr) | ||
if err != nil { | ||
return EthAddress{}, err | ||
func TryEthAddressFromFilecoinAddress(addr address.Address, allowId bool) (EthAddress, bool, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when would we want to not allow ID?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we want to check if we have an eth address (take a look at how we use this)
Previously, we'd use embedded ID addresses.
e156e73
to
247a5e4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will definitely make addresses feel less foreign in tooling compared to their masked ID addresses.
Co-authored-by: Raúl Kripalani <[email protected]>
Previously, we'd use embedded ID addresses.