-
Notifications
You must be signed in to change notification settings - Fork 6
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
WETH Oracle support #429
base: 10-31-weth_from_assethub_support
Are you sure you want to change the base?
WETH Oracle support #429
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
8fa2387
to
8f06f16
Compare
8f06f16
to
aec984b
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.
Main logic for adding Weth looks correct. Only some comments about debug packages and a feature flag
@@ -179,7 +179,7 @@ std = [ | |||
"sp-block-builder/std", | |||
"sp-consensus-aura/std", | |||
"sp-core/std", | |||
# "sp-debug-derive/std", | |||
"sp-debug-derive/std", |
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.
Should this be included again?
@@ -28,7 +28,7 @@ scale-info = { workspace= true, default-features = false, features = [ | |||
lazy_static = "1.5.0" | |||
|
|||
# Uncomment this and the std feature below to see variables instead of <wasm:stripped> in the console output | |||
#sp-debug-derive = { workspace = true, features = ["force-debug"]} | |||
sp-debug-derive = { workspace = true, features = ["force-debug"]} |
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.
Should be remove this?
frame_metadata_hash_extension::CheckMetadataHash::<Runtime>::new(true), | ||
#[cfg(not(feature = "metadata-hash"))] |
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.
How exactly does this work with metadata-hash? Shouldn't we always build the runtime with the new CheckmetadataHash? Was this only for testing purposes?
What?
Why?
How?
Testing?