Amendments: update status of EnforceInvariants & fix1373 in detailed descriptions

This commit is contained in:
mDuo13
2017-07-19 08:38:37 -07:00
parent 0518a3b8e5
commit d7da391d6a
2 changed files with 5 additions and 5 deletions

View File

@@ -370,7 +370,7 @@ TrustSetAuth
<tbody>
<tr>
<td align="left">DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF</td>
<td align="left">In voting; expected 2017-06-29</td>
<td align="left">Enabled</td>
</tr>
</tbody>
</table>
@@ -452,7 +452,7 @@ TrustSetAuth
<tbody>
<tr>
<td align="left">42EEA5E28A97824821D4EF97081FE36A54E9593C6E4F20CBAE098C69D2E072DC</td>
<td align="left">In voting; expected 2017-06-29</td>
<td align="left">Enabled</td>
</tr>
</tbody>
</table>

View File

@@ -146,7 +146,7 @@ Although this amendment is enabled, it has no effect unless the [SusPay](#suspay
| Amendment ID | Status |
|:-----------------------------------------------------------------|:--------|
| DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF | In voting; expected 2017-06-29 |
| DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF | Enabled |
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.
@@ -203,7 +203,7 @@ Fixes a minor bug in transaction processing that causes some payments to fail wh
| Amendment ID | Status |
|:-----------------------------------------------------------------|:----------|
| 42EEA5E28A97824821D4EF97081FE36A54E9593C6E4F20CBAE098C69D2E072DC | In voting; expected 2017-06-29 |
| 42EEA5E28A97824821D4EF97081FE36A54E9593C6E4F20CBAE098C69D2E072DC | Enabled |
Fixes a minor bug in transaction processing that causes failures when trying to prepare certain [payment paths](concept-paths.html) for processing. As a result, payments could not use certain paths that should have been valid but were invalidly prepared. Without this amendment, those payments are forced to use less-preferable paths or may even fail.