NFT Marketplaces Built on Gas-Efficient Standards and Honest Trade-Offs

No, and any agency that promises this is not being straight with you. On most EVM chains, creator royalties are not enforced at the protocol level. The ERC-2981 standard provides a way for a token to declare what royalty it expects and to whom, but it is up to the marketplace executing a sale to read that and actually pay it. When marketplaces compete on fees, some choose to make royalties optional or skip them entirely — the public royalty disputes between major marketplaces made this very visible. There are partial technical mitigations: restricting transfers to an allowlist of marketplaces that honour royalties, or enforcing royalties within your own marketplace contract where you control settlement. Each has trade-offs around composability and user freedom. We implement ERC-2981 correctly, enforce royalties within the platform you control, and explain honestly where royalties will and will not be collected once tokens trade elsewhere.

Almost always off-chain, because storing images or video directly on a blockchain is prohibitively expensive. The token holds a small piece of metadata that points to the media. The critical question is where that media lives. If it sits on a normal web server, it can be moved, changed or switched off — at which point the NFT points at nothing, which has happened to real collections. We default to content-addressed storage: IPFS, where the link is a hash of the content so it cannot be silently altered (paired with reliable pinning so it stays available), or Arweave, which is designed for permanent, pay-once storage. This means the token references durable, tamper-evident content. We are clear that even IPFS requires the content to remain pinned somewhere, and we set up that pinning rather than assuming it.

It depends on who your users are and what obligations you want to carry. In a non-custodial marketplace, users connect their own wallets and trade directly; assets and funds move between their wallets and the marketplace contract, and you never hold their items. This minimises your security burden and is the model most aligned with how NFTs work, but it requires users to manage a wallet, which can be a barrier for mainstream audiences. In a custodial model, you hold users' assets on their behalf — often with email logins and managed wallets — which is far friendlier for newcomers but makes you responsible for safekeeping, with the security weight and potentially regulatory and AUSTRAC implications that custody carries. There are hybrids, such as managed wallets that users can export. We help you choose deliberately and design the security model to match, rather than drifting into custody by accident.

Gas on minting is one of the most common reasons a drop disappoints, so we attack it from several angles. We use gas-efficient token standards — ERC-721A, for example, makes minting several tokens in one transaction dramatically cheaper than minting them one by one, which matters in a high-demand drop. We can use lazy minting, where the token is not written on-chain until it is bought, so the buyer pays the mint cost at purchase rather than the creator funding a whole collection upfront. And most importantly, we typically recommend deploying to an L2 such as Base, Polygon or Arbitrum, where transaction costs are a small fraction of Ethereum mainnet. The right combination depends on your collection size, drop mechanics and where your audience already holds assets, and we model the expected costs before committing to an approach.

They can, and the answer depends heavily on what the NFTs represent and how the marketplace operates — which makes this a question for specialist legal counsel rather than engineers. A purely artistic or collectible NFT is usually treated differently from one that confers financial rights, profit expectations or functions like an investment product, which could engage ASIC oversight under the Corporations Act. If your platform exchanges crypto for fiat, holds customer assets in custody, or operates as a designated service, AUSTRAC's AML/CTF regime — including registration and reporting duties — may apply. We do not give legal advice. We build the marketplace so that controls your lawyers identify can be implemented — KYC at the application layer, allowlisting, geofencing, custody arrangements with appropriate safeguards — and we recommend resolving the regulatory position before launching to the public.

Often, yes, and it can be the pragmatic choice. There are well-established, audited protocols — such as the Seaport protocol that underpins several major marketplaces — that handle the hard, security-critical parts of order settlement. Building on a proven, audited base for the trade-execution layer reduces both your audit surface and your risk, while we focus effort on the parts that differentiate your product: the token contracts, the minting and drop mechanics, the metadata pipeline, the curation logic and the front end. The alternative — bespoke marketplace contracts — gives you full control and is the right call when your trading model is genuinely novel, but it means more contract code to audit and maintain. We will recommend the approach that fits your requirements and risk appetite rather than defaulting to building everything ourselves.