NFT Rarity Scoring Tool – Turnkey Development

You launched a collection, tokens were sold out, but holders doubt the fairness of the rarity ranking. The reason is an inappropriate rarity calculation algorithm. We've helped dozens of projects avoid this issue by building tools that account for each collection's specifics. Our approach combines multiple methodologies with flexible weight tuning and aggressive caching. Our team has 5+ years of experience in Web3 and has delivered over 15 NFT analysis tools—a guarantee of quality. Starting from $5,000, our tool saves up to $20,000 compared to in-house development.

Why a Single Algorithm Doesn't Fit All Collections

Trait Rarity Score is the basic method: sum of inverse probabilities of traits. It's simple but overestimates tokens with many attributes. Statistical Rarity (product of probabilities) is fairer but suppresses singular unique traits. Information Content (−log2(p)) yields a balanced distribution but requires normalization.

We use a combination of Trait Normalization (OpenRarity) and Information Content—this reduces score spread by 2.5× compared to the basic method. In one project with a 10,000-token generative avatar collection, our combined algorithm reduced score variance by 40% relative to Trait Rarity Score, and the entire metadata indexing completed in under 30 seconds. For each collection, we select the optimal algorithm based on its statistics.

OpenRarity (official documentation) recommends combining normalization and information content methods for the most balanced ranking.

How We Collect and Index Metadata

NFT metadata is stored on IPFS or a centralized server via tokenURI. We read contractURI and tokenURI(0..n) through Multicall3—up to 500 RPC calls in a single batch. For IPFS, we use Cloudflare gateways and resolve CIDs. We handle edge cases: null traits (converted to "None" attribute), numeric values (binning), and updates after reveal.

We build the index in PostgreSQL: table token_traits(collection_id, token_id, trait_type, trait_value) plus aggregates per trait. After metadata updates, we recalculate incrementally.

How We Assess Rarity in 5 Steps

1. Analyze collection structure—determine trait types, distributions, identify anomalies.
2. Select algorithm—choose a combination of Trait Normalization and Information Content (or another if needed).
3. Fetch metadata—via Multicall3 batches of 500 tokens, IPFS gateways.
4. Compute scores—apply selected algorithms, calculate rank and percentile for each token.
5. Deploy API and frontend—integrate with marketplace, publish documentation.

How Long Does Development Take?

A typical project takes 2 to 4 weeks. The timeline depends on collection size, number of supported blockchains, and required integrations. The first calculation for a 10k-token collection takes seconds; subsequent ones are milliseconds.

Comparison of Rarity Algorithms

Common Mistakes in Self-Implementation

• Using only one algorithm—leads to biased ranking.
• Ignoring null traits—distorts statistics, tokens without attributes get incorrect rank.
• No caching—each IPFS or RPC request takes up to 500 ms; without cache, a 10k collection takes minutes.
• Not accounting for reveal—if metadata updates after sale, the index must be recalculated incrementally.
• Self-implementation can waste up to 50% of budget on fixes. Our tool cuts development costs by 3× using ready-made modules.

What's Included in the Work

• API with endpoints /rarity/{contract}/{tokenId} and algorithm selection.
• Web interface with rarity table and token percentile.
• Integration with your marketplace via OpenRarity npm package or custom solution.
• Documentation and source code access.
• Team training on the tool.
• Deployment on your infrastructure or cloud.
• One month of post-launch support.

Example Display

We guarantee the tool will pass smart contract audits and work with any standard (ERC-721, ERC-1155). We'll assess your project within 1 day—contact us to discuss details. Get a consultation to learn how our tool saves time and budget for your project.

Why does NFT marketplace development require a comprehensive approach?

We see that at first glance, an NFT contract looks simple: ERC-721, mint(), IPFS for metadata — that's it. In practice, it's this 'simplicity' that hides most problems — from bots buying out the entire mint in the first block to broken royalties on the secondary market. We often hear: Make a collection like others in a week — and a month later it turns out gas has tripled due to an unoptimized for loop, or OpenSea cannot see metadata after reveal. We know each of these pitfalls and build processes to avoid them.

Over 5 years of working with blockchains, we have implemented 40+ NFT projects, including marketplaces with dynamic attributes and cross-chain bridges. We have accumulated a library of proven templates — some of which we break down below.

Which standard to choose: ERC-721 or ERC-1155?

ERC-721 — each token is unique, one owner. Suitable for collections where each NFT has individual attributes and a direct owner → tokenId mapping.
ERC-1155 — multi-token standard: one contract holds both fungible and non-fungible tokens. It uses balanceOf(address, tokenId) instead of ownerOf(tokenId). A single transaction can transfer multiple different tokens via safeBatchTransferFrom. This saves gas on bulk operations — important for game items, tickets, edition collections. ERC-1155 is 2–3× more gas-efficient than ERC-721 for batch transfers.

Specific case: a game project with 50 types of items, each with a supply of 10,000. ERC-721 — 500,000 unique tokens, huge overhead on mappings. ERC-1155 — 50 tokenIds, balanceOf per player. Gas per transfer is 2–3 times lower, contract deployment is cheaper. For such tasks, we use OpenZeppelin ERC-1155 with custom modifications.

Metadata: on-chain vs IPFS vs centralized

The standard route is tokenURI() returning a link to a JSON with fields name, description, image, attributes. Three storage options:

