If funds cannot be sent, the issue is likely due to one of two scenarios: the transaction cannot be initiated, or something went wrong during the transaction. In the case of a failed transaction, the transaction status can be checked on a blockchain explorer like CeloScan or EtherScan. Any errors listed will help identify the issue. For in-app errors, support should be contacted with logs and screenshots.
Here are some common reasons for failed or invalid transactions and how to resolve them:
Invalid Address
Valora verifies that a properly formatted address is used. For example, an address missing a character or not beginning with "0x" will prevent the transaction from being initiated.
To avoid mistakes, it is recommended to send a small test transactions before sending a large amount or when sending to a new wallet address. Copying and pasting the address and comparing the first 4 and last 4 characters will also help ensure accuracy.
Gas Fees
Every transaction requires a fee, which is paid using the network’s default token (e.g., ETH for Ethereum or CELO for Celo). On the Celo network, dapps and wallets may allow fees to be paid with a Celo native stablecoin, which Valora supports.
If a gas fee error occurs, it can be identified by viewing the Transaction Details page on a blockchain explorer. Common error messages indicating gas fee issues include:
- "Error: execution reverted"
- "Insufficient funds for gas * price"
This error can be resolved by increasing the balance of the fee token or reducing the amount being sent. For example, if there is 0.5 ETH and the attempt is to send 0.49 ETH, a gas fee error may occur if gas fees exceed 0.01 ETH. To resolve, either add more ETH or adjust the send amount accordingly.
Network Issues
Occasionally, network issues such as congestion, attacks, bugs, or updates may prevent transactions. In cases of repeated failures, check the network's social media for news. If no outages are reported, waiting and trying again later may be necessary.
Wallet Issues
If none of the above apply, there may be a bug. In this case, contact us directly with your logs attached so we can resolve this as soon as possible.