DepositPreauth reference changes (draft, missing examples)

content/references/rippled-api/ledger-data-formats/ledger-object-types/depositpreauth.md

@@ -0,0 +1,41 @@
+# DepositPreauth
+[[Source]<br>](https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/impl/LedgerFormats.cpp#L172 "Source")
+<!--{# TODO: change from develop to master when 1.1.0 is released #}-->
+
+A `DepositPreauth` object tracks a preauthorization from one account to another. [DepositPreauth transactions][] create these objects.
+
+This has no effect on processing of transactions unless the account that provided the preauthorization requires [Deposit Authorization](depositauth.html). In that case, the account that was preauthorized can send payments and other transactions directly to the account that provided the preauthorization. Preauthorizations are one-directional, and have no effect on payments going the opposite direction.
+
+## Example {{currentpage.name}} JSON
+
+```json
+TODO
+```
+
+## {{currentpage.name}} Fields
+
+A `DepositPreauth` object has the following fields:
+
+| Field               | JSON Type        | [Internal Type][] | Description     |
+|:--------------------|:-----------------|:------------------|:----------------|
+| `LedgerEntryType`   | String           | UInt16            | The value `0x0070`, mapped to the string `DepositPreauth`, indicates that this is a DepositPreauth object. |
+| `Account` | String           | Account           | The account that granted the preauthorization. (The destination of the preauthorized payments.) |
+| `Authorize` | String | Account | The account that received the preauthorization. (The sender of the preauthorized payments.) |
+| `Flags`             | Number           | UInt32            |  A bit-map of boolean flags. No flags are defined for Checks, so this value is always `0`. |
+| `OwnerNode`         | String           | UInt64            | A hint indicating which page of the sender's 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 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. |
+
+
+## DepositPreauth ID Format
+
+The ID of a `DepositPreauth` object is the [SHA-512Half][] of the following values, concatenated in order:
+
+* The DepositPreauth space key (`0x0070`)
+* The AccountID of the owner of this object (the sender of the [DepositPreauth transaction][] that created this object; in other words, the one that granted the preauthorization)
+* The AccountID of the preauthorized account (the `Authorized` field of the [DepositPreauth transaction][] that created this object; in other words, the one that received the preauthorization)
+
+<!--{# common link defs #}-->
+{% include '_snippets/rippled-api-links.md' %}			
+{% include '_snippets/tx-type-links.md' %}			
+{% include '_snippets/rippled_versions.md' %}

content/references/rippled-api/transaction-formats/transaction-results/tem-codes.md

@@ -25,6 +25,7 @@ These codes indicate that the transaction was malformed, and cannot succeed acco
 | `temBAD_SIGNATURE`            | The signature to authorize this transaction is either missing, or formed in a way that is not a properly-formed signature. (See [tecNO_PERMISSION](tec-codes.html) for the case where the signature is properly formed, but not authorized for this account.) |
 | `temBAD_SRC_ACCOUNT`         | The `Account` on whose behalf this transaction is being sent (the "source account") is not a properly-formed [account](accounts.html) address. |
 | `temBAD_TRANSFER_RATE`       | The [`TransferRate` field of an AccountSet transaction](accountset.html#transferrate) is not properly formatted or out of the acceptable range. |
+| `temCANNOT_PREAUTH_SELF`     | The sender of the [DepositPreauth trasaction][] was also specified as the account to preauthorize. You cannot preauthorize yourself. |
 | `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. |

content/references/rippled-api/transaction-formats/transaction-types/depositpreauth.md

@@ -0,0 +1,39 @@
+# DepositPreauth
+[[Source]<br>](https://github.com/ripple/rippled/blob/develop/src/ripple/app/tx/impl/DepositPreauth.cpp "Source") <!--{# TODO: change from develop to master when 1.1.0 is released #}-->
+
+_Requires the [DepositPreauth amendment](known-amendments.html#depositpreauth)._
+
+A DepositPreauth transaction gives another account pre-approval to deliver payments to the sender of this transaction. This is only useful if the sender of this transaction is using (or plans to use) [Deposit Authorization](depositauth.html).
+
+**Tip:** You can use this transaction to preauthorize certain counterparties before you enable Deposit Authorization. This may be useful to ensure a smooth transition from not requiring deposit authorization to requiring it.
+
+## Example {{currentpage.name}} JSON
+
+```json
+TODO
+```
+
+{% include '_snippets/tx-fields-intro.md' %}
+<!--{# fix md highlighting_ #}-->
+
+
+| Field         | JSON Type | [Internal Type][] | Description |
+|:--------------|:----------|:------------------|:-----|
+| `Authorize`   | String    | AccountID         | _(Optional)_ The XRP Ledger address of the sender to preauthorize. |
+| `Unauthorize` | String    | AccountID         | _(Optional)_ The XRP Ledger address of a sender whose preauthorization should be revoked. |
+
+You must provide _either_ `Authorize` or `Unauthorize`, but not both.
+
+This transaction has the following limitations:
+
+- An account cannot preauthorize (or unauthorize) its own address. Attempting to do so fails with the result [`temCANNOT_PREAUTH_SELF`](tem-codes.html).
+- Attempting to preauthorize an account which is already preauthorized fails with the result [`tecDUPLICATE`](tec-codes.html).
+- Attempting to unauthorize an account which is not preauthorized fails with the result [`tecNO_ENTRY`](tec-codes.html).
+- Attempting to preauthorize an address that is not funded in the ledger fails with the result [`tecNO_TARGET`](tec-codes.html).
+- Adding authorization adds a [DepositPreauth object](depositpreauth-object.html) to the ledger, which counts toward the [owner reserve requirement](reserves.html#owner-reserves). If the sender of the transaction does not have enough XRP to pay for the increased reserve, the transaction fails with the result [`tecINSUFFICIENT_RESERVE`](tec-codes.html). If the sender of the account is already at the maximum number of owned objects, the transaction fails with the result [`tecDIR_FULL`](tec-codes.html).
+
+
+<!--{# common link defs #}-->
+{% include '_snippets/rippled-api-links.md' %}
+{% include '_snippets/tx-type-links.md' %}
+{% include '_snippets/rippled_versions.md' %}