feature
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 hasname(may be omitted),enabled(whether the amendment is currently enabled in the latest ledger) andsupported(whether the server knows how to apply it).ledger_hash,ledger_index,validatedThe ledger version the amendment status was read from.
// Result
{
"result": {
"features": {
"00C1FC4A53E60AB02C864641002B3172F38677E29C26C5406685179B37E1EDAC": {
"name": "RequireFullyCanonicalSig",
"enabled": true,
"supported": true
},
"0285B7E5E08E1A8E4C15636F0591D87F73CB6A7B6452A932AD72BBC8E5D1CBE3": {
"name": "fixNFTokenDirV1",
"enabled": false,
"supported": false
},
// ...
},
"ledger_hash": "3FF4EFB0A896061499DCE559C21A44563F74C040226019033B06BA6FC383B450",
"ledger_index": 107292935,
"validated": true,
"status": "success"
}
}Over WebSocket, send {"id":1,"command":"feature"} to wss://mainnet.xrpl.validationcloud.io/v1/<YOUR_API_KEY_HERE>.
Without a
featurefilter the full response lists every amendment (roughly 15 KB). The example above is trimmed to the first two entries.
Last updated
Was this helpful?