[nazreen]

Problem

We have an important partner who uses a non-Squads multisig. The current implementation results in the assertion being triggered. Due to this, that parter's implementation had to fork the devtools-solana package. This PR will remove the need to maintain that fork.

Changes

Introduce env var to allow for skipping of assertValidSolanaAdmin. This was the simplest change possible given the requirement.

Testing

• Deploy Solana OFT as usual.
• Wire as usual.
• Modify LZ Config to update the solanaContract's delegate to be a PDA not owned by System Program or the Squads Multisig Program. For simplicity, we can use the ULN302 Msg Lib PDA (2XgGZG4oP29U3w5h4nTk1V2LFHL23zKDPJjs3psGzLKQ)

Run without the env var

npx hardhat lz:oapp:wire --oapp-config layerzero.config.ts
...
Error: SOLANA_INVALID_OWNER_OR_DELEGATE
Fix suggestion: The owner or delegate of the Solana OApp must either be a regular on curve address or a Squads Vault Account.
Elaboration: Ensure that you are using a regular on-curve Solana address or a Squads Vault PDA as the owner or delegate of the OApp.

error:   [OApp] Failed to check OApp delegate for [DgQrWVJvhgRigzKA5Kyz3qnRHV54X2tPmVRpsULma5Uu @ SOLANA_V2_TESTNET]: Error: Invalid owner/delegate address 2XgGZG4oP29U3w5h4nTk1V2LFHL23zKDPJjs3psGzLKQ. Must be a valid on-curve address or a Squads Vault PDA.
error:   [OApp] Failed to check OApp configuration: Error: Invalid owner/delegate address 2XgGZG4oP29U3w5h4nTk1V2LFHL23zKDPJjs3psGzLKQ. Must be a valid on-curve address or a Squads Vault PDA.
An unexpected error occurred:

Run with the env var

$ LZ_SKIP_SOLANA_ADMIN_VALIDATION=1 npx hardhat lz:oapp:wire --oapp-config layerzero.config.ts
...
info:    [OApp] Checking OApp delegates configuration

Warning:LZ_SKIP_SOLANA_ADMIN_VALIDATION is set. Skipping Solana admin validation. Only use this is you are using a non-Squads Multisig

info:    [OApp] ✓ Checked OApp delegates
info:    [OApp] ✓ Checked OApp configuration
info:    There is 1 transaction required to configure the OApp
? Would you like to preview the transactions before continuing? › (Y/n)

[github-actions]

🚨 E2E Tests Failed

The E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:

• Network connectivity issues
• RPC rate limiting
• External service downtime
  Action Run: https://github.com/LayerZero-Labs/devtools/actions/runs/20175893277

This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information.

[github-actions]

🚨 E2E Tests Failed

The E2E tests failed during CI. These tests validate real blockchain interactions and may fail due to:

• Network connectivity issues
• RPC rate limiting
• External service downtime
  Action Run: https://github.com/LayerZero-Labs/devtools/actions/runs/20720752750

This is non-blocking and does not prevent merging. Check the action logs above for detailed failure information.

[cursor]

PR Summary

Adds an opt-in escape hatch to unblock non-Squads multisig setups.

• Introduces LZ_SKIP_SOLANA_ADMIN_VALIDATION in assertValidSolanaAdmin; when set, validation is skipped with a warning
• Passes the env var through in turbo.json globalPassThroughEnv
• Adds a changeset for a patch release

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

[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 #6613 - Passed - 2026-01-22 18:27 (UTC)