CLI v1.4.0: default Subsquid endpoint /blue/graphql returns 404 (collect-rewards fails)

[ogaworld369]

Summary

After updating to quantus-cli v1.4.0 (running against node v0.7.1-q-day-2), wormhole collect-rewards fails at the "Querying Subsquid for pending transfers" step with a 404. The ZK circuit generation works fine — only the Subsquid query fails.

Steps to reproduce

quantus wormhole collect-rewards --wallet mining --dry-run

Actual output

Step 2: Querying Subsquid for pending transfers...
❌ Error: Subsquid request failed with status 404 Not Found: {"error":"resource does not exist","path":"$","code":"not-found"}

(ZK circuit generation succeeds: num_leaf_proofs: 7, ready in ~3s. Only the Subsquid query fails.)

Endpoint diagnostics (curl)

Path	HTTP status
/blue/graphql	404 (default in v1.4.0 and v1.3.4)
/green/graphql	502
/graphql	404

The 502 on /green/ suggests the indexer is being migrated from blue to green, but green is not up yet. The CLI default --subsquid-url still points to /blue/.

Questions

1. What is the correct Subsquid GraphQL endpoint for the current runtime (spec_version 131)?
2. Is the indexer being redeployed? Please ping when the new endpoint is live.

Environment

OS: Ubuntu 24.04 / node: v0.7.1-q-day-2 / miner: v3.2.0 / CLI: v1.4.0

[dewabisma]

Hi, thanks for raising the issue. We already addressed the problem on this on PR #109 . We released new version v1.5.0 with the fix.

1. The new subsquid graphql use https://sub2.quantus.com/v1/graphql
2. We updated the indexed yes