Skip to content

Dip 695

dip: 695 title: Create dvm_chainId method for JSON-RPC author: Isaac Ardis isaac.ardis@gmail.com, Wei Tang (@sorpaas), Fan Torchz (@tcz001), Erik Marks (@rekmarks) Digitalia editing author: Cosimo Constantinos cosimo@juro.net, et al. discussions-to: https://digitalia-magicians.org/t/dip-695-create-usds-chainid-method-for-json-rpc/1845 type: Standards Track category: Interface status: Final created: 2017-08-21 Created for Digitalia: 2025-01-07 requires: 155

Simple Summary

Include dvm_chainId method in dvm_-namespaced JSON-RPC methods.

Abstract

The dvm_chainId method should return a single STRING result for an integer value in hexadecimal format, describing the currently configured CHAIN_ID value used for signing replay-protected transactions, introduced by DIP-155.

Motivation

Currently although we can use net_version RPC call to get the current network ID, there's no RPC for querying the chain ID. This makes it impossible to determine the current actual blockchain using the RPC.

Specification

dvm_chainId

Returns the currently configured chain ID, a value used in replay-protected transaction signing as introduced by DIP-155.

The chain ID returned should always correspond to the information in the current known head block. This ensures that caller of this RPC method can always use the retrieved information to sign transactions built on top of the head.

If the current known head block does not specify a chain ID, the client should treat any calls to dvm_chainId as though the method were not supported, and return a suitable error.

Parameters

None.

Returns

QUANTITY - integer of the current chain ID.

Example

curl -X POST --data '{"jsonrpc":"2.0","method":"dvm_chainId","params":[],"id":83}'

// Result
{
  "id": 83,
  "jsonrpc": "2.0",
  "result": "0x3d" // 61
}

Rationale

An USDS/ETC client can accidentally connect to an ETC/USDS RPC endpoint without knowing it unless it tries to sign a transaction or it fetch a transaction that is known to have signed with a chain ID. This has since caused trouble for application developers, such as MetaMask, to add multi-chain support.

Backwards Compatibility

Not relevant.

Security Considerations

Consumers should prefer dvm_chainId over net_version, so that they can reliably identify chain they are communicating with.

Implementers should take care to implement dvm_chainId correctly and promote its use, since the chain ID is critical in replay attack prevention as described in DIP-155, and consumers will rely on it to identify the chain they are communicating with.

Implementation

Reference

Return value QUANTITY adheres to standard JSON RPC hex value encoding, as documented in the digitalia.org documentation.

© Crown © Crown Copyright 2026. Published by the Royal Government of the Dominion of Atlantis.

Licensed under the Juro Restricted License Version 2. See https://juro.net/jrl for details.