Wallet and RPC troubleshooting

Use these checks when connecting a wallet, requesting Test TAV or submitting a transaction. Retain the original transaction hash whenever a submission result is unclear.

Common problems

Symptom	What to check
RPC returns HTTP 503	Service availability and endpoint URL; try a read request later.
Balance looks wrong	Selected chain ID 771002 and the intended account.
Wallet cannot add the network	Exact network settings, RPC availability and browser profile where the wallet is installed.
Faucet challenge fails	Complete the challenge normally. Never provide keys or pay for test tokens.
Faucet cooldown	Allow 24 hours for the recipient address; inspect the existing claim/hash.
RPC returns HTTP 429	Back off. Users behind the same public IP share the quota.
Submission times out	Look up the original transaction hash and account nonce before replacing it.
Receipt status is `0x0`	Execution failed; inspect the contract error and gas behavior.
Explorer does not list the transaction	Check the RPC receipt and allow time for indexing.

Get help

Email support@safeney.com with the tool version, network, exact error, reproduction steps and public transaction hash. Use Report an issue for a checklist. Never send seed phrases, private keys, passwords or CAPTCHA secrets. Debug tracing is not a public service; do not expose a private node endpoint to work around it. For a node startup or sync problem, use Troubleshoot a node.

Getting started

Smart contracts

Tools and resources

API reference

Help

Wallet and RPC troubleshooting

Common problems

Get help