✅ Sign in with Solana to interact with smart contracts (canisters) on the Internet Computer (IC)!
✅ Establish a one-to-one relationship between an Solana wallet and an IC identity.
✅ Access the IC capabilities from Solana dapp frontends, create cross-chain dapps! Some of the features IC provide are:
- Native integration with BTC and ETH
- Twin tokens (ckBTC, ckETH)
- Fast finality
- Low transaction fees
- HTTPS outcalls
- Store large amounts of data cheaply
- etc
This React demo application and template demonstrates how to login Solana users into an IC canister using the ic-use-siws-identity hook and ic-siws-provider canister.
The goal of the ic-siws project is to enhance the interoperability between Solana and the Internet Computer platform, enabling developers to build applications that leverage the strengths of both platforms.
👀 Try the live demo: https://guidq-3qaaa-aaaal-qiteq-cai.icp0.io
The demo is buit using Vite to provide a fast development experience. It also uses:
- TypeScript
- TailwindCSS
If you are new to IC, please read the Internet Computer Basics before proceeding.
For a detailed description of the SIWS wallet feature, see the Phantom SIWS description and the SIWE specification, EIP-4361.
This app consists of three main components:
The backend is a Rust based canister that, for demonstration purposes, implements some basic functionality for managing user profiles.
The frontend is a React application that interacts with the backend canister. To be able to make authenticated calls to the backend canister, the frontend needs to have an identity.
The pre-built IC Siws Provider is used to create an identity for the user. It is a a Rust based canister that implements the SIWS login flow. The flow starts with a SIWS message being generated and ends with a Delegate Identity being created for the user. The Delegate Identity gives the user access to the backend canister.
This is the high-level flow between the app components when a user logs in:
- The application requests a SIWS message from the
ic_siws_providercanister on behalf of the user. - The application displays the SIWS message to the user who signs it with their Solana wallet.
- The application sends the signed SIWS message to the
ic_siws_providercanister to login the user. The canister verifies the signature and creates an identity for the user. - The application retrieves the identity from the
ic_siws_providercanister. - The application can now use the identity to make authenticated calls to the app canister.
dfx start --clean --background
make deploy-allThe ic_siws_provider canister is pre-built and added to the project as a dependency in the dfx.json file.
{
"canisters": {
"ic_siws_provider": {
"type": "custom",
"candid": "https://github.com/kristoferlund/ic-siws/releases/download/v0.0.1/ic_siws_provider.did",
"wasm": "https://github.com/kristoferlund/ic-siws/releases/download/v0.0.1/ic_siws_provider.wasm.gz"
},
...
},
...
}Its behavior is configured and passed as an argument to the canister init function. Below is an example of how to configure the canister using the dfx command line tool in the project Makefile:
dfx deploy ic_siws_provider --argument "( \
record { \
domain = \"127.0.0.1\"; \
uri = \"http://127.0.0.1:5173\"; \
salt = \"salt\"; \
chain_id = opt \"mainnet\"; \
scheme = opt \"http\"; \
statement = opt \"Login to the app\"; \
sign_in_expires_in = opt 300000000000; /* 5 minutes */ \
session_expires_in = opt 604800000000000; /* 1 week */ \
targets = opt vec { \
\"$$(dfx canister id ic_siws_provider)\"; \
\"$$(dfx canister id backend)\"; \
}; \
} \
)"For more information about the configuration options, see the ic-siws-provider documentation.
The backend is a Rust based canister that, for demonstration purposes, implements some basic functionality for managing user profiles. It is also given an init argument - the ic_siws_provider canister id - to be able to verify the identity of the user.
dfx deploy backend --argument "$$(dfx canister id ic_siws_provider)"The frontend is a React application that interacts with the backend canister. To be able to make authenticated calls to the backend canister, the frontend needs an identity. The identity is retrieved from the ic_siws_provider canister.
The frontend uses two other packages from the ic-siws project to simplify logging in users and making authenticated calls to canisters:
- ic-use-siws-identity - React hook and context provider for easy frontend integration with SIWS enabled Internet Computer canisters.
- ic-use-actor - A React context provider for managing Internet Computer (IC) actors with enhanced features like type safety and request/response interceptors.
The application's root component is wrapped with SiwsIdentityProvider to provide all child components access to the SIWS identity context.
// main.tsx
import { SiwsIdentityProvider } from 'ic-use-siws-identity';
import { _SERVICE } from "../../declarations/ic_siws_provider/ic_siws_provider.did";
ReactDOM.createRoot(document.getElementById("root")!).render(
<React.StrictMode>
// ...
<SiwsIdentityProvider<_SERVICE>
canisterId={canisterId}
idlFactory={idlFactory}
>
// ... app components
</SiwsIdentityProvider>
// ...
</React.StrictMode>,
);An AuthGuard component is used to protect routes that require the user to be logged in. It also makes sure to log out the user if they change ethereum wallet etc.
To initiate the login flow, the login function is called on the Use the useSiwsIdentity hook.
// LoginButton.tsx
import { useSiwsIdentity } from "ic-use-siws-identity";
function LoginButton() {
const { login, clear, identity, ... } = useSiwsIdentity();
// ...
}See the CHANGELOG for details on updates.
Contributions are welcome. Please submit your pull requests or open issues to propose changes or report bugs.
- kristofer@fmckl.se
- Twitter: @kristoferlund
- Discord: kristoferkristofer
- Telegram: @kristoferkristofer
This project is licensed under the MIT License. See the LICENSE file for more details.