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
The goal here is to show an exchange operation with a custom token (`TestToken`) that supports running workflows on both a private synchronizer and the global synchronizer.
31
31
A private synchronizer helps avoid some of the traffic costs of using the global synchronizer, but still enables parties to do transactions on the global network,
@@ -89,6 +89,12 @@ Vetting matrix (which DAR is vetted where):
89
89
90
90
DARs referenced above:
91
91
92
-
-**TestTokenV1** = `splice-tddest-token-v1-1.0.0.dar` (built locally from `damljs/splice-test-token-v1`)
92
+
-**TestTokenV1** = `splice-test-token-v1-1.0.0.dar` (built locally from `damljs/splice-test-token-v1`)
93
93
-**trading-app** = `splice-token-test-trading-app-1.0.0.dar` (from the localnet bundle)
94
94
-**Amulet\*** = `splice-amulet` — pre-vetted on the **global** synchronizer by localnet, **not** by this example.
95
+
96
+
## Notes
97
+
98
+
- The TestToken registry used here is `@canton-network/example-test-token-v1-registry`.
99
+
- SDK helpers in this flow resolve the TestToken registry via metadata (`token.find`) rather than passing registry URLs through setup objects.
100
+
- OTCTrade and TestToken command/template references are taken from `@canton-network/core-splice-codegen` rather than hard-coded template ID strings.
0 commit comments