Contract Addresses

​

Multi-chain architecture

trUSD and strUSD support native cross-chain transfers via Chainlink CCIP using the Cross-Chain Token (CCT) standard. Ethereum Mainnet is the hub and holds the canonical token behind a Lock & Release CCIP token pool; each additional chain uses a Burn & Mint token pool. Monad, Pharos and Arbitrum are live; their addresses are listed below.

​

Ethereum Mainnet (primary)

​

Core

The Timelock enforces a 24-hour public delay on admin actions. It replaced the original timelock (0x7af35ab3…) on 15 September 2026; the admin role on every core contract moved to it through that timelock’s own 24-hour queue. Roles, Multisig and Timelocks documents what it gates and who holds each role.

​

Chainlink CCIP token pools

The canonical trUSD and strUSD above are bridged through Lock & Release token pools. Tokens sent to another chain are locked here and released on the way back; the pools’ balances are the backing of every trUSD and strUSD minted on Monad, Pharos and Arbitrum.

​

Monad

Chain ID 143. trUSD and strUSD on Monad are Burn & Mint representations of the Ethereum tokens: every unit in circulation here is locked in the Ethereum pool above.

​

Pharos

Chain ID 1672. Same model as Monad: Burn & Mint representations backed by the Ethereum pools. Pharos runs Chainlink’s 2.0.0 token pool generation.

​

Arbitrum

Chain ID 42161. Same model as Monad and Pharos: Burn & Mint representations backed by the Ethereum pools, on Chainlink’s 2.0.0 token pool generation. Lanes run between every pair of these four chains, both ways, with a rate limit of 1,500,000 tokens per lane refilled over six hours. The bridge is the supported way to move between them; a transfer from Ethereum or Arbitrum lands in about 20 minutes, one from Monad or Pharos within a minute.

​

Contract standards

​

Verification

Every Ethereum contract above is verified on Etherscan, with source code matching the deployed bytecode. The same source is published at github.com/Tori-Finance/tori-contracts, where forge build reproduces the deployed code. The protocol has been audited by Sherlock and Nethermind; the reports, each with its scope, are on the audits page. The CCIP token pools are Chainlink’s own audited contracts, deployed unmodified through the CCIP token pool factories.

​

Security best practices

​

Updates

Contract addresses will not change without prior notice. Any protocol upgrades will be announced through official channels:

• Twitter/X
• Official documentation (this site)

---

Questions? Join our Discord for support and community discussion.