Merge pull request #1976 from XRPLF/rippled_1.11.0

rippled 1.11.0 changes

assets/js/apitool-methods-ws.js

@@ -22,7 +22,6 @@ Request('account_currencies', {
  body: {
  "command": "account_currencies",
  "account": DEFAULT_ADDRESS_1,
- "strict": true,
  "ledger_index": "validated"
  }
 })
@@ -34,7 +33,6 @@ Request('account_info', {
  "id": 2,
  "command": "account_info",
  "account": DEFAULT_ADDRESS_1,
- "strict": true,
  "ledger_index": "current",
  "queue": true
  }
@@ -106,7 +104,6 @@ Request('gateway_balances', {
  "id": "example_gateway_balances_1",
  "command": "gateway_balances",
  "account": "rMwjYedjc7qqtKYVLiAccJSmCwih4LnE2q", // btc2ripple
- "strict": true,
  "hotwallet": [
  "rKm4uWpg9tfwbVSeATv4KxDe6mpE9yPkgJ",
  "ra7JkEzrgeKHdzKgo4EUUVBnxggY4z37kt"

content/_snippets/rippled-api-links.md

@@ -216,6 +216,7 @@
  "fixCheckThreading",
  "fixMasterKeyAsRegularKey",
  "fixNFTokenDirV1",
+ "fixNFTokenRemint",
  "fixPayChanRecipientOwnerDir",
  "fixRemoveNFTokenAutoTrustLine",
  "fixQualityUpperBound",

content/_snippets/rippled_versions.md

@@ -42,6 +42,7 @@
  "1.7.2",
  "1.8.1",
  "1.10.0",
+ "1.11.0",
 ] %}
 
 {% for v in rippled_versions %}

content/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md

@@ -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. On the commandline, use 'accept' or 'reject rather than 'true' or 'false'. |
+| `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'. You cannot vote in favor of an amendment that is marked as _obsolete_ in the server's source code. [Updated in: rippled 1.11.0][] |
 
 **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.
 
@@ -188,7 +188,7 @@ The response follows the [standard format][], with a successful result containin
 | `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](amendments.html#amendment-blocked-servers). |
-| `vetoed` | Boolean | Whether the server has been instructed to vote against this amendment. |
+| `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. [Updated in: rippled 1.11.0][] |
 
 **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.
 

content/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md

@@ -55,14 +55,14 @@ rippled account_channels rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn ra5nK24KXen9AHvsdFTK
 
 The request includes the following parameters:
 
-| Field | Type  | Description  |
-|:----------------------|:---------------------------|:------------------------|
-| `account` | String    | The unique identifier of an account, typically the account's [Address][]. The request returns channels where this account is the channel's owner/source. |
-| `destination_account` | String    | _(Optional)_ The unique identifier of an account, typically the account's [Address][]. If provided, filter results to payment channels whose destination is this account. |
-| `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][]) |
-| `limit` | Integer   | _(Optional)_ Limit the number of transactions to retrieve. Cannot be less than 10 or more than 400. The default is 200. |
-| `marker` | [Marker][]   | _(Optional)_ Value from a previous paginated response. Resume retrieving data where that response left off. [Updated in: rippled 1.5.0][] |
+| Field | Type | Required? | Description |
+|:----------------------|:---------------------|:----------|-------------|
+| `account` | String - [Address][] | Yes | Look up channels where this account is the channel's owner/source. |
+| `destination_account` | String - [Address][] | No | A second account; if provided, filter results to payment channels whose destination is this account. |
+| `ledger_hash` | String | No  | A 20-byte hex string for the ledger version to use. (See [Specifying Ledgers][]) |
+| `ledger_index` | Number or String | No | The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) |
+| `limit` | Number | No  | Limit the number of transactions to retrieve. Cannot be less than 10 or more than 400. The default is 200. |
+| `marker` | [Marker][] | No  | Value from a previous paginated response. Resume retrieving data where that response left off. |
 
 ## Response Format
 

content/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md

@@ -21,7 +21,6 @@ An example of the request format:
 {
  "command": "account_currencies",
  "account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
- "strict": true,
  "ledger_index": "validated"
 }
 ```
@@ -35,8 +34,7 @@ An example of the request format:
  {
  "account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
  "account_index": 0,
- "ledger_index": "validated",
- "strict": true
+ "ledger_index": "validated"
  }
  ]
 }
@@ -45,8 +43,8 @@ An example of the request format:
 *Commandline*
 
 ```sh
