The art that needs no marketplace
Some Robinhood Chain collections keep their images inside the contract. Rendering those needs no IPFS, no API key and nobody’s permission.
MadCool Seed ·
Most NFT images are not on the blockchain. The token points at a document, the document points at a picture, and the picture sits on IPFS or on somebody’s web server. The chain holds a receipt; the art holds still only as long as the hosting bill is paid.
Some collections on Robinhood Chain do it differently. Ask the contract for a token’s tokenURI and it hands back the whole thing: a data: URI with the metadata base64-encoded inside it, and the image encoded inside that. No fetch. No gateway. No API key. The art is in the contract, and reading it needs nothing but the chain.
A collection whose art is fully on chain cannot be deplatformed, rate limited or quietly re-pointed. It can only be read.
Four schemes in one window
Fully on-chain art is not the norm here, though. A single 500-block window on this chain contained all four schemes at once: data:, ipfs://, https:// and web3://. Anything that assumes one scheme renders most of the chain blank.
The web3:// ones we name rather than render: resolving them needs an ERC-4804 resolver this site does not have, and saying so beats showing a broken image or pretending the token has no art.
The gateways that stopped answering
The IPFS ones are the fragile case, and not in the way people expect. On 17 September 2026, four of the best-known public IPFS gateways — ipfs.io, dweb.link, nftstorage.link and w3s.link — returned 403 to this site’s server. Two others were unreachable entirely. The collections had not moved and nothing was wrong with their pinning; the route to them had simply closed.
That is the difference the on-chain collections make concrete. One kind of art stopped rendering because a third party changed its mind about us. The other kind could not have.