If you want more content like this, please visit ripple.com.
This notice is for all validator operators, and may be useful for gateways that intend to use tick sizes.
A majority of trusted validators voted to enable the TickSize amendment, which is scheduled to become active on the protocol on Tuesday, 2017-02-21. The amendment changes the way RCL offers are ranked in order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.
For a detailed look into the TickSize feature, see the original TickSize announcement.
If you operate a
rippledserver and accept secure client connections, then you should upgrade to
rippledversion 0.50.2 immediately. If you operate a
rippledserver but do not accept secure client connections, then you should upgrade to version 0.50.0 by Tuesday, 2017-02-21, for service continuity.
If you are a gateway issuer, then please review documentation for the TickSize amendment to determine what tick size is appropriate for your issuing asset.
If you are a market maker and have algorithmic trading bots, then please review documentation for the TickSize amendment to update your trading system to check the tick size for a given issuer.
If you have backend software, which constructs and submits transactions related to the issuing of assets on the Ripple network, then please review documentation for the TickSize amendment to adapt it for correct usage.
For more information, see the following articles in the Ripple Developer Portal:
- Offer Preference – How offers are ranked with and without TickSize.
- AccountSet transaction – How to configure a TickSize.
To continue receiving updates about the rippled server, please subscribe to the Ripple Server Google Group: https://groups.google.com/forum/#!forum/ripple-server
Please visit ripple.com for more information.