The repair1578 modification to the XRP Ledger, launched in
rippled v1.2.0, has gained help from a majority of trusted validators. Presently, it’s anticipated to turn into enabled on 2019-03-23.
The fixTakerDryOfferRemoval modification to the XRP Ledger has additionally gained help from a majority of trusted validators. Presently, it’s anticipated to turn into enabled on 2019-04-02.
So long as the amendments proceed to have the help of not less than 80% of trusted validators repeatedly, they may turn into enabled on the anticipated dates.
Modifications the end result codes returned by two transaction varieties:
- Modifications the OfferCreate transaction to return a brand new end result code,
tecKILLED, if the supply used the
tfFillOrKillflag and was killed. With out this modification, the supply is killed however the transaction result’s
- Modifications the TrustSet transaction to fail with
tecNO_PERMISSIONif it tries to allow the NoRipple flag however can not as a result of the belief line has a unfavorable stability. With out this modification, the transaction doesn’t allow the NoRipple flag, however the transaction result’s
Fixes a bug in auto-bridging that may depart a dry supply within the XRP Ledger. A dry supply is a proposal that, if crossed, can not yield any funds.
With out this repair, the dry supply stays on the ledger and counts towards its proprietor’s reserve requirement with out offering any profit to the proprietor. One other supply crossing of the fitting kind and high quality can take away the dry supply. Nevertheless, if the required supply crossing kind and high quality are uncommon, it might take some time for the dry supply to be eliminated.
With this modification enabled, the XRP Ledger removes these dry presents after they’re matched in auto-bridging.
If you happen to function a
rippledserver, you have to improve to model 1.2.0 (or increased) by 2019-03-23, for service continuity. The newest model of
rippled, model 1.2.2, is really useful.
If you happen to use the XRP Ledger for what you are promoting, be certain you might be able to deal with the brand new response codes that could be returned after the modification turns into enabled.
Impression of Not Upgrading
If you happen to function a
rippled server however don’t improve to model 1.2.0 (or increased) by 2019-03-23, when the repair1578 modification is anticipated to turn into enabled, then your server will turn into modification blocked, which means that your server:
- Can’t decide the validity of a ledger
- Can’t submit or course of transactions
- Doesn’t take part within the consensus course of
- Doesn’t vote on future amendments
- May depend on doubtlessly invalid knowledge
If the repair1578 modification doesn’t turn into enabled, then your server is not going to turn into modification blocked till the fixTakerDryOfferRemoval modification turns into enabled on 2019-04-02. If neither modification turns into enabled, older server variations ought to proceed to function with out turning into modification blocked. Nevertheless, it’s nonetheless really useful that you simply replace to
rippled model 1.2.2 or increased.
For directions on upgrading
rippled on supported platforms, see Set up
Study, ask questions, and focus on
Associated documentation is out there within the XRP Ledger Dev Portal, together with detailed instance API calls and net instruments for API testing.