- What does it mean to mint an NFT on QRL 2.0?
- Minting writes a brand-new NFT to the QRL 2.0 chain — the first event that creates a tokenId and assigns its owner. On-chain it shows up as a QRC-721 or QRC-1155 Transfer sent from the zero address (Q000…000), which has no owner. Every QRL mint is signed with ML-DSA-87, a post-quantum signature scheme, so its record of authenticity stays verifiable.
- Are QRL NFT mints quantum-safe?
- Yes. Every transaction that mints a QRC-721 or QRC-1155 token on QRL 2.0 is signed with ML-DSA-87 — the lattice-based, post-quantum scheme the chain uses instead of ECDSA. An NFT's proof of authenticity and ownership is quantum-resistant from the moment it is minted, with no future migration needed as quantum computers mature.
- What's the difference between QRC-721 and QRC-1155?
- QRC-721 tokens are 1-of-1s: each tokenId is unique and indivisible, so a mint always creates exactly one item (Amount = 1). QRC-1155 is a multi-token standard built for editions — one contract can mint many copies of the same tokenId, so a single QRC-1155 mint can carry an Amount greater than one.
- What counts as a 'mint' on QRL 2.0?
- A QRC-721 or QRC-1155 Transfer event where the `from` address is the all-zero address (Q00…00). That's the on-chain signal a new tokenId is being created — there is no previous owner, so the protocol uses zero as the synthetic source. The detection is protocol-agnostic: it applies the same way to QRC-721 transfers, QRC-1155 TransferSingle events, and each (tokenId, amount) pair inside a QRC-1155 TransferBatch.
- How is the top-minting leaderboard ranked?
- By raw mint count over the last 7 days, served by our `/api/v1/qrl2/nft/top-mints?window=7d` endpoint. Each detected mint event counts as one tick toward that collection's score. Unique minters (distinct recipient addresses) is shown as a secondary signal — it's the best quick heuristic for spotting bot-farms (high mint_count + low unique_minters) versus genuine community drops.
- Why does the leaderboard rotate?
- It's a sliding 7-day window — every passing minute, mints older than 7 days drop out of the count, and newer mints enter. So a collection that minted heavily last week but is quiet now will gradually fall off the leaderboard as its mints age out. The leaderboard reflects who is hot recently, not who was ever popular. (We use a 7-day window rather than 24 hours because mints arrive in bursts — a 24-hour window is empty most of the time on the testnet.)
- How are QRC-1155 batch mints counted?
- QRC-1155 has a TransferBatch event that mints multiple tokenIds in a single transaction (efficient for game-item drops). Quantascan expands each (tokenId, amount) pair from the batch into its own row in our index, so one batch event with N tokenIds contributes N to the leaderboard's mint_count. A drop that mints 1,000 NFTs in one TransferBatch transaction will move the collection up by 1,000, not 1.
- What does 'unique minters' mean in the leaderboard?
- The count of distinct recipient addresses that received a mint from this collection within the leaderboard window. Useful for sanity-checking: a collection with mint_count = 5,000 but unique_minters = 2 is almost certainly bot-minted to two wallets; mint_count = 500 with unique_minters = 480 is a genuine community drop. Always read the two numbers together.
- Are batch mints split into individual rows in the live feed?
- Yes — same as on /nft-transfers. A QRC-1155 TransferBatch that mints 100 tokenIds appears as 100 rows in the feed, each one a separate mint of a specific (tokenId, amount) pair. They all share the same transaction hash and parent `log_index`, so you can tell they came from one batched operation.
- When does a mint count toward this page?
- The moment our ETL decodes the Transfer event with `from = Q000…000` from the block's receipt logs — typically within seconds of the block being sealed by the proposer. There's no delay for confirmations; if a reorg later evicts the block, the index reconciles automatically and the mint row disappears with it.