The announcement presented a document outlining the benefits of the new version and the improvements implemented. According to the document, the new version ensures a better and more flexible performance of the library that now has new methods to access the rippled API (server software that powers XRP Ledger).
The published document describes several new methods including:
- Three new methods, including: request (), hasNextPage () and requestNextPage (), have been added to access the rippled APIs.
- A prepareTransaction () method has been added to prepare an unprocessed txJSON element.
- The new version will allow you to specify XRP amounts in drops. Two conversion methods were provided, including: xrpToDrops () and dropsToXrp ().
- A new getTransaction () method has been added. This includes a property by channelChanges name that will provide details of a particular payment channel.
In addition, the published document also provided general details about the corrections made to the team on the previous version. The announcement confirmed that the amounts in XRP and the drops "have been verified for validity". In addition, the team imposed a maximum commission limit, which "if passed will cause the library a validation error".
Head of the Ripple C ++ development team, Nick Bougalis commented on the updates stating: "The library has a configurable" Maximum tariff limit "to prevent programmers from accidentally specifying too high a commission. set to 2 XRP, which is several orders of magnitude higher than the rate required to pay for a transaction … if you really want to spend more than 2 XRPs in commissions, you can simply ignore the limit in the RippleAPI constructor. "  Source link