​

1.0.0

Released on April 17th, 2026 Wallet SDK v1 is the new long-term API shape for application development. Rather than being an additive patch to v0, v1 introduces a cleaner and more explicit model focused on composability, multi-party flows, and transport flexibility. Why move to v1

• Stateless and safer by default: v1 removes global SDK/controller party state and requires explicit partyId at call time, which improves thread safety and makes concurrent multi-party operations much easier to reason about.
• Clearer transaction lifecycle: flows are modeled as explicit prepare -> sign -> execute steps, improving observability and reducing hidden behavior.
• Better API organization: v0 controllers are replaced by namespaces (ledger, party, token, amulet, user, asset, events) with clearer boundaries and easier discoverability.
• More flexible integration model: v1 supports static configuration and provider-based initialization, making it easier to integrate with browser, dApp, remote wallet, and alternative transport setups.
• Improved extension model: optional functionality can be enabled via extend() which keeps base initialization small and purpose-driven.

This release note intentionally avoids listing every single method-level change. For full migration details and examples, use the migration guide:

• Wallet SDK v1 Migration Guide
• v1 Ledger Migration
• v1 Token Migration
• v1 Party Migration
• v1 User Migration