Update substrate and hardcoded default ChargeAssetTxPayment extension
#330
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsdw
approved these changes
Nov 25, 2021
dvdplm
approved these changes
Nov 25, 2021
sander2
added a commit
to interlay/subxt
that referenced
this pull request
Nov 29, 2021
… extension (paritytech#330)" This reverts commit d6840df.
0623forbidden
pushed a commit
to DEIPworld/substrate-subxt
that referenced
this pull request
Feb 15, 2022
…on (paritytech#330) * Update balances events * Update node_runtime.scale * Update default extra to include ChargeAssetTxPayment with extra field * Fmt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ChargeTransactionPaymentrenamed toChargeAssetTxPaymentand extra field added. This is short term fix, obviously we need a way to allow providing values for these fields if the user wants to actually add a tip. But needs consideration since the signed extensions are configurable in the runtime so would need to be moved to the codegen potentially.