-#Syntax: account_currencies account [ledger_index|ledger_hash] [strict]
-rippled account_currencies rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn validated strict
+#Syntax: account_currencies account [ledger_index|ledger_hash]
+rippled account_currencies rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn validated
 ```
 
 <!-- MULTICODE_BLOCK_END -->
@@ -55,14 +53,13 @@ rippled account_currencies rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn validated strict
 
 The request includes the following parameters:
 
-| `Field` | Type | Description |
-|:---------------|:---------------------------|:-------------------------------|
-| `account` | String | A unique identifier for the account, most commonly the account's [Address][]. |
-| `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][]) |
-| `strict` | Boolean | _(Optional)_ If `true`, then the `account` field only accepts a public key or XRP Ledger address. Otherwise, `account` can be a secret or passphrase (not recommended). The default is `false`. |
+| `Field` | Type | Required? | Description |
+|:---------------|:---------------------|:----------|-------------|
+| `account` | String - [Address][] | Yes | Look up currencies this account can send or receive. [Updated in: rippled 1.11.0][] |
+| `ledger_hash` | String | No | A 20-byte hex string for the ledger version to use. (See [Specifying Ledgers][]) |
+| `ledger_index` | Number or String | No | The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) |
 
-The following field is deprecated and should not be provided: `account_index`.
+The following fields are deprecated and should not be provided: `account_index`, `strict`.
 
 ## Response Format
 
@@ -178,3 +175,4 @@ The response follows the [standard format][], with a successful result containin
 
 
 {% include '_snippets/rippled-api-links.md' %}
+{% include '_snippets/rippled_versions.md' %}

content/references/http-websocket-apis/public-api-methods/account-methods/account_info.md

@@ -24,7 +24,6 @@ An example of an account_info request:
  "id": 2,
  "command": "account_info",
  "account": "rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn",
- "strict": true,
  "ledger_index": "current",
  "queue": true
 }
