[Bug] Legacy tx.pure moveCall argument syntax in account.ts and manual.ts fails under modern @mysten/sui

Start in packages/sdk/src/account.ts at addDelegateKey and removeDelegateKey, then inspect recallManual in packages/sdk/src/manual.ts. Compare the existing pure argument calls with the proposed @mysten/sui v2 helpers and reproduce the transaction-building flow using @mysten/sui@2.5.0 or higher. Done means the listed PTBs construct and execute cleanly without invalid pure arguments.

Surface

TypeScript SDK (@mysten-incubation/memwal)

Network

All networks (Mainnet / Testnet / Local)

Package version

@mysten-incubation/memwal@0.1.5 (main)

What happened?

packages/sdk/package.json specifies "@mysten/sui": ">=2.5.0". In @mysten/sui v1+ and v2+, the Transaction builder (@mysten/sui/transactions) replaced the legacy @mysten/sui.js two-argument x.pure(typeString, value) API with typed method calls (e.g. x.pure.vector('u8', value), x.pure.string(value)) or direct BCS serializations.

However, several on-chain Move call wrappers in packages/sdk/src/account.ts and packages/sdk/src/manual.ts still use the legacy two-argument form:

1. ddDelegateKey (packages/sdk/src/account.ts:290-291):
   ypescript tx.moveCall({ target: ${opts.packageId}::account::add_delegate_key, arguments: [ tx.object(opts.accountId), tx.object(opts.registryId), tx.pure("vector<u8>", Array.from(pkBytes)), tx.pure("string", opts.label), tx.object(SUI_CLOCK), ], });

2. **
   emoveDelegateKey** (packages/sdk/src/account.ts:341):
   ypescript tx.moveCall({ target: ${opts.packageId}::account::remove_delegate_key, arguments: [ tx.object(opts.accountId), tx.object(opts.registryId), tx.pure("vector<u8>", Array.from(pkBytes)), ], });

3. **
   ecallManual** (packages/sdk/src/manual.ts:508):
   ypescript tx.moveCall({ target: ${this.config.sealPolicyPackageId ?? this.config.packageId}::account::seal_approve, arguments: [ tx.pure("vector<u8>", idBytes), tx.object(this.config.registryId), tx.object(this.config.accountId), ], });

Steps to reproduce

1. Instantiate MemWalManual or call ddDelegateKey /
   emoveDelegateKey in a project with @mysten/sui@2.5.0 or higher.
2. Execute wait addDelegateKey(...) or wait memwalManual.recallManual(...).
3. The transaction builder fails serialization or aborts on-chain because "vector" is treated as the input argument rather than the Move type declaration.

Expected

Transaction arguments should use @mysten/sui v2+ compatible serialization helpers so PTBs construct and execute cleanly.

Actual

The call fails or generates invalid PTB pure arguments.

Proposed Fix

Update packages/sdk/src/account.ts and packages/sdk/src/manual.ts to use x.pure.vector("u8", ...) and x.pure.string(...):

` ypescript
// account.ts - addDelegateKey
arguments: [
tx.object(opts.accountId),
tx.object(opts.registryId),
tx.pure.vector("u8", Array.from(pkBytes)),
tx.pure.string(opts.label),
tx.object(SUI_CLOCK),
]

// account.ts - removeDelegateKey
arguments: [
tx.object(opts.accountId),
tx.object(opts.registryId),
tx.pure.vector("u8", Array.from(pkBytes)),
]

// manual.ts - recallManual seal_approve
arguments: [
tx.pure.vector("u8", idBytes),
tx.object(this.config.registryId),
tx.object(this.config.accountId),
]
`

Checks

• I searched existing issues and this is not a duplicate.
• This report contains no private keys, mnemonics, or other secrets.