Source: gopixa – Shutterstock
- Ripple Xpring Development Division announces progress on its multi-language software development kit (SDK) and launches new version of the Xpring SDK.
- The software development kit adds functionality that supports an interledger protocol (ILP).
Ripple’s development division, Xpring, announced the release of a feature that supports the interledger protocol (ILP) for its software development kit, Xpring SDK. In October last year, according to the announcement, Xpring started working on the software development kit (SDK) with support for multiple languages. The Xpring software development kit aimed to “simplify and unify Xpring’s offerings” across all of its protocols and products.
Initially, the SDK was integrated for the XRP Ledger, but the long-term goal was to allow the SDK to expand “beyond the XRP”. The Interledger Protocol (ILP), available today for the JavaScript, Java and Swift programming languages, is a step in that direction:
ILP enables interoperability among different ledgers and expands the SDK’s functionality beyond XRP. This feature addition marked our first step in delivering on our ultimate vision for the SDK: A one stop show for any developer who wants to move value. As we continue to deliver on our promise, we expect our SDK to expand to offer support for additional protocols and compose complex interactions between existing ones.
Ripple’s Xpring contributes to the development of payment protocols
In the announcement, there is an account of the obstacles that the Xpring team has gone through to develop the SDK. After receiving feedback from other developers on the APIs, Xpring was able to build a mature product and apply important API changes to the base code:
Today, our libraries contain stable APIs and additional functionality (most notably: payment status and payment history). More notably, these libraries now connect directly to any rippled node, which lets dApp developers decentralize themselves from Xpring’s infrastructure and rely on their own nodes.
On the interlegder protocol (ILP), the project team has been able to incorporate code that allows users to connect to a remote ILP node and interact with the ILP protocol. Xpring outlines:
The functionality makes heavy use of gRPC’s code generation which helped the team get code working, tested, QA’ed and delivered quickly in all variants of the SDK.
Support for the XPR Ledger also received component enhancements. For example, a feature was added to access payment histories and additional information about an account. The changes applied, says Xpring, have the benefit of having a common library that behaves the same across all the libraries used by the team. The SDK team points out that its most important advance is related to support for the software that drives the XRP Ledger nodes and its validators, rippled:
(…) anyone can run a rippled node and connect to it via the Xpring SDK, removing Xpring as a centralized point of failure. Xpring continues to encourage users to properly decentralize the network and practice self-reliance by running their own nodes (…)
CNF has reported on Xpring’s intentions to promote interoperability not only between payment protocols, but also between independent blockchains. In February this year, Xpring’s intention to build a bridge between Ripple’s native token, XRP and Ethereum was announced. In that sense, Xpring has supported initiatives to foster interoperability between the two communities and has invited developers to contribute to the construction of such a bridge.
Last updated on