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 The XRPL validator resets the Batch vote to align the expected activation time with fixes in the latest server software version
The xrpld 3.4.1 update resolves issues related to Batch transactions and requires node operators to upgrade their servers to stay in sync with the XRPL network. In addition, the activation timer for PermissionDelegationV1_1 has also been reset, and these three amendments still rely on continued support from trusted network verifiers.
Batch amendment activation time realignment
The XRPL validator reset the Batch amendment activation timer to ensure that the feature is coordinated with fixes in the newly released version of xrpld 3.4.1. This adjustment delays Batch's expected activation date from September 29 to October 9, the date when the fixBatchV1_2 amendment is expected to take effect.
The Batch function allows users to package multiple transactions together for batch processing. Previously, Batch had launched a two-week countdown to activation due to majority support. However, newly released fixes also require a validator support period to take effect. To reconcile the two, XRP Ledger contributor Hussein Zangana (net name Vet) coordinated with Ripple and community verifiers to get enough votes to switch from "yes" to "no". This caused Batch's support to briefly fall below the required threshold, triggering a reset of the activation timer. The validator then restored support for it while features and fixes followed the same schedule.
根据 XRPL 的规则，修正案必须在超过 80% 的受信任验证者支持下维持两周方可激活。如果支持率跌破该阈值，一旦修正案重新获得多数支持，计时器将从头开始计算。
xrpld 3.4.1 为计划中的 Batch 上线提供修复方案
xrpld 3.4.1 版本引入了 fixBatchV1_2 修正案，其默认投票设置为“赞成”。根据 XRP Ledger 的发布说明，该修正案旨在拒绝使用错误包装器的 Batch 内部交易。此次发布还包含其他针对安全性和稳定性问题的改进措施。
开发者将 3.4.1 描述为针对敏感协议安全问题的紧急发布版本。目前，他们尚未公开该修复程序的源代码，并计划稍后提供回溯报告。因此，发布说明中关于底层问题的细节有限。
XRP Ledger 基金会敦促服务器运营商在修正案激活前安装 3.4.1 版本。如果 fixBatchV1_2 于 10 月 9 日最终获得批准，运行旧版软件的服务器可能会与网络失去同步。
与此同时，另一个独立的 PermissionDelegationV1_1 修正案也曾短暂失去维持激活计时器运行所需的支持。其预计激活日期已调整为 10 月 8 日，比 Batch 及其修复程序早一天。
10 月 9 日仍被视为预计日期，因为在整个投票期间，验证者支持率必须保持在所需阈值之上。此次重置确保了 Batch 和 fixBatchV1_2 处于同一时间表中，以便服务器运营商能够从容准备软件变更。
