> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.chainstack.com/feedback

```json
{
  "path": "/reference/getconfigspec",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Node configuration

The `/eth/v1/config/spec` method is designed to provide a comprehensive overview of the current specification parameters of the Ethereum Beacon Chain. These parameters define the core rules and configurations that govern the behavior and operations of the network. Access to these specifications is crucial for developers and network participants for aligning their operations and understanding the fundamental mechanisms of the Beacon Chain.

Utilizing this method enables developers and network operators to ensure that their systems and applications are compliant with the current specifications of the Ethereum Beacon Chain, thereby maintaining compatibility and optimal performance.

<Check>
  **Get your own node endpoint today**

  [Start for free](https://console.chainstack.com/) and get your app to production levels immediately. No credit card required.

  You can sign up with your GitHub, X, Google, or Microsoft account.
</Check>

## Parameters

* `none`

## Response

* `object` — specification information.
  * `spec_version` — the version of the current Ethereum Beacon Chain specification. This helps clients and developers identify the set of rules and protocols they need to adhere to.
  * `constants` — a collection of the key constants used in the network's operation, such as the max number of validators, shard count, and other critical numerical values that define the network's structure and limits.
  * `preset_base` — indicates the base preset of the specifications, providing a foundational configuration upon which the network operates.
  * `config_name` — the name of the active configuration, which can be indicative of the network's operational phase or specific updates it has undergone.
  * `forks` — a list of all forks (both past and planned) included in the current specification, providing insight into the network's evolutionary path and future trajectory.

By providing detailed information about the specifications of the Ethereum Beacon Chain, the `/eth/v1/config/spec` method serves as an essential tool for anyone looking to interact with the network effectively and with full awareness of its operational guidelines.


## OpenAPI

````yaml /openapi/ethereum_beacon_chain_api/configuration_info/node_config.json GET /config/spec
openapi: 3.0.0
info:
  title: Ethereum Config Spec API
  version: 1.0.0
servers:
  - url: >-
      https://beacon-nd-422-757-666.p2pify.com/0a9d79d93fb2f4a4b1e04695da2b77a7/eth/v1
security: []
paths:
  /config/spec:
    get:
      summary: Node configuration
      operationId: getConfigSpec
      responses:
        '200':
          description: Specification configuration successfully retrieved
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SpecConfig'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    SpecConfig:
      type: object
      additionalProperties:
        type: string
    Error:
      type: object
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
      required:
        - code
        - message

````