Skip to content

fix: add proton.mypinata.cloud and agent.mypinata.cloud to Next.js image domains - #224

Merged
DoDoIndex merged 1 commit into
XPRNetwork:developfrom
charliebot87:fix/add-pinata-gateway-domains
Mar 30, 2026
Merged

fix: add proton.mypinata.cloud and agent.mypinata.cloud to Next.js image domains#224
DoDoIndex merged 1 commit into
XPRNetwork:developfrom
charliebot87:fix/add-pinata-gateway-domains

Conversation

@charliebot87

Copy link
Copy Markdown
Contributor

Problem

NFTs minted using Pinata's proton.mypinata.cloud and agent.mypinata.cloud gateways are not displaying on nft.xprnetwork.org or in the WebAuth wallet. The IPFS content is accessible but Next.js blocks the images because these domains are not whitelisted.

The IPFS_RESOLVER_IMAGE constant in utils/constants.ts already points to proton.mypinata.cloud but this domain is missing from the Next.js image domains config — causing a mismatch.

Fix

Add the three Pinata gateway subdomains used by the XPR Network ecosystem:

  • proton.mypinata.cloud — used by IPFS_RESOLVER_IMAGE in constants.ts
  • agent.mypinata.cloud — used by nft.charliebot.dev and other tools
  • simplelaunch.mypinata.cloud — used by SimpleDEX token images

Testing

Verified that IPFS hashes are accessible via these gateways (HTTP 200). After this fix, NFT images from chainportra2 and other collections using these gateways will display correctly.

…age domains

NFTs minted via nft.charliebot.dev and other tools using Pinata's proton/agent
gateways were not displaying on nft.xprnetwork.org or WebAuth wallet because
these domains were not whitelisted in Next.js image config.

Also adds simplelaunch.mypinata.cloud used by SimpleDEX token images.
@DoDoIndex
DoDoIndex merged commit 0fbb384 into XPRNetwork:develop Mar 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants