{error.message}
}\nWallet locked. Unlock it to continue.
\n }\n\n // ... your dApp: account.partyId, signMessage(text), execute(params), ledgerApi(params)\n}\n```\n\n`connect()` opens the SDK's wallet picker, a popup by default. There is no mode argument: the picker\nis what chooses the wallet. Dismissing it rejects with `ConnectCancelledError`, which you filter by\n`instanceof`, never by message. Whether `error` records it as well depends on which side saw\nthe close, so do not gate on that.\n\n`signMessage`, `execute` and `ledgerApi` refuse with no session, and refuse again while the wallet\nreports it is not authenticated; that is `isLocked`, and it happens after a successful connect.\n`signMessage` and `execute` also refuse with no party, which `ledgerApi` does not need. The\nreference gateway also refuses `signMessage` for a local party; `usePartyType().readPartyType()`\ntells local from external when you ask. The SDK's status carries one `isConnected` flag, so a lock\nand a wallet-side disconnect look the same\nhere. `useLedger().isReady` covers both, and `useAccount().account` is `undefined` for the duration:\ngate session content on the party, and use `isLocked` only to explain why it went away.\n\n### Connecting through a Wallet Gateway\n\n```tsx\nimport { RemoteAdapter } from '@canton-network/dapp-sdk'\n\nconst config = {\n appName: 'My dApp',\n additionalAdapters: [\n new RemoteAdapter({ name: 'Gateway', rpcUrl: 'http://localhost:3030/api/v0/dapp' }),\n ],\n}\n```\n\n> [!NOTE]\n> The dapp-sdk wallet picker also lets a user paste any gateway URL and connect to it without the\n> dApp listing it. That session does not survive a reload; one with a gateway listed here does.\n\nDetails in [architecture.md](https://github.com/BootNodeDev/canton-dappbooster/blob/main/canton-connect/architecture.md#remote-gateway).\n\n### Connecting through WalletConnect\n\n```tsx\nconst config = {\n appName: 'My dApp',\n networkId: 'canton:devnet',\n walletConnectProjectId: 'YOUR_REOWN_PROJECT_ID',\n}\n```\n\n`networkId` is the Canton network the dApp targets, as a CAIP-2 chain id.\n\nDetails in [architecture.md](https://github.com/BootNodeDev/canton-dappbooster/blob/main/canton-connect/architecture.md#walletconnect).\n\n## Reference\n\nEvery hook and every config field is documented in JSDoc, which your editor surfaces at the call\nsite and which is published at\n[docs.dappbooster.cc](https://docs.dappbooster.cc/). Start at\n`CantonConnectProvider` and `CantonConnectConfig`.\n\n## Testing helpers\n\n- `createMockAdapter()`, from the package root: a `ProviderAdapter` answering `connect`,\n `disconnect`, `status` and `listAccounts` with no wallet installed, so a dApp or a test can\n connect and show a party. Anything else throws, naming the method.\n- From `@bootnodedev/canton-connect/testing`: `createFakeWallet()`, a CIP-0103 extension driven over\n `postMessage` that exercises the SDK's real announce and detect path; `createAutoPicker()`, a\n headless picker so `connect()` runs without a popup; `FakeSessionProvider`, the context rehydrated\n at an asked-for session with no SDK behind it; and `pause(ms)`, a real-timer sleep.\n\n```tsx\nimport { CantonConnectProvider, createMockAdapter } from '@bootnodedev/canton-connect'\nimport { createAutoPicker } from '@bootnodedev/canton-connect/testing'\n\nconst config = {\n appName: 'My dApp',\n additionalAdapters: [createMockAdapter()],\n walletPicker: createAutoPicker(),\n}\n```\n\n## Architecture\n\n[`architecture.md`](https://github.com/BootNodeDev/canton-dappbooster/blob/main/canton-connect/architecture.md)\nmaps the seams; its `architecture/` chapters carry the connection machine and the popup close guard.\n\n## Testing\n\n`pnpm test`: vitest + jsdom + Testing Library. `pnpm coverage` runs the same suite under v8, with\n`testing/`, `mock/` and the barrel excluded.\n","readmeFilename":""}