-
Notifications
You must be signed in to change notification settings - Fork 49
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
Crab Network claim rewards has a high txfee #473
Comments
The But seems the bytes fee not working in previous version (don't know why). |
Might related to this issue: #447 Will progress after substrate dep get upgraded. |
No. The root cause is bytes fee. Not relate to weight. Because the multiplier is still -1 in Crab. |
I mean bytes fees are included in the adjustable fees, and multiplier is not working, could this be the reason why byte fees not working? |
But the fix for #447 was not included in RC2. After I change the bytes fee from |
Don't know why. So the solution is upgrade to RC4. And a hot fix is need, to low down the tx fee for Crab before the RC4 apply. |
How to infer the type of |
#[test]
fn Multiplier() {
let len_fee: u128 = 50;
let weight_fee: u128 = 50;
let adjustable_fee = len_fee.saturating_add(weight_fee);
println!("adjustable_fee: {:?}", adjustable_fee);
let targeted_fee_adjustment: Multiplier = Multiplier::saturating_from_integer(-1);
println!("targeted_fee_adjustment: {:?}", targeted_fee_adjustment);
let adjusted_fee: u128 =
targeted_fee_adjustment.saturating_mul_acc_int(adjustable_fee.saturated_into());
println!("adjusted_fee: u128: {}", adjusted_fee);
let adjusted_fee: i128 =
targeted_fee_adjustment.saturating_mul_acc_int(adjustable_fee.saturated_into());
println!("adjusted_fee: i128: {}", adjusted_fee);
// FIXME: type annotations needed
// adjusted_fee -> ?
// adjusted_fee.saturated_into() -> u128
//
// ```rust
// let adjusted_fee =
// targeted_fee_adjustment.saturating_mul_acc_int(adjustable_fee.saturated_into());
// let _infer: u128 = 1;
// let _infer: u128 = _infer.saturating_add(adjusted_fee.saturated_into());
// ```
} |
Substrate is using u128 in |
There is a temp workaround by changing byte fee to 0, need to change back after this issue fixed or substrate get upgraded: |
1 similar comment
There is a temp workaround by changing byte fee to 0, need to change back after this issue fixed or substrate get upgraded: |
Fixed: paritytech/substrate#6145 |
staking.payoutStakers
The text was updated successfully, but these errors were encountered: