-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing to Transfer Native SOL from Solana to Ethereum #669
Comments
Also failures when trying to bridge WSOL on Ethereum to SOL on Solana when trying to claim assets on Solana:
|
Please confirm if this issue is on Mainnet or Testnet? If on Mainnet, could first try with the Testnet? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to bridge native SOL to WSOL on Ethereum. However, I am getting the following error when bridging:
Its raised when calling initiateTransfer().
When listening to the http requests, the failing rpc call is the following:
It returns the following:
With debug mode switched on for the Solana signer, the logs are the following:
UPDATE 1
I was able to bridge successfully when providing the optional
SolanaSendSignerOptions.PriorityFeeOptions
values to thegetSolanaSignAndSendSigner()
function. However, even when providing very high fee values here:It does not consistently successfully complete the solana transfer, failing with the same above
SendTransactionError: failed to send transaction: Internal error
error often.Example failing RPC request:
Response:
This failing RPC call is after many RPC calls for the method
getBlockHeight
.UPDATE 2
With manually set very high gas values, funds get sent to the bridge but initiateTransfer() still throws
SendTransactionError: failed to send transaction: Internal error
even though funds have been sent to the bridge. No transaction ID is returned either, so I can not programmatically start the recovery process either.Transaction sending 0.0222 SOL to the bridge here.
Error from SDK:
RPC Call:
Result:
The text was updated successfully, but these errors were encountered: