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
We are currently testing integration of wrapped proxy signing based on recently implemented allowCallDataAlteration
The allowCallDataAlteration itself works as expected and the payload validation logic is getting skipped. However, we noticed that an attempt to send proxy-wrapped tx is failing with "Invalid signature" response from the node
After some debugging and investigaiton we found out that despite signedTransaction is handled in signViaSigner in polkadot-js api library, polkadot-js apps itself doesnt use signAndSend which pipes signedTransaction into observeSubscribe but actually usessignAsync and send separetely, which causes signedTransaction to be lost in between since signViaSignermutates only signature and not the modified tx itself, so send uses combination of original extrinsic and signature for the modified transaction
The text was updated successfully, but these errors were encountered:
Hey, thats Valentin from Nova Wallet
We are currently testing integration of wrapped proxy signing based on recently implemented
allowCallDataAlteration
The
allowCallDataAlteration
itself works as expected and the payload validation logic is getting skipped. However, we noticed that an attempt to send proxy-wrapped tx is failing with "Invalid signature" response from the nodeAfter some debugging and investigaiton we found out that despite
signedTransaction
is handled in signViaSigner in polkadot-js api library, polkadot-js apps itself doesnt usesignAndSend
which pipessignedTransaction
intoobserveSubscribe
but actually usessignAsync
andsend
separetely, which causessignedTransaction
to be lost in between sincesignViaSigner
mutates only signature and not the modified tx itself, sosend
uses combination of original extrinsic and signature for the modified transactionThe text was updated successfully, but these errors were encountered: