Skip to main content
This page is for the engineer or operator choosing where an instance runs. After reading it you will know which products work on which network for development and production instances, how to read the same list from the API, and what each refusal for a missing product means. A product runs on a network only where Trusset has deployed its contracts for that instance type. Development instances use the network’s testnet and production instances its mainnet, so the two environments of one network can differ. An instance can be created on any listed network, but on a network where nothing is deployed it can only do what needs no Trusset contract, such as customer verification against an identity register you control.

Availability

Stock lending, commodity lending, Tether Gold lending and the earlier external securities lending generation run on Ethereum development instances only. Every other network answers them with 501 and the code of the family, listed under refusals.
Own register mode works on every EVM network, including those marked not yet available. An instance bound to an ERC-3643 identity registry or a Trusset-compatible register you deploy verifies customers there without any Trusset contract. Bind it under Identity Register in the instance settings of the Issuer Portal.
The Create Instance dialog of the Issuer Portal reads the same list. A network marked not yet available for the chosen instance type cannot be selected, and the line under the network field names the products that run on the selected one.

Read availability from the API

GET /public/networks returns the list above, derived from the contract addresses Trusset has configured for each network. It needs no API key, allows 60 requests a minute per address and may be cached for five minutes.
The example is shortened: the response carries every family in families and every network in networks. Family ids: IDENTITY_REGISTER, LENDING, VAULTS, WHITELISTS, LIQUIDATION_BOTS, NFT_LENDING, FINANCING, STOCK_TOKENS, COMMODITY_TOKENS, EQUITY_SHARES, PRICE_INDEXES.

Contract addresses

Polygon (production instances, chain 137)

Sepolia (Ethereum development instances, chain 11155111)

The settlement assets a lending market can use on each network are listed by List Borrow Assets.

Production access

Production instances need access granted by Trusset. Without it, creating a production instance is refused with 403 PRODUCTION_ACCESS_REQUIRED, in the Issuer Portal and on POST /instances/app alike. Request access by email to [email protected], or with Request access next to Production in the Create Instance dialog. Until it is granted, create development instances. A development instance does not convert into a production one. To go live, create a production instance on a network where the products you need run, and point your integration at its API keys.

Refusals for a missing product

A product that is not deployed for the instance’s network and type is refused with HTTP 501. The answer stays the same until Trusset deploys the product there, so do not retry it. The SDK does not retry a 501. The message names the network, the instance type and where the product is available.

Instances

Instance types, limits and isolation

Customers

Which identity register an instance writes to