Custom Wallet Types

​

Overview

​

When to Use Custom Class Hashes

• Your project has a custom account contract with special features (spending limits, social recovery, multisig)
• You need a specific audited account version (e.g., CHIPI v33 with spending policy)
• You’re building on top of an account standard not yet included in the SDK defaults

​

Requirements

​

Creating a Wallet with Custom Class Hash

const wallet = await serverClient.createWallet({
  params: {
    encryptKey: "user-pin",
    externalUserId: "user-123",
    chain: Chain.STARKNET,
    classHash: "0x0484bbd2404b3c7264bea271f7267d6d4004821ac7787a9eed7f472e79ef40d1",
  },
});

wallet = client.create_wallet(
    encrypt_key="user-pin",
    external_user_id="user-123",
    chain=Chain.STARKNET,
    class_hash="0x0484bbd2404b3c7264bea271f7267d6d4004821ac7787a9eed7f472e79ef40d1",
)

• The SDK uses your class hash instead of the default CHIPI or READY hash
• The wallet address is computed from your class hash + constructor calldata
• The Chipi paymaster sponsors the deployment (if your account supports SNIP-9)

​

Known Compatible Class Hashes

​

Upgrading Custom Wallets

const upgrade = await serverClient.prepareWalletUpgrade({
  publicKey: wallet.publicKey,
  targetClassHash: "0x<new-class-hash>",
});

​

Feature Compatibility

​

Related

• createWallet - API reference
• Wallet Upgrades - Upgrade between wallet types