Setup

Learn how to set up your environment to integrate and use Immutable Orderbook

Sections

• Install
• Initialize
• Create signers for user authorisation

---

Install

Prerequisites

Node Version 20 or later

Immutable's Typescript SDK requires **Node v20** (Active LTS version) or **higher**. Node v20 can be installed via `nvm`.

To install nvm follow these instructions. Once installed, run:

nvm install --lts

• (Optional) To enable Code Splitting (importing only the SDK modules you need) there are additional prerequisites.

Install the Immutable SDK

Run the following command in your project root directory.

npm

npm install -D @imtbl/sdk
# if necessary, install dependencies
npm install -D typescript ts-node

yarn

yarn add --dev @imtbl/sdk
# if necessary, install dependencies
yarn add --dev typescript ts-node

Troubleshooting

The Immutable SDK is still in early development. If experiencing complications, use the following commands to ensure the most recent release of the SDK is correctly installed:

npm

rm -Rf node_modules
npm cache clean --force
npm i

yarn

rm -Rf node_modules
yarn cache clean
yarn install

Initialize

When you initialize the SDK, the chainName configuration will direct the SDK to connect to a specific environment.

Supported values are:

Chain Name	Chain ID	Operator Allowlist Address
imtbl-zkevm-testnet	eip155:13473	https://api.sandbox.immutable.com/v1/chains returns operator_allowlist_address
imtbl-zkevm-mainnet	eip155:13371	https://api.immutable.com/v1/chains returns operator_allowlist_address

import { config, orderbook } from '@imtbl/sdk';
import { ethers } from 'ethers'; // ethers v5

const PUBLISHABLE_KEY = 'YOUR_PUBLISHABLE_KEY'; // Replace with your Publishable Key from the Immutable Hub

const client = new orderbook.Orderbook({
  baseConfig: {
    environment: config.Environment.SANDBOX,
    publishableKey: PUBLISHABLE_KEY,
  },
});

Create signers for user authorisation

Creating, filling and cancelling orders require a user's authorisation.

💡What is a Signer?

A signer is a representation of a user's wallet (account) that is used to authorise transactions. These transactions typically involve transferring the ownership of assets (currencies or NFTs) from one account to another, hence why the user is required to "sign" these transactions. Applications use signers to obtain user signatures to execute payments, asset transfers, and more. For more information, see the Signers definition from the ethers library.

In order to create a signer, you must first establish a connection to the user's wallet. This is how you connect to different user wallets:

Passport

To initialise the passport module, please see the Passport Setup guide.

import { Web3Provider } from '@ethersproject/providers';

const passportWallet = passport.connectEvm(); // returns an EIP-1193 provider
const ethersProvider = new Web3Provider(passportWallet);
const signer = ethersProvider.getSigner();

Browser

import {ethers} from "ethers"; // ethers v5
import CodeBlock from '@theme/CodeBlock';
const browserWallet = new ethers.providers.Web3Provider(window.ethereum);

Then, create a signer from the wallet connection:

const signer = browserWallet.getSigner();

Private key

import { getDefaultProvider, Wallet } from "ethers"; // ethers v5

const rpcProvider = getDefaultProvider("https://rpc.testnet.immutable.com/")

const signer = new Wallet(PRIVATE_KEY, rpcProvider);