Canton MainNet Wallet & dApp Integration Guidance

Hi everyone, we’re preparing Bayzen’s Canton MainNet deployment. Our validator and participant are running successfully, but we need some guidance on the wallet/dApp integration.

Could anyone point us to the official MainNet configuration for:

1. JSON Ledger API URL + Host header
2. Network ID + Synchronizer ID
3. Ledger API / IdP authentication
4. Scan/registry endpoint
5. Wallet Gateway deployment + authentication
6. Required Party/user rights for dApp transactions
7. Whether separate gateway credentials are required beyond the onboarding secret

Any documentation or examples from application developers would be greatly appreciated. Thanks!

Hi,

Can you provide some more information please, a little more context would help identify the MainNet settings you actually need:

1. Intended flow: What’s the first user journey you want working, from connecting a wallet through to signing and submitting a transaction?

2. Components and versions: Which wallet, Wallet Gateway and SDK are you using, and which Canton/Splice versions are deployed? Also, what service do you mean by “registry”? Product names or repository links would help.

3. Current progress: What already works, and where are you blocked? Have you successfully called the JSON Ledger API or authenticated against it? If something fails, please share the request path and sanitized error.

4. Deployment: How is the participant deployed, and where do the application backend and gateway run relative to it? Is connectivity between them already configured?

5. Identity and signing: What IdP/authentication setup is in place? Whose parties will the application transact for, where are they hosted, and who will sign the transactions?

A lot of the info you are looking for will depend on the validator deployment structure you have, but here is a reference for Kube deployments.