Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XRP Ripple announced updates to xrpl.js and xrpl-py to support XRP ledger version 3.3.0
Julian Berridi, product manager of Ripple, recently announced on the X platform that the updated xrpl.js and xrpl-py now support XRP ledger version 3.3.0. The news marks an important development for the enterprise-class blockchain and encryption solutions provider, which is committed to promoting real-time cross-border payments.
New updates to developer tools
xrpl.js is Ripple's JavaScript and TypeScript API that allows developers to interact with XRP ledgers in the Node.js environment and web browser. By providing powerful access to web-and server-based developers, it simplifies the application building process that connects to the XRP ledger.
On the other hand, xrpl-py is aimed at the Python developer community and provides convenient access to the XRP ledger ecosystem through native Python libraries. The library handles complex tasks such as serialization and transaction signing, and provides Python-based methods and models for interacting with transaction and core API server objects.
Client libraries like xrpl.js and xrpl-py are designed to reduce the complexity of accessing, processing and rendering XRP ledger data. By aligning output and structure with the conventions of their respective programming languages, they lower the threshold for developers to build based on XRP ledgers.
Mini Dictionary: xrpld--The main reference server software for implementing the XRP ledger protocol, supporting multiple roles, including the API server model for transaction processing and ledger data access.
XRP ledger 3.3.0 and protocol revisions
Xrpld, the reference server implementation of XRP ledger, released version 3.3.0 on August 6, 2026, and subsequently adjusted multiple protocol revisions, marking an important step in the continued development of the network.
Several long-term revisions, including Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversal Number, have been officially retired and become permanent features of the agreement. These revisions are intended to enhance the security, efficiency and broader usefulness of XRP ledgers.
A noteworthy addition to this upgrade is the fixCleanup3_3_0 revision. The revision integrates multiple fixes, covering single-asset vaults, lending agreements, automated market makers, licensed decentralized exchanges (DEX), checks and fake accounts.
According to the latest data from XRPScan, the fixCleanup3_3_0 revision is close to receiving the support of the majority of verifiers, and the current consensus rate is 77.14%.
Revision status after version 3.3.0
Clawback: permanent; fixDisallowIncomingV1: permanent;fixInnerObjTemplate: permanent;fixNFTokenReserve: permanent;fixUniversalNumber: permanent;fixCleanup3_3_0: pending (consensus rate 77.14%)
Developer and Community Response
Ripple's new releases of xrpl.js and xrpl-py are expected to improve the development experience for building on XRP ledgers, primarily by keeping the tools in sync with the latest protocol features and revisions.
It is worth noting that the fixCleanup3_3_0 revision introduced in xrpld 3.3.0 (including multiple fixes for single asset vaults, loan agreements, automatic market makers, licensed DEXs, checks and fake accounts) is approaching majority support. According to XRPScan data, the current consensus rate has reached 77.14%.
Members of the XRP ledger community are closely monitoring the progress of these agreements, especially as the fixCleanup3_3_0 revision approaches the consensus threshold required for full adoption.
