Deep dive

Where data comes from

The public sources behind ownership, metadata, previews, and artwork.

What each source provides

A token is assembled from several public systems. This table shows where the client reads ownership, metadata, project records, previews, and artwork bytes.

FactRead from
Ownership (Tezos)TzKT token balances on the gentk contracts
Ownership (Ethereum / Base)Blockscout holdings matched against the fxhash collections Whitehash knows about (with a direct blockchain fallback)
Token metadataTezos token_metadata / EVM tokenURI, then the JSON file through your IPFS gateways
ProjectsTezos issuer ledger big maps / EVM ProjectCreated factory events
Artwork bytesIPFS gateways, or onchfs read directly from chain

Tezos contracts

These are the fxhash contracts supported by the chain reader. You can check any of them on tzkt.io.

ContractMainnetGhostnet
gentk v1KT1KEa8z6vWXDJrVqtMrAeDVzsvxat3kHaCEKT1ExHjELnDuat9io3HkDcrBhHmek7h8EVXG
gentk v2KT1U6EHmNxJTkvaWJ4ThczG4FSDaHC21ssviKT1NkZho1yRkDdQnN4Mz93sDYyY2pPrEHTNs
gentk v3KT1EfsNuqwLAWDd3o4pvfUx1CAh5GMdTrRvrKT1TtVAyjh4Ahdm8sLZwFnL7tqoLf59XrK2h
issuer v0KT1AEVuykWeuuFX7QkEAMNtffzwhe1Z98hJSKT1PyfrDD85RxUWz8dMHoC92MxdPzecSQ5t9
issuer v1KT1XCoGnfupWk7Sp8536EfrxcP73LmT68NyrKT1QwWVZogqPZZtGSVxGpLkEWar7LFvAsMdd
issuer v2KT1BJC12dG17CVvPKJ1VYaNnaT5mzfnUTwXvKT1Sy7X6TubmZ39G8CHVrUcxjc3jiF68P8oB
issuer v3KT1Xpmp15KfqoePNW9HczFmqaGNHwadV2a3bKT1DfymMp3qD5Pd5ujPjp7UsQbppY9yY1Hbf

EVM issuer factories

Each network has one FxIssuerFactory, which records when new projects are created. The chain reader scans those records from the start of the factory’s history. Verify any address on the relevant explorer.

NetworkFxIssuerFactoryDeploy block
Ethereum (eip155:1)0x442295de8A31d65026dBc09c29d469F6854f188a18762350
Base (eip155:8453)0xf05636d65c7a10dF989eC2411D4F3230d3A02f3D10786140
Sepolia (eip155:11155111)0x4e9ef916F55B5d4a27E6406C7Ce8bcd29c2693d65013011
Base Sepolia (eip155:84532)0x60cFDE3aaf6E938535767794088cf15EaaC500198763620