Chain profile

Telos EVM chain ID 40 and mainnet RPC URL

Reviewed

Checked June 26, 2026. Telos documentation lists Telos Mainnet RPC URL, chain ID 40, TLOS as the symbol, and Teloscan as the explorer.

Chain ID40 / 0x28
RPC URLhttps://rpc.telos.net
Explorerhttps://www.teloscan.io
Gas tokenTLOS
VerificationVerified metadata
Manual reviewJune 26, 2026
Evidence snapshot

Verification record

Manual metadata review and automated evidence checks are tracked separately. This is not a live uptime, latency, or production reliability monitor.

Manual metadata review
Verification status
Verified metadata
Verification run
source-monitoring-2026-06-26
Verification tool
source-monitoring-refresh
Source set
Telos docs
Manual review cadence
monthly; after July 26, 2026
Latest recorded chain ID probe
eth_chainId matched expected 0x28; observed 0x28 on

MethodologyReport a correction

Telos EVM wallet-add fields

Wallet directory sites often expose a connect button. Main.net keeps the same setup fields as text so developers can compare them with official/source docs before callingwallet_addEthereumChain.

chainId
0x28 (40)
chainName
Telos EVM
nativeCurrency
TLOS; name TLOS, symbol TLOS, decimals 18
rpcUrls
https://rpc.telos.net
blockExplorerUrls
https://www.teloscan.io

Monitoring evidence

These checks are review signals only. They are not uptime, latency, privacy, or production reliability claims.

Snapshot generated
Source checks
2 sources checked
Source changes
0 changes since the previous source hash snapshot
Source fetch failures
0
eth_chainId probe
matched expected 0x28
Per-source check timing
Included in the monitoring snapshot, not used as this page's review date

View monitoring snapshots orsource change history.

Network endpoints

Primary public RPC
https://rpc.telos.net
Explorer
https://www.teloscan.io
Official/source documentation
Telos docs
Chain type
EVM L1 mainnet
Chain ID hex
0x28
Manual review cadence
monthly; next review after July 26, 2026

Telos EVM common questions

What is the Telos EVM mainnet RPC URL?
Telos EVM's listed primary public RPC URL is https://rpc.telos.net.
What is Telos EVM's chain ID?
Telos EVM's listed chain ID is 40.
What block explorer does Telos EVM use?
Telos EVM's listed block explorer is https://www.teloscan.io.
What gas token does Telos EVM use?
Telos EVM's listed gas token is TLOS.

Copy-ready config

Neutral app configuration built from the verified fields above. Copy buttons only place text on your clipboard; they do not connect a wallet, request permissions, or rank RPC providers.

Chain ID decimal40
Chain ID hex0x28
RPC URLhttps://rpc.telos.net
Explorer URLhttps://www.teloscan.io
EIP-3085-shaped JSON

Rendered as text for manual review before use.

{
  "chainId": "0x28",
  "chainName": "Telos EVM",
  "nativeCurrency": {
    "name": "TLOS",
    "symbol": "TLOS",
    "decimals": 18
  },
  "rpcUrls": [
    "https://rpc.telos.net"
  ],
  "blockExplorerUrls": [
    "https://www.teloscan.io"
  ]
}

Developer snippets

Static examples generated from Main.net fields. These snippets are for manual configuration review and read-only RPC checks; they do not connect wallets, create signers, submit writes, or rank providers.

ts

viem chain definition

Read-only snippet generated from Main.net fields. Review official sources before production use.

import { defineChain } from 'viem'

export const telosEvmMainnet = defineChain({
  id: 40,
  name: "Telos EVM",
  nativeCurrency: {
    name: "TLOS",
    symbol: "TLOS",
    decimals: 18,
  },
  rpcUrls: {
    default: { http: ["https://rpc.telos.net"] },
    public: { http: ["https://rpc.telos.net"] },
  },
  blockExplorers: {
    default: {
      name: "teloscan.io",
      url: "https://www.teloscan.io",
    },
  },
})
ts

wagmi read-only config

Read-only transport example generated from Main.net fields. It does not include account adapters or transaction actions.

import { createConfig, http } from 'wagmi'
import { telosEvmMainnet } from './telos-evm'

export const config = createConfig({
  chains: [telosEvmMainnet],
  transports: {
    [telosEvmMainnet.id]: http("https://rpc.telos.net"),
  },
})
ts

ethers read-only provider

Read-only JsonRpcProvider example generated from Main.net fields. It does not create a signer.

import { JsonRpcProvider } from 'ethers'

export const provider = new JsonRpcProvider("https://rpc.telos.net", {
  chainId: 40,
  name: "telos-evm",
})

const network = await provider.getNetwork()
console.log(network.chainId)
bash

curl eth_chainId check

Minimal JSON-RPC identity check. This verifies the endpoint-reported chain ID only, not uptime or production suitability.

curl -s -X POST \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}' \
  https://rpc.telos.net

# Expected chain ID: 40 / 0x28

Developer signals

External dashboards a developer may inspect before choosing where to deploy. Main.net links to these references but does not collect the metric values, normalize methodologies, rank chains, or recommend deployments.

Safety note

Telos documentation notes an EVM 2.0 upgrade period. Confirm the current RPC and explorer against Telos docs before routing production traffic.

Main.net is an independent reference site. It does not operate this chain, custody assets, execute transactions, or provide investment advice.

Report a correction

If this page has stale RPC, explorer, chain ID, or source information, open a public correction issue with a source link so it can be checked.

Report Telos EVM dataSend page feedback