- Scrapes inscription IDs from a Nintondo wallet address OR uses existing inscription data
- Hashes local images to create unique fingerprints
- Hashes inscription content from the blockchain
- Matches images by comparing hashes to assign correct inscription IDs
- Generates reports including missing local images
- What: The Nintondo wallet address containing your inscriptions
- Why needed: To scrape all inscription IDs associated with your wallet
- Example:
PXwoJ2qqYUVLFN2gPj7ThhQL1PorpfTUeQ - Alternative: If you have existing inscription data, the script can use that instead
- What: Local directory containing your NFT images
- Why needed: To hash and match against blockchain content
- Requirements: Images must be named numerically (1.png, 2.png, etc.)
- Example:
/Users/NodeRunners/Desktop/Completed Projects/Pepinals/Devs/devs/completed
- What: Your existing NFT collection metadata file
- Why needed: Contains the NFT names/numbers that will be matched with inscription IDs
- Format: JSON array with entries containing
namefield (e.g., "DEV #1", "Pixel Pepes #123") - Example:
/Users/NodeRunners/Desktop/Completed Projects/Pepinals/devsNintondo.json
- What: Filename for the final matched results
- Why needed: Where to save the updated collection with assigned inscription IDs
- Result: Your original JSON with
idfields populated with correct inscription IDs - Example:
devsNintondo_updated.json
- Main output: Updated JSON with inscription IDs assigned
- Missing images report:
{output_name}_missing_images.txt- lists NFTs without local images - Hash reference:
inscription_hashes.md- technical reference of all hashes
- NFT collectors who need to match local images with blockchain data
- Metadata management for NFT collections
- Verification of image authenticity against blockchain records
- Bulk processing of large NFT collections
- Python 3.9+
- Chrome browser (for scraping)
- Internet connection (for API calls)
- Local image files named numerically