QoL batch 3

[nazreen]

Solana OFT debug script: state that value 0 for confirmations means 'use default'

Closes DEVREL-1238

When running:

npx hardhat lz:oft:solana:debug --eid <eid> --dst-eids <dst-eids>  

Before:

           confirmations: 0                                        

After:

           confirmations: 0 (Use Pathway Defaults)

Solana OFT - updateMetadata script supports Token-2022 Metadata Update

Closes DEVREL-1239

Problem

• lz:oft:solana:update-metadata only supported Metaplex metadata, not Token-2022.

Solution

• Auto-detect metadata type: SPL Token → Metaplex; Token-2022 → probe Metaplex first, else Token Extensions.
• Add updateTokenExtensionsMetadata() with authority validation and rent handling for multisig.

Changes

• updateMetadata.ts: Auto-detect and support Token-2022 metadata with authority checks and rent top-up.

Example Run

pnpm hardhat lz:oft:solana:update-metadata --eid 40168 --mint <MINT> --name "New Name"

[github-actions]

🧪 E2E Test Status

E2E tests are non-blocking and validate real blockchain interactions. Failures may occur due to network issues, RPC rate limits, or external service downtime.

Test Runs (Newest First):

• ✅ Run #6713 - Passed - 2026-02-10 16:40 (UTC)
• ✅ Run #6709 - Passed - 2026-02-10 02:40 (UTC)
• ✅ Run #6673 - Passed - 2026-02-03 17:18 (UTC)
• ✅ Run #6661 - Passed - 2026-01-29 16:57 (UTC)
• ✅ Run #6628 - Passed - 2026-01-23 22:05 (UTC)

[cursor]

PR Summary

Medium Risk
Adds new Solana transaction-building logic for Token-2022 metadata updates (authority checks, rent transfers, multisig flow), which could affect on-chain update behavior if incorrect; other changes are small QoL improvements.

Overview
Improves Solana OFT task UX and expands metadata update support.

lz:oft:solana:update-metadata now auto-detects whether a mint uses Metaplex metadata or Token-2022 Token Extensions metadata, and adds a Token Extensions update path that validates update authority and optionally tops up rent (including multisig/vault flows by emitting base58 tx data for Squads).

lz:oft:solana:debug now labels confirmations: 0 as "0 (Use Pathway Defaults)", and getOftStoreAddress no longer emits a warning when the deployment file is simply missing (returns null silently, warning only on malformed content).

^{Written by Cursor Bugbot for commit cbc787d. This will update automatically on new commits. Configure here.}

[nazreen]

bump @lzJxhn

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

[St0rmBr3w]

debug.ts and index.ts changes look good. The "Use Pathway Defaults" label for 0 confirmations is a nice touch, and silencing the warning when the deployment file doesn't exist yet makes the create flow much cleaner. Changesets are appropriate.

On updateMetadata: the auto-detection logic (SPL Token -> Metaplex, Token-2022 -> probe for Metaplex PDA first, fall back to Token Extensions) is solid. The early hasFieldUpdates check prevents the rent-only footgun that bugbot flagged, and keypair resolution goes through getSolanaKeypair() as expected.

Looks good to merge.

[St0rmBr3w]

LGTM!