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

Add fix1513 and update status of Checks and DepositAuth

Browse Source
This commit is contained in:
mDuo13
2018-02-26 17:30:31 -08:00
parent c32382e59e
commit b146dcee86
1 changed files with 16 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
content/reference-amendments.md
View File

@@ -1,18 +1,18 @@
# Known Amendments
[[Source]<br>](https://github.com/ripple/rippled/blob/master/src/ripple/app/main/Amendments.cpp "Source")
<!--{# TODO: after 0.90.0 releases, change to https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/impl/Feature.cpp #}-->
[[Source]<br>](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/Feature.cpp "Source")
The following is a comprehensive list of all known amendments and their status on the production XRP Ledger:
| Name | Introduced | Status |
|:--------------------------|:-----------|:------------------------------------|
| [fix1513][] | v0.90.0 | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [FlowCross][] | v0.70.0 | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [SHAMapV2][] | v0.33.0 | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [Checks][] | TBD | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [CryptoConditionsSuite][] | TBD | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [DepositAuth][] | TBD | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [OwnerPaysFee][] | TBD | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [Tickets][] | TBD | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [Checks][] | v0.90.0 | [Expected: 2018-03-15](https://ripple.com/dev-blog/rippled-version-0-90-0/ "BADGE_BLUE") |
| [DepositAuth][] | v0.90.0 | [Expected: 2018-03-15](https://ripple.com/dev-blog/rippled-version-0-90-0/ "BADGE_BLUE") |
| [fix1201][] | v0.80.0 | [Enabled: 2017-11-14](https://xrpcharts.ripple.com/#/transactions/B1157116DDDDA9D9B1C4A95C029AC335E05DB052CECCC5CA90118A4D46C77C5E "BADGE_GREEN") |
| [fix1512][] | v0.80.0 | [Enabled: 2017-11-14](https://xrpcharts.ripple.com/#/transactions/63F69F59BEFDC1D79DBF1E4060601E05960683AA784926FB74BC55074C4F6647 "BADGE_GREEN") |
| [fix1523][] | v0.80.0 | [Enabled: 2017-11-14](https://xrpcharts.ripple.com/#/transactions/97FD0E35654F4B6714010D3CBBAC4038F60D64AD0292693C28A1DF4B796D8469 "BADGE_GREEN") |
@@ -52,7 +52,6 @@ This amendment also changes the OfferCreate transaction to return `tecEXPIRED` w
**Caution:** This amendment is [in development](https://github.com/ripple/rippled/pull/2245) and is expected for `rippled` v0.90.0.
## CryptoConditions
[CryptoConditions]: #cryptoconditions
@@ -63,7 +62,6 @@ This amendment also changes the OfferCreate transaction to return `tecEXPIRED` w
Although this amendment is enabled, it has no effect unless the [SusPay](#suspay) amendment is also enabled. Ripple does not expect SusPay to become enabled. Instead, Ripple plans to incorporate crypto-conditions in the [Escrow](#escrow) amendment.
## CryptoConditionsSuite
[CryptoConditionsSuite]: #cryptoconditionssuite
@@ -76,7 +74,6 @@ Implements several types of crypto-conditions from the official [crypto-conditio
**Caution:** This amendment is still [in development](https://github.com/ripple/rippled/pull/2170). The version from `rippled` v0.60.0 to present does not implement the full functionality.
## DepositAuth
[DepositAuth]: #depositauth
@@ -95,7 +92,6 @@ Also fixes a bug in the EscrowCreate and PaymentChannelCreate transactions where
**Caution:** This amendment is [in development](https://github.com/ripple/rippled/pull/2239) and is expected for `rippled` v0.90.0.
## EnforceInvariants
[EnforceInvariants]: #enforceinvariants
@@ -116,7 +112,6 @@ Examples of invariant checks:
- There cannot be a trust line for XRP.
## Escrow
[Escrow]: #escrow
@@ -129,8 +124,6 @@ Replaces the [SusPay](#suspay) and [CryptoConditions](#cryptoconditions) amendme
Provides "suspended payments" for XRP for escrow within the XRP Ledger, including support for [Interledger Protocol Crypto-Conditions](https://tools.ietf.org/html/draft-thomas-crypto-conditions-02). Creates a new ledger object type for suspended payments and new transaction types to create, execute, and cancel suspended payments.
## FeeEscalation
[FeeEscalation]: #feeescalation
@@ -163,7 +156,6 @@ Correctly implements a limit on [transfer fees](concept-transfer-fees.html) to a
With this amendment enabled, an [AccountSet][] transaction that attempts to set `TransferRate` higher than `2000000000` fails with the result code `temBAD_TRANSFER_RATE`. Any existing `TransferRate` which was set to a higher value under the previous rules continues to apply at the higher rate.
## fix1368
[fix1368]: #fix1368
@@ -198,6 +190,18 @@ Fixes a bug in transaction processing that causes some invalid [PaymentChannelCl
With this amendment, the transactions fail with a more appropriate result code, `temBAD_AMOUNT`, instead.
## fix1513
[fix1513]: #fix1513
| Amendment ID | Status |
|:-----------------------------------------------------------------|:----------|
| 67A34F2CF55BFC0F93AACD5B281413176FEE195269FA6D95219A2DF738671172 | Planned |
Fixes a bug that resulted in transaction processing not using new `STAmountCalcSwitchovers` code when the `FeeEscalation` amendment is enabled.
With this amendment, the new `STAmountCalcSwitchovers` code applies, which may cause slight changes to transaction processing due to calculation differences. Amounts may be rounded differently and offers may be executed in a different order as a result.
## fix1523
[fix1523]: #fix1523
@@ -210,7 +214,6 @@ Adds tracking by destination account to [escrows](concept-escrow.html). Without
With this amendment, new escrows are added to the [owner directories](reference-ledger-format.html#directorynode) of both the sender and receiver. This amendment also adds a new `DestinationNode` field to [Escrow ledger objects](reference-ledger-format.html#escrow), indicating which page of the destination's owner directory contains the escrow.
## fix1528
[fix1528]: #fix1528
@@ -223,7 +226,6 @@ Fixes a bug where validators could build consensus ledgers with different timest
This amendment changes how validators negotiate the close time of the consensus ledger so that they cannot reach a consensus on ledger contents but build ledger versions with different timestamps.
## Flow
[Flow]: #flow
@@ -236,7 +238,6 @@ Replaces the payment processing engine with a more robust and efficient rewrite
The Flow Engine also makes it easier to improve and expand the payment engine with further Amendments.
## FlowCross
[FlowCross]: #flowcross
@@ -251,7 +252,6 @@ Streamlines the offer crossing logic in the XRP Ledger's decentralized exchange.
- The new logic may delete more or fewer offers than the old logic. (This includes cases caused by differences in rounding and offers that were incorrectly removed as unfunded by the old logic.)
## FlowV2
[FlowV2]: #flowv2
@@ -262,7 +262,6 @@ Streamlines the offer crossing logic in the XRP Ledger's decentralized exchange.
This is a previous version of the [Flow](#flow) amendment. It was [rejected due to a bug](https://ripple.com/dev-blog/flowv2-amendment-vetoed/) and removed in version 0.33.0.
## MultiSign
[MultiSign]: #multisign
@@ -287,7 +286,6 @@ An address with a SignerList can disable the master key even if a regular key is
* `tefBAD_AUTH_MASTER`
## OwnerPaysFee
[OwnerPaysFee]: #ownerpaysfee
@@ -302,7 +300,6 @@ This Amendment requires the [Flow Amendment](#flow) to be enabled.
**Note:** An incomplete version of this amendment was introduced in v0.33.0 and removed in v0.80.0. (It was never enabled.) Ripple plans to re-add the amendment when the code is stable enough.
## PayChan
[PayChan]: #paychan
@@ -317,7 +314,6 @@ Creates three new transaction types: [PaymentChannelCreate][], [PaymentChannelCl
For more information, see the [Payment Channels Tutorial](tutorial-paychan.html).
## SHAMapV2
[SHAMapV2]: #shamapv2
@@ -330,7 +326,6 @@ Changes the hash tree structure that `rippled` uses to represent a ledger. The n
When this amendment is activated, the XRP Ledger will undergo a brief scheduled unavailability while the network calculates the changes to the hash tree structure. <!-- STYLE_OVERRIDE: will -->
## SortedDirectories
[SortedDirectories]: #sorteddirectories
@@ -343,8 +338,6 @@ Sorts the entries in [DirectoryNode ledger objects](reference-ledger-format.html
**Warning:** Older versions of `rippled` that do not know about this amendment may crash when they encounter a DirectoryNode sorted by the new rules. To avoid this problem, [upgrade](tutorial-rippled-setup.html#updating-rippled) to `rippled` version 0.80.0 or later.
## SusPay
[SusPay]: #suspay
@@ -355,7 +348,6 @@ Sorts the entries in [DirectoryNode ledger objects](reference-ledger-format.html
This amendment is currently enabled on the [Ripple Test Net](https://ripple.com/build/ripple-test-net/). In production, Ripple expects to enable similar functionality with the [Escrow](#escrow) amendment instead.
## Tickets
[Tickets]: #tickets
@@ -368,7 +360,6 @@ Introduces Tickets as a way to reserve a transaction sequence number for later e
**Caution:** This amendment is still in development.
## TickSize
[TickSize]: #ticksize
@@ -381,7 +372,6 @@ Changes the way [Offers](reference-transaction-format.html#lifecycle-of-an-offer
Introduces a `TickSize` field to accounts, which can be set with the [AccountSet transaction type](reference-transaction-format.html#accountset). If a currency issuer sets the `TickSize` field, the XRP Ledger truncates the exchange rate (ratio of funds in to funds out) of Offers to trade the issuer's currency, and adjusts the amounts of the Offer to match the truncated exchange rate. If only one currency in the trade has a `TickSize` set, that number of significant digits applies. When trading two currencies that have different `TickSize` values, whichever `TickSize` indicates the fewest significant digits applies. XRP does not have a `TickSize`.
## TrustSetAuth
[TrustSetAuth]: #trustsetauth