Skip to content

Commit db4d600

Browse files
committed
Updates for implicit --disposable-gas-payer
1 parent 8101505 commit db4d600

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

packages/docs/pages/users/fees.mdx

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ This **might** incentivise validators to prioritise this transaction above those
126126
It is also possible to pay for fees using the MASP when dealing with a transaction involving shielded inputs (shielded and unshielding transfers both natively and over IBC).
127127
This is a good practice when trying to maximize data protection and minimize information leakage.
128128

129-
When dealing with MASP fee payment, the client will first try to deduct the fees from the spending key specfied by `--gas-spending-key` of the shielded transaction and unshield them to the transparent balance of the `--gas-payer` (or the address corresponding to the first key in the `--signing-keys`).
129+
When dealing with MASP fee payment, the client will first try to deduct the fees from the `--source` spending key of the shielded transaction and unshield them to the transparent balance of the `--gas-payer` (or the address corresponding to the first key in the `--signing-keys`).
130130
Then, these fees are paid to the block proposer from the gas payer.
131131

132132
For example, if the user has a spending key `spending-key-1` in their wallet, and they want to pay for the fees of a shielded transfer transaction using the MASP, they would run the following command:
@@ -138,10 +138,9 @@ namadac transfer \
138138
--token OSMO \
139139
--amount 10 \
140140
--gas-payer my-implicit \
141-
--gas-spending-key spending-key-1
142141
```
143142

144-
If `spending-key-1` does not have enough balance or the user simply wants to use a separate key for gas, they can specify a different spending key for fee payment:
143+
If `spending-key-1` does not have enough balance or the user simply wants to use a separate key for gas, they can specify a different spending key for fee payment using the `--gas-spending-key` argument:
145144

146145
```shell copy
147146
namadac transfer \
@@ -165,8 +164,8 @@ For an atomic batch, the masp fee payment transaction (the first one in the batc
165164

166165
It is also possible to use a disposable gas payer to pay for transaction fees.
167166
This is useful (and recommended) in cases where the user does not want to leak information and reveal the identity of the `--gas-payer`.
168-
In order to use a disposable gas payer, the user must include the `--disposable-gas-payer` flag.
169-
The fees will be deducted from the shielded balance of the shielded transactions `--gas-spending-key` and unshielded to the transparent balance of an ephemeral transparent address before being paid by the ephemeral address.
167+
The disposable gas payer is the default option and it's used all the times unless `--gas-payer` is specified.
168+
The fees will be deducted from the shielded balance of the shielded transaction's `--source` or `--gas-spending-key` and unshielded to the transparent balance of an ephemeral transparent address before being paid by the ephemeral address.
170169

171170
For example, if the user has the same two spending keys from the previous example in their wallet, and they want to pay for the fees of an unshield transaction using a disposable address, they would run the following command:
172171

@@ -177,7 +176,6 @@ namadac unshield \
177176
--token OSMO \
178177
--amount 10 \
179178
--gas-spending-key spending-key-2 \
180-
--disposable-gas-payer
181179
```
182180

183181
### MASP fee payment gas limit

0 commit comments

Comments
 (0)