peaq RPC node for machine economy apps

Yes. peaq runs an EVM alongside its Substrate runtime, so Solidity contracts, EVM wallets, and standard Ethereum JSON-RPC methods work as they do on other EVM chains. It supports the Cancun opcode set. As a Polkadot parachain, peaq also exposes Substrate RPC for native runtime data, and precompiles let Solidity contracts call its DID, storage, and access-control modules directly.

GetBlock provides managed peaq mainnet RPC endpoints over HTTPS and WebSocket, so teams don't need to sync, upgrade, or monitor their own parachain node. peaq is available on paid shared plans billed by compute units and as dedicated nodes with isolated resources for production workloads. Endpoints are served from regional data centers, and GetBlock's infrastructure is SOC 2 Type II attested, with a 99.99% uptime SLA on dedicated nodes.

Any EVM-compatible wallet, such as MetaMask, can connect to peaq by adding it as a custom network with Chain ID 3338 and PEAQ as the native currency. Standard EVM libraries and frameworks, including ethers.js, viem, web3.py, Hardhat, and Foundry, work against a peaq RPC URL without changes. peaq also provides its own JavaScript and Python SDKs for machine identity and peaqOS functionality.

peaq RPC nodes return blocks, transactions, receipts, PEAQ account balances, event logs, and smart contract state through EVM JSON-RPC methods. Through the Substrate interface, they also expose runtime storage, extrinsics, and finalized block data. This covers DePIN dashboards, on-chain analytics, and applications that read machine-related contracts.

To connect through GetBlock: generate an access token in the dashboard and get your HTTPS and WSS RPC URLs. To add peaq to MetaMask or another EVM wallet, enter the network name "peaq", your GetBlock RPC URL, Chain ID 3338, and currency symbol PEAQ. In Hardhat or Foundry, use the same RPC URL.

peaq supports EVM RPC methods such as eth_chainId, eth_blockNumber, eth_getBalance, eth_call, and eth_sendRawTransaction. Its underlying Substrate interface also provides methods such as chain_getFinalizedHead to retrieve the latest finalized block, state_getStorage to read runtime storage, and author_submitExtrinsic to submit native Substrate transactions.

Yes. peaq supports WebSocket subscriptions through eth_subscribe, which delivers new block headers, contract logs, and pending-transaction hashes as they happen. Substrate's chain_subscribeNewHeads provides the same for native block headers. For HTTP-only setups, eth_newFilter with eth_getFilterChanges offers polling-based event tracking.

peaq mainnet uses EVM Chain ID 3338, also represented as 0xD0A. The agung testnet uses EVM Chain ID 9990, or 0x2706. These identifiers are used by EVM wallets and libraries to configure a network and sign transactions for the correct chain. The EVM Chain ID is distinct from the parachain identifier used within the Polkadot ecosystem.