Network Health & Validator Intelligence

Amendment ID	2BF037D90E1B676B17592A8AF55E88DB465398B4B597AE46EECEE1399AB05699
Status	Open for Voting
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

This amendment ensures that reward shares for cross-chain transactions are always rounded down. This preserves the original intended behavior.

Without this amendment, the XChainBridge amendment has an incompatibility with the fixUniversalNumber amendment. When those two amendments are both enabled, the Number type may be used for some intermediate calculations of token amounts. In some cases, values that used to round down instead are rounded to nearest, which alters the intended rounding behavior for reward shares in cross-chain transactions.

This amendment restores the intended rounding behavior. It has no effect unless both the XChainBridge and fixUniversalNumber amendments are also enabled.

Amendment ID	894646DD5284E97DECFE6674A6D6152686791C4A95F8C132CCA9BAF9E5812FB6
Status	Obsolete
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

Allows multiple transactions to be bundled into a batch that's processed all together. Standard: XLS-56

Amendment ID	267624F8F744C4A4F1B5821A7D54410BCEBABE987F0172EE89E5FC4B6EDBC18A
Status	Obsolete
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

This amendment fixes an issue where inner transactions of a Batch transaction would be flagged as having valid signatures. Since inner transactions aren't signed directly, they should never have valid signatures.

Amendment ID	81BD2619B6B3C8625AC5D0BC01DE17F06C3F0AB95C7C87C93715B87A4FD240D8
Status	Open for Voting
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

Creates a structure for aggregating assets from multiple depositors. This is intended to be used with the on-chain Lending Protocol.

New ledger entry types:

• Vault entry

New transactions:

• VaultClawback transaction
• VaultCreate transaction
• VaultDelete transaction
• VaultDeposit transaction
• VaultSet transaction
• VaultWithdraw transaction

New API methods:

• vault_info method

Specification: XLS-65.

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 (for example, between Mainnet and a sidechain). Standards draft: XLS-0038 Cross-Chain Bridge.

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.

Amendment ID	565B90CA1AB2B9D42208ED10884188C64F9E19083DECB9634AAF06EB03299509
Status	Open for Voting
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

The Lending Protocol enables on-chain, fixed-term, uncollateralized loans using pooled funds from a Single Asset Vault. This implementation relies on off-chain underwriting and risk management to assess the creditworthiness of borrowers, but offers configurable, peer-to-peer loans.

Specification: XLS-66.

Amendment ID	AE6AB9028EEB7299EBB03C7CBCC3F2A4F5FBE00EA28B8223AA3118A0B436C1C5
Status	Obsolete
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

Allows accounts to delegate some permissions to other accounts. Specification: XLS-75.

Amendment ID	0285B7E5E08E1A8E4C15636F0591D87F73CB6A7B6452A932AD72BBC8E5D1CBE3
Status	Obsolete
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

This amendment fixes an off-by-one error that occurred in some corner cases when determining which NFTokenPage a NFToken object belongs on. It also adjusts the constraints of NFTokenPage invariant checks, so that certain error cases fail with a suitable error code such as tecNO_SUITABLE_TOKEN_PAGE instead of failing with a tecINVARIANT_FAILED error code.

This amendment has no effect unless the NonFungibleTokensV1 amendment is enabled. This amendment is obsolete because its effects are included as part of NonFungibleTokensV1_1.

Amendment ID	36799EA497B1369B170805C078AEFE6188345F9B3E324C21E9CA3FF574E3C3D6
Status	Obsolete
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

This amendment fixes a bug in the NonFungibleTokensV1 amendment code where NFTs could be traded for negative amounts of money. Without this fix, users could place and accept an offer to buy or sell a NFToken for a negative amount of money, which resulted in the person "buying" the NFT also receiving money from the "seller". With this amendment, NFT offers for negative amounts are considered invalid.

This amendment has no effect unless the NonFungibleTokensV1 amendment is enabled. This amendment is obsolete because its effects are included as part of NonFungibleTokensV1_1.

Amendment ID	3C43D9A973AA4443EF3FC38E42DD306160FBFFDAB901CD8BAA15D09F2597EB87
Status	Obsolete
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

Adds native support for non-fungible tokens. Standards Draft: XLS-20d.

There are several known issues with this amendment including one that can cause tecINVARIANT_FAILED errors to appear in the ledger. It has been replaced by the NonFungibleTokensV1_1 amendment.

This amendment adds 5 new transaction types:

• NFTokenAcceptOffer
• NFTokenBurn
• NFTokenCancelOffer
• NFTokenCreateOffer
• NFTokenMint

It also adds 2 new ledger object types:

• NFTokenOffer object
• NFTokenPage object

Additionally, it modifies the AccountRoot object type to add 3 new optional fields: MintedNFTokens, BurnedNFTokens, and NFTokenMinter.

It also modifies the AccountSet transaction type to allow you to set the NFTokenMinter field.

Amendment ID	86E83A7D2ECE3AD5FA87AB2195AE015C950469ABF0B72EAACED318F74886AE90
Status	Obsolete
Default Vote (Latest stable release)	No
Pre-amendment functionality retired?	No

This amendment was intended to add support for several types of crypto-conditions from the official crypto-conditions specification for use in EscrowCreate and EscrowFinish transactions.

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.