Dateverse contract address on Base

Base mainnet contract

Variant: Dateverse Genesis calendar-date registry on Base
Interface: ERC-721

Inspect on BaseScan · Official identity source · Project website

This is a collection contract, not your receiving wallet or a payment destination. A token ID identifies an item within its ledger.

Which Dateverse version is this?

Dateverse runs on Base mainnet. Its date-based token IDs are separate from wallet addresses.

The protocol defines a Genesis range from 1950-01-01 through 2049-12-31 and encodes calendar dates as YYYYMMDD token IDs. Its worked example maps 1969-07-20 to 19690720; this explains the mapping without asserting current ownership or availability.

Check a specific item

1. Open the official protocol specification and compare the Base Mainnet contract address.
2. Open the linked Dateverse marketplace collection or the BaseScan contract page on Base, not an Ethereum mainnet explorer.
3. Read the item’s calendar-date token ID and distinguish it from the chronological index or owner’s wallet.

The complete lookup is Base mainnet + 0x31d4444D8C16D0E1CD8AE75E4B5B77A1b5a6d718 + token ID. The protocol maps 1969-07-20 to token ID 19690720. This encodes the date, not its chronological index in the registry.

Identity evidence and limits

• Official mapping — The protocol specification names this Base Mainnet ERC-721 contract. — reviewed 2026-10-23
• Marketplace corroboration — The officially linked Dateverse collection’s item uses the same contract on Base. — reviewed 2026-10-23

Identity reviewed 2026-10-23. Explorer source-code verification is not proof of project identity or safety. This reference does not endorse a purchase or verify a seller.

Related references

• NFT contract addresses
• NFT contract, wallet address and token ID
• How to verify an NFT collection contract identity
• Original, wrapped and bridged NFT contracts