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
Currently it’s non-trivial to synchronize between participants in a Daml Script, see https://discuss.daml.com/t/init-script-on-a-canton-setup/3009/6 for example. If you don’t create a contract or archive it (e.g. a nonconsuming choice) it becomes close to impossible to synchronize (you can’t poll for the change).
We should try to make that a bit easier. I think to make this work somewhat reliably we need to provide transaction ids and allow polling for those.
The text was updated successfully, but these errors were encountered:
Currently it’s non-trivial to synchronize between participants in a Daml Script, see https://discuss.daml.com/t/init-script-on-a-canton-setup/3009/6 for example. If you don’t create a contract or archive it (e.g. a nonconsuming choice) it becomes close to impossible to synchronize (you can’t poll for the change).
We should try to make that a bit easier. I think to make this work somewhat reliably we need to provide transaction ids and allow polling for those.
The text was updated successfully, but these errors were encountered: