Ripple says asset management company is preparing for XRPL bulk trading

XRP Ledger Batch V1.1 支持率稳固，Ripple 称资产管理公司及商业项目正为月底激活做准备

XRP Ledger（XRPL）的 Batch V1.1 修正案目前的支持率持续高于所需的验证者阈值。Ripple 表示，随着该交易功能有望在本月晚些时候激活，资产管理公司和商业项目正在为此进行准备。

Batch V1.1 保持 30 票支持，9 月 29 日激活倒计时正常推进

目前，Batch V1.1 已获得 30 张验证者投票，确保 XRP Ledger 于 9 月 29 日的激活倒计时按原计划进行。Ripple 指出，资产管理公司正在围绕“批量交易”功能构建应用，尽管具体的合作伙伴名单目前仍保密。

该功能允许将八笔交易打包在一起，使关联的资产转移和支付能够以原子方式共同结算。此前，由于研究人员在二月份发现原始 Batch 存在关键的签名验证漏洞，开发者对其进行了替换。经过扩展审查和对其他安全问题的修复后，XRPL 版本 3.3.0 正式发布了 Batch V1.1。

CoinDesk 在 9 月 19 日报道称，RippleX 工程负责人 Ayo Akinyele 表示，涉及资产管理公司的相关工作正在围绕 Batch V1.1 展开。该功能可将多达八笔交易打包为单个批量操作。截至目前，Ripple 尚未公开披露具体的资产管理公司名称或确切的启动日期。

最新数据：支持率达标，激活窗口期持续开启

Real-time amendment data reviewed as of September 20 showed that 30 of the 35 trusted verifiers tracked supported Batch V1.1. XRP Ledger stipulates that an amendment must maintain support for 14 consecutive days with a support rating of at least 80%, before it can be finally activated. The current threshold is 28 votes. The countdown starts at 14:06:41 UTC on September 15 and is expected to activate shortly after the same time on September 29 if support remains stable.

Breaking news: Asset managers are preparing for XRP Ledger's next payment upgrade

Batch V1.1 can bundle up to eight transactions into one operation. RippleX said commercial projects had already begun building around the feature before the feature was activated.

You may also like:
XRP Ledger 3.4.0 adds lending and agreement repairs
XRP Ledger Batch V1.1 connects settlement legs together

Technical Specifications and Atomic Settlement Mechanism

The XLS-56 specification defines Batch as a transaction type that contains two to eight internal transactions. It supports four processing modes: "all success or all failure","execute only one stroke","until failure", and "run independently". Among them, the "All Success or All Failure" setting requires that the entire group must execute successfully, otherwise it prevents batch taking effect.

Ripple 正在重点讨论交付-versus-支付（DvP）的商业应用。在这种交易中，资产转移及其支付可以置于同一个原子操作中。在“全部成功或全部失败”的设置下，如果支付失败，关联的资产转移将无法完成。

Akinyele 告诉 CoinDesk：“一旦功能上线，我们将分享更多细节，包括与关键资产管理公司的合作情况。” Ripple 尚未确认这些公司的身份，因此这一声明仍属于对公司尚未通过命名合作伙伴公告公开记录的工作描述。

XLS-56 规范列出了信任的多账户交换、平台费用和闪电贷结构等潜在用途。例如，市场或钱包可以将客户付款与服务费打包，而不是要求单独的交易，同时不同的账户可以为同一批次的不同环节授权。

Akinyele 表示：“一些项目已经在考虑使用 Batch 进行开发”，但合作伙伴的身份和生产时间表仍未公布。Ripple 表示，待计划确定后将公布更多细节。

验证者支持保持 9 月 29 日的激活窗口开放

根据 9 月 20 日的最新读数，在 XRPLDashboard 追踪的 35 个验证者中，Batch V1.1 获得了 30 张支持票，约占 85%。因此，支持率保持在继续激活窗口所需的 28 票阈值之上。

预计的 9 月 29 日日期是有条件的。XRPL 修正案不会仅仅因为一次达到 80% 就自动激活。验证者必须在完整的 14 天期间内维持超级多数支持，且在计时期间验证者可能会更改其投票。如果支持率低于所需水平，当前窗口将停止，并在恢复阈值后需要另一个不间断的周期。

最新的计数延续了本月支持率的快速上升势头。在此之前，Batch V1.1 仅有 24 张验证者投票（占 68.57%），低于激活阈值。截至 9 月 15 日，支持率已增至 27 票，随后足够多的验证者背书修正案，从而启动了倒计时。

该修正案本身随 xrpld 版本 3.3.0 于 8 月 6 日发布。官方 XRP Ledger 发行说明将 Batch V1.1 描述为原始 Batch 修正案的替代品，并指出它支持最多八个内部交易，包括原子交换结构。

此后，XRP Ledger Foundation 发布了 xrpld 3.4.0。9 月 16 日的软件更新引入了独立的借贷和清理修正案，并未取代 Batch V1.1，后者仍处于其自身的主网投票过程中。建议服务器运营商升级到 3.4.0 版本以确保服务连续性。

历史背景：从关键漏洞到安全修复

当前的修正案是在开发者于二月份停止原始 Batch 提案之后推出的。XRPL 官方漏洞披露文件指出，安全研究员 Pranamya Keshkamat 和 Cantina AI 的 Apex 工具于 2 月 19 日发现了一个关键的签名验证漏洞。

在特定条件下，易受攻击的代码在遇到新创建的账户后可能停止检查 Batch 签名者。XRPL Labs 表示，攻击者随后可以在不拥有该账户所有者私钥的情况下，包含来自其他账户的未经授权的交易。潜在的交易可能包括支付和某些账本状态变更。

该漏洞从未在 XRP Ledger 主网上激活。原始修正案仍处于投票阶段，XRPL Labs 表示没有资金面临风险。验证者被建议投反对票，而 2 月 23 日发布的 rippled 版本 3.1.1 使 Batch 和 fixBatchInnerSigs 不受支持，从而防止其激活。

随后，开发者更改了替代方案的签名和授权逻辑。漏洞报告指出，补救措施移除了过早的成功条件，增加了授权安全措施，并收紧了签名检查规则。Batch V1.1 在经过开发和审查后，后来被纳入 xrpld 3.3.0 中。

在当前验证者投票之前，安全工作仍在继续。据 crypto.news 在其对 Batch V1.1 安全审查的报道中，在修正案到达目前的投票阶段之前，开发者修复了另外 11 个涉及签名、授权检查和潜在服务器崩溃的问题。

Akinyele told CoinDesk that the review included internal adversarial testing, AI-assisted analysis, the Sherlock security competition, and evaluations involving Halborn and Common Prefix. CoinDesk attributed these details to RippleX; the public partner report covering all parts of the review was not included in the review materials in this report.

As signature design evolves, the XRPL development ecosystem has made corresponding support changes. A June issue record from the xrpl.js warehouse stated that the old Batch signature logic did not match the revised Batch V1.1 format because additional account and sequence information was bound into the signature. JavaScript binary codec release history shows that signature support for Batch V1.1 was added in version 2.9.0 in August.

Asset managers are testing more tokenized settlements on XRPL

Ripple's comments on Batch come at a time when financial institutions and developers are leveraging the XRP Ledger infrastructure for tokenized asset and institutional settlement projects. In June, JPMorgan Chase, MasterCard, Ondo Finance and Ripple participated in a tokenized U.S. Treasury redemption test using XRP Ledger.

Ripple President Monica Long said in August that financial institutions are shifting some of their tokenization of assets from pilot projects to production environments. crypto.news has reported on Ripple's institutional tokenization project, Aviva Investors launched the tokenization fund share category on XRPL in July, and Ripple views RLUSD as a possible cash leg for atomic delivery-versus-payment settlement.

On-chain asset activity has also grown with this development. Another crypto.news review of XRP Ledger RWA data noted that according to RWA.xyz data, excluding stablecoins, the network has added approximately $2.6 billion to the value of tokenized real-world assets in the past six months. The report also warned that the value of representative assets and actual assets in circulation are completely different measures.

Batch V1.1 itself does not require asset management companies to use XRP as assets to be transferred. This feature runs at the transaction level and can package supported XRPL transactions from different accounts. XRP is still associated with ledger transaction fees, while underlying transactions may involve other supporting assets and token structures.

The next procedural event is the end of the current amendment window. The XRPL Dashboard predicts that if at least 80% of validators support is uninterrupted throughout the countdown period, Batch V1.1 will be activated at approximately 14:06:41 UTC on September 29. The latest statistics released on September 20 showed that of the 35 validators tracked, 30 votes were in favor.