Introduction

If you have previously built marketplaces on Ethereum or another EVM chain, building a marketplace on Immutable zkEVM will be similar. However, there are a few key differences to be aware of.

Sections

• Key differences between Immutable zkEVM and other EVM chains
  • 1. Royalty enforcement via Seaport Extension
  • 2. Immutable Orderbook

---

Key differences between Immutable zkEVM and other EVM chains

1. Royalty enforcement via Seaport Extension

To allow for chain-wide royalty enforcement, there is currently only one supported contract for NFT settlement on Immutable zkEVM. This contract is a modified version of the open sourced Seaport contract. If your EVM marketplace uses another settlement contract, you will need to update your integration to use this contract.

Additionally, only orders with royalties that adhere to the ERC2981 standard will be approved by the Immutable Operator and accepted by the settlement contract.

💡Immutable Operator

The Immutable Operator referred to is a mechanism implemented by the Orderbook where an operator signature is used to verify and fulfill orders. This is a crucial part of the order validation process and is provided by the Orderbook API. For more detailed information about Immutable's Operator Allowlist, please refer to the Allowlist Specification section in the guide.

2. Immutable Orderbook

Immutable also requires that all marketplace listings are distributed through the Immutable Orderbook. This allows games to automatically distribute new listings across all Immutable-enabled marketplaces, which massively increases liquidity.

The Orderbook's settlement contract uses a custom Zone to validate the order is signed correctly by the off-chain orderbook. If your EVM marketplace currently operates a private orderbook, you will need to update to support Immutable zkEVM.