How NFTs actually work
An NFT is a token where every unit is distinct and not interchangeable, unlike a normal token where every unit is identical. What lives on the blockchain is the item identifier, the current owner, and a pointer to descriptive data called metadata.
Here is where many projects go wrong: the image is not on the blockchain, because on-chain storage is prohibitively expensive. If the file sits on an ordinary web server and that server is ever switched off, buyers are left holding an identifier pointing at a dead link. We use IPFS, which addresses files by a hash of their contents — so the file cannot be swapped for a different one — and we set up pinning so it genuinely stays available.
What we build
The NFT contract
ERC-721 where every item is one of one, such as artwork or certificates. ERC-1155 where many copies of the same item exist, such as game items or event passes — substantially cheaper when issuing at volume.
Minting
A page where users connect a wallet and mint. Supports per-wallet limits, phased sales, allowlists and delayed reveal, plus lazy minting where the buyer pays the gas at purchase so creators do not fund an entire collection up front.
The marketplace
- Fixed-price listings and timed auctions
- Buyer offers and negotiation
- Configurable platform fees
- Creator royalties paid automatically on every resale
- User profiles, collection pages, trade history and search filters
- Multi-chain support with MetaMask and WalletConnect
What to understand about royalties before you commit
Royalties are not enforced by the blockchain itself. ERC-2981 only declares what should be paid and to whom — each marketplace then chooses whether to honour it, and some do not. If royalty income is central to your business model you need additional design, such as restricting transfers to marketplaces that pay. We walk through this trade-off before you build on the assumption.
How we work
- Scope and standardERC-721 or ERC-1155, supply, sale mechanics, and any special conditions.
- Metadata and storageMetadata structured and uploaded to IPFS with pinning arranged for long-term availability.
- Contract developmentSale logic, access restrictions and royalty configuration.
- Front end and marketplaceMint page, collection pages and trading, wired to user wallets.
- Security review and testingCode review plus full user-journey testing on a test network.
- Launch and handoverProduction deployment with documentation for ongoing configuration.
Frequently asked questions
Do we need our own token first?
No. NFTs trade in the network native coin such as ETH or BNB, or in a stablecoin. Your own token is an optional addition when you want an internal economy.
Where are the image files stored?
On IPFS, which addresses files by a hash of their contents, so they cannot be substituted later. We arrange pinning to keep them available. Ordinary web servers are not recommended — if the server goes away, the NFT points at nothing.
Which chain suits NFTs best?
For international art collectors, Ethereum still carries the most weight. For high volume and low fees — game items, event tickets — Polygon or BNB Chain are the better fit.
Is a custom marketplace worth it when OpenSea exists?
It is worth it when you need control over the experience, want to keep the fees, need royalties genuinely enforced, or have rules general marketplaces do not support. If the goal is simply to sell one collection, an existing marketplace is far cheaper. We will tell you plainly if we think a custom build is not justified.
Can buyers pay by credit card?
Yes, by integrating a payment provider that converts fiat to crypto for the buyer, so people without a wallet can still purchase. This adds KYC obligations that need planning together.
Talk to us before you commit
Tell us what you are trying to solve. Our solution architects reply within 24 hours with an initial scope and approach, at no cost. If we think what you are asking for is not worth building, we will say so.