मुख्य कंटेंट तक स्किप करें

Troubleshooting

The failures you're most likely to hit, and how to fix them. Each one names the error code you'll see so you can match it to the message in front of you.

Publishing / on-chain​

"Insufficient DIG" / "not enough DIG"​

CLI exit 12 · DIGHUb DIG_INSUFFICIENT

Publishing a capsule costs the uniform capsule price in $DIG + a small XCH fee, and your wallet is short on one of them.

  • Check your balance: digstore balance (or the DIGHUb publish screen).
  • Fund the receive address it shows. You need both: XCH for the fee and enough $DIG for the capsule price. DIG arrives as a Chia CAT at the same xch1… address.
  • Need DIG? Swap XCH for it on TibetSwap ↗, dexie.space ↗, or 9mm.pro ↗, then send it to your receive address.

See Where to get DIG and Funding a wallet.

The confirmation timed out​

CLI exit 14 · DIGHUb REG_PENDING

init/commit block until Chia confirms the spend. On a slow block the wait can time out even though the transaction will still confirm. Nothing is lost.

digstore anchor status      # see whether the chain has confirmed it
digstore anchor             # poll and flip the project to confirmed once seen

A failure before the spend (missing seed, insufficient funds) leaves nothing on disk — just fix it and re-run. Do not pay again while a spend is pending.

"non-fast-forward: remote root has advanced"​

CLI exit 7

Someone (or another machine) published a newer capsule than your local copy, so your push isn't a fast-forward.

digstore pull               # bring your local store up to the current root
digstore push               # then push

CI deploy fails or double-spends​

  • The Action never mints — the store must already exist (digstore init once). If you see a mint attempt, you're pointing at a missing/empty store; check store-id in dig.toml.
  • Fund the dedicated deploy wallet with enough $DIG for your expected deploys (the uniform capsule price each). See Deploy from GitHub Actions.
  • Use --if-changed so a no-op build doesn't spend the capsule price on an identical capsule.

Reading / verification​

"verification failed"​

CLI exit 5

The served bytes didn't verify against the on-chain root, or couldn't be decrypted. Almost always one of:

  • Wrong or missing salt for a private store — a private URN needs its ?salt=<hex>. Pass --salt <hex> to digstore cat/checkout.
  • Wrong URN — the URN is the key; a typo yields the wrong decryption key.
  • Genuine tampering — the host returned bytes that don't match the signed root. DIG fails closed by design: nothing is written.

"resource not found"​

CLI exit 4 · RPC -32602

The store id, root, or path doesn't resolve to a committed resource.

digstore log                # list generations (each root hash is a capsule)
digstore keys               # list every committed resource's URN + retrieval key

Confirm the store has at least one confirmed capsule; "latest" on a brand-new store with no confirmed generation is invalid.

Wallet / session​

"Your wallet session can't sign"​

DIGHUb WALLET_SESSION

  • Disconnect and reconnect your wallet in DIGHUb.
  • Make sure Sage is up to date — older versions miss some signing methods.
  • A watch-only wallet can't sign; connect a wallet that holds the key.
  • Wrong network? Connect a Chia mainnet (xch1…) wallet.

"You declined the request"​

DIGHUb WALLET_DECLINED

Not an error — you cancelled the signature in your wallet. Nothing was signed or broadcast. Re-try and approve if you meant to publish.

CLI setup​

"no seed found"​

CLI exit 9

digstore seed generate      # create a wallet (mnemonic shown once — back it up)
# or
digstore seed import        # import an existing BIP-39 mnemonic

"wrong passphrase"​

CLI exit 10

Re-run and enter the correct passphrase. For CI/scripts, set DIGSTORE_PASSPHRASE in the environment. Lost the passphrase? You'll need to re-import from your mnemonic.

"command not found: digstore"​

Open a new terminal after installing (so PATH refreshes), then digstore --version. See Installing the CLI.

Still stuck?​

  • Look up the exact code in Error codes.
  • Ask in the community or file a report — see Get help.