Canton wallet integration support
Start with the ready-made React kit or a generated application. If an integration gets stuck, a small reproduction helps maintainers isolate application configuration, PartyLayer behavior and wallet-provider responses.
Follow the React and Next.js quick start, use the application generator, and check the wallet network and capability directory.
Application teams
- Include package versions, framework, browser, target network and wallet name.
- Link a minimal public reproduction with no credentials, plus the expected and observed result.
- Say which step fails: discovery, connect, restore, sign-in, message signing, transaction submission or independent confirmation.
- For transactions, use a test network and share only redacted diagnostics that you are authorized to make public.
Open an integration support request. Requests are public; there is no guaranteed response time or implied wallet-vendor support agreement.
Wallet providers
Use the shared CIP-0103 announce or official provider-adapter path described in the generic provider guide. Submit registry metadata and evidence through a pull request. New wallets do not need a new PartyLayer-specific package.
Provide supported networks, capabilities, current SDK versions, setup requirements and a usable test flow. Registry inclusion and automated conformance do not replace live connect, rejection, signing, restoration, disconnection and ledger acceptance.
Share a verified integration
If your application uses PartyLayer, select “Share a live integration” in the support form and provide the public URL, version and network. Maintainers verify submissions before adding references; submitting a URL does not automatically publish a logo or endorsement. State logo attribution permission explicitly.