Merge branch 'rippled_170'

2025-12-05 08:48:11 +00:00 · 2021-02-23 22:50:44 -08:00
parent 970ca50281 8852dfe1f4
commit 429d8e3386
87 changed files with 2460 additions and 467 deletions
--- a/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/can_delete.md
+++ b/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/can_delete.md
@@ -66,6 +66,7 @@ Use this command with no parameter to query the existing `can_delete` setting.
 - `lgrNotFound` - The ledger specified by the `can_delete` field of the request does not exist, or it does exist but the server does not have it.
 - `notEnabled` - If either online deletion or advisory deletion are not enabled in the server's configuration.
 - `notReady` - The server is not ready to run online deletion at the moment. This usually means the server has recently started up and has not yet acquired a validated ledger.
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 ## See Also

--- a/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/crawl_shards.md
+++ b/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/crawl_shards.md
@@ -129,6 +129,7 @@ Each member of the `peers` array of the response is an object that describes one

 - Any of the [universal error types][].
 - `invalidParams` - One or more required fields were omitted from the request, or a provided field was specified as the wrong data type.
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.


 <!--{# common link defs #}-->
--- a/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/download_shard.ja.md
+++ b/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/download_shard.ja.md
@@ -53,14 +53,15 @@ _`download_shard`メソッドは、権限のないユーザーは実行できな
 | `Field`    | 型      | 説明                                                  |
 |:-----------|:--------|:------------------------------------------------------|
 | `shards` | 配列 | ダウンロードするシャードとダウンロード元を記述したShard Descriptorオブジェクト（以下の説明を参照）のリスト。 |
-| `validate` | ブール値 | _（省略可）_ `false`の場合はダウンロードしたデータの検証をスキップします。デフォルトは`true`です。この場合、アーカイブのシャードにシャードのデータオブジェクトがすべて含まれており、シャードが現行の検証済みレジャーのレジャー履歴の一部であるか否かが確認されます。 |
+
+`validate`のフィールドは廃止予定であり、今後予告なしに削除される可能性があります。`rippled`は全てのシャードの検証を実行します。[更新: rippled 1.6.0][]

 `shards`配列の各**Shard Descriptorオブジェクト**には以下のフィールドが含まれています。

 | `Field` | 型     | 説明                                                      |
 |:--------|:-------|:----------------------------------------------------------|
 | `index` | 数値 | 取得するシャードのインデックス。本番環境のXRP Ledgerでは、最も古いシャードのインデックスは1であり、このシャードにはレジャー32750～32768が含まれています。次のシャードのインデックスは2であり、このシャードにはレジャー32769～49152が含まれています。 |
-| `url` | 文字列 | このシャードをダウンロードできるURL。このURLは`https://`で始まり`.tar.lz4`（大文字小文字の区別なし）で終わる必要があります。このダウンロードを提供するWebサーバーは、信頼できる認証局（CA）によって署名された有効なTLS証明書を使用する必要があります。（`rippled`はオペレーティングシステムのCAストアーを使用します。） |
+| `url` | 文字列 | このシャードをダウンロードできるURL。このURLは`https://`か`http://`かで始まり`.tar.lz4`（大文字小文字の区別なし）で終わる必要があります。このダウンロードを提供するWebサーバーは、信頼できる認証局（CA）によって署名された有効なTLS証明書を使用する必要があります。（`rippled`はオペレーティングシステムのCAストアーを使用します。） [更新: rippled 1.7.0][] |

 ### 応答フォーマット

--- a/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/download_shard.md
+++ b/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/download_shard.md
@@ -68,7 +68,7 @@ Each **Shard Descriptor object** in the `shards` array has the following fields:
 | `Field` | Type   | Description                                               |
 |:--------|:-------|:----------------------------------------------------------|
 | `index` | Number | The index of the shard to retrieve. In the production XRP Ledger, the oldest shard has index 1 and contains ledgers 32750-32768. The next shard has index 2 and contains ledgers 32769-49152, and so on. |
-| `url`   | String | The URL where this shard can be downloaded. The URL must start with `https://` and must end with `.tar.lz4` (not case-sensitive). The web server providing this download must use a valid TLS certificate signed by a trusted Certificate Authority (CA). (`rippled` uses the operating system's CA store.) |
+| `url`   | String | The URL where this shard can be downloaded. The URL must start with `http://` or `https://` and must end with `.tar.lz4` (not case-sensitive). The web server providing this download must use a valid TLS certificate signed by a trusted Certificate Authority (CA). (`rippled` uses the operating system's CA store.) [Updated in: rippled 1.7.0][] |

 ### Response Format

@@ -132,6 +132,7 @@ The response follows the [standard format][], with a successful result containin
 - `notEnabled` - The server is not configured with a shard store.
 - `tooBusy` - The server is already downloading the shard, either from the peer-to-peer network or as the result of a previous `download_shard` request.
 - `invalidParams` - One or more required fields were omitted from the request, or a provided field was specified as the wrong data type.
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.



--- a/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/ledger_request.md
+++ b/content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/ledger_request.md
@@ -176,9 +176,10 @@ When the server is in the progress of fetching a ledger, but has not yet finishe

 ### Possible Errors

-* Any of the [universal error types][].
-* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing. This error can also occur if you specify a ledger index equal or higher than the current in-progress ledger.
-* `lgrNotFound` - If the ledger is not yet available. This indicates that the server has started fetching the ledger, although it may fail if none of its connected peers have the requested ledger. (Previously, this error used the code `ledgerNotFound` instead.) [Updated in: rippled 0.30.1][]
+- Any of the [universal error types][].
+- `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing. This error can also occur if you specify a ledger index equal or higher than the current in-progress ledger.
+- `lgrNotFound` - If the ledger is not yet available. This indicates that the server has started fetching the ledger, although it may fail if none of its connected peers have the requested ledger. (Previously, this error used the code `ledgerNotFound` instead.) [Updated in: rippled 0.30.1][]
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/peer-management-methods/connect.md
+++ b/content/references/rippled-api/admin-rippled-methods/peer-management-methods/connect.md
@@ -92,9 +92,10 @@ The response follows the [standard format][], with a successful result containin

 ### Possible Errors

-* Any of the [universal error types][].
-* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
-* Cannot connect in standalone mode - Network-related commands are disabled in stand-alone mode.
+- Any of the [universal error types][].
+- `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
+- Cannot connect in standalone mode - Network-related commands are disabled in stand-alone mode.
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/peer-management-methods/peer_reservations_add.md
+++ b/content/references/rippled-api/admin-rippled-methods/peer-management-methods/peer_reservations_add.md
@@ -129,6 +129,7 @@ If the `previous` field is provided, it shows the previous status of this peer r
 - Any of the [universal error types][].
 - `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 - `publicMalformed` - The `public_key` field of the request is not valid. It must be a valid node public key in [base58][] format.
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/peer-management-methods/peer_reservations_del.md
+++ b/content/references/rippled-api/admin-rippled-methods/peer-management-methods/peer_reservations_del.md
@@ -125,6 +125,7 @@ If the `previous` field is provided, it shows the previous status of this peer r
 - Any of the [universal error types][].
 - `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 - `publicMalformed` - The `public_key` field of the request is not valid. It must be a valid node public key in [base58][] format.
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/peer-management-methods/peer_reservations_list.md
+++ b/content/references/rippled-api/admin-rippled-methods/peer-management-methods/peer_reservations_list.md
@@ -127,6 +127,7 @@ Each member of the `reservations` array is a JSON object describing one [peer re
 ### Possible Errors

 - Any of the [universal error types][].
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/peer-management-methods/peers.md
+++ b/content/references/rippled-api/admin-rippled-methods/peer-management-methods/peers.md
@@ -408,7 +408,8 @@ The `metrics` object contains the following fields:

 ### Possible Errors

-* Any of the [universal error types][].
+- Any of the [universal error types][].
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/consensus_info.md
+++ b/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/consensus_info.md
@@ -226,7 +226,8 @@ The results of the `consensus_info` command can vary dramatically if you run it

 ### Possible Errors

-* Any of the [universal error types][].
+- Any of the [universal error types][].
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/feature.md
+++ b/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/feature.md
@@ -186,8 +186,9 @@ The response follows the [standard format][], with a successful result containin

 ### Possible Errors

-* Any of the [universal error types][].
-* `badFeature` - The `feature` specified was invalidly formatted, or the server does not know an amendment with that name.
+- Any of the [universal error types][].
+- `badFeature` - The `feature` 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.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/fetch_info.md
+++ b/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/fetch_info.md
@@ -154,7 +154,8 @@ The fields describing a fetch in progress are subject to change without notice.

 ### Possible Errors

-* Any of the [universal error types][].
+- Any of the [universal error types][].
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/validator_list_sites.md
+++ b/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/validator_list_sites.md
@@ -141,7 +141,8 @@ The `last_refresh_status` field can have the following values:

 ### Possible Errors

-* Any of the [universal error types][].
+- Any of the [universal error types][].
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/validators.md
+++ b/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/validators.md
@@ -176,7 +176,8 @@ Each member of the `publisher_lists` array is an object with the following field

 ### Possible Errors

-* Any of the [universal error types][].
+- Any of the [universal error types][].
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/api-conventions/basic-data-types.md
+++ b/content/references/rippled-api/api-conventions/basic-data-types.md
@@ -68,17 +68,30 @@ Some types of hash appear in API requests and responses. Others are only calcula
 Many API methods require you to specify an instance of the ledger, with the data retrieved being considered up-to-date as of that particular version of the shared ledger. The commands that accept a ledger version all work the same way. There are three ways you can specify which ledger you want to use:

 1. Specify a ledger by its [Ledger Index][] in the `ledger_index` parameter. Each closed ledger has a ledger index that is 1 higher than the previous ledger. (The very first ledger had ledger index 1.)
+
+        "ledger_index": 61546724
+
 2. Specify a ledger by its [Hash][] value in the `ledger_hash` parameter.
+
+        "ledger_hash": "8BB204CE37CFA7A021A16B5F6143400831C4D1779E6FE538D9AC561ABBF4A929"
+
 3. Specify a ledger by one of the following shortcuts, in the `ledger_index` parameter:
-    * `validated` for the most recent ledger that has been validated by the whole network
+
+    * `validated` for the most recent ledger that has been [validated by consensus](consensus.html#validation)
+
+            "ledger_index": "validated"
+
    * `closed` for the most recent ledger that has been closed for modifications and proposed for validation
+
    * `current` for the server's current working version of the ledger.

 There is also a deprecated `ledger` parameter which accepts any of the above three formats. *Do not* use this parameter; it may be removed without further notice.

-If you do not specify a ledger, the `current` (in-progress) ledger is chosen by default. If you provide more than one field specifying ledgers, the deprecated `ledger` field is used first if it exists, falling back to `ledger_hash`. The `ledger_index` field is ignored unless neither of the other two are present.
+If you do not specify a ledger, the server decides which ledger to use to serve the request. By default, the server chooses the `current` (in-progress) ledger. In [Reporting Mode](rippled-server-modes.html#reporting-mode), the server uses the most recent validated ledger instead. Do not provide more than one field specifying ledgers.

-**Note:** Do not rely on this default behavior for specifying a ledger; it is subject to change. Always specify a ledger version in the request if you can.
+**Note:** Do not rely on the default behavior for specifying a ledger; it is subject to change. Always specify a ledger version in the request if you can.
+
+Reporting Mode does not record ledger data until it has been validated. If you make a request to a Reporting Mode server for the `current` or `closed` ledger, the server forwards the request to a P2P Mode server. If you request a ledger index or hash that is not validated, a Reporting Mode server responds with a `lgrNotFound` error.


 ## Specifying Currency Amounts
--- a/content/references/rippled-api/api-conventions/error-formatting.md
+++ b/content/references/rippled-api/api-conventions/error-formatting.md
@@ -101,15 +101,22 @@ For other errors that returned with HTTP status code 200 OK, the responses are f

 All methods can potentially return any of the following values for the `error` code:

-* `amendmentBlocked` - The server is [amendment blocked](amendments.html#amendment-blocked) and needs to be updated to the latest version to stay synced with the XRP Ledger network.
+- `amendmentBlocked` - The server is [amendment blocked](amendments.html#amendment-blocked) and needs to be updated to the latest version to stay synced with the XRP Ledger network.
+- `failedToForward` - ([Reporting Mode][] servers only) The server tried to forward this request to a P2P Mode server, but the connection failed.
 - `invalid_API_version` - The server does not support the [API version number](request-formatting.html#api-versioning) from the request.
-* `jsonInvalid` - (WebSocket only) The request is not a proper JSON object.
-    * JSON-RPC returns a 400 Bad Request HTTP error in this case instead.
-* `missingCommand` - (WebSocket only) The request did not specify a `command` field.
-    * JSON-RPC returns a 400 Bad Request HTTP error in this case instead.
-* `noClosed` - The server does not have a closed ledger, typically because it has not finished starting up.
-* `noCurrent` - The server does not know what the current ledger is, due to high load, network problems, validator failures, incorrect configuration, or some other problem.
-* `noNetwork` - The server is having trouble connecting to the rest of the XRP Ledger peer-to-peer network (and is not running in stand-alone mode).
-* `tooBusy` - The server is under too much load to do this command right now. Generally not returned if you are connected as an admin.
-* `unknownCmd` - The request does not contain a [command](rippled-api.html) that the `rippled` server recognizes.
-* `wsTextRequired` - (WebSocket only) The request's [opcode](https://tools.ietf.org/html/rfc6455#section-5.2) is not text. <!-- SPELLING_IGNORE: opcode -->
+- `jsonInvalid` - (WebSocket only) The request is not a proper JSON object.
+    - JSON-RPC returns a 400 Bad Request HTTP error in this case instead.
+- `missingCommand` - (WebSocket only) The request did not specify a `command` field.
+    - JSON-RPC returns a 400 Bad Request HTTP error in this case instead.
+- `noClosed` - The server does not have a closed ledger, typically because it has not finished starting up.
+- `noCurrent` - The server does not know what the current ledger is, due to high load, network problems, validator failures, incorrect configuration, or some other problem.
+- `noNetwork` - The server is having trouble connecting to the rest of the XRP Ledger peer-to-peer network (and is not running in stand-alone mode).
+- `tooBusy` - The server is under too much load to do this command right now. Generally not returned if you are connected as an admin.
+- `unknownCmd` - The request does not contain a [command](rippled-api.html) that the `rippled` server recognizes.
+- `wsTextRequired` - (WebSocket only) The request's [opcode](https://tools.ietf.org/html/rfc6455#section-5.2) is not text. <!-- SPELLING_IGNORE: opcode -->
+
+
+<!--{# common link defs #}-->
+{% include '_snippets/rippled-api-links.md' %}			
+{% include '_snippets/tx-type-links.md' %}			
+{% include '_snippets/rippled_versions.md' %}
--- a/content/references/rippled-api/api-conventions/response-formatting.md
+++ b/content/references/rippled-api/api-conventions/response-formatting.md
@@ -13,6 +13,7 @@ The fields of a successful response include:
 | `result`        | Object   | The result of the query; contents vary depending on the command. |
 | `warning`       | String   | _(May be omitted)_ If this field is provided, the value is the string `load`. This means the client is approaching the [rate limiting](rate-limiting.html) threshold where the server will disconnect this client. |
 | `warnings`      | Array    | _(May be omitted)_ If this field is provided, it contains one or more **Warnings Objects** with important warnings. For details, see [API Warnings](#api-warnings). [New in: rippled 1.5.0][] |
+| `forwarded`     | Boolean  | _(May be omitted)_ If `true`, this request and response have been forwarded from a [Reporting Mode][] server to a P2P Mode server (and back) because the request requires data that is not available in Reporting Mode. The default is `false`. |


 ## Example Successful Response
@@ -151,6 +152,27 @@ This warning indicates that the server is [amendment blocked](amendments.html#am

 The server administrator must [upgrade `rippled`](install-rippled.html) to a version that supports the activated amendments.

+### 1003. This is a reporting server
+[New in: rippled 1.7.0][]
+
+Example warning:
+
+```json
+"warnings" : [
+  {
+    "id" : 1003,
+    "message" : "This is a reporting server. The default behavior of a reporting server is to only return validated data. If you are looking for not yet validated data, include \"ledger_index : current\" in your request, which will cause this server to forward the request to a p2p node. If the forward is successful the response will include \"forwarded\" : \"true\""
+  }
+]
+```
+
+This warning indicates that the server answering the request is running [Reporting Mode][]. Certain API methods are not available or behave differently because Reporting Mode does not connect to the peer-to-peer network and does not track ledger data that has not yet been validated.
+
+It is generally safe to ignore this warning.
+
+**Caution:** If you request ledger data without explicitly [specifying a ledger version][Specifying Ledgers], Reporting Mode uses the latest validated ledger by default instead of the current in-progress ledger.
+
+
 ## See Also

 - **Concepts:**
--- a/content/references/rippled-api/ledger-data-formats/ledger-object-types/accountroot.md
+++ b/content/references/rippled-api/ledger-data-formats/ledger-object-types/accountroot.md
@@ -53,6 +53,7 @@ The `AccountRoot` object has the following fields:
 | `EmailHash`                   | String    | Hash128           | _(Optional)_ The md5 hash of an email address. Clients can use this to look up an avatar through services such as [Gravatar](https://en.gravatar.com/). |
 | `MessageKey`                  | String    | Blob              | _(Optional)_ A public key that may be used to send encrypted messages to this account. In JSON, uses hexadecimal. Must be exactly 33 bytes, with the first byte indicating the key type: `0x02` or `0x03` for secp256k1 keys, `0xED` for Ed25519 keys. |
 | `RegularKey`                  | String    | AccountID         | _(Optional)_ The address of a [key pair](cryptographic-keys.html) that can be used to sign transactions for this account instead of the master key. Use a [SetRegularKey transaction][] to change this value. |
+| `TicketCount`                 | Number    | UInt32            | _(Optional)_ How many [Tickets](tickets.html) this account owns in the ledger. This is updated automatically to ensure that the account stays within the hard limit of 250 Tickets at a time. This field is omitted if the account has zero Tickets. _(Added by the [TicketBatch amendment][] :not_enabled:)_ |
 | `TickSize`                    | Number    | UInt8             | _(Optional)_ How many significant digits to use for exchange rates of Offers involving currencies issued by this address. Valid values are `3` to `15`, inclusive. _(Added by the [TickSize amendment][].)_ |
 | `TransferRate`                | Number    | UInt32            | _(Optional)_ A [transfer fee](https://ripple.com/knowledge_center/transfer-fees/) to charge other users for sending currency issued by this account to each other. |
 | `WalletLocator`               | String    | Hash256           | _(Optional)_ **DEPRECATED**. Do not use. |
--- a/content/references/rippled-api/ledger-data-formats/ledger-object-types/check.md
+++ b/content/references/rippled-api/ledger-data-formats/ledger-object-types/check.md
@@ -65,7 +65,8 @@ The ID of a `Check` object is the [SHA-512Half][] of the following values, conca

 * The Check space key (`0x0043`)
 * The AccountID of the sender of the [CheckCreate transaction][] that created the `Check` object
-* The Sequence number of the [CheckCreate transaction][] that created the `Check` object
+* The `Sequence` number of the [CheckCreate transaction][] that created the `Check` object.
+    If the CheckCreate transaction used a [Ticket](tickets.html), use the `TicketSequence` value instead.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}			
--- a/content/references/rippled-api/ledger-data-formats/ledger-object-types/escrow.md
+++ b/content/references/rippled-api/ledger-data-formats/ledger-object-types/escrow.md
@@ -71,6 +71,7 @@ The ID of an `Escrow` object is the [SHA-512Half][] of the following values, con
 * The Escrow space key (`0x0075`)
 * The AccountID of the sender of the [EscrowCreate transaction][] that created the `Escrow` object
 * The Sequence number of the [EscrowCreate transaction][] that created the `Escrow` object
+    If the EscrowCreate transaction used a [Ticket](tickets.html), use the `TicketSequence` value instead.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}			
--- a/content/references/rippled-api/ledger-data-formats/ledger-object-types/offer.md
+++ b/content/references/rippled-api/ledger-data-formats/ledger-object-types/offer.md
@@ -77,6 +77,7 @@ The ID of an `Offer` object is the [SHA-512Half][] of the following values, conc
 * The Offer space key (`0x006F`)
 * The AccountID of the account placing the offer
 * The Sequence number of the [OfferCreate transaction][] that created the offer
+    If the OfferCreate transaction used a [Ticket](tickets.html), use the `TicketSequence` value instead.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}			
--- a/content/references/rippled-api/ledger-data-formats/ledger-object-types/paychannel.md
+++ b/content/references/rippled-api/ledger-data-formats/ledger-object-types/paychannel.md
@@ -103,7 +103,8 @@ The ID of a `PayChannel` object is the [SHA-512Half][] of the following values,
 * The PayChannel space key (`0x0078`)
 * The AccountID of the source account
 * The AccountID of the destination account
-* The Sequence number of the transaction that created the channel
+* The Sequence number of the [PaymentChannelCreate transaction][] that created the channel
+    If the PaymentChannelCreate transaction used a [Ticket](tickets.html), use the `TicketSequence` value instead.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}			
--- a/content/references/rippled-api/ledger-data-formats/ledger-object-types/ticket.md
+++ b/content/references/rippled-api/ledger-data-formats/ledger-object-types/ticket.md
@@ -0,0 +1,58 @@
+---
+html: ticket.html
+funnel: Build
+doc_type: References
+supercategory: rippled API
+category: Ledger Data Formats
+subcategory: Ledger Object Types
+blurb: A Ticket tracks an account sequence number that has been set aside for future use.
+parent: ledger-object-types.html
+---
+# Ticket
+
+[[Source]](https://github.com/ripple/rippled/blob/76a6956138c4ecd156c5c408f136ed3d6ab7d0c1/src/ripple/protocol/impl/LedgerFormats.cpp#L155-L164)
+
+_(Requires the [TicketBatch amendment][] :not_enabled:)_
+
+The `Ticket` object type represents a [Ticket](tickets.html), which tracks an account [sequence number][Sequence Number] that has been set aside for future use. You can create new tickets with a [TicketCreate transaction][]. [New in: rippled 1.7.0][]
+
+## Example {{currentpage.name}} JSON
+
+```json
+{
+  "Account" : "rEhxGqkqPPSxQ3P25J66ft5TwpzV14k2de",
+  "Flags" : 0,
+  "LedgerEntryType" : "Ticket",
+  "OwnerNode" : "0000000000000000",
+  "PreviousTxnID" : "F19AD4577212D3BEACA0F75FE1BA1644F2E854D46E8D62E9C95D18E9708CBFB1",
+  "PreviousTxnLgrSeq" : 4,
+  "TicketSequence" : 3
+}
+```
+
+## {{currentpage.name}} Fields
+
+A `Ticket` object has the following fields:
+
+| Name                | JSON Type | Internal Type | Description                |
+|:--------------------|:----------|:--------------|:---------------------------|
+| `LedgerEntryType`   | String    | UInt16        | The value `0x0054`, mapped to the string `Ticket`, indicates that this object is a {{currentpage.name}} object. |
+| `Account`           | String    | AccountID     | The [account](accounts.html) that owns this Ticket. |
+| `Flags`             | Number    | UInt32        | A bit-map of Boolean flags enabled for this Ticket. Currently, there are no flags defined for Tickets. |
+| `OwnerNode`         | String    | UInt64        | A hint indicating which page of the owner directory links to this object, in case the directory consists of multiple pages. **Note:** The object does not contain a direct link to the owner directory containing it, since that value can be derived from the `Account`. |
+| `PreviousTxnID`     | String    | Hash256       | The identifying hash of the [transaction](transaction-basics.html) that most recently modified this object. |
+| `PreviousTxnLgrSeq` | Number    | UInt32        | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this object. |
+| `TicketSequence`    | Number    | UInt32        | The [Sequence Number][] this Ticket sets aside. |
+
+## {{currentpage.name}} ID Format
+
+The ID of a Ticket object is the SHA-512Half of the following values, concatenated in order:
+
+* The Ticket space key (`0x0054`)
+* The AccountID of the owner of the Ticket
+* The `TicketSequence` number of the Ticket
+
+<!--{# common link defs #}-->
+{% include '_snippets/rippled-api-links.md' %}
+{% include '_snippets/tx-type-links.md' %}
+{% include '_snippets/rippled_versions.md' %}
--- a/content/references/rippled-api/peer-port-methods/health-check.md
+++ b/content/references/rippled-api/peer-port-methods/health-check.md
@@ -5,7 +5,7 @@ The Health Check is a special [peer port method](peer-port-methods.html) for rep

 This method checks several metrics to see if they are in ranges generally considered healthy. If all metrics are in normal ranges, this method reports that the server is healthy. If any metric is outside normal ranges, this method reports that the server is unhealthy and reports the metric(s) that are unhealthy. Since some metrics may rapidly fluctuate into and out of unhealthy ranges, you should not raise alerts unless the health check fails multiple times in a row.

-**Note:** Since the health check is a [peer port method](peer-port-methods.html), it is not available when testing the server in [stand-alone mode](rippled-server-modes.html#reasons-to-run-a-rippled-server-in-stand-alone-mode).
+**Note:** Since the health check is a [peer port method](peer-port-methods.html), it is not available when testing the server in [stand-alone mode][].


 ## Request Format
--- a/content/references/rippled-api/peer-port-methods/validator-list.md
+++ b/content/references/rippled-api/peer-port-methods/validator-list.md
@@ -35,9 +35,7 @@ The JSON object has the following fields:
 | `blob`           | String | Base64-encoded JSON data representing the validator list. |
 | `signature`      | String | The signature of the `blob` data, in hexadecimal. |
 | `version`        | Number | The version of the validator list protocol this object uses. The current version is **1**. A higher version number indicates backwards-incompatible changes with a previous version of the validator list protocol. |
-<!--{# This field isn't included in the rippled response, but should be. https://github.com/ripple/rippled/issues/3392
-| `public_key`     | String | The public key used to verify this validator list data, in hexadecimal. This is a 32-byte Ed25519 public key prefixed with the byte `0xED`. |
-#}-->
+| `public_key`     | String | The public key used to verify this validator list data, in hexadecimal. This is a 32-byte Ed25519 public key prefixed with the byte `0xED`. [New in: rippled 1.7.0][] |

 ### Manifest Data
 [[Source]](https://github.com/ripple/rippled/blob/97712107b71a8e2089d2e3fcef9ebf5362951110/src/ripple/app/misc/impl/Manifest.cpp#L43-L66 "Source")
--- a/content/references/rippled-api/public-rippled-methods/account-methods/account_info.md
+++ b/content/references/rippled-api/public-rippled-methods/account-methods/account_info.md
@@ -56,7 +56,7 @@ The request contains the following parameters:
 | `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][] |
+| `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`. |

--- a/content/references/rippled-api/public-rippled-methods/account-methods/account_lines.md
+++ b/content/references/rippled-api/public-rippled-methods/account-methods/account_lines.md
@@ -422,12 +422,12 @@ Each trust line object has some combination of the following fields:
 | `limit_peer`     | String           | The maximum amount of currency that the counterparty account is willing to owe the perspective account |
 | `quality_in`     | Unsigned Integer | Rate at which the account values incoming balances on this trust line, as a ratio of this value per 1 billion units. (For example, a value of 500 million represents a 0.5:1 ratio.) As a special case, 0 is treated as a 1:1 ratio. |
 | `quality_out`    | Unsigned Integer | Rate at which the account values outgoing balances on this trust line, as a ratio of this value per 1 billion units. (For example, a value of 500 million represents a 0.5:1 ratio.) As a special case, 0 is treated as a 1:1 ratio. |
-| `no_ripple`      | Boolean          | _(May be omitted)_ `true` if this account has enabled the [No Ripple flag](rippling.html) for this line. If omitted, that is the same as `false`. |
-| `no_ripple_peer` | Boolean          | _(May be omitted)_ `true` if the peer account has enabled the [No Ripple flag](rippling.html). If omitted, that is the same as `false`. |
-| `authorized`     | Boolean          | _(May be omitted)_ `true` if this account has [authorized this trust line](authorized-trust-lines.html). If omitted, that is the same as `false`. |
-| `peer_authorized`| Boolean          | _(May be omitted)_ `true` if the peer account has [authorized this trust line](authorized-trust-lines.html). If omitted, that is the same as `false`. |
-| `freeze`         | Boolean          | _(May be omitted)_ `true` if this account has [frozen](freezes.html) this trust line. If omitted, that is the same as `false`. |
-| `freeze_peer`    | Boolean          | _(May be omitted)_ `true` if the peer account has [frozen](freezes.html) this trust line. If omitted, that is the same as `false`. |
+| `no_ripple`      | Boolean          | _(May be omitted)_ If `true`, this account has enabled the [No Ripple flag](rippling.html) for this trust line. If present and `false`, this account has disabled the No Ripple flag, but, because the account also has the Default Ripple flag enabled, that is not considered [the default state](ripplestate.html#contributing-to-the-owner-reserve). If omitted, the account has the No Ripple flag disabled for this trust line and Default Ripple disabled. [Updated in: rippled 1.7.0][] |
+| `no_ripple_peer` | Boolean          | _(May be omitted)_ If `true`, the peer account has enabled the [No Ripple flag](rippling.html) for this trust line. If present and `false`, this account has disabled the No Ripple flag, but, because the account also has the Default Ripple flag enabled, that is not considered [the default state](ripplestate.html#contributing-to-the-owner-reserve). If omitted, the account has the No Ripple flag disabled for this trust line and Default Ripple disabled. [Updated in: rippled 1.7.0][] |
+| `authorized`     | Boolean          | _(May be omitted)_ If `true`, this account has [authorized this trust line](authorized-trust-lines.html). The default is `false`. |
+| `peer_authorized`| Boolean          | _(May be omitted)_ If `true`, the peer account has [authorized this trust line](authorized-trust-lines.html). The default is `false`. |
+| `freeze`         | Boolean          | _(May be omitted)_ If `true`, this account has [frozen](freezes.html) this trust line. The default is `false`. |
+| `freeze_peer`    | Boolean          | _(May be omitted)_ If `true`, the peer account has [frozen](freezes.html) this trust line. The default is `false`. |

 ## Possible Errors

--- a/content/references/rippled-api/public-rippled-methods/account-methods/account_objects.md
+++ b/content/references/rippled-api/public-rippled-methods/account-methods/account_objects.md
@@ -12,7 +12,7 @@ The types of objects that may appear in the `account_objects` response for an ac
 - [PayChannel objects](paychannel.html) for open payment channels.
 - [Check objects](check.html) for pending Checks.
 - [DepositPreauth objects](depositpreauth-object.html) for deposit preauthorizations. [New in: rippled 1.1.0][]
- [Ticket objects](known-amendments.html#tickets) :not_enabled: for tickets.
+- [Ticket objects](known-amendments.html#tickets) :not_enabled: for Tickets.


 ## Request Format
--- a/content/references/rippled-api/public-rippled-methods/account-methods/account_tx.ja.md
+++ b/content/references/rippled-api/public-rippled-methods/account-methods/account_tx.ja.md
@@ -587,7 +587,6 @@ rippled -- account_tx r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 -1 -1 2 5 1 0 1
 * いずれかの[汎用エラータイプ][]。
 * `invalidParams` - 1つ以上のフィールドの指定が正しくないか、1つ以上の必須フィールドが指定されていません。
 * `actMalformed` - 要求の`account`フィールドに指定した[アドレス][]が、正しいフォーマットではありません。
-* `actBitcoin` - `account`フィールドに指定された[アドレス][]が、XRP LedgerアドレスではなくBitcoinアドレスのようなフォーマットになっています。
 * `lgrIdxMalformed` - `ledger_index_min`または`ledger_index_max`で指定したレジャーが存在しないか、存在してはいるもののサーバーが保有していません。
 * `lgrIdxsInvalid` - 要求で`ledger_index_min`の前にある`ledger_index_max`を指定したか、[ネットワークと同期](troubleshoot-the-rippled-server.html)されていないためにサーバーに検証済みレジャーの範囲が存在しません。<!-- TODO: link more specific docs when https://github.com/ripple/xrpl-dev-portal/issues/714 is done. -->

--- a/content/references/rippled-api/public-rippled-methods/account-methods/account_tx.md
+++ b/content/references/rippled-api/public-rippled-methods/account-methods/account_tx.md
@@ -450,7 +450,6 @@ Each transaction object includes the following fields, depending on whether it w
 * Any of the [universal error types][].
 * `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
 * `actMalformed` - The [Address][] specified in the `account` field of the request is not formatted properly.
-* `actBitcoin` - The [Address][] specified in the `account` field is formatted like a Bitcoin address instead of a XRP Ledger address.
 * `lgrIdxMalformed` - The ledger specified by the `ledger_index_min` or `ledger_index_max` does not exist, or if it does exist but the server does not have it.
 * `lgrIdxsInvalid` - Either the request specifies a `ledger_index_max` that is before the `ledger_index_min`, or the server does not have a validated ledger range because it is [not synced with the network](server-doesnt-sync.html).

--- a/content/references/rippled-api/public-rippled-methods/ledger-methods/ledger_entry.md
+++ b/content/references/rippled-api/public-rippled-methods/ledger-methods/ledger_entry.md
@@ -59,6 +59,7 @@ This method can retrieve several different types of data. You can select which t
 7. `escrow` - Retrieve an [Escrow object](escrow-object.html), which holds XRP until a specific time or condition is met. [New in: rippled 1.0.0][]
 8. `payment_channel` - Retrieve a [PayChannel object](paychannel.html), which holds XRP for asynchronous payments. [New in: rippled 1.0.0][]
 9. `deposit_preauth` - Retrieve a [DepositPreauth object](depositpreauth-object.html), which tracks preauthorization for payments to accounts requiring [Deposit Authorization](depositauth.html). [New in: rippled 1.1.0][]
+10. `ticket` - Retrieve a [Ticket object](ticket.html), which records a [sequence number][] set aside for future use. _(Requires the [TicketBatch amendment][])_

 If you specify more than one of the above items, the server retrieves only one of them; it is undefined which it chooses.

@@ -86,6 +87,9 @@ The full list of parameters recognized by this method is as follows:
 | `ripple_state`          | Object                     | _(Optional)_ Object specifying the RippleState (trust line) object to retrieve. The `accounts` and `currency` sub-fields are required to uniquely specify the RippleState entry to retrieve. |
 | `ripple_state.accounts` | Array                      | _(Required if `ripple_state` is specified)_ 2-length array of account [Address][]es, defining the two accounts linked by this [RippleState object](ripplestate.html). |
 | `ripple_state.currency` | String                     | _(Required if `ripple_state` is specified)_ [Currency Code][] of the [RippleState object](ripplestate.html) to retrieve. |
+| `ticket`                | Object or String           | _(Optional)_ Object specifying the [Ticket object](ticket.html) to retrieve. If a string, the must be the [object ID](ledger-object-ids.html) of the Ticket, as hexadecimal. If an object, the `owner` and `ticket_sequence` sub-fields are required to uniquely specify the Ticket entry to retrieve. |
+| `ticket.owner`          | String - [Address][]       | _(Required if `ticket` is specified as an object)_ The owner of the Ticket object. |
+| `ticket.ticket_sequence` | Unsigned Integer          | _(Required if `ticket` is specified as an object)_ The Ticket Sequence number of the Ticket entry to retrieve. |
 | `binary`                | Boolean                    | _(Optional)_ If true, return the requested ledger object's contents as a hex string. Otherwise, return data in JSON format. The default is `false`. [Updated in: rippled 1.2.0][] |
 | `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][]) |
--- a/content/references/rippled-api/public-rippled-methods/public-rippled-methods.md
+++ b/content/references/rippled-api/public-rippled-methods/public-rippled-methods.md
@@ -75,7 +75,7 @@ Use these methods to retrieve information about the current state of the `ripple
 * **[`fee`](fee.html)** - Get information about transaction cost.
 * **[`server_info`](server_info.html)** - Retrieve status of the server in human-readable format.
 * **[`server_state`](server_state.html)** - Retrieve status of the server in machine-readable format.
-
+- **[`manifest`](manifest.html)** - Retrieve the latest ephemeral public key information about a known validator.

 ## [Utility Methods](utility-methods.html)

--- a/content/references/rippled-api/public-rippled-methods/server-info-methods/fee.md
+++ b/content/references/rippled-api/public-rippled-methods/server-info-methods/fee.md
@@ -157,7 +157,7 @@ The response follows the [standard format][], with a successful result containin

 ## Possible Errors

-* Any of the [universal error types][].
+- Any of the [universal error types][].


 <!--{# common link defs #}-->
--- a/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/manifest.md
+++ b/content/references/rippled-api/admin-rippled-methods/status-and-debugging-methods/manifest.md
@@ -1,9 +1,7 @@
 # manifest
 [[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/Manifest.cpp "Source")

-The `{{currentpage.name}}` method reports the current "manifest" information for a given validator public key. The "manifest" is the public portion of that validator's configured token.
-
-_The `{{currentpage.name}}` method is an [admin method](admin-rippled-methods.html) that cannot be run by unprivileged users._
+The `{{currentpage.name}}` method reports the current "manifest" information for a given validator public key. The "manifest" is the public portion of that validator's configured token. [Updated in: rippled 1.7.0][]


 ### Request Format
@@ -143,6 +141,7 @@ If provided, the `details` object contains the following fields:

 - Any of the [universal error types][].
 - `invalidParams` - The `public_key` field was missing or specified incorrectly.
+- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode.

 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}
--- a/content/references/rippled-api/public-rippled-methods/subscription-methods/subscribe.md
+++ b/content/references/rippled-api/public-rippled-methods/subscription-methods/subscribe.md
@@ -69,14 +69,17 @@ The following parameters are deprecated and may be removed without further notic

 The `streams` parameter provides access to the following default streams of information:

-* `server` - Sends a message whenever the status of the `rippled` server (for example, network connectivity) changes
-* `ledger` - Sends a message whenever the consensus process declares a new validated ledger
-* `transactions` - Sends a message whenever a transaction is included in a closed ledger
-* `transactions_proposed` - Sends a message whenever a transaction is included in a closed ledger, as well as some transactions that have not yet been included in a validated ledger and may never be. Not all proposed transactions appear before validation.
+- `consensus` - Sends a message whenever the server changes phase in the consensus cycle (open, establish, accepted, and so forth)
+- `ledger` - Sends a message whenever the consensus process declares a new validated ledger
+- `manifests` - Sends a message whenever the server receives an update to a validator's ephemeral signing key.
+- `peer_status` - **(Admin only)** Information about connected peer `rippled` servers, especially with regards to the consensus process.
+- `transactions` - Sends a message whenever a transaction is included in a closed ledger
+- `transactions_proposed` - Sends a message whenever a transaction is included in a closed ledger, as well as some transactions that have not yet been included in a validated ledger and may never be. Not all proposed transactions appear before validation.
    **Note:** [Even some transactions that don't succeed are included](transaction-results.html) in validated ledgers, because they take the anti-spam transaction fee.
-* `validations` - Sends a message whenever the server receives a validation message, regardless of if the server trusts the validator. (An individual `rippled` declares a ledger validated when the server receives validation messages from at least a quorum of trusted validators.)
-* `consensus` - Sends a message whenever the server changes phase in the consensus cycle (open, establish, accepted, and so forth)
-* `peer_status` - **(Admin only)** Information about connected peer `rippled` servers, especially with regards to the consensus process.
+- `server` - Sends a message whenever the status of the `rippled` server (for example, network connectivity) changes
+- `validations` - Sends a message whenever the server receives a validation message, regardless of if the server trusts the validator. (An individual `rippled` declares a ledger validated when the server receives validation messages from at least a quorum of trusted validators.)
+
+**Note:** The following streams are not available from servers in [Reporting Mode][]: `server`, `manifests`, `validations`, `peer_status`, `consensus`. Reporting Mode servers return the error `reportingUnsupported` if you request one of these streams.

 Each member of the `books` array, if provided, is an object with the following fields:

--- a/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md
+++ b/content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md
@@ -293,7 +293,7 @@ The response follows the [standard format][], with a successful result containin
 | `account_sequence_available` | Number | _(Omitted in sign-and-submit mode)_ The next [Sequence Number][] available for the sending account after all pending and [queued](transaction-queue.html) transactions. [New in: rippled 1.5.0][] |
 | `account_sequence_next` | number  | _(Omitted in sign-and-submit mode)_ The next [Sequence Number][] for the sending account after all transactions that have been provisionally applied, but not transactions in the [queue](transaction-queue.html). [New in: rippled 1.5.0][] |
 | `applied`               | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates that this transaction was applied to the open ledger. In this case, the transaction is likely, but not guaranteed, to be validated in the next ledger version. [New in: rippled 1.5.0][] |
-| `broadcast`             | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates this transaction was broadcast to peer servers in the peer-to-peer XRP Ledger network. (Note: if the server has no peers, such as in [stand-alone mode](rippled-server-modes.html#reasons-to-run-a-rippled-server-in-stand-alone-mode), the server uses the value `true` for cases where it _would_ have broadcast the transaction.) The value `false` indicates the transaction was not broadcast to any other servers. [New in: rippled 1.5.0][] |
+| `broadcast`             | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates this transaction was broadcast to peer servers in the peer-to-peer XRP Ledger network. (Note: if the server has no peers, such as in [stand-alone mode][], the server uses the value `true` for cases where it _would_ have broadcast the transaction.) The value `false` indicates the transaction was not broadcast to any other servers. [New in: rippled 1.5.0][] |
 | `kept`                  | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates that the transaction was kept to be retried later. [New in: rippled 1.5.0][] |
 | `queued`                | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates the transaction was put in the [Transaction Queue](transaction-queue.html), which means it is likely to be included in a future ledger version. [New in: rippled 1.5.0][] |
 | `open_ledger_cost`      | String  | _(Omitted in sign-and-submit mode)_ The current [open ledger cost](transaction-cost.html#open-ledger-cost) before processing this transaction. Transactions with a lower cost are likely to be [queued](transaction-queue.html). [New in: rippled 1.5.0][] |
--- a/content/references/rippled-api/transaction-formats/transaction-common-fields.md
+++ b/content/references/rippled-api/transaction-formats/transaction-common-fields.md
@@ -7,7 +7,7 @@ Every transaction has the same set of common fields, plus additional fields base
 | `Account`            | String           | AccountID         | _(Required)_ The unique address of the [account](accounts.html) that initiated the transaction. |
 | `TransactionType`    | String           | UInt16            | _(Required)_ The type of transaction. Valid types include: `Payment`, `OfferCreate`, `OfferCancel`, `TrustSet`, `AccountSet`, `AccountDelete`, `SetRegularKey`, `SignerListSet`, `EscrowCreate`, `EscrowFinish`, `EscrowCancel`, `PaymentChannelCreate`, `PaymentChannelFund`, `PaymentChannelClaim`, and `DepositPreauth`. |
 | `Fee`                | String           | Amount            | _(Required; [auto-fillable][])_ Integer amount of XRP, in drops, to be destroyed as a cost for distributing this transaction to the network. Some transaction types have different minimum requirements. See [Transaction Cost][] for details. |
-| `Sequence`           | Number           | UInt32            | _(Required; [auto-fillable][])_ The [sequence number](basic-data-types.html#account-sequence) of the account sending the transaction. A transaction is only valid if the `Sequence` number is exactly 1 greater than the previous transaction from the same account. |
+| `Sequence`           | Number           | UInt32            | _(Required; [auto-fillable][])_ The [sequence number](basic-data-types.html#account-sequence) of the account sending the transaction. A transaction is only valid if the `Sequence` number is exactly 1 greater than the previous transaction from the same account. The special case `0` means the transaction is using a [Ticket](tickets.html) instead _(Requires the [TicketBatch amendment][] :not_enabled:)_. |
 | [`AccountTxnID`](#accounttxnid) | String | Hash256          | _(Optional)_ Hash value identifying another transaction. If provided, this transaction is only valid if the sending account's previously-sent transaction matches the provided hash. |
 | [`Flags`](#flags-field) | Number        | UInt32            | _(Optional)_ Set of bit-flags for this transaction. |
 | `LastLedgerSequence` | Number           | UInt32            | _(Optional; strongly recommended)_ Highest ledger index this transaction can appear in. Specifying this field places a strict upper limit on how long the transaction can wait to be validated or rejected. See [Reliable Transaction Submission](reliable-transaction-submission.html) for more details. |
@@ -15,6 +15,7 @@ Every transaction has the same set of common fields, plus additional fields base
 | [`Signers`](#signers-field) | Array     | Array             | _(Optional)_ Array of objects that represent a [multi-signature](multi-signing.html) which authorizes this transaction. |
 | `SourceTag`        | Number             | UInt32            | _(Optional)_ Arbitrary integer used to identify the reason for this payment, or a sender on whose behalf this transaction is made. Conventionally, a refund should specify the initial payment's `SourceTag` as the refund payment's `DestinationTag`. |
 | `SigningPubKey`    | String           | Blob              | _(Automatically added when signing)_ Hex representation of the public key that corresponds to the private key used to sign this transaction. If an empty string, indicates a multi-signature is present in the `Signers` field instead. |
+| `TicketSequence`   | Number           | UInt32            | _(Optional)_ The sequence number of the [ticket](tickets.html) to use in place of a `Sequence` number. If this is provided, `Sequence` must be `0`. Cannot be used with `AccountTxnID`. |
 | `TxnSignature`     | String           | Blob              | _(Automatically added when signing)_ The signature that verifies this transaction as originating from the account it says it is from. |

 [auto-fillable]: #auto-fillable-fields
@@ -26,12 +27,13 @@ Every transaction has the same set of common fields, plus additional fields base

 <!-- SPELLING_IGNORE: AccountTxnID -->

-The `AccountTxnID` field lets you chain your transactions together, so that a current transaction is not valid unless the previous one (by Sequence Number) is also valid and matches the transaction you expected.
+The `AccountTxnID` field lets you chain your transactions together, so that a current transaction is not valid unless the previous transaction sent from the same account has a specific [transaction hash][identifying hash].

-Unlike the `PreviousTxnID` field, which tracks the last transaction to _modify_ an account (regardless of sender), the `AccountTxnID` tracks the last transaction _sent by_ an account. To use `AccountTxnID`, you must first set the [`asfAccountTxnID`](accountset.html#accountset-flags) flag, so that the ledger keeps track of the ID for the account's previous transaction. (`PreviousTxnID`, by comparison, is always tracked.)
+Unlike the `PreviousTxnID` field, which tracks the last transaction to _modify_ an account (regardless of sender), the `AccountTxnID` tracks the last transaction _sent by_ an account. To use `AccountTxnID`, you must first enable the [`asfAccountTxnID`](accountset.html#accountset-flags) flag, so that the ledger keeps track of the ID for the account's previous transaction. (`PreviousTxnID`, by comparison, is always tracked.)

 One situation in which this is useful is if you have a primary system for submitting transactions and a passive backup system. If the passive backup system becomes disconnected from the primary, but the primary is not fully dead, and they both begin operating at the same time, you could potentially have serious problems like some transactions sending twice and others not at all. Chaining your transactions together with `AccountTxnID` ensures that, even if both systems are active, only one of them can submit valid transactions at a time.

+The `AccountTxnID` field cannot be used on transactions that use [Tickets](tickets.html) :not_enabled:. Transactions that use `AccountTxnID` cannot be placed in the [transaction queue](transaction-queue.html).



--- a/content/references/rippled-api/transaction-formats/transaction-results/tef-codes.md
+++ b/content/references/rippled-api/transaction-formats/transaction-results/tef-codes.md
@@ -22,6 +22,7 @@ These codes indicate that the transaction failed and was not included in a ledge
 | `tefMASTER_DISABLED`    | The transaction was signed with the account's master key, but the account has the `lsfDisableMaster` field set. |
 | `tefMAX_LEDGER`         | The transaction included a [`LastLedgerSequence`](reliable-transaction-submission.html#lastledgersequence) parameter, but the current ledger's sequence number is already higher than the specified value. |
 | `tefNO_AUTH_REQUIRED`  | The [TrustSet transaction][] tried to mark a trust line as authorized, but the `lsfRequireAuth` flag is not enabled for the corresponding account, so authorization is not necessary. |
+| `tefNO_TICKET`         | The transaction attempted to use a [Ticket](tickets.html), but the specified `TicketSequence` number does not exist in the ledger, and cannot be created in the future because it is earlier than the sender's current sequence number. |
 | `tefNOT_MULTI_SIGNING` | The transaction was [multi-signed](multi-signing.html), but the sending account has no SignerList defined. |
 | `tefPAST_SEQ`           | The sequence number of the transaction is lower than the current sequence number of the account sending the transaction. |
 | `tefTOO_BIG`            | The transaction would affect too many objects in the ledger. For example, this was an [AccountDelete transaction][] but the account to be deleted owns over 1000 objects in the ledger. |
--- a/content/references/rippled-api/transaction-formats/transaction-results/tem-codes.md
+++ b/content/references/rippled-api/transaction-formats/transaction-results/tem-codes.md
@@ -29,6 +29,7 @@ These codes indicate that the transaction was malformed, and cannot succeed acco
 | `temDST_IS_SRC`              | The transaction improperly specified a destination address as the `Account` sending the transaction. This includes trust lines (where the destination address is the `issuer` field of `LimitAmount`) and payment channels (where the destination address is the `Destination` field). |
 | `temDST_NEEDED`               | The transaction improperly omitted a destination. This could be the `Destination` field of a [Payment transaction][], or the `issuer` sub-field of the `LimitAmount` field fo a `TrustSet` transaction. |
 | `temINVALID`                   | The transaction is otherwise invalid. For example, the transaction ID may not be the right format, the signature may not be formed properly, or something else went wrong in understanding the transaction. |
+| `temINVALID_COUNT`            | The transaction includes a `TicketCount` field, but the number of Tickets specified is invalid. |
 | `temINVALID_FLAG`             | The transaction includes a [Flag](transaction-common-fields.html#flags-field) that does not exist, or includes a contradictory combination of flags. |
 | `temMALFORMED`                 | Unspecified problem with the format of the transaction. |
 | `temREDUNDANT`                 | The transaction would do nothing; for example, it is sending a payment directly to the sending account, or creating an offer to buy and sell the same currency from the same issuer. |
--- a/content/references/rippled-api/transaction-formats/transaction-results/ter-codes.md
+++ b/content/references/rippled-api/transaction-formats/transaction-results/ter-codes.md
@@ -15,6 +15,7 @@ These codes indicate that the transaction failed, but it could apply successfull
 | `terNO_RIPPLE`    | Used internally only. This code should never be returned. |
 | `terOWNERS`        | The transaction requires that account sending it has a nonzero "owners count", so the transaction cannot succeed. For example, an account cannot enable the [`lsfRequireAuth`](accountset.html#accountset-flags) flag if it has any trust lines or available offers. |
 | `terPRE_SEQ`      | The `Sequence` number of the current transaction is higher than the current sequence number of the account sending the transaction. |
+| `terPRE_TICKET`   | The transaction attempted to use a [Ticket](tickets.html), but the specified `TicketSequence` number does not exist in the ledger. However, the Ticket could still be created by another transaction. |
 | `terRETRY`         | Unspecified retriable error.                              |
 | `terQUEUED`        | The transaction met the load-scaled [transaction cost](transaction-cost.html) but did not meet the open ledger requirement, so the transaction has been queued for a future ledger. |

--- a/content/references/rippled-api/transaction-formats/transaction-types/escrowcancel.md
+++ b/content/references/rippled-api/transaction-formats/transaction-types/escrowcancel.md
@@ -24,7 +24,7 @@ Return escrowed XRP to the sender.
 | Field           | JSON Type | [Internal Type][] | Description                |
 |:----------------|:----------|:------------------|:---------------------------|
 | `Owner`         | String    | AccountID         | Address of the source account that funded the escrow payment. |
-| `OfferSequence` | Number    | UInt32            | Transaction sequence of [EscrowCreate transaction][] that created the escrow to cancel. |
+| `OfferSequence` | Number    | UInt32            | Transaction sequence (or [Ticket](tickets.html) :not_enabled: number) of [EscrowCreate transaction][] that created the escrow to cancel. |

 Any account may submit an EscrowCancel transaction.

--- a/content/references/rippled-api/transaction-formats/transaction-types/offercancel.md
+++ b/content/references/rippled-api/transaction-formats/transaction-types/offercancel.md
@@ -24,7 +24,7 @@ An OfferCancel transaction removes an Offer object from the XRP Ledger.

 | Field           | JSON Type | [Internal Type][] | Description                  |
 |:----------------|:----------|:------------------|:-----------------------------|
-| `OfferSequence` | Number    | UInt32            | The sequence number of a previous OfferCreate transaction. If specified, cancel any offer object in the ledger that was created by that transaction. It is not considered an error if the offer specified does not exist. |
+| `OfferSequence` | Number    | UInt32            | The sequence number (or [Ticket](tickets.html) :not_enabled: number) of a previous OfferCreate transaction. If specified, cancel any offer object in the ledger that was created by that transaction. It is not considered an error if the offer specified does not exist. |

 *Tip:* To remove an old offer and replace it with a new one, you can use an [OfferCreate transaction][] with an `OfferSequence` parameter, instead of using OfferCancel and another OfferCreate.

--- a/content/references/rippled-api/transaction-formats/transaction-types/ticketcreate.md
+++ b/content/references/rippled-api/transaction-formats/transaction-types/ticketcreate.md
@@ -0,0 +1,55 @@
+---
+html: ticketcreate.html
+funnel: Build
+doc_type: References
+supercategory: rippled API
+category: Transaction Formats
+subcategory: Transaction Types
+blurb: Set aside one or more sequence numbers as Tickets.
+parent: transaction-types.html
+---
+# TicketCreate
+
+[[Source]](https://github.com/ripple/rippled/blob/develop/src/ripple/app/tx/impl/CreateTicket.cpp "Source")
+
+_(Requires the [TicketBatch amendment][] :not_enabled:)_
+
+A TicketCreate transaction sets aside one or more [sequence numbers][Sequence Number] as [Tickets](tickets.html).
+
+## Example {{currentpage.name}} JSON
+
+```json
+{
+    "TransactionType": "TicketCreate",
+    "Account": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn",
+    "Fee": "10",
+    "Sequence": 381,
+    "TicketCount": 10
+}
+```
+
+{% include '_snippets/tx-fields-intro.md' %}
+<!--{# fix md highlighting_ #}-->
+
+| Field            | JSON Type        | [Internal Type][] | Description        |
+|:-----------------|:-----------------|:------------------|:-------------------|
+| `TicketCount`    | Number           | UInt32            | How many Tickets to create. This must be a positive number and cannot cause the account to own more than 250 Tickets after executing this transaction. |
+
+If the transaction cannot create _all_ of the requested Tickets (either due to the 250-Ticket limit or the [owner reserve](reserves.html)), it fails and creates no Tickets. To look up how many Tickets an account currently owns, use the [account_info method][] and check the `account_data.TicketCount` field.
+
+**Tip:** This transaction increases the sending account's [sequence number][Sequence Number] by the number of tickets created (`TicketCount`). This is the only transaction that increases an account's sequence number by more than 1.
+
+## Error Cases
+
+In addition to errors that can occur for all transactions, {{currentpage.name}} transactions can result in the following [transaction result codes](transaction-results.html):
+
+| Error Code                | Description                                      |
+|:--------------------------|:-------------------------------------------------|
+| `temINVALID_COUNT`        | The `TicketCount` field is invalid. It must be an integer from 1 to 250. |
+| `tecDIR_FULL`             | This transaction would cause the account to own more than the limit of 250 Tickets at a time, or more than the maximum number of ledger objects in general. |
+| `tecINSUFFICIENT_RESERVE` | The sending account does not have enough XRP to meet the [owner reserve](reserves.html) of all the requested Tickets. |
+
+<!--{# common link defs #}-->
+{% include '_snippets/rippled-api-links.md' %}
+{% include '_snippets/tx-type-links.md' %}
+{% include '_snippets/rippled_versions.md' %}