@@ -38,7 +37,6 @@ An example of an account_info request:
  "params": [
  {
  "account": "rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn",
- "strict": true,
  "ledger_index": "current",
  "queue": true
  }
@@ -49,8 +47,8 @@ An example of an account_info request:
 *Commandline*
 
 ```sh
-#Syntax: account_info account [ledger_index|ledger_hash] [strict]
-rippled account_info rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn validated strict
+#Syntax: account_info account [ledger_index|ledger_hash]
+rippled account_info rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn validated
 ```
 
 <!-- MULTICODE_BLOCK_END -->
@@ -59,16 +57,15 @@ rippled account_info rG1QQv2nh2gr7RCZ1P8YYcBUKCCN633jCn validated strict
 
 The request contains the following parameters:
 
-| `Field` | Type | Description |
-|:---------------|:---------------------------|:-------------------------------|
-| `account` | String | A unique identifier for the account, most commonly the account's [Address][]. |
-| `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][]) |
-| `queue` | Boolean | _(Optional)_ If `true`, and the [FeeEscalation amendment][] is enabled, also returns stats about queued transactions associated with this account. Can only be used when querying for the data from the current open ledger. [New in: rippled 0.33.0][] Not available from servers in [Reporting Mode][]. |
-| `signer_lists` | Boolean | _(Optional)_ If `true`, and the [MultiSign amendment][] is enabled, also returns any [SignerList objects](signerlist.html) associated with this account. [New in: rippled 0.31.0][] |
-| `strict` | Boolean | _(Optional)_ If `true`, then the `account` field only accepts a public key or XRP Ledger address. Otherwise, `account` can be a secret or passphrase (not recommended). The default is `false`. |
+| `Field` | Type | Required? | Description |
+|:---------------|:---------------------|:----------|-------------|
+| `account` | String - [Address][] | Yes | The account to look up. [Updated in: rippled 1.11.0][] |
+| `ledger_hash` | String | No | A 20-byte hex string for the ledger version to use. (See [Specifying Ledgers][]) |
+| `ledger_index` | Number or String | No | The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) |
+| `queue` | Boolean | No | If `true`, return stats about [queued transactions](transaction-queue.html) sent by this account. Can only be used when querying for the data from the current open ledger. Not available from servers in [Reporting Mode][]. |
+| `signer_lists` | Boolean | No | If `true`, return any [SignerList objects](signerlist.html) associated with this account. |
 
-The following fields are deprecated and should not be provided: `ident`, `ledger`.
+The following fields are deprecated and should not be provided: `ident`, `ledger`, `strict`.
 
 ## Response Format
 
@@ -206,13 +203,32 @@ The response follows the [standard format][], with the result containing the req
 | `Field` | Type | Description |
 |:-----------------------|:--------|:------------------------------------------|
 | `account_data` | Object | The [AccountRoot ledger object](accountroot.html) with this account's information, as stored in the ledger. |
+| `account_flags` | Object | The account's flag statuses (see below), based on the `Flags` field of the account. [New in: rippled 1.11.0][] |
 | `signer_lists` | Array | _(Omitted unless the request specified `signer_lists` and at least one SignerList is associated with the account.)_ Array of [SignerList ledger objects](signerlist.html) associated with this account for [Multi-Signing](multi-signing.html). Since an account can own at most one SignerList, this array must have exactly one member if it is present. [New in: rippled 0.31.0][] |
 | `ledger_current_index` | Integer | _(Omitted if `ledger_index` is provided instead)_ The [ledger index][] of the current in-progress ledger, which was used when retrieving this information. |
 | `ledger_index` | Integer | _(Omitted if `ledger_current_index` is provided instead)_ The [ledger index][] of the ledger version used when retrieving this information. The information does not contain any changes from ledger versions newer than this one. |
 | `queue_data` | Object | _(Omitted unless `queue` specified as `true` and querying the current open ledger.)_ Information about [queued transactions](transaction-cost.html#queued-transactions) sent by this account. This information describes the state of the local `rippled` server, which may be different from other servers in the [peer-to-peer XRP Ledger network](consensus-network.html). Some fields may be omitted because the values are calculated "lazily" by the queuing mechanism. |
 | `validated` | Boolean | True if this data is from a validated ledger version; if omitted or set to false, this data is not final. [New in: rippled 0.26.0][] |
 
-The `queue_data` parameter, if present, contains the following fields:
+The `account_flags` field contains the following nested fields:
+
+| `Field` | Type | Description |
+|:-----------------------|:--------|:------------------------------------------|
+| `defaultRipple` | Boolean | If `true`, the account allows [rippling](rippling.html) on its trust lines by default. |
+| `depositAuth` | Boolean | If `true`, the account is using [Deposit Authorization](depositauth.html) and does not accept any payments from unknown parties. |
+| `disableMasterKey` | Boolean | If `true`, the account's [master key pair](cryptographic-keys.html) is disabled. |
+| `disallowIncomingCheck` | Boolean | If `true`, the account does not allow others to send [Checks](checks.html) to it. _(Requires the [DisallowIncoming amendment][])_ |
+| `disallowIncomingNFTokenOffer` | Boolean | If `true`, the account does not allow others to make [NFT buy or sell offers](non-fungible-token-transfers.html) to it. _(Requires the [DisallowIncoming amendment][])_ |
+| `disallowIncomingPayChan` | Boolean | If `true`, the account does not allow others to make [Payment Channels](payment-channels.html) to it. _(Requires the [DisallowIncoming amendment][])_ |
+| `disallowIncomingTrustline` | Boolean | If `true`, the account does not allow others to make [trust lines](trust-lines-and-issuing.html) to it. _(Requires the [DisallowIncoming amendment][])_ |
+| `disallowIncomingXRP` | Boolean | If `true`, the account does not want to receive XRP from others. (This is advisory, and not enforced at a protocol level.) |
+| `globalFreeze` | Boolean | If `true`, all tokens issued by the account are currently frozen. |
+| `noFreeze` | Boolean | If `true`, the account has permanently given up the abilities to freeze individual trust lines or end a global freeze. See [No Freeze](freezes.html#no-freeze) for details. |
+| `passwordSpent` | Boolean | If `false`, the account can send a special [key reset transaction](transaction-cost.html#key-reset-transaction) with a transaction cost of 0. The protocol turns this flag on and off automatically; it is not controlled by a user-facing setting. |
+| `requireAuthorization` | Boolean | If `true`, the account is using [Authorized Trust Lines](authorized-trust-lines.html) to limit who can hold the tokens it issues. |
+| `requireDestinationTag` | Boolean | If `true`, the account [requires a destination tag](require-destination-tags.html) on all payments it receives. |
+
+The `queue_data` field, if present, contains the following nested fields:
 
 | `Field` | Type | Description |
 |:------------------------|:--------|:-----------------------------------------|
@@ -223,7 +239,7 @@ The `queue_data` parameter, if present, contains the following fields:
 | `max_spend_drops_total` | String | (May be omitted) Integer amount of [drops of XRP][] that could be debited from this address if every transaction in the queue consumes the maximum amount of XRP possible. |
 | `transactions` | Array | (May be omitted) Information about each queued transaction from this address. |
 
-Each object in the `transactions` array, if present, may contain any or all of the following fields:
+Each object in the `transactions` array of `queue_data`, if present, may contain any or all of the following fields:
 
 | `Field` | Type | Description |
 |:------------------|:--------|:-----------------------------------------------|