Part of #111. Depends on 3/7, 4/7 (cas messages).
The deeper win: ION peers serve each other the content-addressed CAS blobs for anchored CIDs, self-verifying by CID hash — so the network is resilient to IPFS GC/unpinning (the live pendingRetryable problem). Wire the getcas/cas path into the CAS layer as an additional tier alongside IPFS (cache → ION peer → IPFS), and let a node serve blobs it holds in its cas-cache. Bounded/rate-limited. Could ship before or alongside the anchor fast-sync — it's independently valuable. Tests: a CID resolvable via an ION peer when IPFS returns not-found; CID-mismatch content is rejected.
Part of #111. Depends on 3/7, 4/7 (cas messages).
The deeper win: ION peers serve each other the content-addressed CAS blobs for anchored CIDs, self-verifying by CID hash — so the network is resilient to IPFS GC/unpinning (the live
pendingRetryableproblem). Wire thegetcas/caspath into the CAS layer as an additional tier alongside IPFS (cache → ION peer → IPFS), and let a node serve blobs it holds in its cas-cache. Bounded/rate-limited. Could ship before or alongside the anchor fast-sync — it's independently valuable. Tests: a CID resolvable via an ION peer when IPFS returns not-found; CID-mismatch content is rejected.