Skip to content
Start a project

Blockchain and DeFi

NFT marketplaces where creators mint, sell and receive royalties on-chain

We build NFT marketplaces end to end: collection and minting contracts, listings, auctions and offers, and the storefront collectors use. Royalties, fees and metadata live in contracts and storage your team controls.

NFT marketplaces at a glance

Workflows
Minting and drops, fixed-price listings, auctions, offers, royalty payouts, collection management
Chains
Ethereum, Polygon, BNB Smart Chain, Moonbeam, Moonriver and EVM Layer 2s
Controls
Signed orders with nonces and expiry, allowlist proofs, metadata freeze, pausable trading
Start
A 30-minute scoping call

What can we build for you?

Drops

A collection launch that limits bot minting

Allowlist phases with Merkle proofs, per-wallet caps and a reveal that keeps traits hidden until minting closes.

Marketplace

Collectors list and bid without paying gas each time

Signed orders settle on-chain only when a sale happens, across fixed-price, English and Dutch auction formats.

Creator tools

Creators publish collections without writing code

Lazy minting, collection setup and royalty settings in a dashboard, with each token minted when its first buyer pays.

Gaming

In-game items that players own

ERC-1155 items with crafting, upgrades and transfers that your game server and contracts both recognize.

Social commerce

Influencers sell digital collectibles to their audience

A storefront per creator, social sharing and buyer rewards, with sales tracked back to the creator who drove them.

Memberships

Access passes and tickets that verify at the door

Token-gated content, event tickets with check-in and membership tiers that read ownership straight from the chain.

How we work on it

Metadata that outlives any single server

Images and traits are pinned to IPFS and referenced by hash from the contract.

Dashboards for creators and collectors

Creators manage collections and royalties; collectors track items, bids and sales history.

Launch mechanics chosen per drop

Allowlists, reveals, auctions and editions are configured for each release.

Which risks do we engineer for?

Risks in NFT marketplaces work and how we handle them
RiskWhy it mattersHow we handle it
Signature replayA signed listing that can be reused lets a buyer take items at a stale price.Nonces, expiry times and on-chain cancellation for every order, signed as EIP-712 typed data users can read.
Metadata that changes or disappearsIf images and traits sit on one server, a shutdown or edit changes what collectors bought.Metadata pinned to IPFS, content hashes in the contract and a freeze once the collection is final.
Royalty bypassRoyalties are optional at the token level, so other venues can skip them.Royalties paid by your marketplace contract, ERC-2981 for other venues and transfer rules where creators accept the trade-offs.
Mint-day failureGas spikes and bot traffic can stall a public mint and push fees onto real collectors.Allowlist phases, per-wallet caps, gas-efficient batch minting and a load test of the mint page before launch.
Approval exposureCollectors approve the marketplace to move whole collections, so a bug there exposes every listed item.A small, non-upgradeable transfer contract, approvals scoped to it and audit time focused on settlement.

How is it delivered?

  1. Scope the mechanism

    We map the mechanism, the assets at risk and the chains you need.

    Output Written specification and milestone plan

  2. Architecture and threat model

    We design the contracts, roles and upgrade path, then list how each part could be attacked.

    Output Architecture document and threat model

  3. Milestone builds on testnet

    Each milestone ships to testnet with unit, fuzz and invariant tests.

    Output Tested contracts and a testnet deployment

  4. Audit, mainnet and after

    We freeze the code for an independent audit and fix the findings. Then we deploy, verify and stay on after launch.

    Output Audit report, verified contracts and a deployment record

Contracts
Solidity, ERC-721 and ERC-1155, ERC-2981 royalties, Hardhat
Storage
IPFS pinning, content hashes stored on-chain
Marketplace services
Order service, PostgreSQL, subgraphs for sales history
Storefront
React web and React Native mobile apps; MetaMask and Trust Wallet connections

Shipped work

Questions

Short answers to the questions we hear most often.

Can we see NFT work you have shipped?

Ask on the scoping call. Where clients allow it, we walk you through NFT work we have shipped, such as NFT staking contracts.

Can royalties be guaranteed on every sale?

Not across every marketplace. Your own marketplace pays them, and ERC-2981 tells other venues what to honor. Stricter transfer rules are possible but limit where tokens can trade.

Where are images and metadata stored?

On IPFS by default, pinned through an account you control, with hashes recorded on-chain. Game items that change use a versioned metadata service that logs every edit.

Which token standard should our collection use?

ERC-721 suits one-of-one art and unique items. ERC-1155 suits editions, game items and tickets. Most marketplaces support both, and we design around your catalog.

What drives the cost of an NFT marketplace?

Every engagement is quoted after a scoping call. Cost depends on sale formats, creator tooling, chains, payment options and whether you need a mobile app.

Have an agent, protocol or product to ship?

Send a short brief and we'll reply with times for a 30-minute scoping call.