Build on Tuven

Public contract directory

Find fixed network primitives and configured application contracts.

The directory below shows fixed predeploy addresses and the application addresses configured for this website. An address is not proof that a contract is deployed, verified, or safe to use. Inspect its code and network before interacting with it.

Validate a contract

1. Check eth_chainId against the expected Tuven chain ID.
2. Use eth_getCode to confirm bytecode exists at the address.
3. Inspect verified source and the ABI in the explorer when available.
4. Read relevant owner, pause, fee, or upgrade settings from the contract.
5. Simulate the exact call with the account and amount you intend to use before requesting a signature.

Application contracts

The launchpad and bridge addresses are deployed after genesis and may differ between environments. Use the configured addresses shown here. When an address is unavailable, that application integration is not enabled on this site.

import { createPublicClient, http } from 'viem';

const client = createPublicClient({ transport: http('https://rpc.tuven.io') });
const code = await client.getCode({
  address: '0x3600000000000000000000000000000000000000'
});
if (!code || code === '0x') throw new Error('No deployed code');

Review permissions

Protocol and application contracts have different trust models. USDX includes asset-administration roles. The launchpad can be paused. The LP vault is upgradeable. The bridge relies on an authorized relayer and an owner-controlled policy. Verify these controls for the particular deployment rather than assuming that all contracts are immutable.