CURRENT RESULT
Checking
Loading the latest comparison evidence.
VERIFICATION
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
Loading the latest comparison evidence.
EVIDENCE
——EVM endpoint availability, data freshness and native chain integrity are reported as separate conditions.
Generated at 2026-07-31T14:36:31.084186Z.
The endpoint responded successfully during preview generation.
Validated through eth_chainId.
Read through eth_blockNumber at the recorded update time.
This describes the EVM endpoint only, not native-chain agreement.
Independent multi-node comparison remains required.
Unverified third-party explorers are excluded as chain references.
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.
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.
Public RMS services with explicit source boundaries and visible service states.
Claim scope: EVM_JSON_RPC_ONLY. A responsive EVM endpoint is not proof of canonical native-chain agreement or complete native-node synchronization.
Current non-production service catalogue.
HTTP transport responded for 5/5 probes. 4/5 JSON-RPC methods returned usable results. Live EVM block height: 16,094,065.
Degraded →Dedicated wallet route; not used as native-chain verification.
Published →Non-production explorer interface from the current RMS stage.
Preview →Separates endpoint availability from native-chain integrity.
Preview →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.
BlockDAGScan is listed solely as an external technical comparison point. RMS node comparisons indicate that it tracks a different chain branch than the verified RMS and community nodes. It must not be used as a reference for canonical block height, block hashes, synchronization status, chain validation, or node integrity checks.