The changes in this commit were auto-generated by running tool/migrate.sh Following this commit, the Dactyl build no longer works but the Redocly build (mostly) should.
1.9 KiB
html, parent, blurb, labels
| html | parent | blurb | labels | ||
|---|---|---|---|---|---|
| configure-amendment-voting.html | configure-rippled.html | Set your server's votes on protocol amendments. |
|
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 %}
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.
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.
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.
See Also
- Amendments
- [feature method][]
{% raw-partial file="/_snippets/common-links.md" /%}