ChainPulseIndependent BlockDAG infrastructure

VERIFICATION

Chain comparison against BlockDAG Engineering.

RMS compares safety-lagged EVM block hashes with explorer.blockdag.engineering. The result is deliberately scoped: matching EVM evidence does not by itself prove native DAG consensus.

CURRENT RESULT

Checking

Loading the latest comparison evidence.

RMS chain ID—Expected: 1404
Reference chain ID—BlockDAG Engineering
Sample height—Safety-lagged comparison
Hash result—EVM block hash

EVIDENCE

Latest sampled block

RMS block hash
—
Engineering block hash
—
Last checked
—
Claim scope
EVM block-hash comparison against BlockDAG Engineering
Native DAG status
Not derived from EVM-only evidence
Existing network information
RMS Network Monitoring

Service state without overstating verification

EVM endpoint availability, data freshness and native chain integrity are reported as separate conditions.

← Back

Current status model

Generated at 2026-07-31T14:36:31.084186Z.

Public EVM RPC
Online

The endpoint responded successfully during preview generation.

Chain ID
1404

Validated through eth_chainId.

Displayed EVM height
16,088,625

Read through eth_blockNumber at the recorded update time.

EVM RPC synchronization
Responding

This describes the EVM endpoint only, not native-chain agreement.

Native-chain integrity
Not verified

Independent multi-node comparison remains required.

Reference policy
Independent sources

Unverified third-party explorers are excluded as chain references.

CHAIN_NOT_VERIFIED

The public RPC is operational, but this alone does not prove that Node 1, Node 2 and Node 3 agree on the native BlockDAG chain. No complete-chain comparison status claim is made by this preview.

Verification scope

Claim scope: EVM_JSON_RPC_ONLY

Native-chain integrity: CHAIN_NOT_VERIFIED

Public endpoint availability and EVM JSON-RPC responses do not prove canonical native-chain agreement or complete native-node synchronization.

Independent community infrastructure

Community Network

Public RMS services with explicit source boundaries and visible service states.

← Back

Native-chain integrity: CHAIN_NOT_VERIFIED

Claim scope: EVM_JSON_RPC_ONLY. A responsive EVM endpoint is not proof of canonical native-chain agreement or complete native-node synchronization.

Community services

Current non-production service catalogue.

01

Public EVM JSON-RPC

HTTP transport responded for 5/5 probes. 4/5 JSON-RPC methods returned usable results. Live EVM block height: 16,094,065.

Degraded →
02

Wallet EVM RPC

Dedicated wallet route; not used as native-chain verification.

Published →
03

RMS Explorer

Non-production explorer interface from the current RMS stage.

Preview →
04

RMS Network

Separates endpoint availability from native-chain integrity.

Preview →

Verification policy

Values require a source and timestamp. Endpoint availability, data freshness and native-chain integrity are separate claims. Unverified third-party explorers are not used as chain references.