v11.7.1

What's Changed

Fixed: wallet-auth writes were corrupting camelCase request bodies

Fetcher.request snake_cases every request body by default, but four wallet-auth endpoints declare camelCase properties in their OpenAPI schemas, so they were being sent keys the server doesn't recognise:

Method	Behaviour on 11.7.0
setProfileNftPfp	Always failed — contractAddress and tokenId are required
createProfileImageUpload	Always failed — imageType and contentType are required
updateProfileSettings	Returned 200 but silently discarded displayName, externalUrl, profileImageToken, bannerImageToken (only bio applied)
cancelOrder	Silently dropped offererSignature, turning a signed cancel into an unsigned one

All four now send the body verbatim, the same opt-out the Seaport order and offer helpers already used. Endpoints whose wire format really is snake_case are unchanged.

If you called setProfileNftPfp or createProfileImageUpload on 11.7.0, they could not have succeeded — upgrading is required, not optional.

Added: wallet visibility and agent profile relationships

• WalletAuthAPI.makeWalletPrivate(wallet) — PUT /api/v2/accounts/wallets/{wallet}/private
• WalletAuthAPI.makeWalletPublic(wallet) — DELETE /api/v2/accounts/wallets/{wallet}/private
• WalletAuthAPI.getAgentProfileRelationships(addressOrUsername) — GET /api/v2/accounts/{address_or_username}/agent-relationships
• New exported types: WalletVisibilityResponse, AgentProfileRelationshipsResponse, SvmInstructionAccountResponse, SvmInstructionResponse, SvmTransactionDetailsResponse

Also

• Chain.StableChain (chain id 988) added to the SDK and generated chain maps.
• SwapTransactionResponse.svm is now typed for structured Solana transaction contents. Swap execution remains EVM-only for now.

Full Changelog: v11.7.0...v11.7.1