Conversation
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 <ideogram758@gmail.com>
9408e2b to
63b1403
Compare
mjuchli-da
left a comment
There was a problem hiding this comment.
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.
|
Hi March , Actually we were on maintenance right now and a newer version of
extension wallet have been pushed and it will take some time in review , i
will surely ping you once the new version gets released it would be super
efficient to use .
Meanwhile you can checkout the app at slay.money with all working features
, the new extension contains robust support for CIP 103 native connections
and swaps .
You need to make an account and will need a bypass coupon to access the
wallet at earliest use this : SLAY-659645CE
I would ping you as soon as the new extension gets reviewed and published,
kindly keep this on hold and not reject .
…On Wed, Aug 19, 2026 at 2:31 PM Marc Juchli ***@***.***> wrote:
***@***.**** commented on this pull request.
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.
—
Reply to this email directly, view it on GitHub
<#2313?email_source=notifications&email_token=BCHPKMZ2TIE6GRKUVNGEVXT5KVUFHA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTIOJXGAZTMMBSGYZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#pullrequestreview-4970360262>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BCHPKM736YQANO4H2TX6HIL5KVUFHAVCNFSNUABFKJSXA33TNF2G64TZHM4TSMZTGM2DEMBSHNEXG43VMU5TKMJYGUYDAMZZGY4KC5QC>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/BCHPKM4MZ4DBXYM47D2XOIT5KVUFHA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTIOJXGAZTMMBSGYZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG>
and Android
<https://github.com/notifications/mobile/android/BCHPKM4AQTZSSWQNRNFNX235KVUFHA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTIOJXGAZTMMBSGYZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hi @mjuchli-da this is ready for another look. The maintenance is done and the fixes that blocked your last test are live: • Updated build v0.5.3 is published on the Chrome Web Store: Two-minute test:
Runtime discovery already works (the wallet is announced automatically); this |
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 usesbrowser:ext:<extension-id>, but announce-discovery.ts storesdetail.idverbatim with no transformation, so the registry id has to match what the wallet actually announces — for us that ismoney.slay. Using thebrowser: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.