Three Amendments Expected on 2021-04-08
Two bug-fixing amendments to the XRP Ledger protocol and one amendment that improves robustness of consensus, all introduced in
rippled v1.6.0, have gained support from a majority of trusted validators: fix1781, fixAmendmentMajorityCalc, and HardenedValidations. Currently, they are expected to become enabled on 2021-04-08. Any of these amendments that continue to have the continuous support of at least 80% of trusted validators will become enabled on the scheduled date.
Server operators should be sure to upgrade
rippled before this date.
If you operate a
rippledserver, you must upgrade to version 1.6.0 or higher by 2021-04-08, for service continuity. Version 1.7.0 is recommended.
If you have code that submits XRP Ledger payments, make sure your code correctly handles the
temBAD_PATH_LOOPerror code. As a
temcode, this error only occurs on transaction submission and does not appear in validated ledger data.
Impact of Not Upgrading
If you operate a
rippled server but don’t upgrade to version 1.6.0 (or higher) by 2021-04-08, when the amendments are expected to become enabled, then your server will become 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
If none of the amendments becomes enabled, then your server will not become amendment blocked and should continue to operate.
For instructions on upgrading
rippled on supported platforms, see Install
Fixes a bug where certain XRP endpoints were not checked when detecting circular paths.
Without this amendment, it is possible to have a payment path where the input to the path is XRP, and an intermediate path step also outputs XRP. This is a "loop" payment, and the payment engine typically disallows such paths because they can have different results when executed forward compared to backwards.
With this amendment, those payments fail with the
temBAD_PATH_LOOP result code instead.
Fixes a bug that could cause an amendment to achieve a majority and later activate with support of slightly less than 80% of trusted validators due to rounding semantics.
Without this amendment, the minimum threshold for amendment activation is any value that rounds to 204/256 of trusted validators, which depends on the number of trusted validators at the time. For example, an amendment could activate with exactly 28 out of 36 validators (approximately 77.8%). With this amendment, the actual minimum number of validators needed is never less than 80% of trusted validators.
Allows validators to include a new optional field in their validations to attest to the hash of the latest ledger that the validator considers to be fully validated. The consensus process can use this information to increase the robustness of consensus.
Learn, ask questions, and discuss
To receive email updates whenever there are important releases or changes to the XRP Ledger server software subscribe to the ripple-server Google Group.
Related documentation is available in the XRP Ledger Dev Portal, including detailed example API calls and web tools for API testing.