Overview
In any web application that integrates CSPR.click you'll be using the Core Web SDK. It provides the essential functionality to interact with wallets and the CSPR.click servers. Through it, you'll request a connection with a wallet to start a user session, and ask the user to sign a transaction or a message. You'll get a complete graphical interface that manages for you the interactions with the user to perform the account management and the signature requests operations.
Get your application Id
To initialize CSPR.click library, you need an appId
for your application. By default, our examples use the csprclick-template
identifier. You may use this value to try out CSPR.click and start developing your application.
Note, though, that this identifier is only valid for development on localhost
. Before you push your application to a server, you must get your own appId
on console.cspr.build.
Supported wallets
CSPR.click supports almost every wallet built for the Casper ecosystem.
Wallet | Provider key | Name |
---|---|---|
| Casper Wallet | |
| Ledger | |
| WalletConnect | |
| CasperDash | |
| Metamask (Snap) | |
| Torus | |
| Casper Signer |
In your application, you can decide which wallets you want to enable. To do so, set accordingly the array of providers in the CsprClickInitOptions initialization object.
Last updated