Transparency
On-chain collection data, not black-box counters
A launchpad can show any number it likes. Elevate shows the contract's numbers. This page lists what is read from the chain, how, and how you check it yourself.
What is read from the contract
| Supply | The contract's maximum supply. |
|---|---|
| Minted count | The contract's total minted, and per-phase counts. |
| Remaining | Supply minus minted, computed from the two values above. |
| Phase status | Each phase's start, end, cap, price and pause flag, evaluated against the current time. |
| Wallet limits | Per-phase and global per-wallet counters for the connected wallet. |
| Transfer lock | The contract's transfersLocked flag. |
| Royalties | ERC-2981 receiver and rate. |
| Contract address | The deployed address on chain ID 964, shown on every collection page with an explorer link. |
How it flows
- Collection contract on Bittensor EVM
- Backend reads it over JSON-RPC and caches briefly
- Collection page renders the values server-side
- Page refreshes from the chain before every mint
- You confirm the same values on the explorer
Check it yourself
Open any collection page and copy the contract address. Paste it into Taostats EVM Explorer . The token count there is the number the page calls “minted”. The recent transactions are the mints the page's activity feed shows.
Step-by-step: how to verify an NFT contract. Technical detail: on-chain status and real-time data.
What this means for marketing copy
Elevate does not invent scarcity. Phrases like “only 3 left” or “last chance” appear only when the contract's remaining supply says so. Status is always textual — Minting now, Upcoming, Ended — not a coloured dot, and mint times are stated in UTC.
Frequently asked questions
- What does “on-chain data” mean here?
- That the value shown was read from the collection's smart contract over JSON-RPC, not typed into a database. Anyone with the contract address can read the same value from the explorer.
- Why should collectors care?
- Because a counter in a database can say whatever its operator wants. A counter in the contract says how many tokens actually exist. On Elevate the page shows the second kind.
- Does Elevate cache anything?
- Briefly, to avoid hammering the RPC. The cache is refreshed on a short interval and immediately before any mint, and the chain always wins on disagreement.
- Can the collection page and the explorer disagree?
- Only for the seconds between a new mint and the next refresh. If they disagree for longer, something is wrong — ask on the official Discord.
See it on a live collection
Every collection page carries its contract address and reads its numbers from it.