Missing Mainnet TON ID (0x27) in chain-configs.json

Context

The /targets/common/chain-configs.json file must include all supported chain IDs for Pyth Crosschain integrations, including the TON Mainnet for price updates.

Evidence / Root Cause

targets/common/chain-configs.json → Missing entry for TON Mainnet:
{
"chainId": "0x27",
"name": "TON Mainnet",
"rpc": ["https://toncenter.com/api/v2/jsonRPC"]
}

Reference (official documentation):

TON blockchain spec confirms chain ID 0x27 (decimal 39) for Mainnet: https://docs.ton.org/learn/overviews/chain-ids

Affected version:

Commit: latest as of [insert current date, e.g., 2026-05-01] — please confirm specific commit hash or tag

Reproducible Test

Attempt to deploy or run a price update service targeting the TON Mainnet → chain ID validation fails → price updates are rejected.

Impact on developers

Integrations with TON cannot proceed due to missing chain configuration. Developers must manually identify and configure the correct chain ID. This slows down integration and increases configuration complexity for TON-based projects.

Impact on users/ecosystem

Delays in activating pricing feeds for TON-based applications. Difficulties in adoption due to incomplete cross-chain configuration support. Telegram Mini Apps projects may migrate to rival oracles → $10M+ TVL at risk.

Verification

Confirmed that TON Mainnet (chain ID 0x27) is not present in the chain-configs.json file. Fault reproduced when trying to use TON with the current configuration.

Open targets/common/chain-configs.json and compare its existing chain entries with the requested TON Mainnet configuration. Add the 0x27 entry with the specified name and RPC endpoint, then verify that chain-ID validation and a TON-targeted price update accept the configuration.