2.0 KiB
html, parent, seo, labels
| html | parent | seo | labels | ||||
|---|---|---|---|---|---|---|---|
| configure-amendment-voting.html | configure-rippled.html |
|
|
Configure Amendment Voting
Servers configured as validators can vote on amendments to the XRP Ledger protocol using the [feature method][]. (This method requires admin access.)
For example, to vote against the "SHAMapV2" amendment, run the following command:
{% tabs %}
{% tab label="WebSocket" %}
{
"id": "any_id_here",
"command": "feature",
"feature": "SHAMapV2",
"vetoed": true
}
{% /tab %}
{% tab label="JSON-RPC" %}
{
"method": "feature",
"params": [
{
"feature": "SHAMapV2",
"vetoed": true
}
]
}
{% /tab %}
{% tab label="Commandline" %}
rippled feature SHAMapV2 reject
{% /tab %}
{% /tabs %}
{% admonition type="info" name="Note" %}The short name of the amendment is case-sensitive. You can also use an amendment's ID as hexadecimal, which is not case sensitive.{% /admonition %}
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.
{% admonition type="warning" name="Caution" %}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.{% /admonition %}
See Also
- Amendments
- [feature method][]
{% raw-partial file="/docs/_snippets/common-links.md" /%}