You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Signed TX: (address, signature, extensions, call_data)
We'll add:
Unsigned TX with extensions: (extensions, call_data)
We are also renaming SignedExtensions to TransactionExtensions and changing the traits in Substrate a bit for how they work.
On the Subxt side we should do something along the lines of:
Rename our SignedExtensions to TransactionExtensions (updating the other naming around these as appropriate, eg I think "additional signed" becomes "implicit").
2 Rename our tx client methods to match the update, eg create_unsigned becomes create_bare.
Introduce a new method, maybe on the offline side of the tx client which can construct such an extrinsic (maybe create_general).
The text was updated successfully, but these errors were encountered:
See eg paritytech/polkadot-sdk#2280 and my comment here links to the bit showing the new encoding: paritytech/polkadot-sdk#2280 (comment) (though note that the actual extrinsic version will change to 5 for the new type based on latest comments).
Essentially right now we have:
(call_data)
(address, signature, extensions, call_data)
We'll add:
(extensions, call_data)
We are also renaming
SignedExtension
s toTransactionExtension
s and changing the traits in Substrate a bit for how they work.On the Subxt side we should do something along the lines of:
SignedExtension
s toTransactionExtension
s (updating the other naming around these as appropriate, eg I think "additional signed" becomes "implicit").2 Rename our
tx
client methods to match the update, egcreate_unsigned
becomescreate_bare
.tx
client which can construct such an extrinsic (maybecreate_general
).The text was updated successfully, but these errors were encountered: