How to Verify the peaq Mainnet Launch Date and RPC in 2024–2025
Confirm the peaq mainnet launch date, validate that an RPC endpoint connects to peaq, and understand why RPC access is different from indexed blockchain data.
The peaq mainnet launched on November 12, 2024, not in 2025. To validate that your application is connected to the correct network, query the chain ID and current block number through a peaq mainnet RPC. This confirms RPC connectivity; it does not by itself provide an indexed history of launch events.
Choose a peaq mainnet RPC endpoint
Open the peaq network page and copy an RPC endpoint listed for the peaq mainnet. Store it in the RPC_URL environment variable rather than embedding an endpoint in application code.
An RPC endpoint is a request-response interface to a node. It lets your program submit JSON-RPC methods such as eth_chainId and eth_blockNumber, but it is not automatically an indexed query service.
- Use a peaq mainnet endpoint, not a testnet endpoint.
- Do not treat the latest block number as evidence of the launch date; block height changes continuously.
export RPC_URL='PASTE_THE_PEAQ_MAINNET_RPC_URL_HERE'
node --versionExpected result: Node.js prints version 18 or newer. Keep the RPC_URL value private if the endpoint includes credentials.
Run a Node.js 18+ network check
The following script sends two JSON-RPC requests, checks that the response is valid, and rejects a connection to a different EVM network. The expected peaq mainnet chain ID is 3338 decimal, represented as 0xd0a in hexadecimal.
- A successful response confirms that the endpoint is reachable and identifies itself as peaq mainnet.
- The block number is intentionally reported as a live value rather than a fabricated measurement.
const rpcUrl = process.env.RPC_URL;
if (!rpcUrl || rpcUrl.includes('PASTE_THE_')) {
throw new Error('Set RPC_URL to a peaq mainnet RPC endpoint before running this script.');
}
async function rpc(method, params = []) {
const response = await fetch(rpcUrl, {
method: 'POST',
headers: { 'content-type': 'application/json' },
body: JSON.stringify({ jsonrpc: '2.0', id: 1, method, params }),
signal: AbortSignal.timeout(10000)
});
if (!response.ok) {
throw new Error(`RPC returned HTTP ${response.status}`);
}
const body = await response.json();
if (body.error) {
throw new Error(`RPC error ${body.error.code}: ${body.error.message}`);
}
if (body.result === undefined) {
throw new Error('RPC response did not contain a result');
}
return body.result;
}
try {
const [chainId, blockNumber] = await Promise.all([
rpc('eth_chainId'),
rpc('eth_blockNumber')
]);
if (chainId.toLowerCase() !== '0xd0a') {
throw new Error(`Unexpected chain ID ${chainId}; expected peaq mainnet 0xd0a`);
}
console.log(JSON.stringify({ network: 'peaq mainnet', chainId, blockNumber }, null, 2));
} catch (error) {
console.error(`Network check failed: ${error.message}`);
process.exitCode = 1;
}Expected result: a JSON object containing network set to peaq mainnet, chainId set to 0xd0a, and a current blockNumber supplied by the RPC.
Failure handling covers a missing URL, timeout or connection failure, non-2xx HTTP responses, JSON-RPC errors, malformed responses, and an endpoint connected to the wrong chain.
Know what the check proves
The check proves that your application can reach an RPC endpoint and that the endpoint reports the peaq mainnet chain ID. It does not prove when the network launched, nor does it provide a searchable table of all historical transfers, contracts, or application entities.
RPC methods expose node data one request at a time. Indexing pipelines consume blockchain data, transform it into a queryable model, and commonly support application-specific historical queries. Choose an indexer when your task requires repeatable queries across many blocks or relationships between decoded entities.
- Use RPC for submitting transactions, reading contract state, and retrieving individual blocks or logs.
- Use indexed data for application APIs, historical aggregation, and queries that span large ranges.
- If you need to independently investigate launch activity, define the block range and event signatures first, then query the relevant blocks or indexed data instead of inferring a date from the current height.
Choose the next implementation step
For more practical guidance on connecting applications to blockchain networks and deciding between direct RPC calls and indexed data, continue with OnFinality Learn.
If you still need to identify a suitable RPC configuration for your peaq application, use the RPC Assistant after confirming the network and access requirements.
- Keep the network check in CI or deployment diagnostics so configuration mistakes fail early.
- Measure latency, error rates, and rate-limit behavior in your own environment if those values matter to your application; do not assume them from the chain ID check.