ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-26 14:45:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

rippled 0.70.0: corrections; add new result codes

Browse Source
This commit is contained in:
mDuo13
2017-06-15 14:04:34 -07:00
parent 1ae928ef54
commit 5a81943cc8
9 changed files with 37 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
concept-amendments.html
View File

@@ -374,8 +374,8 @@ TrustSetAuth
</tr>
</tbody>
</table>
<p>Adds sanity checks to transaction processing to ensure that certain conditions are always met. This provides an extra layer of protection against bugs in transaction processing that could otherwise cause exploits and vulnerabilities in the Ripple Consensus Ledger. Ripple expects to add more invariant checks in future versions of <code>rippled</code> without additional amendments.</p>
<p>Introduces two new transaction error codes, <code>tecINVARIANT_FAILED</code> and <code>tefINVARIANT_FAILED</code>. Changes transaction processing to add the new checks. Adds a configuration option to disable invariant-checking.</p>
<p>Adds sanity checks to transaction processing to ensure that certain conditions are always met. This provides an extra, independent layer of protection against bugs in transaction processing that could otherwise cause exploits and vulnerabilities in the Ripple Consensus Ledger. Ripple expects to add more invariant checks in future versions of <code>rippled</code> without additional amendments.</p>
<p>Introduces two new transaction error codes, <code>tecINVARIANT_FAILED</code> and <code>tefINVARIANT_FAILED</code>. Changes transaction processing to add the new checks.</p>
<p>Examples of invariant checks:</p>
<ul>
<li>The total amount of XRP destroyed by a transaction must match the <a href="concept-transaction-cost.html">transaction cost</a> exactly.</li>

3
concept-paths.html
View File

@@ -228,7 +228,7 @@
<tr>
<td align="left"><code>issuer</code></td>
<td align="left">String - Address</td>
<td align="left"><em>(Optional)</em> If the path step represents changing currencies through an order book, this field indicates the issuer of the new currency. If omitted in a step with a non-XRP <code>currency</code>, the previous step of the path defines the issuer. MUST be omitted if the <code>currency</code> is XRP. MUST NOT be provided if this step specifies the <code>account</code> field.</td>
<td align="left"><em>(Optional)</em> If present, this path step represents changing currencies and this address defines the issuer of the new currency. If omitted in a step with a non-XRP <code>currency</code>, a previous step of the path defines the issuer. If present when <code>currency</code> is omitted, indicates a path step that uses an order book between same-named currencies with different issuers. MUST be omitted if the <code>currency</code> is XRP. MUST NOT be provided if this step specifies the <code>account</code> field.</td>
</tr>
<tr>
<td align="left"><code>type</code></td>
@@ -247,6 +247,7 @@
<li><code>account</code> by itself</li>
<li><code>currency</code> by itself</li>
<li><code>currency</code> and <code>issuer</code> as long as the <code>currency</code> is not XRP</li>
<li><code>issuer</code> by itself</li>
</ul>
<p>Any other use of <code>account</code>, <code>currency</code>, and <code>issuer</code> fields in a path step is invalid.</p>
<p>The <code>type</code> field, used for the binary serialization of a path set, is actually constructed through bitwise operations on a single integer. The bits are defined as follows:</p>

4
content/concept-amendments.md
View File

@@ -148,9 +148,9 @@ Although this amendment is enabled, it has no effect unless the [SusPay](#suspay
|:-----------------------------------------------------------------|:--------|
| DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF | In voting; expected 2017-06-29 |
Adds sanity checks to transaction processing to ensure that certain conditions are always met. This provides an extra layer of protection against bugs in transaction processing that could otherwise cause exploits and vulnerabilities in the Ripple Consensus Ledger. Ripple expects to add more invariant checks in future versions of `rippled` without additional amendments.
Adds sanity checks to transaction processing to ensure that certain conditions are always met. This provides an extra, independent layer of protection against bugs in transaction processing that could otherwise cause exploits and vulnerabilities in the Ripple Consensus Ledger. Ripple expects to add more invariant checks in future versions of `rippled` without additional amendments.
Introduces two new transaction error codes, `tecINVARIANT_FAILED` and `tefINVARIANT_FAILED`. Changes transaction processing to add the new checks. Adds a configuration option to disable invariant-checking.
Introduces two new transaction error codes, `tecINVARIANT_FAILED` and `tefINVARIANT_FAILED`. Changes transaction processing to add the new checks.
Examples of invariant checks:

5
content/concept-paths.md
View File

@@ -72,7 +72,7 @@ A path set is an array. Each member of the path set is another array that repres
|:-----------|:-----------------------|:---------------------------------------|
| `account` | String - Address | _(Optional)_ If present, this path step represents rippling through the specified address. MUST NOT be provided if this step specifies the `currency` or `issuer` fields. |
| `currency` | String - Currency Code | _(Optional)_ If present, this path step represents changing currencies through an order book. The currency specified indicates the new currency. MUST NOT be provided if this step specifies the `account` field. |
| `issuer` | String - Address | _(Optional)_ If the path step represents changing currencies through an order book, this field indicates the issuer of the new currency. If omitted in a step with a non-XRP `currency`, the previous step of the path defines the issuer. MUST be omitted if the `currency` is XRP. MUST NOT be provided if this step specifies the `account` field. |
| `issuer` | String - Address | _(Optional)_ If present, this path step represents changing currencies and this address defines the issuer of the new currency. If omitted in a step with a non-XRP `currency`, a previous step of the path defines the issuer. If present when `currency` is omitted, indicates a path step that uses an order book between same-named currencies with different issuers. MUST be omitted if the `currency` is XRP. MUST NOT be provided if this step specifies the `account` field. |
| `type` | Integer | **DEPRECATED** _(Optional)_ An indicator of which other fields are present. |
| `type_hex` | String | **DEPRECATED**: _(Optional)_ A hexadecimal representation of the `type` field. |
@@ -81,11 +81,10 @@ In summary, the following combination of fields are valid, optionally with `type
- `account` by itself
- `currency` by itself
- `currency` and `issuer` as long as the `currency` is not XRP
- `issuer` by itself
Any other use of `account`, `currency`, and `issuer` fields in a path step is invalid.
The `type` field, used for the binary serialization of a path set, is actually constructed through bitwise operations on a single integer. The bits are defined as follows:
| Value (Hex) | Value (Decimal) | Description |

2
content/reference-rippled.md
View File

@@ -3497,7 +3497,7 @@ Each member of the `queue_data` array represents one transaction in the queue. S
| `max_spend_drops` | String | _(May be omitted)_ The maximum amount of XRP, [in drops](#specifying-currency-amounts), this transaction could send or destroy. |
| `seq` | Integer | _(May be omitted)_ The [Sequence Number][] of this transaction. |
If the request specified `"owner_funds": true` and expanded transactions, the response has a field `owner_funds` in the `metaData` object of each [OfferCreate-type transaction](reference-transaction-format.html#offercreate). The purpose of this field is to make it easier to track the [funding status of offers](reference-transaction-format.html#lifecycle-of-an-offer) with each new validated ledger. This field is defined slightly different than the version of this field in [Order Book subscription streams](#order-book-streams):
If the request specified `"owner_funds": true` and expanded transactions, the response has a field `owner_funds` in the `metaData` object of each [OfferCreate-type transaction](reference-transaction-format.html#offercreate). The purpose of this field is to make it easier to track the [funding status of offers](reference-transaction-format.html#lifecycle-of-an-offer) with each new validated ledger. This field is defined slightly differently than the version of this field in [Order Book subscription streams](#order-book-streams):
| `Field` | Value | Description |
|:--------------|:-------|:----------------------------------------------------|

5
content/reference-transaction-format.md
View File

@@ -1374,6 +1374,7 @@ These codes indicate that the transaction failed and was not included in a ledge
| `tefEXCEPTION` | While processing the transaction, the server entered an unexpected state. This may be caused by unexpected inputs, for example if the binary data for the transaction is grossly malformed. If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues) to get it fixed. |
| `tefFAILURE` | Unspecified failure in applying the transaction. |
| `tefINTERNAL` | When trying to apply the transaction, the server entered an unexpected state. If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues) to get it fixed. |
| `tefINVARIANT_FAILED` | An invariant check failed when trying to claim the [transaction cost](concept-transaction-cost.html). Requires the [EnforceInvariants amendment](concept-amendments.html#enforceinvariants). If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues). |
| `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`](#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 trustline as authorized, but the `lsfRequireAuth` flag is not enabled for the corresponding account, so authorization is not necessary. |
@@ -1414,6 +1415,7 @@ These codes indicate that the transaction failed, but it was applied to a ledger
| Code | Value | Explanation |
|:---------------------------|:------|:----------------------------------------|
| `tecCLAIM` | 100 | Unspecified failure, with transaction cost destroyed. |
| `tecCRYPTOCONDITION_ERROR` | 146 | This [EscrowCreate][] or [EscrowFinish][] transaction contained a malformed or mismatched crypto-condition. |
| `tecDIR_FULL` | 121 | The address sending the transaction cannot own any more objects in the ledger. |
| `tecDST_TAG_NEEDED` | 143 | The [Payment](#payment) transaction omitted a destination tag, but the destination account has the `lsfRequireDestTag` flag enabled. [New in: rippled 0.28.0][] |
| `tecFAILED_PROCESSING` | 105 | An unspecified error occurred when processing the transaction. |
@@ -1421,7 +1423,8 @@ These codes indicate that the transaction failed, but it was applied to a ledger
| `tecINSUF_RESERVE_LINE` | 122 | The transaction failed because the sending account does not have enough XRP to create a new trust line. (See: [Reserves](concept-reserves.html)) This error occurs when the counterparty already has a trust line in a non-default state to the sending account for the same currency. (See `tecNO_LINE_INSUF_RESERVE` for the other case.) |
| `tecINSUF_RESERVE_OFFER` | 123 | The transaction failed because the sending account does not have enough XRP to create a new Offer. (See: [Reserves](concept-reserves.html)) |
| `tecINSUFFICIENT_RESERVE` | 141 | The transaction would increase the [reserve requirement](concept-reserves.html) higher than the sending account's balance. [SignerListSet][], [PaymentChannelCreate][], [PaymentChannelFund][], and [EscrowCreate][] can return this error code. See [SignerLists and Reserves](reference-ledger-format.html#signerlists-and-reserves) for more information. |
| `tecINTERNAL` | 144 | Unspecified internal error, with transaction cost applied. This error code should not normally be returned. |
| `tecINTERNAL` | 144 | Unspecified internal error, with transaction cost applied. This error code should not normally be returned. If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues). |
| `tecINVARIANT_FAILED` | An invariant check failed when trying to execute this transaction. Requires the [EnforceInvariants amendment](concept-amendments.html#enforceinvariants). If you can reproduce this error, please [report an issue](https://github.com/ripple/rippled/issues). |
| `tecNEED_MASTER_KEY` | 142 | This transaction tried to cause changes that require the master key, such as [disabling the master key or giving up the ability to freeze balances](#accountset-flags). [New in: rippled 0.28.0][] |
| `tecNO_ALTERNATIVE_KEY` | 130 | The transaction tried to remove the only available method of [authorizing transactions](#authorizing-transactions). This could be a [SetRegularKey transaction][] to remove the regular key, a [SignerListSet transaction][] to delete a SignerList, or an [AccountSet transaction][] to disable the master key. (Prior to `rippled` 0.30.0, this was called `tecMASTER_DISABLED`.) |
| `tecNO_AUTH` | 134 | The transaction failed because it needs to add a balance on a trust line to an account with the `lsfRequireAuth` flag enabled, and that trust line has not been authorized. If the trust line does not exist at all, `tecNO_LINE` occurs instead. |

2
reference-rippled.html
View File

@@ -4463,7 +4463,7 @@ rippled ledger current
</tr>
</tbody>
</table>
<p>If the request specified <code>"owner_funds": true</code> and expanded transactions, the response has a field <code>owner_funds</code> in the <code>metaData</code> object of each <a href="reference-transaction-format.html#offercreate">OfferCreate-type transaction</a>. The purpose of this field is to make it easier to track the <a href="reference-transaction-format.html#lifecycle-of-an-offer">funding status of offers</a> with each new validated ledger. This field is defined slightly different than the version of this field in <a href="#order-book-streams">Order Book subscription streams</a>:</p>
<p>If the request specified <code>"owner_funds": true</code> and expanded transactions, the response has a field <code>owner_funds</code> in the <code>metaData</code> object of each <a href="reference-transaction-format.html#offercreate">OfferCreate-type transaction</a>. The purpose of this field is to make it easier to track the <a href="reference-transaction-format.html#lifecycle-of-an-offer">funding status of offers</a> with each new validated ledger. This field is defined slightly differently than the version of this field in <a href="#order-book-streams">Order Book subscription streams</a>:</p>
<table>
<thead>
<tr>

16
reference-transaction-format.html
View File

@@ -2372,6 +2372,10 @@
<td align="left">When trying to apply the transaction, the server entered an unexpected state. If you can reproduce this error, please <a href="https://github.com/ripple/rippled/issues">report an issue</a> to get it fixed.</td>
</tr>
<tr>
<td align="left"><code>tefINVARIANT_FAILED</code></td>
<td align="left">An invariant check failed when trying to claim the <a href="concept-transaction-cost.html">transaction cost</a>. Requires the <a href="concept-amendments.html#enforceinvariants">EnforceInvariants amendment</a>. If you can reproduce this error, please <a href="https://github.com/ripple/rippled/issues">report an issue</a>.</td>
</tr>
<tr>
<td align="left"><code>tefMASTER_DISABLED</code></td>
<td align="left">The transaction was signed with the account's master key, but the account has the <code>lsfDisableMaster</code> field set.</td>
</tr>
@@ -2486,6 +2490,11 @@
<td align="left">Unspecified failure, with transaction cost destroyed.</td>
</tr>
<tr>
<td align="left"><code>tecCRYPTOCONDITION_ERROR</code></td>
<td align="left">146</td>
<td align="left">This <a href="#escrowcreate">EscrowCreate</a> or <a href="#escrowfinish">EscrowFinish</a> transaction contained a malformed or mismatched crypto-condition.</td>
</tr>
<tr>
<td align="left"><code>tecDIR_FULL</code></td>
<td align="left">121</td>
<td align="left">The address sending the transaction cannot own any more objects in the ledger.</td>
@@ -2523,7 +2532,12 @@
<tr>
<td align="left"><code>tecINTERNAL</code></td>
<td align="left">144</td>
<td align="left">Unspecified internal error, with transaction cost applied. This error code should not normally be returned.</td>
<td align="left">Unspecified internal error, with transaction cost applied. This error code should not normally be returned. If you can reproduce this error, please <a href="https://github.com/ripple/rippled/issues">report an issue</a>.</td>
</tr>
<tr>
<td align="left"><code>tecINVARIANT_FAILED</code></td>
<td align="left">An invariant check failed when trying to execute this transaction. Requires the <a href="concept-amendments.html#enforceinvariants">EnforceInvariants amendment</a>. If you can reproduce this error, please <a href="https://github.com/ripple/rippled/issues">report an issue</a>.</td>
<td align="left"></td>
</tr>
<tr>
<td align="left"><code>tecNEED_MASTER_KEY</code></td>

16
tutorial-listing-xrp.html
View File

@@ -519,12 +519,12 @@ XRP Balances</i></b></td>
<tr>
<td>Charlie</td>
<td><s>100,000</s>
<br/>50,000</td>
<br>50,000</br></td>
<td></td>
<td>789</td>
<td>Charlie</td>
<td><s>0</s>
<br/>50,000</td>
<br>50,000</br></td>
</tr>
<tr>
<td></td>
@@ -553,7 +553,7 @@ XRP Balances</i></b></td>
<tr>
<td>Alpha Cold</td>
<td><s>0</s>
<br/>50,000</td>
<br>50,000</br></td>
<td></td>
<td></td>
<td></td>
@@ -599,7 +599,7 @@ Off-Ledger Balances</i></b></td>
<td></td>
<td>Hot</td>
<td><s>0</s>
<br/>80,000</td>
<br>80,000</br></td>
</tr>
<tr>
<td>456</td>
@@ -624,7 +624,7 @@ Off-Ledger Balances</i></b></td>
<td></td>
<td>Cold</td>
<td><s>180,000</s>
<br/>100,000</td>
<br>100,000</br></td>
</tr>
<tr>
<td></td>
@@ -690,7 +690,7 @@ Off-Ledger Balances</i></b></td>
<td></td>
<td>Hot</td>
<td><s>80,000</s>
<br/>55,000</td>
<br>55,000</br></td>
</tr>
<tr>
<td>Edward</td>
@@ -717,12 +717,12 @@ Off-Ledger Balances</i></b></td>
<tr>
<td>Charlie RCL</td>
<td><s>50,000</s>
<br/>75,000</td>
<br>75,000</br></td>
<td></td>
<td>789</td>
<td>Charlie</td>
<td><s>50,000</s>
<br/>25,000</td>
<br>25,000</br></td>
<td></td>
<td>Cold</td>
<td>100,000</td>