noripple_check
The noripple_check
command provides a quick way to check the status of the Default Ripple field for an account and the No Ripple flag of its trust lines, compared with the recommended settings.
Request Format
An example of the request format:
The request includes the following parameters:
Field
Type
Description
account
String
A unique identifier for the account, most commonly the account's address.
role
String
Whether the address refers to a gateway
or user
. Recommendations depend on the role of the account. Issuers must have Default Ripple enabled and must disable No Ripple on all trust lines. Users should have Default Ripple disabled, and should enable No Ripple on all trust lines.
transactions
Boolean
[API v1][]: (Optional) If true
, include an array of suggested transactions, as JSON objects, that you can sign and submit to fix the problems. The default is false
.
[API v2][]: Identical to v1, but also returns an invalidParams
error if you use a non-boolean value.
limit
Unsigned Integer
(Optional) The maximum number of trust line problems to include in the results. Defaults to 300.
ledger_hash
String
(Optional) A 20-byte hex string for the ledger version to use. (See [Specifying Ledgers][])
ledger_index
String or Unsigned Integer
(Optional) The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][])
Response Format
An example of a successful response:
The response follows the [standard format][], with a successful result containing the following fields:
Field
Type
Description
ledger_current_index
Number
The [ledger index][] of the ledger used to calculate these results.
problems
Array
Array of strings with human-readable descriptions of the problems. This includes up to one entry if the account's Default Ripple setting is not as recommended, plus up to limit
entries for trust lines whose No Ripple setting is not as recommended.
transactions
Array
(May be omitted) If the request specified transactions
as true
, this is an array of JSON objects, each of which is the JSON form of a transaction that should fix one of the described problems. The length of this array is the same as the problems
array, and each entry is intended to fix the problem described at the same index into that array.
Possible Errors
Any of the [universal error types][].
invalidParams
- One or more fields are specified incorrectly, or one or more required fields are missing.actNotFound
- The [Address][] specified in theaccount
field of the request does not correspond to an account in the ledger.lgrNotFound
- The ledger specified by theledger_hash
orledger_index
does not exist, or it does exist but the server does not have it.
Last updated