ts-sdk-account

TypeScript SDK: Account (Signer)

Purpose

Guide creation and use of Account (signer) in @aptos-labs/ts-sdk. An Account holds address + key material and can sign transactions and messages. Creating an Account does NOT create the account on-chain; use faucet or transfer to fund it.

ALWAYS

1. Use Account.generate() or Account.fromPrivateKey() only in server/script – never in frontend; use wallet adapter for end users.
2. Load private keys from env (e.g. process.env.PRIVATE_KEY) on server – never hardcode.
3. Use account.accountAddress when building transactions – pass as sender/secondary signers.
4. Use aptos.signAndSubmitTransaction({ signer: account, transaction }) with the same Account instance that holds the key.

NEVER

1. Do not use Account.generate() or raw private keys in browser/frontend – use wallet adapter.
2. Do not hardcode private keys in source or commit to git.
3. Do not confuse Account (API namespace) with Account (signer class) – API is aptos.account.*; signer is the class from Account module (e.g. Account.fromPrivateKey).

---

Account types (signing schemes)

Type	Class	Use case
Ed25519 (legacy)	Ed25519Account	Single Ed25519 key, legacy auth
SingleKey	SingleKeyAccount	Ed25519 or Secp256k1, unified auth
MultiKey	MultiKeyAccount	Multi-sig
Keyless	KeylessAccount	Keyless (e.g. OIDC)
Federated Keyless	FederatedKeylessAccount	Federated keyless

---

Generate new account (server/script only)

import { Account, SigningSchemeInput } from "@aptos-labs/ts-sdk";

// Default: Ed25519 legacy
const ed25519Account = Account.generate();

// SingleKey (unified) with Ed25519
const singleKeyAccount = Account.generate({ scheme: SigningSchemeInput.Ed25519, legacy: false });

// SingleKey with Secp256k1
const secpAccount = Account.generate({ scheme: SigningSchemeInput.Secp256k1 });

// Access address and public key
const address = ed25519Account.accountAddress;
const pubKey = ed25519Account.publicKey;