HelixWallet split from HelixIdentity.

What changed

Before: one HelixIdentity object held both the anchor state (helper data p, rotation history) and the asset bag. After: identity holds anchor state; wallet is a separate object that points to an identity.

Why this matters: it lets us upgrade the wallet layer (address derivation, signing path, asset bag semantics) without touching the identity anchor. The anchor is the load-bearing thing; keeping it stable while iterating on the wallet is architecturally cleaner.

Migration

All existing anchors were migrated in a single atomic transaction — one Sui checkpoint, no downtime, no user action required. Wallet objects were created and bound to their identities via the same bind intent every future wallet will use.

What this unlocks

• Multi-wallet per identity — one biometric can back multiple wallets (checking, savings, cold, hot). All rotate together, all revoke together.
• Foundation upgrades — when the Foundation ships in Q2 2027, it can propose wallet-layer upgrades without touching the identity module. Cleaner governance surface.
• zkLogin variants — different wallets can use different zkLogin proof systems (native, batched, aggregated) without protocol-level changes.

Full ABI diff in the whitepaper appendix D. SDKs already updated (TS + Move). Rust SDK ships with the two-module ABI baked in.