Invalid param: could not find account
The RPC node cannot find an account at the specified address. The account either never existed, was closed, or you are querying the wrong network.
Common causes
- Account does not exist. The address was never funded or the account was never created.
- Wrong network. The account exists on devnet but you are querying mainnet, or vice versa.
- Account was closed. A program account (like a token account) was closed and its lamports returned to the owner.
- Wrong address. Typo in the public key, or you passed a mint address instead of a token account address (or vice versa).
How to fix
- Verify the address is correct and on the right network.
- Use getAccountInfo — it returns
nullfor nonexistent accounts without throwing an error. - For token accounts, derive the correct Associated Token Account (ATA) address from the wallet and mint.
FAQ
Does this mean I lost funds? No. If the account never existed, no funds were there. If it was closed, the lamports were sent to a recipient specified in the close instruction.
How do I check if an account exists?
Use getAccountInfo with the address. A null result means the account does not exist. A non-null result includes the account data and owner program.
Why does getBalance work but getAccountInfo returns null?
Both return null/zero for nonexistent accounts. If you see a balance but getAccountInfo fails, double-check you are using the same address and commitment level.
Error text variants
-
Invalid param: could not find account -
could not find account
Updated: