Bitcoin-anchored permanence for IPFS - seeking technical review

I’ve been working on an architecture that addresses IPFS’s permanence and retrieval incentive challenges by integrating with Bitcoin’s infrastructure.

The problem: IPFS provides content-addressed storage, but lacks built-in economic incentives for permanent retention and retrieval. Current solutions rely on centralized pinning services or separate blockchain storage markets.

The approach:

  • Anchor IPFS content hashes to Bitcoin’s timechain via OP_RETURN (minimal blockchain footprint, verifiable timestamps)

  • Transform IPFS’s BitSwap (chunk-for-chunk exchange) into “SatSwap” (chunk-for-sats exchange) using Lightning Network micropayments

  • Create retrieval incentives without requiring a separate blockchain or storage contracts

  • Data stays in IPFS, Bitcoin provides verification and economic coordination layer

This complements existing IPFS infrastructure - it’s not replacing any current approaches, just offering an alternative economic model using Bitcoin/Lightning’s existing payment channels.

Current state: I have a detailed specification document, but it was developed with AI assistance because I lack the technical depth to verify if the architecture is fundamentally sound or has fatal flaws.

What I’m looking for: Technical review from people who understand IPFS protocols and distributed storage incentive systems. Not asking for implementation - just feedback on whether this architecture makes sense or what the obvious problems are.

The goal: build public infrastructure that anyone can use, leverage existing Bitcoin/IPFS protocols, create sustainable permanence incentives without centralized services.

If this seems worth reviewing, I’m happy to share the specification document. If the architecture is broken, I need to know that before promoting it further.

Appreciate any feedback the community can offer.