From 9ed7120a79688513ef56639054b72c12bc36e8a8 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 28 Jan 2019 18:34:09 -0800 Subject: [PATCH 1/2] Known Amendments: slight rewordings for two amendments that are new in 1.2.0 --- content/news/known-amendments.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/news/known-amendments.md b/content/news/known-amendments.md index 9cee9bae1c..62e6b16f8f 100644 --- a/content/news/known-amendments.md +++ b/content/news/known-amendments.md @@ -329,9 +329,9 @@ The fix1623 amendment has no effect on [CheckCash transactions][] for a fixed am Fixes a bug in [auto-bridging](autobridging.html) that can leave a dry offer in the XRP Ledger. A dry offer is an offer that, if crossed, cannot yield any funds. -Without this fix, the dry offer remains on the ledger and uses up [reserves](reserves.html) in the offer owner's directory without providing any benefit to the owner. Another offer crossing of the right type and quality can remove the dry offer. However, if the required offer crossing type and quality are rare, it may take a while for the dry offer to be removed. +Without this fix, the dry offer remains on the ledger and counts toward its owner's [reserve requirement](reserves.html#owner-reserves) without providing any benefit to the owner. Another offer crossing of the right type and quality can remove the dry offer. However, if the required offer crossing type and quality are rare, it may take a while for the dry offer to be removed. -With this amendment enabled, the XRP Ledger removes these dry offers. +With this amendment enabled, the XRP Ledger removes these dry offers when they're matched in auto-bridging. ## Flow @@ -405,7 +405,7 @@ Reduces the [owner reserve](reserves.html#owner-reserves) counted against your X Without this amendment, the owner reserve for a SignerList ranges from 15 to 50 XRP, depending on the number of signers in the list. -With this amendment enabled, the owner reserve for a SignerList is 5 XRP, regardless of the number of signers. To receive the reduced reserve, you must wait for this amendment to be enabled and then use the [SignerListSet transaction](signerlistset.html) to create a SignerList, or replace or remove a SignerList that you created before the MultiSignReserve amendment was enabled. +With this amendment enabled, the owner reserve for a new SignerList is 5 XRP, regardless of the number of signers. The reserve requirement for previously-created SignerList objects remains unchanged. To reduce the reserve requirement of SignerList objects created before this amendment was enabled, use a [SignerListSet transaction](signerlistset.html) to replace the SignerList after this amendment has been enabled. (The replacement can be identical to the previous version.) ## OwnerPaysFee From 2f6195bc8fd205eec369643859e16625ea3112ae Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 28 Jan 2019 18:49:15 -0800 Subject: [PATCH 2/2] Update recently updated: known amendments for 1.2.0 --- dactyl-config.yml | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/dactyl-config.yml b/dactyl-config.yml index 665aa029f3..12fbfa5a1f 100644 --- a/dactyl-config.yml +++ b/dactyl-config.yml @@ -45,6 +45,8 @@ targets: github_forkurl: https://github.com/ripple/ripple-dev-portal github_branch: master recently_updated: + - html: known-amendments.html + date: 2019-01-28 - html: transaction-malleability.html date: 2019-01-14 - html: ledger-history.html @@ -53,12 +55,6 @@ targets: date: 2019-01-14 - html: configure-online-deletion.html date: 2019-01-14 - - html: configure-advisory-deletion.html - date: 2019-01-14 - - html: configure-full-history.html - date: 2019-01-14 - - html: list-your-exchange-on-xrp-charts.html - date: 2019-01-11 # Data API target for porting changes to the README in the upstream repo # Intended for use in markdown (--md) mode.