## Description Closes: #12422 --- ### Author Checklist *All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.* I have... - [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title - [ ] added `!` to the type prefix if API or client breaking change - [ ] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting)) - [ ] provided a link to the relevant issue or specification - [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/building-modules) - [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing) - [ ] added a changelog entry to `CHANGELOG.md` - [ ] included comments for [documenting Go code](https://blog.golang.org/godoc) - [ ] updated the relevant documentation or specification - [ ] reviewed "Files changed" and left comments if necessary - [ ] confirmed all CI checks have passed ### Reviewers Checklist *All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.* I have... - [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title - [ ] confirmed `!` in the type prefix if API or client breaking change - [ ] confirmed all author checklist items have been addressed - [ ] reviewed state machine logic - [ ] reviewed API design and naming - [ ] reviewed documentation is accurate - [ ] reviewed tests and test coverage - [ ] manually tested (if applicable)
24 lines
1.2 KiB
Go
24 lines
1.2 KiB
Go
/*
|
|
Package feegrant provides functionality for authorizing the payment of transaction
|
|
fees from one account (key) to another account (key).
|
|
|
|
Effectively, this allows for a user to pay fees using the balance of an account
|
|
different from their own. Example use cases would be allowing a key on a device to
|
|
pay for fees using a master wallet, or a third party service allowing users to
|
|
pay for transactions without ever really holding their own coins. This package
|
|
provides ways for specifying fee allowances such that authorizing fee payment to
|
|
another account can be done with clear and safe restrictions.
|
|
|
|
A user would authorize granting fee payment to another user using
|
|
MsgGrantAllowance and revoke that delegation using MsgRevokeAllowance.
|
|
In both cases, Granter is the one who is authorizing fee payment and Grantee is
|
|
the one who is receiving the fee payment authorization. So grantee would correspond
|
|
to the one who is signing a transaction and the granter would be the address that
|
|
pays the fees.
|
|
|
|
The fee allowance that a grantee receives is specified by an implementation of
|
|
the FeeAllowance interface. Two FeeAllowance implementations are provided in
|
|
this package: BasicAllowance and PeriodicAllowance.
|
|
*/
|
|
package feegrant
|