Error Codes & Troubleshooting

When interacting with the Verdant Program or SDK, you may encounter specific error codes. This reference guide helps debug common integration issues.

SDK Error Codes

Error Code	Name	Description	Suggested Fix
0x1000	INVALID_SIGNATURE	The wallet signature does not match the Intent data.	Ensure the user has not rejected the signature request and that the payload is not malformed.
0x1001	INSUFFICIENT_SHARD_BALANCE	The aggregate balance of the active shards is less than the requested transfer amount.	Deposit more funds into the Persona or reduce the transfer amount.
0x1002	ROUTE_NOT_FOUND	The routing engine could not find a path that meets the privacy constraints.	Increase the Slippage tolerance or lower the PrivacyLevel to allow for more direct routes.
0x1003	NETWORK_CONGESTION	The Solana network is experiencing high traffic, causing transaction timeouts.	Retry the intent with a higher priority fee setting in the SDK config.

RPC & Network Issues

Problem: "Transaction expired" or "Blockhash not found"

• Cause: This usually happens on Solana Devnet when the network is unstable.

• Solution: Implement a retry logic in your application with an exponential backoff strategy. The Verdant SDK has a built-in autoRetry config that can be enabled.

Problem: Shards not appearing after generation

• Cause: The indexing service may be lagging behind the blockchain.

• Solution: Call client.refreshShards() to force a re-fetch of the on-chain state for the current Persona.

Getting Support

If you encounter an error not listed here, please open an issue on our GitHub repository or join the #dev-support channel in our Discord community. Please provide the Intent Hash and the Error Code to help us diagnose the issue faster.