Omnichain-NFT (ONFT) Development with LayerZero

Omnichain-NFT (ONFT) Development

We develop Omnichain-NFT (ONFT) turnkey solutions, enabling your NFT collection to operate across multiple blockchains natively. Unlike single-chain NFTs, ONFT allows users to move assets between networks without bridges, expanding your audience by up to 5 times. Our expertise in LayerZero integration ensures atomic cross-chain transfers with full metadata synchronization.

ONFT (Omnichain Non-Fungible Token) is the LayerZero standard for NFT with native cross-chain transfer. Not a bridge with lock-and-mint risks, but a single contract deployed on multiple chains that atomically moves the NFT between them without losing metadata and ownership history.

How ONFT Works at the Protocol Level

LayerZero: Endpoints and Ultra Light Node

LayerZero is not a separate blockchain. It is a messaging protocol with Endpoint contracts on each supported chain (~50+: Ethereum, Polygon, Arbitrum, Optimism, BSC, Solana, Aptos, and others).

Note: when an NFT is sent from Ethereum to Arbitrum:

1. sendFrom() on Ethereum calls Endpoint.send() with encoded payload (tokenId, recipient)
2. LayerZero Oracle (Chainlink, Sequencer, or Google Cloud) records the block header on Arbitrum
3. LayerZero Relayer sends the proof of the transaction
4. Endpoint on Arbitrum verifies the proof via the Ultra Light Node (ULN) — not full block verification, only the required storage proof
5. lzReceive() on the ONFT contract on Arbitrum is called with the payload, minting the NFT to the recipient

On the source chain, the NFT is burned (or locked depending on implementation). On the destination, it is minted. The total supply remains unchanged.

ONFT721 vs. Custom Implementation

LayerZero provides the ONFT721 base contract in @layerzerolabs/solidity-examples. It is an ERC-721 with added sendFrom and lzReceive functions. The simplest ONFT implementation is inheriting from ONFT721 and adding custom logic.

Key parameters during deployment:

constructor(
    string memory name,
    string memory symbol,
    uint256 _minGasToTransfer, // minimum gas for lzReceive on destination
    address _lzEndpoint        // LayerZero Endpoint address for this chain
) ONFT721(name, symbol, _minGasToTransfer, _lzEndpoint) {}

_minGasToTransfer is critical: if set too low, lzReceive on the destination reverts due to out-of-gas, and the NFT gets stuck between chains. LayerZero recommendation: 200,000 gas for basic ONFT721, more if lzReceive contains additional logic.

Problems to Solve During Development

Metadata Synchronization in Cross-Chain Transfer

NFT metadata stored on IPFS or Arweave is not a problem—the URI is the same on all chains. The problem is with dynamic metadata: if the NFT has on-chain attributes (character level in a game, accumulated points), this data is stored in the contract storage. When moving to another chain, the on-chain state is not transferred automatically.

Solution: include the state in the LayerZero payload. A custom _debitFrom on source packs the state, and a custom _creditTo on destination restores it. This increases the gas cost of the transfer but preserves the full state.

function _debitFrom(address _from, uint16, bytes memory, uint _tokenId)
    internal override returns(bytes memory) {
    // Collect token state
    TokenState memory state = tokenStates[_tokenId];
    _burn(_tokenId); // or lock
    return abi.encode(_tokenId, state); // include in payload
}

function _creditTo(uint16, address _toAddress, bytes memory _payload)
    internal override returns(uint) {
    (uint tokenId, TokenState memory state) = abi.decode(_payload, (uint, TokenState));
    _mint(_toAddress, tokenId);
    tokenStates[tokenId] = state; // restore state
    return tokenId;
}

Estimating and Paying LayerZero Fees

Transferring via LayerZero is not free: the user pays in the native currency of the source chain for:

• Gas on the source chain (Endpoint.send)
• Oracle and relayer fee (goes to LayerZero)
• Gas estimation on the destination chain (prepaid) The client side must call estimateSendFee() before the transfer and pass the result as msg.value. If msg.value is less than the estimate, the transaction reverts.

function estimateSendFee(
    uint16 _dstChainId,
    bytes calldata _toAddress,
    uint _tokenId,
    bool _useZro,
    bytes calldata _adapterParams
) public view returns (uint nativeFee, uint zroFee);

Typical transfer cost ETH → Arbitrum: $0.50–2.00 in ETH depending on congestion.

Trusted Remote Configuration

Each ONFT contract on each chain must know the addresses of its "siblings" on other chains. This is managed via trustedRemote, an authorized list. Without it, any contract could mint ONFTs via LayerZero message.

// Executed after deployment on each chain
function setTrustedRemoteAddress(
    uint16 _remoteChainId,   // LayerZero chain ID
    bytes calldata _remoteAddress
) external onlyOwner;

Common mistake: forgetting to set trusted remote bidirectionally. Transfer Ethereum→Polygon works, but Polygon→Ethereum fails because the Polygon contract did not add Ethereum to trusted remote.

Nonce and Ordering Guarantees

LayerZero v1 guarantees ordered delivery: messages between two chains are delivered in the order they were sent. If a transaction with nonce N gets stuck (relayer failed to deliver), all subsequent ones with nonce N+1, N+2 wait. This can block all transfers from a specific chain.

LayerZero v2 transitions to unordered delivery with application-level ordering—a more flexible model that does not block the queue.

What Risks Are Involved in ONFT Development?

The main risks are related to trusted remote configuration (must be set bidirectionally) and choosing _minGasToTransfer (too little gas leads to stuck transfers). Also, testing custom state logic via LZEndpointMock is crucial to avoid data loss. In our practice, we always use formal verification for contracts.

Tech Stack for a Full ONFT Project

Comparison of ONFT vs Regular NFT with Bridge

LayerZero Protocol ensures atomicity, and OpenZeppelin provides standard contracts.

Why ONFT is Better Than Regular NFT with Bridge

ONFT surpasses classic bridges by 3 times in security thanks to atomic transfer without lock-and-mint. Additionally, the transfer speed is 2 times higher, as there is no need to wait for multiple block confirmations on the bridge. For the user, this means a single token with history on all chains. Gas cost savings for cross-chain operations reach up to 40%.

We have specialized in ONFT development for over 5 years and have completed more than 10 projects with LayerZero integration, handling over 100,000 cross-chain transfers with 99.9% uptime. Our solutions have helped projects reduce bridging costs by up to 60%.

What’s Included in the Work

• Requirements analysis and chain selection (Ethereum, Polygon, Arbitrum, BSC, Optimism, Base, etc.)
• Development of ONFT contracts with custom logic (state, fee, access control)
• Comprehensive tests (unit + integration with LZEndpointMock)
• Frontend component for bridging (network selection, fee estimation, status)
• Deployment to all target chains and trusted remote configuration
• Delivery of source code, deployment scripts, and configuration files
• Operational documentation and 1-month post-launch support
• Smart contract audit (optional)

Process and Timeline

Design (1 day): list of target chains, on-chain state to synchronize, custom logic in _debitFrom/_creditTo.

Contract development (2–3 days): ONFT721 with custom logic, tests via LZEndpointMock.

Frontend component (1 day): bridge interface with destination chain selection, fee estimation, transfer status.

Deployment and configuration (0.5 day): deploy to all chains, set trustedRemote.

Total: 3–5 days for basic ONFT without on-chain state. With complex state synchronization — 1–2 weeks. Basic package starts at $4,000; custom quotes after project analysis.

We have specialized in ONFT development for over 5 years and have completed more than 10 projects with LayerZero integration. Order a turnkey ONFT development—we will find the optimal architecture and timeline. Contact us to evaluate 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.