Skip to main content
Returns information about amendments the server knows about, including whether they are enabled on the ledger and whether the server knows how to apply them. This method will use 20 Compute Units.

Reference: Here

Parameters

  • 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.

Returns

  • features (object) A map of amendment IDs to amendment objects. Each amendment object has name (may be omitted), enabled (whether the amendment is currently enabled in the latest ledger) and supported (whether the server knows how to apply it).
  • ledger_hash, ledger_index, validated The ledger version the amendment status was read from.
Over WebSocket, send {"id":1,"command":"feature"} to wss://mainnet.xrpl.validationcloud.io/v1/<YOUR_API_KEY_HERE>.
Without a feature filter the full response lists every amendment (roughly 15 KB). The example above is trimmed to the first two entries.