Skip to main content
This is the fastest path to a working self-custodial wallet. No seed phrase. You hold the wallet and the WalletSuite signing service holds a co-signing share, so both are needed to sign. A few steps and you have a signed transaction on chain.

Prerequisites

Steps

1

Install the SDK

Add the WalletSuite wallet SDK to your project.
2

Create your wallet

Create an SDK client pointed at the WalletSuite signing service and pass your API key.Creating the wallet returns the wallet blob. Save it to your own storage before you continue, since you hold it and WalletSuite does not.
Persist the wallet to durable storage you control, never a temp directory, and keep a secure backup. Your backup is your recovery. It is 2-of-2 by default. For storage patterns, see Shares & thresholds.
3

Derive an address

Turn the wallet into an on-chain address. This runs locally with no network call. One wallet works everywhere, so the same wallet derives addresses across 84 chains.
One wallet covers every chain. Pass it to deriveAddress for any of them. See One wallet, every chain.
4

Sign the transaction

Sign with signEvm7702, which signs the EIP-7702 (type-4) smart-account transaction format and returns it ready to broadcast.Each signature is authorized automatically: the SDK mints a single-use, payload-bound signing intent for you, so you pass only the transfer. See Signing intents for how that works under the hood.
The SDK signs but does not broadcast, so send the result in the next step. For more signing paths, see Signing.
5

Broadcast the transaction

Submit the signed transaction. Use your own RPC, or POST the raw transaction to WalletSuite and check status by hash. See the send endpoint reference at https://api.walletsuite.io/docs#tag/transactions/POST/api/txs/send.
For confirmation handling and event-driven delivery, see Broadcasting. To react to confirmed transfers without polling, see Webhooks.

Next steps

End-to-end walkthrough

The complete journey from wallet creation to a confirmed transaction.

Signing intents

How every signature is pre-authorized under the hood, with nothing to implement.

Signing

Every signing path across 84 chains.

Broadcasting

Submit signed transactions through WalletSuite or your own RPC, and track confirmation.