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

Order amendment details alphabetically

Browse Source
This commit is contained in:
Amarantha Kulkarni
2024-04-12 14:04:31 -07:00
parent 0b832b27bc
commit ba247bb8e1
1 changed files with 130 additions and 140 deletions
Download Patch File Download Diff File Expand all files Collapse all files

270
resources/known-amendments.md
View File

@@ -112,111 +112,6 @@ The following is a list of known [amendments](../docs/concepts/networks-and-serv
## Details about Known Amendments
### fixAMMOverflowOffer
[fixAMMOverflowOffer]: #fixammoverflowoffer
| Amendment | fixAMMOverflowOffer |
|:-------------|:--------------|
| Amendment ID | 12523DF04B553A0B1AD74F42DDB741DE8DC06A03FC089A0EF197E2A87F1D8107 |
| Status | Enabled |
| Default Vote (Latest stable release) | Yes |
| Pre-amendment functionality retired? | No |
This amendment fixes the improper handling of large synthetic AMM offers in the payment engine. Due to the importance of this fix, the default vote in the source code has been set to YES.
### fixInnerObjTemplate
[fixInnerObjTemplate]: #fixinnerobjtemplate
| Amendment | fixInnerObjTemplate |
|:-------------|:--------------|
| Amendment ID | C393B3AEEBF575E475F0C60D5E4241B2070CC4D0EB6C4846B1A07508FAEFC485 |
| Status | Enabled |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
This amendment fixes an issue with accessing the AMM `sfTradingFee` and `sfDiscountedFee` fields in the inner objects of `sfVoteEntry` and `sfAuctionSlot`.
Currently, the inner object template isn't set upon object creation. If the object contains an `soeDEFAULT` field and is initially set to the default value, accessing the field results in a `tefEXCEPTION` error in some circumstances. This amendment adds an `STObject` constructor overload that includes an additional boolean argument to set the inner object template.
### fixNFTokenReserve
[fixNFTokenReserve]: #fixnftokenreserve
| Amendment | fixNFTokenReserve |
|:-------------|:--------------|
| Amendment ID | 03BDC0099C4E14163ADA272C1B6F6FABB448CC3E51F522F978041E4B57D9158C |
| Status | Enabled |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
This amendment adds a check to the `NFTokenAcceptOffer` transactor to see if the `OwnerCount` changes. If it does, it makes an additional check that the reserve requirement is met for the updated owner count.
### fixDisallowIncomingV1
[fixDisallowIncomingV1]: #fixdisallowincomingv1
| Amendment | fixDisallowIncomingV1 |
|:-------------|:--------------|
| Amendment ID | 15D61F0C6DB6A2F86BCF96F1E2444FEC54E705923339EC175BD3E517C8B3FF91 |
| Status | Enabled |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
This amendment fixes an issue with approving trustlines after a user enables the `lsfDisallowIncomingTrustline` flag on their account.
To recreate this issue:
1. An issuer sets `asfRequireAuth` on their account.
2. The user sets `asfDisallowIncomingTrustline` on their account.
3. The user submits a `SetTrust` transaction to the issuer.
4. The issuer is unable to authorize the trustline.
With this amendment, the issuer can now authorize the trustline.
This amendment has no effect unless the [DisallowIncoming][] amendment is enabled.
### fixFillOrKill
[fixFillOrKill]: #fixfillorkill
| Amendment | fixFillOrKill |
|:-------------|:--------------|
| Amendment ID | 3318EA0CF0755AF15DAC19F2B5C5BCBFF4B78BDD57609ACCAABE2C41309B051A |
| Status | Enabled |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
This amendment fixes an issue introduced in the `FlowCross` amendment. Offers with the `tfFillOrKill` flag set and `tfSell` not set will fail if the exchange rate on the offer is better than, but doesn't exactly match, the order book rate.
This amendment enables the payment engine to properly handle this scenario and allow offers to cross.
This amendment has no effect unless the [FlowCross][] amendment is enabled.
### DID
[DID]: #did
| Amendment | DID |
|:-------------|:----|
| Amendment ID | DB432C3A09D9D5DFC7859F39AE5FF767ABC59AED0A9FB441E83B814D8946C109 |
| Status | Open for Voting |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
Adds to the ledger Decentralized Identifier (DID) functionality that conforms to the [World Wide Web Consortium](https://www.w3.org/press-releases/2022/did-rec/) standard. DIDs provide a digital identity, not dependent on a centralized authority and controlled by the DID subject.
Adds new transactions:
- DIDDelete - Delete the DID associated with your XRPL account.
- DIDSet - Create a new DID or update an existing one.
Adds a new `DID` ledger entry type.
Adds several new transaction result codes.
### AMM
[AMM]: #amm
@@ -300,38 +195,6 @@ Clawback is disabled by default. To use clawback, you must set the `lsfAllowTrus
See [Clawback](../docs/concepts/tokens/fungible-tokens/clawing-back-tokens.md) for details on this amendment.
### XChainBridge
[XChainBridge]: #xchainbridge
| Amendment | XChainBridge |
|:-------------|:-----------------|
| Amendment ID | C98D98EE9616ACD36E81FDEB8D41D349BF5F1B41DD64A0ABC1FE9AA5EA267E9C |
| Status | Open for Voting |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
Adds cross-chain bridges, enabling the transfer of digital assets between networks, such as Mainnet and a sidechain.
Adds new transactions:
- XChainAccountCreateCommit - Create a new account for a witness server to submit transactions on an issuing chain..
- XChainAddAccountCreateAttestation - Provide an attestation that an account was created for a witness server to use.
- XChainAddClaimAttestation - Provide an attestation that assets were locked on a locking chain.
- XChainClaim - Claim assets on the destination chain.
- XChainCommit - Locks assets on the locking chain.
- XChainCreateBridge - Create a bridge ledger object.
- XChainCreateClaimID - Create a new cross-chain claim ID that is used for a cross-chain transfer.
- XChainModifyBridge - Modify the parameters of a bridge.
Adds new ledger entry types:
- Bridge - A single cross-chain bridge that connects the XRP Ledger with another blockchain.
- XChainOwnedClaimID - A cross-chain transfer of value that includes information of the account on the source chain that locks or burns the funds on the source chain.
- XChainOwnedCreateAccountClaimID - Collects attestations for creating an account via a cross-chain transfer.
Adds several new transaction result codes.
### CryptoConditions
[CryptoConditions]: #cryptoconditions
@@ -360,6 +223,28 @@ This amendment was intended to add support for several types of crypto-condition
However, the amendment was added to `rippled` v0.60.0 before implementation was complete. As a result, this amendment ID refers to incomplete code which does almost nothing. Modifying the existing amendment to add support for other crypto-conditions would cause a conflict with old versions of the amendment already in released software. If a future release adds support for additional crypto-conditions, it must use a new and different amendment ID.
### DID
[DID]: #did
| Amendment | DID |
|:-------------|:----|
| Amendment ID | DB432C3A09D9D5DFC7859F39AE5FF767ABC59AED0A9FB441E83B814D8946C109 |
| Status | Open for Voting |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
Adds to the ledger Decentralized Identifier (DID) functionality that conforms to the [World Wide Web Consortium](https://www.w3.org/press-releases/2022/did-rec/) standard. DIDs provide a digital identity, not dependent on a centralized authority and controlled by the DID subject.
Adds new transactions:
- DIDDelete - Delete the DID associated with your XRPL account.
- DIDSet - Create a new DID or update an existing one.
Adds a new `DID` ledger entry type.
Adds several new transaction result codes.
### DeletableAccounts
[DeletableAccounts]: #deletableaccounts
@@ -725,6 +610,20 @@ Without this amendment, it is possible to have a [payment path](../docs/concepts
With this amendment, those payments fail with the [`temBAD_PATH_LOOP` result code](../docs/references/protocol/transactions/transaction-results/tem-codes.md) instead.
### fixAMMOverflowOffer
[fixAMMOverflowOffer]: #fixammoverflowoffer
| Amendment | fixAMMOverflowOffer |
|:-------------|:--------------|
| Amendment ID | 12523DF04B553A0B1AD74F42DDB741DE8DC06A03FC089A0EF197E2A87F1D8107 |
| Status | Enabled |
| Default Vote (Latest stable release) | Yes |
| Pre-amendment functionality retired? | No |
This amendment fixes the improper handling of large synthetic AMM offers in the payment engine. Due to the importance of this fix, the default vote in the source code has been set to YES.
### fixAmendmentMajorityCalc
[fixAmendmentMajorityCalc]: #fixamendmentmajoritycalc
@@ -755,6 +654,63 @@ Changes the way Checks transactions affect account metadata, so that Checks are
Without this amendment, Checks transactions ([CheckCreate][], [CheckCash][], and [CheckCancel][]) only update the account history of the sender. With this amendment, those transactions affect both the sending and receiving accounts. This amendment has no effect unless the [Checks amendment](#checks) is also enabled.
### fixDisallowIncomingV1
[fixDisallowIncomingV1]: #fixdisallowincomingv1
| Amendment | fixDisallowIncomingV1 |
|:-------------|:--------------|
| Amendment ID | 15D61F0C6DB6A2F86BCF96F1E2444FEC54E705923339EC175BD3E517C8B3FF91 |
| Status | Enabled |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
This amendment fixes an issue with approving trustlines after a user enables the `lsfDisallowIncomingTrustline` flag on their account.
To recreate this issue:
1. An issuer sets `asfRequireAuth` on their account.
2. The user sets `asfDisallowIncomingTrustline` on their account.
3. The user submits a `SetTrust` transaction to the issuer.
4. The issuer is unable to authorize the trustline.
With this amendment, the issuer can now authorize the trustline.
This amendment has no effect unless the [DisallowIncoming][] amendment is enabled.
### fixFillOrKill
[fixFillOrKill]: #fixfillorkill
| Amendment | fixFillOrKill |
|:-------------|:--------------|
| Amendment ID | 3318EA0CF0755AF15DAC19F2B5C5BCBFF4B78BDD57609ACCAABE2C41309B051A |
| Status | Enabled |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
This amendment fixes an issue introduced in the `FlowCross` amendment. Offers with the `tfFillOrKill` flag set and `tfSell` not set will fail if the exchange rate on the offer is better than, but doesn't exactly match, the order book rate.
This amendment enables the payment engine to properly handle this scenario and allow offers to cross.
This amendment has no effect unless the [FlowCross][] amendment is enabled.
### fixInnerObjTemplate
[fixInnerObjTemplate]: #fixinnerobjtemplate
| Amendment | fixInnerObjTemplate |
|:-------------|:--------------|
| Amendment ID | C393B3AEEBF575E475F0C60D5E4241B2070CC4D0EB6C4846B1A07508FAEFC485 |
| Status | Enabled |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
This amendment fixes an issue with accessing the AMM `sfTradingFee` and `sfDiscountedFee` fields in the inner objects of `sfVoteEntry` and `sfAuctionSlot`.
Currently, the inner object template isn't set upon object creation. If the object contains an `soeDEFAULT` field and is initially set to the default value, accessing the field results in a `tefEXCEPTION` error in some circumstances. This amendment adds an `STObject` constructor overload that includes an additional boolean argument to set the inner object template.
### fixMasterKeyAsRegularKey
[fixMasterKeyAsRegularKey]: #fixmasterkeyasregularkey
@@ -823,6 +779,20 @@ The amendment also introduces a new account deletion restriction. An account can
**Warning:** This is a **breaking change** for projects & tools relying on their own locally computed NFTokenID for minted tokens. If you have code to calculate NFTokenIDs, you must update it to match the new fomula. For an example of how to do so with backwards compatibility, see this [well known reference implementation in JavaScript](https://gist.github.com/N3TC4T/a20fb528931ed009ebdd708be4938748?permalink_comment_id=4738760#gistcomment-4738760).
### fixNFTokenReserve
[fixNFTokenReserve]: #fixnftokenreserve
| Amendment | fixNFTokenReserve |
|:-------------|:--------------|
| Amendment ID | 03BDC0099C4E14163ADA272C1B6F6FABB448CC3E51F522F978041E4B57D9158C |
| Status | Open for Voting |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
This amendment adds a check to the `NFTokenAcceptOffer` transactor to see if the `OwnerCount` changes. If it does, it makes an additional check that the reserve requirement is met for the updated owner count.
### fixNonFungibleTokensV1_2
[fixNonFungibleTokensV1_2]: #fixnonfungibletokensv1_2
@@ -1379,13 +1349,33 @@ With this amendment enabled, a `TrustSet` transaction with [`tfSetfAuth` enabled
[XChainBridge]: #xchainbridge
| Amendment | XChainBridge |
|:-------------|:-------------|
|:-------------|:-----------------|
| Amendment ID | C98D98EE9616ACD36E81FDEB8D41D349BF5F1B41DD64A0ABC1FE9AA5EA267E9C |
| Status | In Development |
| Status | Open for Voting |
| Default Vote (Latest stable release) | No |
| Pre-amendment functionality retired? | No |
Adds "cross-chain bridges" for synchronizing assets between different networks, such as Mainnet and a sidechain. Standards draft: [XLS-38d Cross-Chain Bridge](https://github.com/XRPLF/XRPL-Standards/blob/master/XLS-38d-XChainBridge/README.md).
Adds cross-chain bridges, enabling the transfer of digital assets between networks, such as Mainnet and a sidechain.
Standards draft: [XLS-38d Cross-Chain Bridge](https://github.com/XRPLF/XRPL-Standards/blob/master/XLS-38d-XChainBridge/README.md).
Adds new transactions:
- XChainAccountCreateCommit - Create a new account for a witness server to submit transactions on an issuing chain..
- XChainAddAccountCreateAttestation - Provide an attestation that an account was created for a witness server to use.
- XChainAddClaimAttestation - Provide an attestation that assets were locked on a locking chain.
- XChainClaim - Claim assets on the destination chain.
- XChainCommit - Locks assets on the locking chain.
- XChainCreateBridge - Create a bridge ledger object.
- XChainCreateClaimID - Create a new cross-chain claim ID that is used for a cross-chain transfer.
- XChainModifyBridge - Modify the parameters of a bridge.
Adds new ledger entry types:
- Bridge - A single cross-chain bridge that connects the XRP Ledger with another blockchain.
- XChainOwnedClaimID - A cross-chain transfer of value that includes information of the account on the source chain that locks or burns the funds on the source chain.
- XChainOwnedCreateAccountClaimID - Collects attestations for creating an account via a cross-chain transfer.
Adds several new transaction result codes.
### XRPFees