Repository navigation
fix(cli): verify tries Filebase, Pinata, ipfs.io, dweb.link by default (3.1.1) - #270
Merged
Merged
Conversation
With no --gateway, `nirium verify` only tried gateway.pinata.cloud. Pinata serves our pins but often takes 5-7s, and a live run on 7 Nov timed out at the 8s default, so a healthy CID failed to verify. The default is now the same chain the verify-audit-cid Action uses since #259 (Filebase dedicated gateway, ipfs.io, dweb.link), with Pinata second. Measured on 7 Nov against two real receipt CIDs: Filebase 200 in 0.6-1.5s, Pinata 200 in 5-7s, ipfs.io and dweb.link 429. Passing --gateway still replaces the list. Adds a test for the default order that never touches the network (1ms timeout), and bumps nirium-cli to 3.1.1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
M0nsxx
approved these changes
Nov 7, 2026
M0nsxx
left a comment
M0nsxx
left a comment
Collaborator
There was a problem hiding this comment.
Approving. The CLI never got the default chain #259 gave the Action, so nirium verify with no --gateway depended on Pinata alone and timed out on a healthy CID. Filebase first, then Pinata, ipfs.io and dweb.link matches the gateway numbers in the description. --gateway still replaces the list, the new test checks the order without touching the network, and the 3.1.1 bump plus CHANGELOG entry are scoped to this one fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
With no
--gateway,nirium verifyonly triedgateway.pinata.cloud. Pinata has our pins but often answers in 5-7s, and on 7 Nov a livenpx nirium-cli@3.1.0 verify Qmb41zz...timed out at the 8s default: a healthy CID reported as not reachable. That's the exact example on nirium.xyz/docs.#259 already fixed this for the
verify-audit-cidAction (#185). The CLI never got the same default.What
--gatewayis passed: Filebase dedicated gateway, Pinata,ipfs.io,dweb.link.--gatewaystill replaces it.nirium-cli3.1.0 -> 3.1.1.Measured 7 Nov, two real receipt CIDs
Qmb41zz...QmVWZM1...(TIA)Tests
verify-retry-gateway+verify-hash-only: 25/25 locally. Full CLI suite on my Windows machine: 101/107; the 6 failures are stdin/TTY and local config-store tests (config set,serve,anchor --signwith no key) that fail the same way onmainwithout this change. CI on Linux is the real check.🤖 Generated with Claude Code