You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am encountering a signature verification failure when using the transferNativeSol function from the Wormhole SDK. The issue arises during the bridging of native SOL tokens from Solana to another chain. Specifically, the transaction fails with a signature verification error for Program Derived Addresses (PDAs) or ancillary accounts that should not require manual signatures.
I am manually signing the transaction using the necessary keypairs (payer and sender) as expected. However, the error persists, indicating that signatures for certain PDAs are missing or invalid, even though these addresses should be handled automatically by the Solana runtime.
Steps to reproduce
Use transferNativeSol from Wormhole SDK to initiate a native SOL token transfer.
Sign the transaction with the payer / sender keypairs.
The transaction fails with the following error message:
Error: Signature verification failed.
Invalid signature for public key(s) [`7o62Jhwp1WHnSiUrfYGTo3D9cb33tDwxU1H3uqvCezdL`, `HMFJPt3hGdtNRwXcQa3moEEwkZaPukjR9G3i4hdbY2aU`].
These public keys correspond to PDAs or ancillary accounts, which are derived automatically by the Wormhole SDK or the Solana runtime. These addresses should not require manual signatures.
Expected behavior
The Program Derived Addresses (PDAs) or ancillary accounts created during the transaction should not require explicit manual signing. The Solana runtime is expected to handle the signature verification for these addresses without issues. The transaction should succeed with only the necessary keypairs being signed (payer and sender).
Solution recommendation
Ensure that PDAs and ancillary accounts used in the transferNativeSol function are handled automatically by the Wormhole SDK, without requiring manual signatures. The SDK should align with Solana's expected runtime behavior where PDAs are verified without manual intervention.
The text was updated successfully, but these errors were encountered:
Description and context
I am encountering a signature verification failure when using the
transferNativeSol
function from the Wormhole SDK. The issue arises during the bridging of native SOL tokens from Solana to another chain. Specifically, the transaction fails with a signature verification error for Program Derived Addresses (PDAs) or ancillary accounts that should not require manual signatures.I am manually signing the transaction using the necessary keypairs (payer and sender) as expected. However, the error persists, indicating that signatures for certain PDAs are missing or invalid, even though these addresses should be handled automatically by the Solana runtime.
Steps to reproduce
transferNativeSol
from Wormhole SDK to initiate a native SOL token transfer.Code Snippet:
Experienced behavior
The transaction fails with the following error message:
These public keys correspond to PDAs or ancillary accounts, which are derived automatically by the Wormhole SDK or the Solana runtime. These addresses should not require manual signatures.
Expected behavior
The Program Derived Addresses (PDAs) or ancillary accounts created during the transaction should not require explicit manual signing. The Solana runtime is expected to handle the signature verification for these addresses without issues. The transaction should succeed with only the necessary keypairs being signed (payer and sender).
Solution recommendation
Ensure that PDAs and ancillary accounts used in the
transferNativeSol
function are handled automatically by the Wormhole SDK, without requiring manual signatures. The SDK should align with Solana's expected runtime behavior where PDAs are verified without manual intervention.The text was updated successfully, but these errors were encountered: