What problem does your feature solve?
I did not manage to easily use the CLI to call my contract in a multisig setup.
E.g. using this argument twice is failing
error: the argument '--sign-with-key <SIGN_WITH_KEY>' cannot be used multiple times
What would you like to see?
We need to promote multisig in all its forms. I am trying to have a G address which is a multisig, using this with the CLI proves to be hard if not impossible. I did not yet manage to do stellar contract deploy for instance. I could build the TX with the CLI but then using labs to sign twice does not work and returns an error.
The only way I could find was to initialise first the contract with a normal G, then update the admin with a multisig G. Then we can build a TX XDR with the CLI and call multiple times the CLI to sign with different addresses and send. Or use labs, but here as well multisig is not easy to use and involves copy pasting.
Side note: on the contract initialisation I was faced with data:["[recording authorization only] encountered authorization not tied to the root contract invocation for an address. Use require_auth() in the top invocation or enable non-root authorization. as I wanted to directly pass the G multisig to be used. But this does not work, I had to then add another admin function to go around the problem. I could not find how to enable non-root authorization after looking into the docs and the code of the SDK.
What alternatives are there?
- Not using a G address with multisig for calling contracts.
- Continue like that. Which to me is a terrible DX.
What problem does your feature solve?
I did not manage to easily use the CLI to call my contract in a multisig setup.
E.g. using this argument twice is failing
error: the argument '--sign-with-key <SIGN_WITH_KEY>' cannot be used multiple timesWhat would you like to see?
We need to promote multisig in all its forms. I am trying to have a G address which is a multisig, using this with the CLI proves to be hard if not impossible. I did not yet manage to do
stellar contract deployfor instance. I could build the TX with the CLI but then using labs to sign twice does not work and returns an error.The only way I could find was to initialise first the contract with a normal G, then update the admin with a multisig G. Then we can build a TX XDR with the CLI and call multiple times the CLI to sign with different addresses and send. Or use labs, but here as well multisig is not easy to use and involves copy pasting.
Side note: on the contract initialisation I was faced with
data:["[recording authorization only] encountered authorization not tied to the root contract invocation for an address. Userequire_auth()in the top invocation or enable non-root authorization.as I wanted to directly pass the G multisig to be used. But this does not work, I had to then add another admin function to go around the problem. I could not find how toenable non-root authorizationafter looking into the docs and the code of the SDK.What alternatives are there?