> For the complete documentation index, see [llms.txt](https://docs.chestfi.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chestfi.cash/support/troubleshooting.md).

# Troubleshooting

#### "Wrong network" or the network indicator isn't green

You're connected to a chain other than Robinhood Chain. Switch networks in your wallet, or add the network manually using the parameters in Getting Started. Reload the Web App after switching.

#### The Connect Wallet button does nothing

* Disable aggressive ad-blockers or privacy extensions for `app.chestfi.cash`.
* Make sure your wallet extension is unlocked.
* Try a different browser. Brave and hardened Firefox profiles sometimes block wallet injection.
* On mobile, open the app through your wallet's built-in browser rather than Safari or Chrome.

#### My transaction failed / reverted

Work through these in order:

1. **Insufficient ETH.** You need enough for both the ChestFi fee and gas. Check your balance in the header.
2. **Missing approval.** Locking and burning require an `approve` transaction first. If you rejected it or it's still pending, the second transaction reverts.
3. **Insufficient token balance.** You can't lock or burn more than you hold at execution time.
4. **Unlock date in the past.** `Lock Until` must be in the future. If you set a time only minutes ahead and the transaction sat pending, it may have expired.
5. **Incompatible token.** Tax, fee-on-transfer, and rebasing tokens will fail — or worse, succeed and strand your funds. See Token Locker.

#### I created a token but don't see it in my wallet

Wallets don't discover tokens automatically. Import it manually using the contract address returned at deployment. Search your deployment transaction on [robinhoodchain.blockscout.com](https://robinhoodchain.blockscout.com) if you didn't save the address.

#### I lost my token's contract address

Open your wallet address on the explorer, find the deployment transaction, and read the created contract address from it. Every deployment is permanently recorded.

#### My lock isn't showing in "My Locks"

* Confirm you're connected with the **same wallet** that created the lock. Locks are indexed by creator address.
* Confirm you're on Robinhood Chain mainnet, not testnet.
* Wait for confirmation, then hard-refresh. Indexing can lag a block or two.

#### The Withdraw button is greyed out

The unlock timestamp hasn't passed yet. The contract enforces this — the button is only reflecting on-chain state. Check the exact unlock date on the lock's proof page.

#### I set the wrong unlock date

There is nothing to be done. The unlock timestamp is immutable and there is no admin key. This is precisely the property that makes a lock meaningful as a trust signal, and it applies to you as much as to anyone else.

#### I burned the wrong amount

The tokens are at the dead address permanently. No recovery exists. If your token contract's supply is fixed, the burn is now part of its supply history.

#### Liquidity Locker / Vesting / Multi-Send show "Coming Soon"

They aren't live yet. For LP tokens, use Token Locker — LP tokens are ERC-20s. Follow [@ChestFiCash](https://x.com/ChestFiCash) for launch news.

#### RPC errors, timeouts, or stale balances

Public RPC endpoints are rate-limited. Switch your wallet to a dedicated endpoint from Alchemy, QuickNode, dRPC, or another supported provider.

#### Still stuck?

Reach out on [@ChestFiCash](https://x.com/ChestFiCash) with your transaction hash. A hash lets anyone diagnose the failure in seconds; a description of what you think happened rarely does.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.chestfi.cash/support/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.