// the take
A from-scratch ERC-721 implementation split into composable pieces (base token, metadata extension, enumerable extension) rather than one monolithic contract, published to npm with ABI JSON for JS consumers. Aimed at developers who want to mint/burn NFTs on Ethereum, Wanchain, or other EVM chains without writing the standard from scratch.
Clean separation of ERC-165, base token, metadata, and enumerable logic into separate contracts so you only inherit what you need instead of pulling in one bloated base class. Ships a Hardhat test suite with Codecov tracking and an online validator (erc721validator.org) to check conformance of any deployed contract, not just this one. Includes a bug bounty program with a defined scope rather than just a disclaimer.
It's explicitly non-payable-by-default and deviates from the full ERC-721 spec, so you're patching in functionality OpenZeppelin already ships correctly. The README still points at Ropsten testnet deployments, a network that's been deprecated since 2022 — a sign the docs haven't been fully re-reviewed despite a recent push. The project has changed hands twice (0xcert to Nibbstack to an individual maintainer in 2026), which is a real continuity risk for something holding audited financial logic. For a token standard this common, OpenZeppelin's implementation has vastly more production usage and audit history; picking this instead means betting on a smaller, less battle-tested codebase for no clear functional gain.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →