Header Background

Environments & Networks

Table of contents

Environments & Networks

Two separate ideas are easy to confuse: the platform environment you are using (production or a testing deployment) and the blockchain network an offering is deployed on (a mainnet or a testnet). Production T-Suite supports both mainnet and testnet offerings side by side.

Platform environments

EnvironmentWhat it isWho uses it
ProductionThe live T-Suite platform at app.libertum.io and on each whitelabel tenant’s custom domain. Real accounts, real KYC/KYB, real billing.Investors, issuers, asset managers, transfer agents
SandboxA separate deployment of the same software with its own database, used by Libertum to test releases and run demonstrations.Libertum

Data never crosses between the two: an account, offering or subscription created in one does not exist in the other. The API host for each environment is provided as part of an integration arrangement — in these docs it is referred to as “the T-Suite API host for your deployment”.

Mainnets and testnets

Within production, each offering lives on the blockchain network chosen when it was created.

Chain familyMainnets used for tokenizationTestnets available
EVMBase, Ethereum, Polygon, ArbitrumBase Sepolia, Ethereum Sepolia, Polygon Amoy, Arbitrum Sepolia, Avalanche Fuji
CardanoCardano mainnet — CIP-20 metadata tokensPreview testnet — CIP-113 programmable tokens
XRPLInfrastructure only — not yet selectable by issuers—

Which token standards run on which mainnet is listed in the chain matrix. BNB Chain and Avalanche are not live mainnets for tokenization; Avalanche appears only as a testnet.

CIP-113 is not live on Cardano mainnet. It runs on the preview testnet; mainnet support follows the Cardano Foundation’s canonical CIP-113 mainnet release.

Using testnet offerings for trials

Testnet offerings are the safe way to try the full flow end to end — create an offering in the Tokenization Wizard, deploy its contracts, onboard a test investor, place and settle an order — without real money or real assets.

  • Testnet tokens and testnet stablecoins have no value.
  • Testnet offerings are for evaluation and demonstrations; do not present them to investors as real offerings.
  • The Custodian Wallet deposit card warns when a network is a testnet, so test assets and real assets are not mixed up.
  • The Stablecoin Studio Starter tier is limited to testnets; Growth adds Cardano mainnet.

Plan limits count mainnet only

Plan offering limits (for example, 3 mainnet offerings on Issuer Starter and 10 on Issuer Growth) count mainnet offerings only, and are enforced at publish time across the whole organisation. Testnet offerings do not consume the allowance, so an issuer can rehearse freely before going live. See Plans and pricing.

Networks for the Custodian Wallet

The Custodian Wallet software supports EVM networks (Ethereum, Base, Polygon, Arbitrum, Avalanche, BNB Chain), Cardano, Solana and XRPL, but the networks actually enabled vary per deployment. A network appearing in the Custodian Wallet does not mean tokenized offerings can be issued on it — tokenization follows the table above.

Good practice for integrators

  • Build and test against testnet offerings first; move to mainnet only once the flow is agreed.
  • Never reuse wallets, keys or credentials between testing and production.
  • Treat any address or identifier from one network as meaningless on another — a contract address on a testnet does not exist on the matching mainnet.