search

Tooling & SDKs

(Hardhat, Foundry, etc.)

Relix is built to work with the same tools developers already use on other EVM networks. In most cases, the only changes you need are:

  • The RPC URL: https://rpc-testnet.relixchain.com

  • The chain ID: 4127

  • The native token symbol: RLX

This section outlines how common frameworks, SDKs, and libraries fit into a Relix-based workflow.

hashtag
Hardhat

Hardhat is a natural choice for contract development, testing, and deployments.

Typical use cases on Relix:

  • Compiling and testing Solidity contracts

  • Running local unit tests before hitting the testnet

  • Deploying contracts to Relix Testnet via a dedicated network entry

All you need is a Relix network definition in hardhat.config and a funded deployer key. From there, scripts and tasks you already use on other chains can usually be reused as-is.

hashtag
Foundry

Foundry is popular with teams that prefer a fast, CLI-focused toolchain.

On Relix, Foundry works well for:

  • High-speed unit tests written directly in Solidity

  • Script-based deployments using forge create

  • On-chain simulations against the Relix RPC endpoint

Configuring Foundry with a relixTestnet RPC entry lets you switch between networks simply by changing the --rpc-url and --chain flags during deployment.

hashtag
Remix

For quick experiments or demonstrations, Remix in the browser is often the easiest way to get started:

  • Write or paste Solidity contracts

  • Connect MetaMask to Relix Testnet

  • Deploy and interact with contracts directly from the UI

This is especially useful when testing small changes, validating ideas, or giving non-technical stakeholders a live preview of contract behavior on Relix.

hashtag
JavaScript & TypeScript SDKs

On the application side, most modern dApps rely on a combination of JavaScript or TypeScript libraries. Relix supports the same patterns.

Common choices include:

  • ethers.js – general-purpose EVM library for reading data, sending transactions, and interacting with contracts.

  • viem – a type-safe alternative with a strong focus on developer ergonomics.

  • wagmi – React hooks for managing wallet connections and contract interactions in frontend applications.

All of these can talk to Relix as soon as you:

  1. Point the provider to https://rpc-testnet.relixchain.com.

  2. Configure the chain ID as 4127.

  3. Use RLX as the native currency symbol in your UIs.

hashtag
Frontend integration patterns

For web frontends, Relix fits into existing EVM connection flows:

  • Wallets connect via MetaMask, Rabby, OKX Wallet, or any WalletConnect-compatible client.

  • The dApp reads the active network and either:

    • Prompts the user to switch to Relix Testnet, or

    • Adds Relix as a custom network if not already present.

Once connected, contract calls and transactions use the same abstractions as on other chains—only the network configuration changes.

Typical frontend stack on Relix:

  • React or similar SPA framework

  • wagmi/ethers/viem for blockchain interactions

  • Relix Testnet RPC for on-chain reads and writes

  • Relix Testnet Explorer links in UIs for viewing transactions and addresses

hashtag
Backend services and indexers

Backend systems that need deeper insight into on-chain activity can use:

  • Direct JSON-RPC calls for targeted queries

  • Log filters (eth_getLogs) for tracking specific events

  • Custom indexing pipelines to maintain application-specific databases (positions, orders, game states, etc.)

Relix does not impose a special backend SDK; any EVM-aware stack that already ingests data from Ethereum-style chains can be adapted by:

  • Adding Relix RPC as another source

  • Recognizing chain ID 4127 as a distinct environment

  • Recording RLX-denominated balances and fees where relevant

hashtag
Environment separation and configuration

As your project grows, it helps to keep Relix-specific settings centralized:

  • A small chains module or config file that defines:

    • Name: Relix Testnet

    • Chain ID: 4127

    • Native currency: RLX

    • RPC URL: https://rpc-testnet.relixchain.com

    • Explorer URL: https://testnet.relixchain.com

  • Separate environment files for:

    • Local development

    • Relix Testnet

    • Future Relix mainnet

With this structure, switching from another EVM chain to Relix—or adding Relix as an additional deployment target—becomes a configuration change rather than a rebuild of your tooling stack.

hashtag
Summary

Relix does not require a new generation of tools. Instead, it integrates cleanly with the existing EVM ecosystem:

  • The same compilers and frameworks (Hardhat, Foundry, Remix)

  • The same JavaScript/TypeScript SDKs (ethers, viem, wagmi, and others)

  • The same patterns for deployment, testing, and indexing

By leaning on proven tooling, Relix lets teams move quickly while keeping their development workflow familiar and maintainable.

PreviousUsing Relix RPC (HTTP & WebSocket)NextTesting & Debugging

Last updated