NFT marketplace visibility audit - OpenSea, Rarible, Zora, explorers

[magent-cryptograss]

Overview

Systematic audit of cryptograss NFT visibility across all major marketplaces and block explorers. Ensure collections are properly indexed, displayed, and discoverable.

NFT Contracts to Audit

Collection	Chain	Address	Minted
Set Stones	Arbitrum	`0x39269b3FddFc9bf0626e5CFe4424aa51A77f7678`	5
Blue Railroad	Optimism	`0xCe09A2d0d0BDE635722D8EF31901b430E651dB52`	3
Revealerfacts	Mainnet	`0xa812137EFf2B368d0B2880A39B609fB60c426850`	(contribution tracker, not ERC721)

Marketplaces to Check

OpenSea

• Set Stones collection visible?
• Blue Railroad collection visible?
• Collection metadata (name, description, banner)?
• Individual token images displaying?
• Traits/attributes showing in filters?
• Collection verified/claimed?

Rarible

• Collections indexed?
• Metadata displaying correctly?
• Search discoverable?

Zora

• Listed on Zora marketplace?
• (May not be relevant for Arbitrum/Optimism contracts)

Chain-Native Explorers

• Arbiscan: Set Stone contract verified?
• Arbiscan: NFT tab showing tokens?
• Optimistic Etherscan: Blue Railroad verified?
• Optimistic Etherscan: NFT display working?

Audit Checklist Per Collection

For each collection, check:

Contract Level

• Contract source verified on explorer?
• Read functions accessible?
• ContractURI returns valid JSON? (if implemented)
• BaseURI returns valid endpoint?

Token Level

• TokenURI returns valid JSON?
• Image URL in metadata resolves?
• Attributes properly formatted?
• Name and description present?

Marketplace Level

• Collection auto-indexed or needs manual import?
• Collection page exists with correct name?
• Banner/logo images set?
• Description accurate?
• Social links configured?
• Creator fees set correctly?

Known Issues (from previous investigation)

1. Set Stones: tokenURI returns 404 (see Set Stone metadata returns 404 - contract baseURI mismatches deployment #334)
2. Blue Railroad: tokenURI returns Discord URL (see Blue Railroad Train tokenURI points to Discord URLs instead of JSON metadata #335)
3. Both: Likely not visible on any marketplace due to metadata issues

Actions Needed

Immediate (after fixing metadata)

• Import collections to OpenSea if not auto-indexed
• Set up collection pages with proper branding
• Verify all token images display

Collection Setup

• Create collection banner images
• Write collection descriptions
• Set creator/royalty addresses
• Link social media accounts

Ongoing Monitoring

• Bookmark collection pages
• Check periodically for indexing issues
• Monitor for any delisting/flagging

Depends On

• Set Stone metadata returns 404 - contract baseURI mismatches deployment #334 (Set Stone metadata fix)
• Blue Railroad Train tokenURI points to Discord URLs instead of JSON metadata #335 (Blue Railroad metadata fix)

Acceptance Criteria

• All ERC721 contracts visible on OpenSea
• Token images displaying correctly
• Collection pages have proper branding
• Verified on block explorers
• Search discoverable on major platforms

Labels

nft, audit, lone-star-release