-
Notifications
You must be signed in to change notification settings - Fork 220
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
fix: feature flag separation for validation #5137
fix: feature flag separation for validation #5137
Conversation
25b8887
to
d358a3e
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.
Agree with the idea, but there are too many cfg's here. It's a recipe for dev mistakes and it's not clear when it needs to be applied versus not. I can see someone just adding #cfg[base_node]
to every method.
Is there not a way we can group it all of this together under a common crate or file?
d358a3e
to
e245adc
Compare
b1fad3d
to
38a06a8
Compare
remove base_node from wallet_ffi
c96c385
to
2cba74a
Compare
Just waiting for CI |
Description
Removes OpenSSL from the WalletFFI lib as its not required or used by it.
Fixes validation feature flags.
Motivation and Context
Recent refactor added
base_node
feature flag to the walletFFI. This should not be done as it adds in all the base nodespecific crates that not required by the wallet like randomX, lmdb etc.
This splits the validation traits and implementations between the features
transactions
andbase_node
.How Has This Been Tested?
Manual and unit tests
Fixes: #4974