I updated the domain conf file, and added both participants:
canton {
domains {
mydomain {
storage.type = memory
admin-api {
port = 10017
address = 192.168.61.129 // is the default value if omitted
}
public-api {
port = 10018
address = 192.168.61.129 // is the default value if omitted
}
}
}
remote-participants {
participant1 {
admin-api {
port = 5012
address = 192.168.61.128
}
ledger-api {
port = 5011
address = 192.168.61.128
}
}
}
remote-participants {
participant2 {
admin-api {
port = 5012
address = 192.168.61.130
}
ledger-api {
port = 5011
address = 192.168.61.130
}
}
}
}
This is why now i am able to upload the dar and it is visible to participant1 and 2
I just use the daml start --script-option --output-file=parties.json to get the Party ids, in order to create contracts with json api. I need the Party id for alice and bob that are specified in that file.
Itâs not entirely clear what problem youâre now facing. You tell us the dar upload is now working; can you explain what you still need help with? What error are you now seeing?
Thatâs a weird error essage, but letâs assume for a second it may be related to the daml start issue. When you run daml start, by default it will run a local sandbox and run its commands against that. Iâm not seeing anything in your daml.yaml or your CLI arguments to overwrite that default behaviour. This means that the parties you have created with your script get created on the sandbox created by daml start, and not on the participants in your domain.
In order to create the parties, youâll need to run the script against the appropriate participant (I imagine that, as you have two participants, you probably want to create different parties in each one). You can do that with the daml script command, which, unlike daml start, does not start its own sandbox but instead runs against the participant you point it to (run daml script --help for details). Youâll need to first compile the DAR containing your script with daml build, then run something like: