# getVersion

> Returns the software version and feature set of the node that answers the request.

Source: https://docs.constant-k.com/rpc/http/getversion/

`getVersion` reports the client version (`solana-core`) and a numeric `feature-set` identifier for the node that served the call. `feature-set` is a hash of the runtime features compiled into that build, letting clients detect compatible nodes without comparing version strings.

It confirms which client line a provider runs (Agave, Jito-Solana, Firedancer) and whether a fleet-wide upgrade has finished; every node reports the same `feature-set` once it has.

- Transport: HTTP, JSON-RPC 2.0 `POST` to `https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY` (New York) or `https://rpc-frankfurt.constant-k.com/?api-key=YOUR_API_KEY` (Frankfurt) or `https://rpc-amsterdam.constant-k.com/?api-key=YOUR_API_KEY` (Amsterdam). The key also works as an `x-api-key` header.
- Category: Network & Cluster
- Availability: All plans
- Rate limits: Free 5/s · Operator 50/s · Blade Runner 200/s · Nexus 500/s

## Parameters

None.

## Result

- `result` (object, optional): An object describing the responding node's client build.
  - `solana-core` (string, required): Client version string, e.g. `4.3.0-rc.0`.
  - `feature-set` (integer | null, optional): 32-bit identifier computed from the runtime features this build supports. Nodes must share a `feature-set` to be considered version-compatible for consensus purposes.

## Example: Get node version

Request:

```bash
curl "https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "getVersion" }'
```

Response:

```json
{
  "jsonrpc": "2.0",
  "result": {
    "feature-set": 2409014235,
    "solana-core": "4.3.0-rc.0"
  },
  "id": 1
}
```

## Notes

- constant-k runs a current Agave/Jito build tracking the 4.x release line; expect `solana-core` and `feature-set` to change whenever the fleet upgrades.
- Different requests can land on different backend nodes behind the same endpoint, so a rolling upgrade can briefly show two different `feature-set` values.