set placeholder fee for fee-calculating transaction #283
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.
@katomm has already suggested a PR be opened for this.
This is a response to a documentation problem reported here, saying that the fee itself must be known before the transaction that calculates the fee. I believe this results from people running through the token creation exercises without yet having the basic transaction building experience (e.g. the process described here for stake pool operators).
The forum comment implies setting
fee="0"
occurs so early in the flow of the affected page-- where it's included with general variables for the testing environment-- that it's easily missed. I've moved it forward into the "Build the raw transaction" section so that the fee is initialised to zero immediately before that test transaction, along with an explanation of why the fee has to be specified twice (first an ignored value, then the calculated value).