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

chore: avoid access Distance private field of U256 #2520

Merged
merged 1 commit into from
Dec 11, 2024

Conversation

maqi
Copy link
Member

@maqi maqi commented Dec 11, 2024

Description

avoid access Distance private field of U256
also rolls back the libp2p dependency to the previous 0.54.1

@maqi maqi force-pushed the bypass_Distance_private_field branch from e938394 to 8e4335e Compare December 11, 2024 13:20
@jacderida jacderida merged commit 35c7963 into maidsafe:main Dec 11, 2024
25 checks passed
@@ -20,6 +20,7 @@ upnp = ["libp2p/upnp"]

[dependencies]
aes-gcm-siv = "0.11.1"
alloy = { version = "0.5.3", default-features = false, features = ["std", "reqwest-rustls-tls", "provider-anvil-node", "sol-types", "json", "signers", "contract", "signer-local", "network"] }
Copy link
Contributor

@mickvandijke mickvandijke Dec 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this only added for the U256 type? Cause the type is in ant_evm::common::U256 already 🤔

EDIT: Hmm actually, it is in evmlib::common::U256, but ant_evm doesn't re-export it yet. I think it would be a cleaner solution to re-export it through ant_evm than adding Alloy as dependency.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^ I'll do that in my merge commit for PR # 2519

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