Skip to main content

Authentication

Use the useHeliusWallet hook to read auth state and drive sign-in:
Calling login() opens the wallet modal with the auth methods you enabled. After sign-in, status becomes "authenticated" and user is populated with the user’s id, sub-organization id, and wallet id. Choose which sign-in methods appear in the dashboard — see Configure sign-in methods.

Signing and sending

useHeliusWallet exposes the wallet address, signing methods, and a ready-to-use Solana Connection wired to Helius RPC.

Sign a message

Sign and send a transaction

signAndSendTransaction signs the transaction client-side and submits it through Helius. It takes a serialized transaction and returns the transaction signature.
Use signTransaction instead of signAndSendTransaction when you want the wallet’s signature without broadcasting — for example, to add it to a multi-party transaction before submitting it yourself.

Read transaction history

getTransactions requires the server route handler — it isn’t available in the default client-only (Secure RPC) mode.

Export the wallet

Wallets are non-custodial, so users can take their keys with them. exportWallet opens a secure, encrypted flow for the signed-in user to reveal and export their private key.

Next steps

API reference

The full useHeliusWallet() surface and imports.

Migrating from Privy

Move existing Privy wallets to Helius WaaS