sithbit-gateway: the IPFS HTTP gateway

Standard port(s): bind 8183, health 8198.

A read-only IPFS path gateway (GET/HEAD /ipfs/{cid}) serving mail blobs straight out of the same block/pin bucket the node writes — deserialized file bytes by default, trustless raw-block and CARv1 responses via ?format=raw|car (or the matching Accept types), with the standard immutable-caching, conditional-request, and range semantics of the IPFS gateway specs.

It is deliberately local-content-only: a CID whose blocks are not in the bucket answers 404 — the gateway never fetches foreign content from the IPFS network. Point [blobs] at the shared S3 bucket (or share the local ipfs/ directory) and it serves exactly what the node/cluster pinned, nothing else.

When you need it: only when pinned mail blobs should be fetchable over plain HTTP — a recipient’s client verifying an on-chain CID without running IPFS, a load-balancer-friendly read path in front of the bucket, or public retrievability without opening the swarm port. Mail delivery itself never needs it; sithbitd and decentralized clients read blobs through IPFS directly.

Quickstart:

cargo run -p ipfs-gateway

Config file ipfs_gateway.toml, or point IPFS_GATEWAY_CONFIG at an alternate path.

See the Configuration reference for the full key/default table.