Troubleshooting

Symptoms, in rough order of how often they come up.

"Gas price must be set in the client options when auto gas is used"

Every transaction fails at signing time, before it reaches the chain.

The deployment is not configured with a gas price. This is a build configuration problem, not something you can fix from your side — report it to whoever runs the deployment.

The page has no Connect button, or no wallet at all

Check the page title and the URL first.

If the tab says PREVIEW, you are on /preview.html — the fixtures page. It renders the same screens against hard-coded numbers, with signing disabled, so layout can be reviewed without a chain or a wallet. It has no wallet connection by design.

It is easy to land on by accident and hard to notice: once you visit it, browsers autocomplete it over the real URL whenever you type the host. Click Open the real app → in its banner, or go to the site root. In Chrome you can highlight the offending address-bar suggestion and press Shift+Delete to evict it.

On the real app, Connect is in the header on every view.

My changes to the app are not showing up

Check build <sha> in the small print at the foot of the page against the commit you expect.

If it does not match, you are looking at a stale page or a different server. In local development the usual cause is two dev servers: the port is taken, so a second one starts somewhere else and you have two servers on different ports serving different code. See the local devnet setup in the repository's README.

My wallet is not detected

See connecting an account. Reloading fixes it most of the time — extensions inject into the page as it loads and can lose the race. If the extension is genuinely absent, the app says so rather than doing nothing.

My balance is zero but I know I have ATOM

Your wallet is probably on a different account: wallets expose whichever account is currently selected, so switch it in the extension and the app follows.

Also confirm you are on the network you think you are. The header badge names it, and the foot of the page gives the RPC host.

"Cannot read the contract"

The app cannot reach the contract. Either the RPC endpoint is down or the contract address is wrong or unset — both are shown in the error.

You can still connect an account in this state, by design. Staking and redeeming stay hidden, because they need the current exchange rate to quote you anything honestly.

The Claim button is disabled

Deliberate — a claim would fail right now. Check the withdrawal's state:

• Payout: not yet known → your batch has not been finalized. This is the most common case. Anyone can finalize it, including you — see keeping it running
• Claimable at is in the future → still unbonding, nothing to do but wait
• Claimable at: not yet known → your batch has not been processed yet, so the clock has not started

My batch matured days ago and nothing happened

Finalization does not happen on its own. It is a permissionless call that somebody has to make. See keeping it running.

My payout is less than what I redeemed for

A validator was slashed while your ATOM was unbonding. The batch shows a haircut below 100% and the shortfall is shared proportionally across everyone in it. See the lifecycle.

"deposit would take the pool to X, above the Y cap"

The deposit cap is full. Stake a smaller amount, or wait — redemptions free up room. The dashboard shows current headroom.

"contract is paused"

An admin has frozen staking, redeeming and claiming. Only they can unfreeze it. Existing positions are unaffected.

"stake amount is too small to mint any vATOM at the current exchange rate"

Your deposit rounds to zero vATOM. Stake more.

"a reward vesting window is still active"

You tried to compound rewards while the previous batch is still vesting in. Expected, not an error condition — wait for the window to elapse. Rewards accumulate in the vault meanwhile and are not lost. See the exchange rate.

Transaction fails with an unclear error

Full list with explanations: errors.

Still stuck

Note the build sha and the RPC host from the foot of the page, and the exact error text. Those three identify almost any deployment-side problem immediately.