The IPFS gateway for nft.storage is not "another gateway", but a set of caching layers for NFT’s that sits on top of existing IPFS public gateways.

Table of Contents

• Usage
• Packages
  • API
  • Client
  • Edge gateway
• Building
• Contributing
• License

Usage

Get your NFTs from the IPFS Network via their unique content identifier with a lightning fast experience. Like any other IPFS gateway, nftstorage.link supports IPFS path style resolutions https://nftstorage.link/ipfs/{cid} and subdomain style resolution https://{CID}.ipfs.nftstorage.link/{optional path to resource}

> curl https://nftstorage.link/ipfs/bafkreidyeivj7adnnac6ljvzj2e3rd5xdw3revw4da7mx2ckrstapoupoq
Hello nft.storage! 😎

> curl https://bafkreidyeivj7adnnac6ljvzj2e3rd5xdw3revw4da7mx2ckrstapoupoq.ipfs.nftstorage.link
Hello nft.storage! 😎

Packages

API

nftstorage.link provides an HTTP API that allows the optimization of our caching strategies to given content.

Check out the API documentation.

Client

A set of utilities for working with the NFT.Storage IPFS Edge Gateway and its API.

Check out the Client documentation.

Edge gateway

The core of nftstorage.link, the Edge Gateway is serverless code running across the globe to provide fast IPFS content retrieval.

Check out the Edge Gateway documentation.

Building

Want to help us improve nftstorage.link? Great! This project uses node v16 and pnpm. It's a monorepo that use workspaces to handle resolving dependencies between the local packages/* folders.

Copy the <.env.tpl> file to .env and install the deps with pnpm.

# install deps
pnpm install

Contributing

Feel free to join in. All welcome. Open an issue!

If you're opening a pull request, please see the guidelines in DEVELOPMENT.md on structuring your commit messages so that your PR will be compatible with our release process.

License

Dual-licensed under MIT + Apache 2.0