-
Between 5.7 and 6.3 the output of wallet.signTransaction() has changed slightly. This is causing failures on the chain I'm using. Can someone explain the details behind this change? The code in both cases is: The unsigned_txn and the wallet sig are the same input in both cases. Using sample data for unsigned_txn and wallet key, the beginning of the signed_txn compares as: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
What version of v5 were you using? The above examples indicate with v5 you were using a legacy transaction while with v6 it detected the network supports type 1 (transaction envelope) transactions and so used that instead. What chain are you using? Does it indeed support type 1 (but oddly not type 2 transactions)? You can always force the transaction type to use legacy by including |
Beta Was this translation helpful? Give feedback.
What version of v5 were you using?
The above examples indicate with v5 you were using a legacy transaction while with v6 it detected the network supports type 1 (transaction envelope) transactions and so used that instead.
What chain are you using? Does it indeed support type 1 (but oddly not type 2 transactions)?
You can always force the transaction type to use legacy by including
type: 0
in your tx, but it’d be preferable if it could detect that on its own.