Skip to main content
Wallet creation is the first place where the SDK’s prepared-transaction model shows up clearly.

​
Two create modes

You can create a wallet either:
  • from a policy with policyId
  • from an inline initialUser
If policyId is omitted, the backend can create a no-recovery wallet from the inline authority you provide. Common authority shapes are ed25519, secp256k1, and secp256r1.

​
Basic create flow

const created = await swig.wallets.create({
  feePayer,
  initialUser: {
    ed25519: {
      publicKey: userPublicKey,
    },
  },
});
Passkey-backed creation works the same way with secp256r1: 
const created = await swig.wallets.create({
  feePayer,
  initialUser: {
    secp256r1: {
      publicKey: passkeyPublicKey,
    },
  },
});
EVM-backed creation works the same way with secp256k1: 
const created = await swig.wallets.create({
  feePayer,
  initialUser: {
    secp256k1: {
      publicKey: evmPublicKey,
    },
  },
});

​
What you get back

The result is not just one transaction. It is a categorized create plan:
FieldMeaning
walletthe config address and wallet address
transactionsfull ordered transaction list
clientAuthorityTransactionstransactions the initial authority must sign
operatorSignedTransactionstransactions already signed by the backend operator
feePayerOnlyTransactionstransactions that only need fee payer or sponsor handling
For plain non-recovery creates, this usually collapses to one main creation transaction plus any client authority signing the create flow needs.

​
Recovery-enabled create flows

If the policy is recovery-enabled and the SDK can derive both the requester authority and guardian information, create(...) also returns recoverySetup. That setup plan is not the same thing as completed recovery setup. It is the follow-up input for wallet.recovery.prepareSetup(...).

​
What to submit

Always submit the prepared transactions in order. Do not reorder the list. If clientAuthorityTransactions.length > 0, those transactions must be signed by the client authority before submission. If operatorSignedTransactions.length > 0, treat them as already operator signed. They still need fee payer or sponsor submission, but not another authority signature.