React SDK

In this section, you'll learn how to go mainnet by using our React SDK

Go live with the React SDK

To move your React SDK integration to mainnet, update three network-specific values.

Do not mix testnet and mainnet values.

If one value still points to testnet, the flow can fail.

1

Use the mainnet asset issuer

Your escrow asset must use the mainnet issuer address.

If you send a testnet issuer, such as testnet USDC, it will not work on mainnet.

Review the issuer addresses here:

Trustlines

2

Change the provider base URL to mainnet

In your TrustlessWorkProvider, update baseURL from development to mainNet.

Use the provider setup shown in Getting Started, but switch the network value before going live.

src/trustless-work-provider.tsx

"use client";

import React from "react";
import {
  development,
  mainNet,
  TrustlessWorkConfig,
} from "@trustless-work/escrow";

interface TrustlessWorkProviderProps {
  children: React.ReactNode;
}

export function TrustlessWorkProvider({
  children,
}: TrustlessWorkProviderProps) {
  const apiKey = process.env.NEXT_PUBLIC_API_KEY || "";

  return (
    <TrustlessWorkConfig baseURL={mainNet} apiKey={apiKey}>
      {children}
    </TrustlessWorkConfig>
  );
}

development points to testnet.

mainNet points to production.

3

Generate a mainnet API key

Mainnet requires a mainnet API key.

A testnet API key will not authenticate against the mainnet environment.

When requesting the key in the dApp, switch to the Mainnet tab first.

Then request and store the key securely.

See the full process here:

Request API Key

Mainnet checklist

Before shipping your React app, confirm this:

• Your asset issuer is the mainnet issuer.

• Your provider uses baseURL={mainNet}.

• Your API key was generated from the Mainnet tab.

• The wallets involved have the correct mainnet trustlines.

If these four checks pass, your React SDK integration is ready for production.