• Centralized server — cheapest and most flexible. Risk: server goes down, company closes — NFT loses metadata. Not suitable for collections claiming long-term value.
• IPFS + Pinning — content-addressed storage, the link is bound to the content hash. Pinata or NFT.Storage provide pinning. Important: IPFS does not guarantee availability by itself — an active pinning service is needed. If it shuts down, data may disappear if no one keeps a copy.
• On-chain metadata — base64-encoded SVG or JSON directly in tokenURI. Maximum reliability, but expensive: for a collection of 10,000 tokens, gas costs may exceed $5,000. Suitable for generative art projects where visuals are generated from on-chain attributes (Nouns, Loot).

For most collections, we choose IPFS with Pinata for images + on-chain attributes for traits — a good balance. We validate files against a JSON Schema before upload; a typical mistake is unescaped quotes, causing marketplaces to display a blank screen.

{
  "name": "Token #1",
  "description": "A unique NFT",
  "image": "ipfs://QmHash/image.png",
  "attributes": [{"trait_type": "Background", "value": "Red"}]
}

Dynamic NFT: metadata that changes

Dynamic NFT updates metadata in response to external events — match results, character levels, real-world data via Chainlink. Architecturally, it's a combination: the smart contract stores state → tokenURI() generates metadata from the state on-chain. Caching problem: OpenSea and other marketplaces aggressively cache. The standard invalidation mechanism is a MetadataUpdate(tokenId) event from ERC-4906. OpenSea listens to this event and clears the cache. Without it, updated metadata may not appear for weeks.

Chainlink Automation (formerly Keepers) for automatically updating state on the contract on a schedule or condition — a standard solution for dynamics.

How to protect mint from bots?

Allowlist via Merkle tree — standard. The list of addresses is hashed into a Merkle root, stored in the contract. During mint, the user provides a Merkle proof — the contract verifies without storing the full list. We use OpenZeppelin MerkleProof library.

Reveal mechanism — on mint, a placeholder is issued; real traits are revealed after the sale ends. Otherwise, bots can scan pending transactions and snipe rare traits via frontrunning. But reveal requires a commitment scheme — the random seed must be fixed before mint or use Chainlink VRF.

Chainlink VRF for fair randomization of traits. VRF request at mint → callback with verifiable random number → assign traits. This adds ~2 transactions and latency but guarantees fairness. Chainlink VRF v2.5.

Rate limiting — require(mintedPerWallet[msg.sender] < maxPerWallet). Does not protect against multi-wallets but raises attack cost. For premium projects, we often add proof-of-work directly in the contract (via EIP-2612 signatures).

Royalties: the real market state

ERC-2981 — on-chain royalty standard. The contract returns (recipient, amount) for any sale price via royaltyInfo(tokenId, salePrice). Marketplaces query this on each sale. Problem: adherence to royalties is voluntary for marketplaces. Blur launched with zero royalties, triggering a wave of other platforms. The situation has partially stabilized: OpenSea supports ERC-2981, Blur added optional ones. Royalty payments can represent 5–10% of secondary sale volume, so getting them right matters.

Attempts to enforce royalties on-chain by restricting transfers only to approved marketplaces (operator filtering) were proposed by OpenSea via OperatorFilterRegistry. This breaks composability — you cannot transfer an NFT through a custom contract. Most serious projects have abandoned this approach. For projects where royalties are critical, we build a custom marketplace within the ecosystem plus an incentive structure for users to trade there.

Lazy minting and gas-free mint

Gas-free mint via signature: the creator signs a voucher (tokenId, tokenURI, price, signature), the buyer provides the voucher in mint() — the contract verifies the signature via ECDSA.recover() and mints. Works on OpenSea via their Seaport protocol. Seaport is an optimized contract with minimal gas usage. Understanding its mechanics is important when integrating custom marketplace logic.

Stack for NFT projects

• Contracts: Solidity 0.8.x, OpenZeppelin ERC721Enumerable or ERC721A (Azuki) for gas-optimized batch mint, ERC1155 from OpenZeppelin
• VRF and automation: Chainlink VRF v2.5, Chainlink Automation
• Storage: Pinata (IPFS pinning), NFT.Storage, Arweave for permanent storage
• Marketplace: OpenSea Seaport protocol, custom integration
• Frontend: wagmi v2 + viem, RainbowKit for wallet connection, React + TypeScript

Development process

1. Mint mechanics design — allowlist, public sale, price curve (Dutch auction or fixed), limits per wallet
2. Contracts — with Foundry fuzz tests on mint limits, Merkle proof verification, royalty calculations
3. IPFS deployment — upload metadata and images before reveal, pin on at least two services
4. Reveal — if using Chainlink VRF, test on testnet mandatory: VRF subscription must be funded with LINK tokens
5. Marketplace integration — verify collection on OpenSea, configure royalties, test MetadataUpdate events
6. Deployment and monitoring — Tenderly for reentrancy detection, Etherscan API for contract verification, set up event alerts

Deliverables

• Source code of smart contracts (Solidity, Rust for Solana) with comments
• Test suite (Foundry/Hardhat) with ≥90% coverage
• Deployment documentation and integration instructions
• Access to pinning services (Pinata/Pinfluence)
• Metadata generation scripts (Python/JS)
• Support during marketplace verification
• 30 days of technical support after deployment

Timeline

Cost is calculated individually after auditing your task. Send a brief with your project description — we will provide a transparent estimate within 3 business days. For regular clients, there is a flexible discount system on batch orders. If you need a gas-optimized contract, order a free gas analysis. Get a consultation on marketplace architecture — leave a request, and we will evaluate your project in three days.