DEVREL-916 fix (examples/oapp-solana): update message library PDAs and config PDAs checks

[nazreen]

Problem

Running the wire task might result in

error:   [OApp] Failed to check send libraries for [CbUo5icVrxb1Gq9UhZKs7zQnzZxcx3PCWfKitwta4eiy @ SOLANA_V2_MAINNET] → [0x8e06d6df9880b641662D8e12a35c09c05c1e1CDe (BBOApp) @ BOUNCEBIT_V2_MAINNET]: Error: Failed to check the default send library for Solana program @ [76y77prsiCMvXMjuoZ5VRrhG5qYBrUMYTE5WgHqgjEn6 @ SOLANA_V2_MAINNET] for CbUo5icVrxb1Gq9UhZKs7zQnzZxcx3PCWfKitwta4eiy for BOUNCEBIT_V2_MAINNET: Error: Unable to find defaultSendLibraryConfig/sendLibraryConfig account at 8o69tuDaboy2Vu6NuLJx1joh8Ri4UMSUGEfxdvM2frB7/C53akiGwMxaaUk1a13UNLi8Aqeqyx4RmW7sUBRmagmyB

Diagnosis:

• the sendLibraryConfig account was not initialized despite having run init-config prior to running the wire task

Background

For a Solana OApp wiring to work, there are two types of PDAs that are needed: Send/Receive Library PDAs (owned by Endpoint program) and ULN Config PDAs (owned by the ULN program)

#1645 fixed an issue that would appear during wiring where init-config would falsely report that all PDAs were initialized (bug introduced by a change upstream) when in fact they were not, resulting in an error when running the wire command. This PR however applied the fix only for oft-solana, but not for oapp-solana.

The fix involves updating sendConfigIsInitialized to also check send/library config accounts. We need the same for oapp-solana.

Changes

Instead of checking only for ULN config accounts, we should also check for send/receive library config accounts.

[DanL0]

Testing:

LAYERZERO_EXAMPLES_REPOSITORY_REF=fix-oapp-solana-init-config LZ_ENABLE_SOLANA_OAPP_EXAMPLE=1 npx create-lz-oapp@latest

[DanL0]

it works

proof of test:

• https://testnet.layerzeroscan.com/tx/KxEc9R5wN5rWayK37G93WwL7jxG1L9iPXL7FzMvVaHtRRPV1Ab1dJ4zWp5ApnNj2Dty5jn5Enh2gYCmr3qY2KsD
• https://testnet.layerzeroscan.com/tx/0xec9af6946491514fa80982c81df5133506e4d0b6ba56c1ada2cd77836ed8d090

[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/19745705086

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/19772090685

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/19914368194

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/19914521581

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