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.
Description:
This HIP proposes an expansion to the approval and allowance network logic (e.g.
CryptoApproveAllowance
) by allowing any account on the network to sponsor the payment of the fees for another account’s submitted transactions. In this way account Alice may assign an HBAR / token transaction fee allowance for EOA account Bob or Contract account Carol and pay the fees due to nodes, the network and accounts for any transactions they submit, thus allowing Bob or Carol to have zero balance and still transact on chain.This proposal extends the existing Approval and Allowance API by adding 2 new allowance types (
TransactionFeeAllowance
andCustomFeeAllowance
) that inform the delegation of fee payments to another account without requiring one-off approval for each transaction. This feature enhances flexibility and efficiency in managing transaction costs, particularly for high volume applications.Related issue(s):
Fixes #912
Notes for reviewer:
Expect more changes soon.
There's an outstanding item to condense the Allowances types to instead be scopes on the existing allowances as a cleaner API form
Checklist