Issue description

If you use Solana on Fireblocks, you may have recently experienced a situation where you may not see it in your Fireblocks Console transaction history or when using Fireblocks API.

If this occurs when transferring SOL_TEST to a Fireblocks vault account, you may see the transaction as confirmed on-chain, but do not see it in your Fireblocks wallet. Also, when you examine the wallet address balance on a chain explorer, you do not see the transfer.

There are two separate non-production Solana chains: Testnet and Devnet. Fireblocks only supports the Devnet chain. In this case, the transfer you expected to receive was sent on the wrong Solana chain - the Solana Testnet chain. You cannot use these chains interchangeably.

Resolution

Refer to the following steps to verify the correct chain is being used:

1. Search for the transaction by the transaction hash or destination address incoming transaction on the Solana Testnet explorer.
   • If you find it, that means the sender sent it to a blockchain network that Fireblocks does not support. Unfortunately, we will not be able to recognize this transaction. Ask the sender to resubmit it on the Solana Devnet blockchain.
     • Your sender then initiates a new transaction on the correct chain.
2. Search for the incoming transaction on the Solana Devnet explorer, by transaction hash or by destination address.
   • If you find the transaction, that means you sent it on the correct chain but still had an issue. This likely means that the asset that was transferred to you is on the correct blockchain, but it is not in your list of supported assets in your workspace yet. In this case, contact Fireblocks Support to examine this further and add it.
3. If you do not find it, it means the sender either sent it to a different destination contract address.
   • Ask the sender to specify which asset contract address they sent it to.
   • Ask the sender to specify which blockchain network they sent it on.
   • Ask Fireblocks Support to add that asset to your workspace and to recognize the incoming transaction in your workspace. Then ask them to re-scan for it.