-
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(no-std): enable no_std
support for op consensus rules
#13684
Conversation
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.
cool, could we also add this to the .github/assets/check_wasm.sh
script?
nvm, this is already not excluded from the check_wasm
script
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.
I think we want all of this to be fully no-std and should be doable if we do some prep first
ref #13686
@@ -0,0 +1,188 @@ | |||
//! Optimism beacon consensus rule set. | |||
|
|||
#![cfg(feature = "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.
we can likely make this fully no-std if we do some prep first on these
reth/crates/optimism/consensus/Cargo.toml
Lines 22 to 25 in 28fde3f
reth-optimism-forks.workspace = true | |
reth-optimism-chainspec.workspace = true | |
# TODO: remove this after feature cleanup | |
reth-optimism-primitives = { workspace = true, features = ["serde"] } |
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.
hm, the issue is std::time::SystemTime
, wdym?
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.
ah I found this now #13683 (comment)
sorry, force merged the wrong pr... see #13689 |
yes, it's flaky |
Closes #13683.