v12.0.1
Important Changes:
- Addition of an optional
signedTransactionfield to theSignerResultresponse for injected signers. This only applies to thesignPayloadmethod exposed in theSignerinterface for polkadot-js. As the name suggests the field expects a signed transaction (extrinsic) when inputted. When its present, the api will not add the signature to the payload, but instead broadcast the inputted signed transaction. This means the signer may modify the payload it's given. The only part of the payload that may not be modified is the call data. This is verified on the api, and will throw an error if it does not match the initial payloads call data.- This is very useful for signers that want to adjust the
modeandmetadataHashfield for theCheckMetadataHashsigned extension. - Note that this is not your traditional breaking change since it more-so acts as an addition, but since this is a high magnitude change it is going to be considered a MAJOR bump.
- For more info please review the following PR (#5914)
- This is very useful for signers that want to adjust the
Changes:
- Replace
system_accountNextIndexwith runtime api callaccountNonceApiforapi.derive.tx.signingInfo - Sanitize
erasforapi.derive.staking._stakerRewards