Skip to navigation
Publish content with ipfs
08.10.26
after i publish a file it content is stored as blocks in kubo's repo (/var/lib/ipfs/.ipfs/blocks), kept alive by the recursive pin, and served from there over port 4001. + Thought: 7.1s - Stored: at ipfs add time — the folder is split into blocks, written to /var/lib/ipfs/.ipfs/blocks (that's before any publish). - Kept alive: by the recursive pin — unpinned blocks get swept by repo gc. - Served: over 4001 to other peers (bitswap protocol) when they ask for those CIDs. Your own gateway (8080, localhost) reads the same blocks directly. ipfs name publish adds nothing to the store — it only writes the "the name → this CID" record. So the correct chain: add (writes blocks) → pin (protects) → publish (points name). Content is on the network the moment those blocks are reachable on 4001 — the name is just a convenience layer on top
Reply
Anonymous
Information Epoch 1791551146
Don't do anything the computer can do for you.
Home
Notebook
Contact us