Pharos RPC for real-world finance

Yes. Pharos Network positions itself as a RealFi Layer 1 that brings tokenized real-world assets, payments, and financial workflows onchain. Unlike most EVM chains, which parallelize only transaction execution, Pharos parallelizes consensus, execution, and storage through leaderless BFT consensus, the DTVM dual-VM runtime, and Pharos Store. Special Processing Networks (SPNs) add application-specific environments secured by native restaking, and the roadmap extends to AI agents that hold and move assets onchain.

GetBlock provides managed access to Pharos mainnet through full-node endpoints over JSON-RPC and WebSocket. You get an endpoint with a private access token from the GetBlock dashboard, without syncing or maintaining a node. Teams with heavier workloads can request Dedicated Pharos nodes.

Pharos is EVM-equivalent, so standard EVM wallets such as MetaMask connect once you add the network with chain ID 1672 and PROS as the currency. Common Ethereum libraries, including ethers.js, viem, and web3.py, work against a Pharos endpoint unchanged. Foundry and Hardhat cover contract development and deployment, and Rust is supported for WASM contracts that run on DTVM.

Pharos RPC nodes return account balances, nonces, contract code, and storage values, along with full block and transaction data and receipts. They support log queries for contract events, gas and fee history for EIP-1559 pricing, and Merkle proofs through eth_getProof for state verification. Pharos also adds eth_getAccount, which returns an account's balance, nonce, code hash, and storage root in a single call.

Create a Pharos mainnet endpoint in the GetBlock dashboard and copy the URL. Point your EVM library or tooling at that URL and set chain ID 1672 with PROS as the native currency. For real-time subscriptions, create a WebSocket endpoint in the same dashboard.

Pharos supports the standard Ethereum namespaces, so eth_blockNumber, eth_getBalance, eth_call, eth_estimateGas, eth_getLogs, and eth_sendRawTransaction behave as on other EVM chains. Pharos adds eth_getAccount as an extension method, and its eth_getProof response uses a Pharos-specific proof format suited to SPV verification. Trace methods such as debug_traceTransaction currently support only the callTracer tracer.

Yes. Pharos supports WebSocket subscriptions through eth_subscribe and eth_unsubscribe, with newHeads for new blocks and logs for contract events. Subscriptions work only over WebSocket connections, not HTTP. Pending-transaction subscriptions are not listed in Pharos's RPC documentation.

Pharos Pacific Mainnet uses chain ID 1672, which is 0x688 in hexadecimal as returned by eth_chainId. The Atlantic Testnet uses chain ID 688689. GetBlock currently serves Pharos mainnet, so configure 1672 when connecting through a GetBlock endpoint.