Uploading a site to IPFS is the easy part. Here is the full picture: CID, gateway access, a real domain, and the pinning step most tutorials skip.

IPFS node types aren't a full-vs-light weight class the way some blockchains work. They are specific jobs a node opts into. Here is what each one does.

IPFS content is public by default: anyone with the CID can read it. See exactly what IPFS does and does not protect, and how to actually keep content private.

IPFS and Filecoin are separate protocols that work together: IPFS addresses and moves content by CID, while Filecoin pays storage providers to keep holding it.

IPFS retrieval speed is not one number: transport handshakes and routing lookups stack up. Here is which steps are slow on IPFS and what fixes each of them.

Running a full DHT client is too heavy for a browser. Delegated routing lets a light client get the same answers over plain HTTP instead. Here is how.

A minted NFT can still show a broken image months later. Here is exactly what that failure looks like, why it happens, and why it's hard to undo.

The AIOZ Pin wallet is a deposit address made with your account. Send AIOZ tokens and each deposit turns into credit at the AIOZ/USDT rate at the time it lands.

Content moderation on IPFS stops at each operator's copy. A pinning service can unpin and a gateway can block a CID, but neither removes it from the network.

libp2p connections can run over more than one transport. Here is exactly what changes with QUIC instead of TCP, and why IPFS dials both at once.

GossipSub is the libp2p publish-subscribe protocol IPFS uses to push messages to every topic subscriber, through a peer mesh backed by IHAVE and IWANT gossip.

Helia is the TypeScript implementation of IPFS that replaced the deprecated js-ipfs. See how its modules, light mode, and verified-fetch work with AIOZ Pin.