Skip to content
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

Merged
merged 2 commits into from
Oct 21, 2022

Conversation

Stebalien
Copy link
Member

Previously, we'd use embedded ID addresses.

@Stebalien Stebalien requested a review from a team as a code owner October 21, 2022 08:17
@Stebalien
Copy link
Member Author

Builds on #9531, merge that first.

@Stebalien Stebalien requested a review from vyzo October 21, 2022 08:19
id, err := address.IDFromAddress(addr)
if err != nil {
return EthAddress{}, err
func TryEthAddressFromFilecoinAddress(addr address.Address, allowId bool) (EthAddress, bool, error) {
Copy link
Contributor

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?

Copy link
Member Author

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)

Base automatically changed from steb/cbor-encode-tx to raulk/lisbon October 21, 2022 10:59
Previously, we'd use embedded ID addresses.
@raulk raulk force-pushed the steb/f4-addresses-everywhere branch from e156e73 to 247a5e4 Compare October 21, 2022 11:03
Copy link
Member

@raulk raulk left a 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.

@raulk raulk merged commit b30fdfe into raulk/lisbon Oct 21, 2022
@raulk raulk deleted the steb/f4-addresses-everywhere branch October 21, 2022 11:13
vyzo pushed a commit that referenced this pull request Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants