Endpoint structure
Avalanche runs three built-in chains (C, X, P) on the same node. Your Chainstack base endpoint serves all three — to target a specific chain, append the chain-specific URI before your auth key. The URL pattern is:The most common reason an Avalanche endpoint “doesn’t work” is forgetting the chain URI. The node access page in the Chainstack console shows the full URL for each chain — copy from there to avoid path errors.
C-Chain HTTPS
To call EVM methods, use the C-Chain HTTPS endpoint:C-Chain WebSocket
For real-time subscriptions, connect over WSS to the C-Chain WSS endpoint:C-Chain
MetaMask
On node access details, click Connect wallet.Hardhat
Configure Hardhat to deploy contracts and interact through your Avalanche nodes.-
Install Hardhat 2 with the ethers plugin by running
npm install --save-dev hardhat@hh2 @nomicfoundation/hardhat-ethers@hh2 ethers, and create a project withnpx hardhat init. Thehh2tag installs Hardhat 2, which this configuration uses. -
Create a new environment in
hardhat.config.js:where- YOUR_CHAINSTACK_ENDPOINT — your node HTTPS or WSS endpoint protected either with the key or password. See node access details.
- YOUR_PRIVATE_KEY — the private key of the account that you use to deploy the contract
-
Run
npx hardhat run scripts/deploy.js --network chainstackand Hardhat will deploy using Chainstack.
Remix IDE
To make Remix IDE interact with the network through a Chainstack node:- Get MetaMask and set it to interact through a Chainstack node. See Interacting through MetaMask.
- In Remix IDE, navigate to the Deploy tab. Select Injected Provider - MetaMask in Environment.
web3.py
Build DApps using web3.py and Avalanche nodes deployed with Chainstack.- Install web3.py.
- Connect over HTTP or WebSocket. See also EVM node connection: HTTP vs WebSocket.
HTTP
Use theHTTPProvider to connect to your node endpoint and get the latest block number.
- YOUR_CHAINSTACK_ENDPOINT — your node HTTPS endpoint protected either with the key or password
- HOSTNAME — your node HTTPS endpoint hostname
- USERNAME — your node access username (for password-protected endpoints)
- PASSWORD — your node access password (for password-protected endpoints)
WebSocket
UseAsyncWeb3 with the WebSocketProvider object to connect to your node WSS endpoint and get the latest block number. The web3.py WebSocket provider is asynchronous, so the example runs in an asyncio event loop.
- YOUR_CHAINSTACK_ENDPOINT — your node WSS endpoint protected either with the key or password
- HOSTNAME — your node WSS endpoint hostname
- USERNAME — your node access username (for password-protected endpoints)
- PASSWORD — your node access password (for password-protected endpoints)
web3.php
Build DApps using web3.php and Avalanche nodes deployed with Chainstack.- Install web3.php.
-
Connect over HTTP:
where YOUR_CHAINSTACK_ENDPOINT is your node HTTPS endpoint protected either with the key or password
-
Use JSON-RPC methods to interact with the node.
Example to get the latest block number:
web3j
Build DApps using web3j and Avalanche nodes deployed with Chainstack. Use theHttpService object to connect to your node endpoint.
Example to get the latest block number:
- ENDPOINT — your node HTTPS endpoint
- USERNAME — your node access username
- PASSWORD — your node access password
ethers.js
Build DApps using ethers.js and Avalanche nodes deployed with Chainstack.- Install ethers.js.
- Connect over HTTP or WebSocket. See also EVM node connection: HTTP vs WebSocket.
HTTP
Use theJsonRpcProvider object to connect to your node endpoint and get the latest block number:
- YOUR_CHAINSTACK_ENDPOINT — your node HTTPS endpoint protected either with the key or password
- USERNAME — your node access username (for password-protected endpoints)
- PASSWORD — your node access password (for password-protected endpoints)
-
NETWORK_ID — Avalanche C-Chain network ID:
- Mainnet:
43114 - Fuji Testnet:
43113
- Mainnet:
WebSocket
Use theWebSocketProvider object to connect to your node WSS endpoint and get the latest block number:
- YOUR_CHAINSTACK_ENDPOINT — your node WSS endpoint endpoint protected either with the key or password
-
NETWORK_ID — Avalanche C-Chain network ID:
- Mainnet:
43114 - Fuji Testnet:
43113
- Mainnet:
Brownie
- Install Brownie.
-
Use the
brownie networks addcommand with the node endpoint:where-
ID — any name that you will use as the network tag to run a deployment. For example,
chainstack-mainnet. - NETWORK_NAME — any name that you want to identify the network by in the list of networks. For example, Mainnet (Chainstack).
- YOUR_CHAINSTACK_ENDPOINT — your node HTTPS or WSS endpoint protected either with the key or password
-
NETWORK_ID — Avalanche C-Chain network ID:
- Mainnet:
43114 - Fuji Testnet:
43113
- Mainnet:
-
ID — any name that you will use as the network tag to run a deployment. For example,
Foundry
- Install Foundry.
- Use
--rpc-urlto run the operation through your Chainstack node.
Forge
Useforge to develop, test, and deploy your smart contracts.
To deploy a contract:
- CONTRACT_NAME — name of the contract in the Solidity source code
- CONTRACT_PATH — path to your smart contract
- YOUR_PRIVATE_KEY — the private key to your funded account that you will use to deploy the contract
- YOUR_CHAINSTACK_ENDPOINT — your node HTTPS endpoint protected either with the key or password
Cast
Usecast to interact with the network and the deployed contracts.
To get the latest block number:
X-Chain
JSON-RPC API
Interact with the X-Chain through your Avalanche nodes using JSON-RPC API. Use curl or Postman to invoke Avalanche X-Chain API methods. Example below demonstrates how to get AVAX balance of an address through your Avalanche node HTTPS endpoint on the X-Chain mainnet:AvalancheJS
- Install AvalancheJS:
- Create a chain API client with your node’s base endpoint and authenticate with the username and password from your node’s access and credentials. AvalancheJS appends the chain path, such as
/ext/bc/X, to the base endpoint, so pass the endpoint without the auth token.