# Configure Amendment Voting

Servers configured as validators can vote on [amendments](/es-es/docs/concepts/networks-and-servers/amendments) to the XRP Ledger protocol using the [feature method](/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature). (This method requires [admin access](/es-es/docs/tutorials/http-websocket-apis/build-apps/get-started#admin-access).)

For example, to vote against the "SHAMapV2" amendment, run the following command:

WebSocket

```json
{
  "id": "any_id_here",
  "command": "feature",
  "feature": "SHAMapV2",
  "vetoed": true
}
```

JSON-RPC

```json
{
    "method": "feature",
    "params": [
        {
            "feature": "SHAMapV2",
            "vetoed": true
        }
    ]
}
```

Commandline

```sh
rippled feature SHAMapV2 reject
```

The short name of the amendment is case-sensitive. You can also use an amendment's ID as hexadecimal, which is not case sensitive.

## Using the Config File

If you prefer to use the config file to configure amendment voting, you can add a line to the `[rpc_startup]` stanza to run the command automatically on startup for each explicit vote. For example:


```
[rpc_startup]
{ "command": "feature", "feature": "SHAMapV2", "vetoed": true }
```

Be sure to restart your server for changes to take effect.

Any commands in the `[rpc_startup]` stanza run each time the server starts up, which can override voting settings you configured while the server was running.

## See Also

- [Amendments](/es-es/docs/concepts/networks-and-servers/amendments)
  - [Known Amendments](/resources/known-amendments)
- [feature method](/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature)