The DepositPreauth and fix1515 amendments, added in
rippled v1.1.0, became enabled on the XRP Ledger today, 2018-10-09.
- If you operate a
rippledserver, you should upgrade to version 1.1.0 (or higher) immediately.
For instructions on upgrading
rippled on supported platforms, see Updating
rippled on supported platforms.
Impact of Not Upgrading
If you operate a
rippled server on a version older than 1.1.0, then your server is now amendment blocked, meaning that your server:
- Cannot determine the validity of a ledger
- Cannot submit or process transactions
- Does not participate in the consensus process
- Does not vote on future amendments
- Could rely on potentially invalid data
The DepositPreauth amendment provides users of deposit authorization with a way to preauthorize specific senders so those senders are allowed to send payments directly.
The amendment adds:
- A new transaction type, DepositPreauth, for adding or removing preauthorization.
- A DepositPreauth ledger object type for tracking preauthorizations from one account to another.
- A JSON-RPC command,
deposit_authorized, to query whether an account is authorized to send payments directly to another.
This amendment also changes the behavior of cross-currency Payments from an account to itself when that account requires deposit authorization. Without this amendment, those payments always fail with the code tecNO_PERMISSION. With this amendment, those payments succeed as they would with Deposit Authorization disabled.
The fix1515 amendment changes how Payment transactions consume offers to remove a minor difference in how payment processing and offer processing consume liquidity.
Without the amendment, payment processing gives up on using a particular path if the transaction would consume over 2000 offers from the same order book at the same exchange rate. In this case, the payment does not use the liquidity from those offers, and does not consider that order book’s remaining liquidity when attempting to complete the payment.
With this amendment, if any transaction processes over 1000 offers at the same exchange rate, the transaction consumes the liquidity from the first 1000 offers, then does not consider that order book’s remaining liquidity when attempting to complete the payment.
In both cases, transaction processing can still complete by using liquidity from other paths or exchange rates.
Related documentation is available in the XRP Ledger Dev Portal, including detailed example API calls and web tools for API testing.
- The Ripple Forum
- The Ripple Dev Blog
- Ripple Technical Services: firstname.lastname@example.org
- XRP Chat