bug: an error will be reported when executing the multi-signature command

[lispking]

• https://docs.sui.io/guides/developer/cryptography/multisig

1. Call the publish command to generate <TX_BYTES>.
2. Executing according to the document will report an error when it comes to the last step.

$ sui client publish ${package} --serialize-unsigned-transaction
Raw tx_bytes to execute: <TX_BYTES>

$ sui client execute-signed-tx --tx-bytes <TX_BYTES> --signatures <SERIALIZED-MULTISIG>

[warning] Client/Server api version mismatch, client api version : 1.39.1, server api version : 1.39.3
RPC call failed: ErrorObject { code: ServerError(-32002), message: "Invalid user signature: Required Signature from 0xa0e9e2f2c4db22b37d7b61269aab4a42bfcad9eb51d5ca0329942b3d4bc327ab is absent [\"0x233215dd07c98701d5d8a2635b46786508201b06b630be6c9c2a94e55b7320da\"]", data: None }

[stefan-mysten]

Can you double check that indeed all signatures were included? Also, the multisig address is different than the active address that is set when executing a transaction, so you likely have to pay for gas from a different gas object, I think.

[lispking]

I think it's a problem with the sui client command, because I've tried it dozens of times according to the documentation. The only difference is that it's applied in the publish scenario.

[stefan-mysten]

The documentation might be wrong too 😅

[stefan-mysten]

Can you run the same tx bytes and multisig via GraphQL?

mutation {
  executeTransactionBlock(txBytes:"", signatures:"")
}

[lispking]

Now a tool has been encapsulated using the TypeScript SDK, and it's much easier to use than the one in the documentation.