Integrations
Build on Quai with the tools you know
Quai Network is EVM-compatible, so the standard developer stack carries over. Each guide covers how a tool fits Quai, setup, working code, and honest notes on what differs.
Development Environment
Hardhat
Quai's zone chains run an EVM, so the Hardhat workflow Solidity teams already know — compile, test, script, deploy — carries over directly. Point your config at chain ID 9, swap Ethers for the quais SDK in deploy scripts, and ship.
Read the integration guide +Development Toolkit
Foundry
Foundry's forge is the fastest way to build and fuzz EVM contracts — and because Quai zones are EVM-compatible, your forge build and test loop works unchanged. Deployment pairs forge artifacts with a small quais script, since Quai nodes speak the quai_ RPC namespace.
Read the integration guide +JavaScript SDK
ethers.js
Quai's official JavaScript SDK, quais, is a maintained fork of Ethers v6. Providers, wallets, signers, contracts — the API you know carries over nearly one-to-one, extended for Quai's multi-chain hierarchy, sharded addresses, and quai_ RPC namespace.
Read the integration guide +TypeScript Client
viem
viem works with Quai today through the path most modern dApps already use: an injected EIP-1193 provider. With Pelagus wallet as the transport, viem wallet clients connect accounts and route requests — and the quais SDK covers programmatic transaction flows the node's quai_ namespace requires.
Read the integration guide +Wallet Connectivity
WalletConnect
Every dApp lives or dies by its connect button. On Quai, the supported connection path today is Pelagus — the network's flagship wallet — over the same EIP-1193 injected-provider standard WalletConnect-era dApps are built on. Structure the connection layer right, and additional connectors drop in without a rewrite.
Read the integration guide +Data & Indexing
Subgraph
Apps that need rich on-chain data — dashboards, feeds, analytics — usually reach for a subgraph. On Quai, the same outcomes come from three building blocks: GraphQL served by the node itself, Quaiscan's explorer dataset, and custom indexers streaming events over WebSockets with the quais SDK.
Read the integration guide +