feature
The feature
command returns information about amendments this server knows about, including whether they are enabled and whether the server is voting in favor of those amendments in the amendment process.
You can use the feature
command to configure the server to vote against or in favor of an amendment. This change persists even if you restart the server.
The feature
method is an admin method that cannot be run by unprivileged users.
Request Format
An example of the request format:
{ "id": "list_all_features", "command": "feature" }
The request includes the following parameters:
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.
Response Format
An example of a successful response:
{ "id": "list_all_features", "status": "success", "type": "response", "result": { "features": { "42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE": { "enabled": false, "name": "FeeEscalation", "supported": true, "vetoed": false }, "4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373": { "enabled": false, "name": "MultiSign", "supported": true, "vetoed": false }, "6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC": { "enabled": false, "name": "TrustSetAuth", "supported": true, "vetoed": false }, "C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490": { "enabled": false, "name": "Tickets", "supported": true, "vetoed": false }, "DA1BD556B42D85EA9C84066D028D355B52416734D3283F85E216EA5DA6DB7E13": { "enabled": false, "name": "SusPay", "supported": true, "vetoed": false } } } }
The response follows the standard format, with a successful result containing a map of amendments as a JSON object. The keys of the object are amendment IDs. The values for each key are amendment objects that describe the status of the amendment with that ID. If the request specified a feature
, the map contains only the requested amendment object, after applying any changes from the request. Each amendment object has the following fields:
Field | Type | Description |
---|---|---|
enabled | Boolean | Whether this amendment is currently enabled in the latest ledger. |
name | String | (May be omitted) The human-readable name for this amendment, if known. |
supported | Boolean | Whether the server knows how to apply this amendment. If this field is set to false (the server does not know how to apply this amendment) and enabled is set to true (this amendment is enabled in the latest ledger), this amendment may cause your server to be amendment blocked. |
vetoed | Boolean or String | For most amendments, this is a boolean value indicating whether the server has been instructed to vote against this amendment. For amendments that are marked as obsolete in the code, this is the string Obsolete instead. |
Caution: The name
for an amendment does not strictly indicate what that amendment does. The name is not guaranteed to be unique or consistent across servers.
Possible Errors
- Any of the universal error types.
badFeature
- Thefeature
specified was invalidly formatted, or the server does not know an amendment with that name.reportingUnsupported
- (Reporting Mode servers only) This method is not available in Reporting Mode.