Skip to content

feat(dapp-sdk): add Slay Money to the wallet registry - #2313

Open
aniiiiXD wants to merge 1 commit into
canton-network:mainfrom
aniiiiXD:add-slay-money-wallet
Open

feat(dapp-sdk): add Slay Money to the wallet registry#2313
aniiiiXD wants to merge 1 commit into
canton-network:mainfrom
aniiiiXD:add-slay-money-wallet

Conversation

@aniiiiXD

Copy link
Copy Markdown

Slay Money is a CIP-0103 browser wallet for Canton, published on the Chrome Web Store. It already announces itself via canton:announceProvider, so it is discoverable at runtime; this entry adds it to the installable list so users who do not have it yet can find it in the picker.

All ten dApp API methods and all three events are implemented and exercised against a live MainNet validator: connect, disconnect, isConnected, status, getActiveNetwork, listAccounts, getPrimaryAccount, signMessage, prepareExecute, ledgerApi, plus accountsChanged, statusChanged and txChanged.

One note on providerId. The existing entry uses browser:ext:<extension-id>, but announce-discovery.ts stores detail.id verbatim with no transformation, so the registry id has to match what the wallet actually announces — for us that is money.slay. Using the browser:ext: form would leave the picker unable to tell the announced provider and this entry apart, and likely show Slay twice. Happy to change it if the convention is meant to be the other way round.

@aniiiiXD
aniiiiXD requested a review from a team as a code owner August 18, 2026 18:29
Slay Money is a CIP-0103 browser wallet for Canton, published on the Chrome
Web Store. It already announces itself via canton:announceProvider, so it is
discoverable at runtime; this entry adds it to the installable list so users
who do not have it yet can find it in the picker.

All ten dApp API methods and all three events are implemented and exercised
against a live MainNet validator: connect, disconnect, isConnected, status,
getActiveNetwork, listAccounts, getPrimaryAccount, signMessage,
prepareExecute, ledgerApi, plus accountsChanged, statusChanged and txChanged.

One note on `providerId`. The existing entry uses `browser:ext:<extension-id>`,
but announce-discovery.ts stores `detail.id` verbatim with no transformation,
so the registry id has to match what the wallet actually announces — for us
that is `money.slay`. Using the `browser:ext:` form would leave the picker
unable to tell the announced provider and this entry apart, and likely show
Slay twice. Happy to change it if the convention is meant to be the other way
round.

Signed-off-by: aniiiiXD <[email protected]>
@aniiiiXD
aniiiiXD force-pushed the add-slay-money-wallet branch from 9408e2b to 63b1403 Compare August 18, 2026 18:46
@mjuchli-da mjuchli-da self-assigned this Aug 18, 2026

@mjuchli-da mjuchli-da left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much for your contribution and the intention to list your wallet.
We are happy to do so once we confirm that the wallet is working.
I've installed the Slay Wallet, was able to discover it in the Wallet Picker, but unfortunately I was unable to complete basic workflows.
I think the root of the problem is that upon my registration, no party has been allocated:

No Canton account yet

Also note that I receive the error Invalid Origin when attempting an account with my @digitalasset.com email address. A temporary email did work.

Please provide instructions here for testing your wallet.

@aniiiiXD

aniiiiXD commented Aug 19, 2026 via email

Copy link
Copy Markdown
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants