fix(deepbook-v3): set sender on read-only query transactions

[tonylee08]

Description

Every read-only query method in packages/deepbook-v3/src/queries/ builds its own Transaction, adds a Move call, and simulates it — but none of them ever call tx.setSender(...). This is tolerated under SuiGrpcClient because its core resolution plugin silently substitutes 0x0 for a missing sender. SuiJsonRpcClient has no such substitution, so every single query (e.g. client.deepbook.whitelisted('SUI_USDC')) throws:

Error: Missing transaction sender
  at TransactionDataBuilder.build
  at JSONRpcCoreClient.simulateTransaction
  at PoolQueries.whitelisted

This affects real users today (e.g. market-maker setups still on JSON-RPC) and will continue to until the JSON-RPC sunset on July 31, 2026.

The fix is a one-liner per internal Transaction construction:

const tx = new Transaction();
tx.setSender(this.#ctx.address);

applied to every query method across the ten affected modules (88 total insertions). QueryContext.address is already populated via normalizeSuiAddress(address) in DeepBookConfig, so no new plumbing is needed. The gRPC path is unchanged (an explicit sender takes precedence over the resolution plugin's default).

Follows the pattern of #1018, but applied consistently across all query modules rather than a subset.

Test plan

• pnpm --filter @mysten/deepbook-v3 tsc --noEmit passes.
• pnpm exec prettier -c clean.
• Manually re-run a JSON-RPC reproduction of client.deepbook.whitelisted('SUI_USDC') on mainnet — should return true instead of throwing Missing transaction sender.
• Spot-check gRPC parity (one read-only query from each module) to confirm no behavioral regression.

---

AI Assistance Notice

Please disclose the usage of AI. This is primarily to help inform reviewers of how careful they need to review PRs, and to keep track of AI usage across our team. Please fill this out accurately, and do not modify the content or heading for this section!

• This PR was primarily written by AI.
• I used AI for docs / tests, but manually wrote the source code.
• I used AI to understand the problem space / repository.
• I did not use AI for this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sui-typescript-docs	Ready	Preview, Comment	Apr 16, 2026 2:26pm