XRP Ledger 3.3.0 Support Goes Live Across Key Developer Libraries

요약:XRP Ledger developer tools get major boost with 3.3.0 support.

Julian Berridi, product manager at Ripple, announced new releases of xrpl.js and xrpl-py with support for XRP Ledger version 3.3.0 in a recent X post.

xrpl.js refers to a JavaScript/TypeScript API for interacting with the XRP Ledger in Node.js and the browser.

On the other hand, xrpl-py is a pure Python implementation for interacting with the XRP Ledger. The xrpl-py library simplifies the hardest parts of XRP Ledger interaction, like serialization and transaction signing, and also provides native Python methods and models for XRP Ledger transactions and core server API objects.

Users can communicate directly with the XRP Ledger through HTTP-based APIs provided by the core xrpld server as well as the Clio server. Client libraries such as xrpl.js and xrpl-py simplify some of the common work of accessing and processing XRP Ledger data and present it in a form that matches the native conventions of their respective programming languages, in this case JavaScript and Python.

The xrpld server software can run in several modes depending on its configuration; one of these is API Server, which provides API access to read data from the shared ledger, submit transactions, and watch activity in the ledger.

XRPL 3.3.0

Version 3.3.0 of xrpld, the reference server implementation of the XRP Ledger protocol, was launched on August 6, 2026.

This release introduced several new amendments alongside bug fixes and build improvements. Six amendments enabled by xrpld version 3.3.0, including atomic batch transactions, privacy-preserving Multi-Purpose Token transfers, Multi-Purpose Token properties that issuers can make permanently immutable, granular account permission delegation, reserve and transaction sponsoring (XLS-68), as well as a bundle of amendment-gated bug fixes, have been up for voting since August 6.

The long-active Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversalNumber amendments were also retired following xrpld version 3.3.0, making them a permanent part of the protocol.

Notably, the fixCleanup3_3_0 amendment, a collection of fixes for Single Asset Vaults, the Lending Protocol, Automated Market Makers, the permissioned DEX, Checks, and pseudo-accounts introduced by xrpld version 3.3.0, is approaching majority, currently at 77.14% according to XRPScan data.

면책 성명

본 기사의 견해는 저자의 개인적 견해일 뿐이며 본 플랫폼은 투자 권고를 하지 않습니다. 본 플랫폼은 기사 내 정보의 정확성, 완전성, 적시성을 보장하지 않으며, 개인의 기사 내 정보에 의한 손실에 대해 책임을 지지 않습니다.
전편

찰스 호스킨슨 ‘카르다노 승리…이더리움 필요’

다음

리볼루트 유로 스테이블코인 3가지