SubmitMulti with parties on different participant nodes

Questions
,
1

Hi Team,

I tried to run a script with submitMulti [alice,bob] but alice and bob exist on different participant nodes. I received this error message.

Exception in thread "main" com.daml.lf.engine.script.ScriptF$FailedCmd: Command submit failed: All parties must be on the same participant but parties were allocated as follows: List((Alice::1220b82bd4ed68376659781069c100b5152a680c79ee8cabde95bbff179a257f1d6a,com.daml.lf.engine.script.ledgerinteraction.GrpcLedgerClient@6bf0db57), (Bob::1220f356d6e990c2bfeb2a15310871c900603091eb19dbb7cfb98b44c5dfe5d724bf,com.daml.lf.engine.script.ledgerinteraction.GrpcLedgerClient@20ef0aa3))

In such a scenario, what is the best practice to use the submitMulti in the script?

Many thanks in advance.

kc

1 Like
2

Multi-party submissions always require that all actAs and readAs parties are hosted on the participant you’re submitting on. So if they are on different participants, then you cannot use a multi-party submission (whether through Daml script or directly through the ledger API). Instead follow the standard patterns for gathering authorization like propose/accept.

2 Likes