Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Refund the extrinsic execution fee for calls that require a JWT
Why?
The fee payment is used to avoid spamming and stalling the chain, but all JWT calls from regular KYCs need to either pay a fee with OTM, or lock up PLMC.
And the other ones are locked behind an institutional JWT, so even if they act malicious we could check who they are and take action.
This should provide better UX, since you can say you spend 100USDT and spend 100USDT, instead of 100.03
How?
Instead of returning
Ok(())
returnTesting?
Tests don't include fee payments for extrinsics. So only way I can see to test this is creating a network with chopsticks/zombienet and trying it out ourselves.
For now it hasn't been tested, but its a simple change so should work.