Skip to content

Commit

Permalink
Removes misleading aliases and useless gas payers args
Browse files Browse the repository at this point in the history
  • Loading branch information
grarco authored and brentstone committed Sep 8, 2024
1 parent 75f7b9d commit 6032c97
Showing 1 changed file with 5 additions and 10 deletions.
15 changes: 5 additions & 10 deletions packages/docs/pages/users/fees.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,19 +12,17 @@ Fees are **always** paid from the balance of an **implicit** address. When expli
Note the use of the placeholder `keysha` for the key parameter. This is a completely configurable parameter, and should just refer to the alias of the key signing the transaction (that has a positive nam balance).
</Callout>

Let's suppose to have two accounts in our wallet, `accountant` controlling the `my-new-acc` implicit address and `keysha` controlling the `keysha-acc` implicit address.

This means that in the transaction
```shell copy
namada client transfer \
--source my-new-acc \
--source accountant \
--target validator-1 \
--token NAM \
--amount 10 \
--signing-keys keysha
```

the account `accountant` should pay the fees since it's the source of the transaction but given that the user provided the `--signing-keys` argument, the associated key `keysha` will be required to pay the fee from the balance of its implicit `keysha-acc` address. This means that even though the address `my-new-acc` may have a positive NAM balance, `keysha` will need to have the associated NAM in order to pay the transaction fee.
the account `accountant` should pay the fees since it's the source of the transaction but given that the user provided the `--signing-keys` argument, the associated key `keysha` will be required to pay the fee from the balance of its implicit address. This means that even though the account `accountant` may have a positive NAM balance, `keysha` will need to have the associated NAM in order to pay the transaction fee.

An identical result can be achieved with `--gas-payer keysha`. The two args `--signing-keys` and `--gas-payer` can also be used in conjuction: this is useful when we want to manually specify the signer of the transaction (if, for example, the client cannot infer the source by itself) but, at the same time, pay fees with a separate account that is not involved in the transaction.

Expand All @@ -45,12 +43,11 @@ For example, the following command will simulate a transfer transaction, and ret

```shell copy
namadac transfer \
--source my-new-acc \
--source accountant \
--target validator-1 \
--token NAM \
--amount 10 \
--signing-keys keysha \
--gas-payer accountant \
--dry-run-wrapper
```

Expand All @@ -65,25 +62,23 @@ Hence, when making the transfer, we could specify the `gas-limit` as follows:

```shell copy
namadac transfer \
--source my-new-acc \
--source accountant \
--target validator-1 \
--token NAM \
--amount 10 \
--signing-keys keysha \
--gas-payer accountant \
--gas-limit 150000
```

If for some reason, we wanted to pay a higher gas fee, we could also specify that as follows:

```shell copy
namadac transfer \
--source my-new-acc \
--source accountant \
--target validator-1 \
--token NAM \
--amount 10 \
--signing-keys keysha \
--gas-payer accountant \
--gas-limit 150000 \
--gas-price 0.01
```
Expand Down

0 comments on commit 6032c97

Please sign in to comment.