We have set up a Kubernetes environment on Minikube for Canton components, including canton-domain, canton-participant, and http-json, using Helm charts. Additionally, we have configured a synchronization domain (synchronizer) and a participant ledger on our local Minikube setup.
Now, we want to set up the Hub Ledger CLI using the synchronizerURL to connect our local participant ledger (participant ID) to Daml Hub. Given our existing setup, is it possible to connect both the synchronization domain and the participant ledger to Daml Hub? If so, what would be the recommended approach?
Hi Pratik,
Initial question: what are you trying to run on your local Canton instance, and what data are you expecting to see?
If you have already setup canton domain, participant and http json to run locally, you have a blank local self-standing Canton node and actually do not need to connect the the Hub synchronizer at all.
If you want to run a participant locally and connect to the a canton synchronizer, you do not need to run canton-domain locally. You would need to first authorize your local participant ID on the Hub hosted synchronizer, and then connect your participant to that synchronizer.
Please note that this would cause your local participant to be a secondary participant connected to that synchronizer, but you would need see data from the first participant unless you allocate parties on your secondary participant and involve them in workflow involving parties from the hub hosted participant connected to that synchronizer.
1 Like
We have set up canton-domain, canton-participant, and http-json in a Kubernetes environment on Minikube using Helm charts as a proof of concept (PoC). Once the PoC is complete, we plan to deploy the full setup on an EKS cluster for production.
Given this setup, we would like to understand whether we can connect our fully closed local Canton setup, including both the domain and participant, to a remote Hub-hosted synchronizer. Can we use this setup Participant+Synchronizer: A combined setup of both a participant and a synchronizer as mentioned in hub ui ?
A participant can only be connected to a single domain (aka synchronizer)
So if you have a local setup with both a participant and a domain, and the participant is connected to that domain. they are a self-standing environment, and you cannot connect that participant to a Hub-hosted domain.
However, if you run just a participant, you can connect that participant remotely to a Hub-hosted synchronizer.
You would need to permission the Synchronizer on Hub to that local participant based on the local participant ID, and then configure your local participant to connect to that remote synchronizer.
But, more broadly speaking, do you require the data that is present on the Hub-hosted environment, or are you trying mostly to create a self-standing participant / synchronizer pair running either locally on your machine or in an EKS cluster?
Also happy to have a call to discuss further if that helps to progress.