", "Adrian Wrona "]>" />

Casper Chains

Author , "Adrian Wrona
Discussions-To https://github.com/ChainAgnostic/namespaces/pull/100
Status Draft
Type Standard
Created 2024-01-12
Requires CAIP-2


For context, see the CAIP-2 specification.


The Chain ID is a human-readable identifier for a Casper network blockchain. It should not be confused with the genesis_hash, which is the true and unique identifier of a chain.


It consists of the prefix casper: followed by the chainspec name of that network. Such name is a string that permits to easily identify the network and protect from replay attacks.

Resolution Method

To resolve the chainspec name for a given Casper network chain, send an RPC request with method info_get_status to a Casper node in that network. The result object in the RPC response will contain the property chainspec_name containing the chainspec name corresponding to that network.

For example:

// Command
curl --request POST \
  --header "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0", "id": 1, "method":"info_get_status", "params":{}}' \ | jq .result.chainspec_name

// Result

Append the prefix "casper:" to form the Chain Id for that chain. In the example above: casper:casper-test.

Test Cases

This is a list of manually composed Chain Id examples

# Casper Mainnet

# Casper Testnet

For testing purposes, the Casper Association maintains the following RPC endpoints:

  • Casper Mainnet:
  • Testnet:


Copyright and related rights waived via CC0.


Please cite this document as:

, "Adrian Wrona, "namespaces/casper-caip2: Casper Chains [DRAFT]," Chain Agnostic Namespaces, casper-caip2, January 2024 / . [Online serial]. Available: https://github.com/ChainAgnostic/namespaces/casper-caip2.md