XRP News

fixTakerDryOfferRemoval is Now Available

If you want more content like this, please visit Ripple.com.


Top Cryptocurrency Hardware Wallets
Crypto Ledger (Check price) | KeepKey (Check price) | Ledger Nano (Check price) | Trezor (Check price)

As previously announced, the fixTakerDryOfferRemoval amendment became enabled on the XRP Ledger on 2019-04-02.

Action Required

  • If you operate a rippled server, you should upgrade to version 1.2.0 (or higher) immediately. Version 1.2.3 is recommended.

For instructions on upgrading rippled on supported platforms, see Install rippled.

Impact of Not Upgrading

If you operate a rippled server on a version older than 1.2.0, then your server has been amendment blocked since 2019-03-23, when the fix1578 amendment became enabled. If your server is amendment blocked, that means it:

  • 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

fixTakerDryOfferRemoval Summary

Fixes a bug in auto-bridging that can leave a dry offer in the XRP Ledger. A dry offer is an offer that, if crossed, cannot yield any funds.

Without this fix, the dry offer remains on the ledger and counts toward its owner’s reserve requirement without providing any benefit to the owner. Another offer crossing of the right type and quality can remove the dry offer. However, if the required offer crossing type and quality are rare, it may take a while for the dry offer to be removed.

With this amendment enabled, the XRP Ledger removes these dry offers when they’re matched in auto-bridging.

Learn, ask questions, and discuss

Related documentation is available in the XRP Ledger Dev Portal, including detailed example API calls and web tools for API testing.

Other resources:

The post fixTakerDryOfferRemoval is Now Available appeared first on Ripple.



Please visit Ripple.com for more information.

Leave a Reply

Your email address will not be published. Required fields are marked *