Metadata & IPFS

Before your collection can go live you provide a base URI: a URL prefix where each token's metadata JSON lives.

<baseURI>/1  →  metadata for token #1
<baseURI>/2  →  metadata for token #2

{
  "name": "Deng #1",
  "description": "One of 5,000 Dengs.",
  "image": "ipfs://bafy.../1.png",
  "attributes": [
    { "trait_type": "Background", "value": "Ape Blue" },
    { "trait_type": "Hat", "value": "Launch Helmet" }
  ]
}

Rules DengPad validates automatically when you paste your base URI into the wizard:

• The URI resolves (we check several sampled token ids).
• Each file is valid JSON with name and image.
• The image URL is reachable (IPFS gateways are used for ipfs://).

1. IPFS via a pinning service (recommended): Pinata, web3.storage, or NFT.Storage. Upload your images folder first, put the resulting ipfs://CID/… URLs into your JSON files, upload the JSON folder, and use ipfs://<jsonCID> as your base URI.
2. Arweave: permanent one-time-fee storage (Irys tooling).
3. Your own HTTPS server: allowed, but minters can see that you hold the keys to the files. They notice these things.

If you choose delayed reveal in the wizard, DengPad serves your pre-reveal image until you trigger reveal(baseURI) from your dashboard (allowed after mint end + your chosen delay). Optionally commit a provenance hash(a hash of all final metadata) before mint. It's frozen on-chain at mint open, so collectors can verify you didn't reshuffle.

"Failed to fetch metadata" in the wizard. Usually one of three things: the base URI has a trailing slash it shouldn't (we append /<tokenId> directly), the JSON files aren't named as bare token ids (1, not 1.json, unless your URI includes the extension pattern), or the pin hasn't propagated yet — freshly pinned CIDs can take a few minutes to be reachable through public gateways.

Images load slowly or not at all. Public IPFS gateways rate-limit. If your images are large, a dedicated gateway from your pinning service keeps the mint page snappy.

Validation passes but images look wrong. Check the image field points at the file, not the folder, and that token #1's JSON describes token #1's art. Off-by-one errors here are a classic.

• Image files uploaded and pinned (check a few in a browser)
• Metadata JSONs uploaded; base URI + token id resolves
• Token ids start at 1 (DengPad collections start at token #1)
• Royalty percentage and treasury address decided
• Pre-reveal image uploaded if using delayed reveal