Blog
/
2020
/
fixCheckThreading and fixPayChanRecipientOwnerDir Amendments Lost Majority
Last updated

fixCheckThreading and fixPayChanRecipientOwnerDir Amendments Lost Majority

On 2019-01-11, the fixCheckThreading and fixPayChanRecipientOwnerDir amendments lost the support of several validators, causing those amendments' support to fall below the 80% threshold for approval. (EnableAmendment LostMajority transactions: fixCheckThreading, fixPayChanRecipientOwnerDir.) As a result, these amendments are no longer expected to become enabled on 2020-01-18, and their status depends on more validators to resume voting in favor of the amendments.

For more information on the Amendment process, see Amendments in the XRP Ledger Dev Portal.

Ripple's Statement

Ripple is one of several validators in the recommended list that are currently voting against enabling the fixCheckThreading and fixPayChanRecipientOwnerDir amendments. Ripple's statement on the validator voting is as follows:

We would like to see these amendments enabled before Deletable Accounts because they fix some edge cases that could be more confusing with Deletable Accounts. However, we have seen a slower than usual uptake of the new core XRP Ledger server version, with almost half the network still using version 1.3.1 instead of the newer 1.4.0. Additionally, the announcement about these amendments getting a majority was the first time it was reported that fixPayChanRecipientOwnerDir would result in a backwards-incompatible change in the behavior in the API for Payment Channels. Since neither amendment fixes an immediate bug, and enabling either one would amendment block everyone who's still on v1.3.1, we decided to temporarily have our validators vote against the amendments with the hopes that it would give people more time to upgrade.

All XRP Ledger servers should continue to operate as normal for now. If any new amendment gains (or regains) a majority of 80% of validators, it must hold that majority for a continuous period of two weeks to become enabled. However, the following actions are strongly recommended to prepare for the likelihood of future amendments:

  • If you operate a rippled server, please upgrade to version 1.4.0.

    Caution: Upgrading to v1.4.0 may take longer than usual because of SQL database cleanup the server performs the first time after upgrading. For more information, see XRP Ledger version 1.4.0 Upgrade Advisory.

  • If you use the XRP Ledger APIs to list payment channels, such as using the account_channels method, be aware that the fixPayChanRecipientOwnerDir amendment affects the results of this API. Specifically, the method will list newly-created channels for which the specified account is the recipient. Previously, this method only listed channels for which the account is the sender. (Existing payment channels for which the specified account is the recipient will continue not to appear in the results. Only new channels, created after the amendment becomes enabled, are affected.)

  • If you use the XRP Ledger, you may want to read about how Deletable Accounts work in case the changes affect your use of the XRP Ledger. The Deletable Accounts amendment is open for voting, so it may become available within a few weeks depending on how the network's trusted validators vote. (See also: the Deletable Accounts Draft Specification.)

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.

Other resources:

Previous page
Next page