Skip to main content

Troubleshooting

Frontend Issues

”Failed to fetch” during CoFHE encryption

Symptoms: Browser console shows Failed to fetch or NetworkError during encryption. Causes:
  • Stale IndexedDB cache in @cofhe/sdk
  • ZK proof verifier endpoint unavailable
  • Rate limiting
Fix:

Browser freezes during encryption

Symptoms: Browser becomes unresponsive for 10-30 seconds after submitting. Cause: CoFHE ZK proof generation runs on main thread (useWorkers: false). Fix: Show a warning to the user:

MetaMask doesn’t open for storeKey

Symptoms: Transaction doesn’t prompt in MetaMask. Cause: storeKey is called before user interaction, or wallet not connected. Fix:

ICL Issues

”not enough active nodes available for the requested quorum”

Symptoms: GET /v1/inference/quorum-preview returns 400 with this message. Cause: Fewer than 3 nodes (1 leader + 2 verifiers) are active in the pool. Fix:

ICL MongoDB connection fails

Symptoms: ICL falls back to in-memory persistence. Cause: MongoDB Atlas URI incorrect, network issues, or IP not allowlisted. Fix:

Node Issues

”Missing CoFHE key handles — cannot decrypt prompt”

Symptoms: Job aborts after claiming. Cause: claim_task returned empty handles or claim failed. Fix:

“Too Many Requests” from Alchemy

Symptoms: CoFHE operations fail with rate limit errors. Cause: Alchemy free tier limits requests. Fix:

Contract Issues

”storeKey transaction reverted”

Symptoms: MetaMask shows transaction failed. Causes:
  • Insufficient gas
  • Wrong PromptKeyStore address
  • Invalid ciphertext handles
Fix:

“ResultRegistry not found”

Symptoms: ICL cannot commit results on-chain. Cause: Wrong ResultRegistry address or contract not deployed. Fix:

Network Issues

Cannot connect to Arbitrum Sepolia

Symptoms: Transactions fail, RPC errors. Fix:

IPFS download timeout

Symptoms: Nodes cannot download prompt/output blobs. Fix:

Getting Help

If none of the above fixes work:
  1. Collect logs:
    • Frontend: Browser console logs (F12 → Console)
    • ICL: tail -n 1000 icl.log
    • Node: tail -n 1000 ~/.blindference/node.log
  2. Open an issue:
  3. Join Discord: Blindference Community