IPFS Checker

Purpose: verify IPFS content availability and integrity via a gateway using a CID. Audience: developers, DevOps, auditors deploying IPFS assets. How it helps: reduces deployment risk by validating reachability, size, and CID alignment before pinning. Core logic: multi-field inputs, gateway flexibility, and optional size checks. It computes response latency, validates status, and reports whether the retrieved size matches expectations. Outputs include status, actual size, and gateway details. Algorithms: fetch /ipfs/{cid} through a gateway, measure latency, read Content-Length, compare to optional expected size, and perform a hash- or CID-based integrity check when feasible. Error handling covers missing data, timeouts, and gateway failures, returning diagnostic context for remediation. Core features: support for multiple gateways, CID validation, optional size validation, and a pass/fail/unknown result model. Use cases: pre-pin verification, content migration checks, multi-gateway reliability assessment. Exclusions: full DAG traversal, client-side rendering, or UI logic; no guaranteed cross-gateway consensus without explicit configuration.