mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-12-02 01:25:50 +00:00
Merge pull request #1088 from crypticrabbit/master
Clarify that issuing `feature` via the commandline requires 'accept' or 'reject' booleans.
This commit is contained in:
@@ -68,7 +68,7 @@ The request includes the following parameters:
|
||||
| `Field` | Type | Description |
|
||||
|:----------|:--------|:-------------------------------------------------------|
|
||||
| `feature` | String | _(Optional)_ The unique ID of an amendment, as hexadecimal; or the short name of the amendment. If provided, limits the response to one amendment. Otherwise, the response lists all amendments. |
|
||||
| `vetoed` | Boolean | (Optional; ignored unless `feature` also specified) If true, instructs the server to vote against the amendment specified by `feature`. If false, instructs the server to vote in favor of the amendment. |
|
||||
| `vetoed` | Boolean | (Optional; ignored unless `feature` also specified) If true, instructs the server to vote against the amendment specified by `feature`. If false, instructs the server to vote in favor of the amendment. On the commandline, use 'accept' or 'reject rather than 'true' or 'false'. |
|
||||
|
||||
**Note:** You can configure your server to vote in favor of a new amendment, even if the server does not currently know how to apply that amendment, by specifying the amendment ID in the `feature` field. For example, you might want to do this if you plan to upgrade soon to a new `rippled` version that _does_ support the amendment.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user