Start with the network and address#

Open the contract details from the collection page and use its explorer link. Confirm the network and contract address before comparing balances, ownership or results. A token ID identifies an NFT only together with its contract and network.

Read CONTRACT_VERSION and ALGORITHM_VERSION before interpreting the numbers. V11 reports affiliate-v11 and unique-rank-v6 and uses the full equal affiliate pool. V10 reports affiliate-v10 and unique-rank-v6; V9 reports affiliate-v9 and unique-rank-v5. The version on the deployed contract is authoritative. Older collections intentionally expose different interfaces and rules. Source verification on an explorer lets you inspect the deployed code; it is not the same as an independent security audit.

Useful contract reads#

For V10, combination(tokenId) returns the permanent numbers before finalization with result = 0 to mean the score is pending. Zero is not a losing score: settled scores start at one. The score and scoreCombination reads reject an unfinished draw with RevealNotAvailable. Check revealed before presenting a result, even when the NFT already displays numbers.

V10 resolves numbers back to an existing minted NFT before checking its score. A valid four-number shape alone is not proof that a ticket exists in that collection. Identity reads reject nonexistent or refunded-and-burned tokens. A metadata image alone cannot establish a final score, winning status or unpaid prize.

Reading a contract does not require a wallet signature or a gas payment. Sending a mint, enrollment, claim or refund is a separate write transaction. Do not approve a transaction just to view your numbers.

The website and the chain#

The app uses an indexed database to make collections, history, holdings and balances easier to browse. Confirmed transactions made outside Tincta, including through explorers, can also be indexed. Confirmations, provider delays and chain reorganizations can make the displayed state lag behind a transaction.

Refreshing asks for a newer view; it does not generate a result, enroll an affiliate or withdraw funds. If a displayed value disagrees with the canonical contract state, the contract is authoritative.

Trust and availability#

The contract enforces reward rules and sends valid claims without a team approval step. This does not mean every operation happens by itself: sale activation, randomness funding, the draw request and finalization still require transactions. The website and supporting services help execute or display those steps; they cannot rewrite a deployed collection’s fixed reward terms.

On-chain checks constrain claims and protect the configured reserves, but participation still involves contract risk, wallet security, Ethereum network availability and the randomness provider. Affiliate admission also depends on configured verification services and a signer. Official collection and reward registries have governance-controlled registration.

An interface, local test suite or source-verified contract is not proof of a completed Mainnet rollout or an audit. Use the collection’s actual deployed addresses and published release evidence rather than assuming that every feature in these guides is enabled everywhere.