Getting started
Troubleshooting
The failures that actually happen, what each one means, and the fix.
Most problems in this console are an RPC problem wearing a different name. Start there, then work down this page.
Nothing reads, or numbers look stale
| Symptom | Cause | Fix |
|---|---|---|
| Balances do not change after a transfer you can see on the explorer | The endpoint serves stale state | Wait a moment, or switch endpoint |
| Balances flicker between two values | Requests are load balanced across nodes at different heights | Use a single-node endpoint |
429, or reads failing in bursts | Rate limiting | Fewer wallets per run, or a paid endpoint |
| A launch cannot price itself | An eth_call failed or timed out | Same as above |
See Setting an RPC.
A bundle does not land
Nothing has been spent. An unlanded bundle is a transaction that was never included, not one that failed.
| Message | Meaning | Fix |
|---|---|---|
nonce too low: address ..., tx: 0 state: 1 | Two transactions from one address in the bundle | Usually the creator is also in the buyer book. The console drops it now and says so |
| Accepted by both builders, never included, six rounds | Your RPC's head is behind the chain | A faster endpoint |
Bundle has N txs but the max is 5 | No BlockRazor token on the deployment | Fewer wallets, or ask the operator to configure one |
| Insufficient funds at the escalated bid | The creator cannot cover its buy plus the full gas limit | Top the creator up |
A buy or sell reverts
| Message | Meaning |
|---|---|
could not be quoted | The venue could not price it. Usually the wrong venue for this token's phase |
| Reverts at exactly the same size every time | The token caps trade size. The console splits sales, but a launch buy cannot be split |
| Sells nothing, quotes zero | The token is on a curve and the trade was routed to a pool, or the reverse |
max fee per gas less than block base fee | The gas price went stale. Retry; long runs re-price themselves as they go |
nonce has already been used, or nonce too low on a funding wallet | The node's pending count was behind a transaction it had itself accepted. The send is retried once on a freshly read nonce |
internal server error from the RPC | The endpoint hiccuped. The transfer may still have landed, so it is retried on the same footing rather than blindly resent |
could not coalesce error | An RPC error ethers could not classify. The log now prints the node's own message in brackets after it |
A wallet cannot sell
The Tokens page says why per wallet:
- no key kept for this wallet. The position was created with key keeping turned off. Nothing can sell it from here.
- holds none of this token. Already sold, or the buy never landed.
- not enough coin to pay for the sale. Use the gas top-up option in the sell form. On PONS this is normal: the bundler buys out of the creator's balance, so buyer wallets hold no coin at all.
- not enough coin for N sales. The token caps trade size and this wallet needs several transactions, each with its own gas.
A volume bot stops early or reports oddly
| What you see | What it means |
|---|---|
base wallet holds X, not enough for another wallet | Working as intended. The base wallet keeps a reserve so a round's gas is always affordable |
| Only two wallets ever seem to trade | Trading at a time is 2. See Volume Bots |
| Wallets listed as failed, not stranded | Their funding never landed. Nothing to recover |
| Wallets listed as stranded | The chain says they still hold something. Use Recover funds |
| The venue shown is not the one you picked | You left it on Read from the token. The panel shows what the run resolved |
This token is still on the ... curve | The pinned venue disagrees with the token's phase. Pick the one the message names |
A fee was not charged
Every outcome is logged. The line says which:
admin accounts are exempt. Run it from a user account to see the fee path.this deployment has no fee recipient configured.the fee works out to zero.- No fee line at all: the action did not complete, so nothing was due.
See Fees.
Something is missing rather than broken
Settings lists what the deployment has configured. A missing Forgot password link means no outgoing mail; a Seed Sweeper that finds coin but no tokens means no indexer; a OneMeme launch that will not attach metadata means no IPFS pinning.
After a deployment update
The service restarts, which ends every running volume bot. Their keys are in the vault and the Unrecovered runs list replays the sweep. Positions, wallets and accounts are untouched.