Skip to content
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.

Sign up for GitHub

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

Jump to bottom

TransactionPayment*Api does not support SkipCheckIfFeeless #7811

Open
bkchr opened this issue Mar 5, 2025 · 0 comments
Open

TransactionPayment*Api does not support SkipCheckIfFeeless #7811

bkchr opened this issue Mar 5, 2025 · 0 comments
Labels
I3-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue.

Comments

@bkchr
Copy link
Member

bkchr commented Mar 5, 2025

When querying the fees for a transaction/call using the runtime apis, we don't check if the fees will be skipped by the SkipCheckIfFeeless transaction extension. So, the runtime apis would return an incorrect fee.

A simple solution could be to mimic the functions called by the runtime api in the SkipCheckIfFeeless extension and then to call this instead of directly calling the transaction payment api.
@bkchr bkchr added the I3-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue. label Mar 5, 2025
@bkontur bkontur mentioned this issue Mar 6, 2025
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
I3-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue.
Projects
Runtime / FRAME
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bkchr