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
I have a set of scripts for composing & executing contract transactions via contract.tx.method. But my current contract is governed by a multisig, which means certain tx's need to be performed on behalf of that. I know how to initiate & approve multisig tx's in polkadot-js/apps – but not withinapi/api-contract.
My idea was to (a) initiate it in my scripts as I usually would, export the call data (as hex or bytes), and use this to (b) approve it in polkadot-js/apps (doesn't need to happen within the script). But I neither know how to do (a) on behalf of a multisig nor do I know (b) how to export the call data.
It would be awesome to get some help on this, @jacogr.
The text was updated successfully, but these errors were encountered:
jacogr
added
the
Support
Tracks issues or requests related to troubleshooting, answering questions, and user assistance.
label
Nov 18, 2023
Hey,
I have a set of scripts for composing & executing contract transactions via
contract.tx.method
. But my current contract is governed by a multisig, which means certain tx's need to be performed on behalf of that. I know how to initiate & approve multisig tx's inpolkadot-js/apps
– but not withinapi
/api-contract
.My idea was to (a) initiate it in my scripts as I usually would, export the call data (as hex or bytes), and use this to (b) approve it in
polkadot-js/apps
(doesn't need to happen within the script). But I neither know how to do (a) on behalf of a multisig nor do I know (b) how to export the call data.It would be awesome to get some help on this, @jacogr.
The text was updated successfully, but these errors were encountered: