tecINSUFFICIENT_RESERVE: remove mention of tecUNFUNDED

This commit is contained in:
mDuo13
2017-04-22 00:24:17 -07:00
parent 7cbe4f21b6
commit 8131e8409e
2 changed files with 2 additions and 2 deletions

View File

@@ -1422,7 +1422,7 @@ These codes indicate that the transaction failed, but it was applied to a ledger
| `tecFROZEN` | 137 | The [OfferCreate transaction][] failed because one or both of the assets involved are subject to a [global freeze](concept-freeze.html). |
| `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 or `tecUNFUNDED`. See [SignerLists and Reserves](reference-ledger-format.html#signerlists-and-reserves) for more information. |
| `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. |
| `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`.) |

View File

@@ -2514,7 +2514,7 @@
<tr>
<td align="left"><code>tecINSUFFICIENT_RESERVE</code></td>
<td align="left">141</td>
<td align="left">The transaction would increase the <a href="concept-reserves.html">reserve requirement</a> higher than the sending account's balance. <a href="#signerlistset">SignerListSet</a>, <a href="#paymentchannelcreate">PaymentChannelCreate</a>, <a href="#paymentchannelfund">PaymentChannelFund</a>, and <a href="#escrowcreate">EscrowCreate</a> can return this error code or <code>tecUNFUNDED</code>. See <a href="reference-ledger-format.html#signerlists-and-reserves">SignerLists and Reserves</a> for more information.</td>
<td align="left">The transaction would increase the <a href="concept-reserves.html">reserve requirement</a> higher than the sending account's balance. <a href="#signerlistset">SignerListSet</a>, <a href="#paymentchannelcreate">PaymentChannelCreate</a>, <a href="#paymentchannelfund">PaymentChannelFund</a>, and <a href="#escrowcreate">EscrowCreate</a> can return this error code. See <a href="reference-ledger-format.html#signerlists-and-reserves">SignerLists and Reserves</a> for more information.</td>
</tr>
<tr>
<td align="left"><code>tecINTERNAL</code></td>