Docs/developersNew

Getting Started

The fastest path from zero to your first compliant token on T-REX.

The fastest path from zero to your first compliant token on T-REX.

Choose your path

There are three ways to build on T-REX, depending on what you're trying to do.

I want to deploy and manage a token without writing code

Use the official T-REX | Token Factory dApp. Deploy a compliant ERC-3643 token in a few clicks on the T-REX Ledger Testnet (Ingen), manage its lifecycle, and verify the result in the explorer.

Best for: issuers, transfer agents, and ops teams running pilots or production workflows. No Solidity required.

→ T-REX AppStore — Token Factory

I want to integrate ERC-3643 into a production application

Use the T-REX Engine API. A stable, SOC 2 Type 2 certified REST API that abstracts the protocol's smart contracts across every supported chain, including the T-REX Ledger.

Best for: financial institutions, distribution platforms, custodians, and software vendors building production-grade integrations.

→ T-REX Engine · API reference at docs.tokeny.com

I want to build directly on the protocol

Work directly with the open-source ERC-3643 reference implementation and deploy to the T-REX Ledger Testnet (Ingen).

Best for: protocol developers, application builders preparing AppStore submissions, and teams that need fine-grained control over contracts and modules.

Continue with the quickstart below.

Quickstart: deploy your first compliant token on testnet

A 5-minute walkthrough using the T-REX Ledger Testnet (Ingen).

1. Configure your wallet

Add the Ingen network to your EVM wallet using the RPC endpoint:

https://rpc.ingen.t-rex.network/

See T-REX Ledger Testnet for full network details.

2. Get test gas

Visit the Ingen faucet and request test tokens for your wallet address.

3. Deploy a compliant token

Two options:

Option A — Use the Token Factory dApp (no code) Open T-REX | Token Factory on Ingen, connect your wallet, configure your token (name, symbol, compliance rules, eligibility criteria), and deploy. Done.

Option B — Deploy from source (code) Clone the ERC-3643 reference implementation, point your deployment scripts at the Ingen RPC, and run the standard deploy flow. The protocol behaves identically to other EVM environments.

Deployed contract addresses for shared infrastructure (identity factories, compliance modules) on Ingen are published in the Deployed contracts section as they are finalized.

4. Create identities and claims

Compliance follows the verified identity, not the wallet. Use the T-REX | Identity dApp to create OnchainIDs and issue claims for your test investors — or do it through the ERC-3643 contracts directly.

5. Make a compliant transfer

With identities and claims in place, transfer your token between verified participants. Watch the transaction land on the Ingen explorer. Try a transfer to an address without a valid OnchainID and observe the protocol-level rejection.

6. Try cross-chain

Use the Ingen bridge to test cross-chain flows. The freeze/mint reconciliation model preserves canonical accounting — see T-REX Ledger for the architecture.

You want to... Go to
Understand the protocol standard ERC-3643 Protocol → erc3643docs.erc3643.org
Understand the Ledger architecture T-REX Ledger
Use the Engine API T-REX Engine → docs.tokeny.com
List an application on the AppStore T-REX AppStore — Becoming a Builder
Get help or talk to the team Community · contact@t-rex.network