Skip to content

Add Synex Chain (eip155:10224) support #7277

Description

@Bhushankumar1435

Request to Add Synex Chain (eip155:10224) to WalletConnect Explorer

JSON-RPC Specification for Wallets

Not required. Synex Chain is fully EVM-compatible and adheres to the standard Ethereum eip155 JSON-RPC specification.

Reference:
https://docs.walletconnect.com/2.0/advanced/rpc-reference/ethereum-rpc


CASA Namespace Specification

Not required. Synex Chain operates within the existing eip155 namespace for EVM-compatible networks.

Reference:
https://github.com/ChainAgnostic/namespaces/blob/main/eip155/caip2.md


Namespaces

  • eip155

Chains

  • eip155:10224 — Synex Chain Mainnet

Network Details

  • Chain Name: Synex Chain
  • Chain ID (Decimal): 10224
  • Chain ID (Hex): 0x27F0
  • Network Type: Mainnet

RPC Endpoints


Block Explorer


Native Currency

  • Name: SYNEX
  • Symbol: SYNEX
  • Decimals: 18

SLIP-0044 Coin Type

  • 60 (Ethereum standard, as Synex Chain is EVM-compatible)

Reference:
https://github.com/satoshilabs/slips/blob/master/slip-0044.md


References


Additional Context

Synex Chain is an EVM-compatible blockchain designed to support decentralized finance (DeFi), token swap infrastructure, and cross-chain interactions.

The network is live and publicly accessible via its RPC endpoint and block explorer. It is currently being integrated into a production-grade token swap application utilizing WalletConnect for mobile wallet connectivity (e.g., MetaMask Mobile).

However, WalletConnect session initialization fails due to the chain not being recognized:

"We don't support the chainId you provided: eip155:10224"


Request

We kindly request the addition of the following chain to WalletConnect’s supported networks:

  • eip155:10224 (Synex Chain Mainnet)

This will enable seamless WalletConnect integration and allow users to interact with Synex Chain via supported wallets.


Declaration

I confirm that the network details provided above are accurate and that the RPC endpoint and explorer are publicly accessible and operational.

I have read and understood the WalletConnect chain onboarding requirements.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions