v0.9.1

First published release with 0x hex address format (shell-chain >= v0.23.0). Breaking from 0.8.x: bech32m removed. 48/48 tests pass.

shell-sdk v0.8.2 — aligned with shell-chain v0.22.2

What's Changed

Compatibility

• Version bump aligned with shell-chain v0.22.2
• No breaking API changes from v0.8.1

Full Changelog: v0.8.1...v0.8.2

shell-sdk v0.8.0

shell-sdk v0.8.0 — Proof Input Decode Types

Aligned with shell-chain v0.22.0.

Added

• ShellDecodedProofInput type: structured proof amendment payload decoded from starkReward settlement transactions (requires shell-chain v0.22+).
  Fields: layer, blockNumber, startBlock, endBlock, nSigs, compressedSize, originalSize, settlementTxHash.
• ShellRpcTransaction.decodedInput?: ShellDecodedProofInput | null — filled by the node for starkReward system transactions; null/absent otherwise.
• ShellDecodedProofInput exported from the package root.

Changed

• Aligned with shell-chain v0.22.0 RPC surface.

---

npm install @shellprotocol/shell-sdk@0.8.0

shell-sdk v0.7.1

Added

• Typed Shell RPC reward metadata for address-history and transaction-summary responses, including block gas rewards, STARK rewards, reward layers, source hashes, and compression accounting fields.

Changed

• Preserve pq1-only compatibility from 0.7.0 while aligning the SDK type surface with shell-chain v0.21.1.

shell-sdk v0.7.0

Highlights

• Breaking: SDK address handling is pq1-only; legacy 0x address helpers and normalization are removed.
• Added pq1Address(pubkey, sigType) as the canonical address derivation helper.
• Added SK-only keystore format compatibility with shell-node key generation.
• Fixed ML-DSA-65 signature type ID compatibility and uses the real FIPS 204 implementation.

Compatibility

Requires shell-chain v0.21.0+.

Validation

PR #8 passed Typecheck, Test & Build.

v0.5.0 — AA Phase 2 TypeScript SDK

What's New in v0.5.0

Adds full AA Phase 2 client support aligned with shell-chain v0.19.0.

⚠️ Breaking change: hashBatchTransaction RLP now includes paymaster_context as the 3rd field (was 2-field). Clients on v0.4.x signing AA bundles must upgrade.

---

Added

Types (types.ts)

• SessionAuth interface: session PQ key authorization with session_pubkey, session_algo, target?, value_cap, expiry_block, root_signature, session_signature
• GuardianConfig interface: on-chain guardian set descriptor
• RecoveryProposal interface: active recovery proposal state
• AaBundle extended with optional paymaster_context and session_auth fields
• Constants: AA_MAX_PAYMASTER_CONTEXT = 256, AA_SESSION_KEY_GAS_SURCHARGE = 20_000

Transaction Builders (transactions.ts)

• buildContractPaymasterTransaction: AA bundle with contract paymaster context
• buildSessionKeyTransaction: AA bundle with session key authorization
• hashBatchTransaction: updated to 3-field RLP (adds paymaster_context)

System Contract Encoders (system-contracts.ts)

• encodeSetGuardiansCalldata, encodeSubmitRecoveryCalldata, encodeExecuteRecoveryCalldata, encodeCancelRecoveryCalldata

---

Full changelog: https://github.com/ShellDAO/shell-sdk/blob/main/CHANGELOG.md
Requires: shell-chain v0.19.0+

v0.4.0 — AA Client Types + ML-DSA-65 Canonical Naming

shell-sdk 0.4.0

Consumes shell-chain v0.18.0 AA and Ops features.

Native Account Abstraction (AA) client

• New builders: buildBatchTransaction, buildSponsoredTransaction, buildInnerTransfer, buildInnerCall
• Hash function: hashBatchTransaction — computes batch_signing_hash (domain 0x42)
• New types: AaInnerCall, AaBundle, ShellEstimateBatchResult, ShellBatchInnerGas, ShellPaymasterPolicy, ShellIsSponsoredResult, ShellWitnessRootResult
• Constants: AA_BUNDLE_TX_TYPE = 0x7e, AA_MAX_INNER_CALLS = 16

New provider methods

• estimateBatch(request) → shell_estimateBatch
• getPaymasterPolicy(address) → shell_getPaymasterPolicy
• isSponsored(txHash) → shell_isSponsored
• verifyWitnessRoot(block) → shell_verifyWitnessRoot

ML-DSA-65 canonical naming

• "ML-DSA-65" is now the canonical SignatureTypeName (FIPS 204)
• "Dilithium3" and "MlDsa65" remain as backwards-compat aliases

Compatibility

• Fully backwards-compatible with sdk 0.3.x and chain v0.17.0