-
Notifications
You must be signed in to change notification settings - Fork 106
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
Namadillo: Fees #904
Namadillo: Fees #904
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.
Looks good! I just a left of couple of comments and I would like to quickly check this again after the merge conflicts are fixed.
@@ -30,7 +30,8 @@ export const fetchMinimumGasPrice = async ( | |||
({ token }) => token === nativeToken | |||
); | |||
invariant(!!nativeTokenCost, "Error querying minimum gas price"); | |||
const asBigNumber = new BigNumber(nativeTokenCost.amount); | |||
// TODO: this should be removed after indexer error is fixed! |
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.
It looks like this is fixed now.
className="font-medium" | ||
forceBalanceDisplay={true} | ||
amount={gasPrice.data.multipliedBy( | ||
gasLimits.data[txKind].native.multipliedBy(numberOfTransactions) |
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.
Will this still be correct in cases where a reveal PK is needed?
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 I need to review it again after the batch tx PR gets in
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.
With batch Tx in, RevealPk wasn't considered when calculating fees - it is overestimating though so will work as is (though is incorrect). We still need to determine how fees can be calculated when we have a batch with of Txs, and (currently) at most 2 Tx types in that batch (RevealPK + the type of other Txs). I'm up for taking a look, and we don't necessarily need to address that in this PR!
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.
LGTM! Left a comment about fee estimation - that can be handled separately, as it needs a bit of investigation and discussion!
Closing it for now |
This PR adds back the fees panel with its respective warning