-
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
🔖 Release 0.7.5 #342
🔖 Release 0.7.5 #342
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @JuaniRios and the rest of your teammates on Graphite |
044ae4d
to
2ac7d6a
Compare
2ac7d6a
to
5e0a173
Compare
@@ -22,7 +22,7 @@ use polimec_common::USD_UNIT; | |||
use sp_arithmetic::{FixedU128, Percent}; | |||
use sp_std::{collections::btree_map::BTreeMap, vec, vec::Vec}; | |||
|
|||
#[cfg(feature = "fast-mode")] | |||
#[cfg(any(feature = "fast-mode", not(any(feature = "fast-mode", feature = "instant-mode"))))] |
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 can simplify this as we have 3 states. Normal, fast-mode and instant-mode.
We describe normal mode as !(fast-mode or instant-mode)
. We are currently using Hours in both normal mode and fast-mode, so only not in instant-mode. So think we can change this to cfg(not(feature = "instant-mode"))
.
Wdty?
@@ -86,7 +86,7 @@ pub const SUCCESS_TO_SETTLEMENT_TIME: BlockNumber = 4; | |||
#[cfg(feature = "fast-mode")] | |||
pub const SUCCESS_TO_SETTLEMENT_TIME: BlockNumber = 5 * crate::MINUTES; | |||
#[cfg(not(any(feature = "fast-mode", feature = "instant-mode")))] | |||
pub const SUCCESS_TO_SETTLEMENT_TIME: BlockNumber = 4 * crate::DAYS; | |||
pub const SUCCESS_TO_SETTLEMENT_TIME: BlockNumber = 1 * HOURS; |
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.
Are we completely clear about this change? I understood that the 4 days were for some legal reasons, right? Just wanted to double check that this was cleared with Ken.
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.
Yes, we are clear. This change follows a discussion we had with the legal team
What?
SuccessToSettlementTime
from 4 days to 1 hourWhy?
Anything Else?
try-runtime check
srtool build:
subwasm info:
subwasm diff