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 核心要点
在检查时，Batch V1.1 已获得 27 位支持者的认可。该提案需要获得为期两周的 80% 支持率才能激活。一个批次（Batch）可以包含八个关联的交易。全部或无（All-or-nothing）模式可避免部分完成的情况。首个 Batch 版本从未激活。
XRP Ledger 的 Batch V1.1 修正案进展
根据 XRPScan 追踪的数据，XRP Ledger 的 Batch V1.1 修正案在检查时已获得 35 位验证者中的 27 位支持。该修正案正接近激活所需的 80% 门槛。若获通过，它将允许应用程序将多达八个相关的交易归组为一个 Batch 操作。其实际目的是使多步骤支付和交易流程更加稳健。应用程序可以将一系列必须同时发生的指令链接起来，而不是将它们视为可能因中途失败而导致流程不完整的事件。
需要两周的 80% 支持率
在被追踪的 35 位验证者中，达到 80% 阈值需要 28 位验证者支持。这将启动激活期；随后，支持率需连续保持两周稳定，Batch V1.1 才能成为 XRP Ledger 的规则。这两周的时间给予了验证者审查修正案并确认支持率稳定的机会。代码可以包含在服务器软件中而不改变主网行为，但验证者必须先表明他们已准备好按照相同的规则运行它。
批次如何防止半完成的支付
Batch V1.1 allows up to eight associated transactions to be submitted together. Instead of requiring each step to be submitted and confirmed separately, the ledger will review and record the selected instructions during the same ledger closure cycle. Take market sales as an example: the buyer sends payment, the seller transfers assets, and the market collects fees. In all or no mode of Batch, all necessary instructions either succeed or the entire batch fails. The buyer will not fall into a situation where he has paid but not received the assets.
Correlation of all or no patterns
When each part of the payment must be successful together, all or no patterns are the relevant choice.
Batch V1.1 Overview
- Up to eight connected transactions: A Batch can contain up to eight connected instructions.
- All or unprotected: Each necessary instruction is completed together, otherwise the ledger rejects the entire batch.
- Multiple accounts are involved: A batch can coordinate instructions involving multiple participants.
- Aspects that won't change automatically: Batch does not change the ledger closure rate, nor does it require every wallet and market to support it.
V1.1 replaces the previously suspended Batch amendment
The original Batch amendment was flawed in the way transactions within batches were authorized. Security researchers discovered the problem in February, when the feature was still waiting to be activated. Verifiers are advised to withdraw support before it reaches the main network, so the flaw never affects user funds. Vulnerability disclosure details document this response and flag early Batch implementations as unsupported. Batch V1.1 replaces the old version with a new implementation that removes identified logical issues. RippleX said the revised version went through additional code review, testing and external security assessments before entering the current voting process.
With revised code now approaching the required level of support, Batch has gone further than several XRPL features that are still awaiting validator approval.
Batch is closer to passing than the XRPL program's lending system
Batch's votes can be viewed along with two other XRP Ledger changes that are passing through the amendment process. The fixCleanup3_3_0 proposal focuses on maintenance and security issues that affect vaults, automated market makers and licensing transactions. It improves existing transaction paths rather than creating new consumer-facing payment tools. The planned institutional credit system lags behind. It requires both Single Asset Vaults and Lending Protocols to have sufficient validator support; approving only one of them will not create a usable lending market.
Batch 的作用范围较窄。它为应用程序提供了一种协调 XRP Ledger 上现有交易（包括支付、转账和费用）的方法。其 27 位支持验证者使 Batch 比原生借贷所需的两个修正案更接近激活阈值，尽管活跃的修正案仍仅为应用程序集成提供工具。
激活将使 Batch 对开发者可用
如果 Batch V1.1 完成激活过程，钱包、市场和其他服务将决定是否将其添加到产品中。钱包用户可能只有在应用程序能够一次性完成支付和资产转移，而不是在一步失败后要求重试时，才会注意到这一变化。潜在的早期集成包括那些已经为一个客户请求组合多个动作的服务。Batch 将使这些服务能够定义哪些指令必须在操作被视为完成之前完成。
Batch 使复杂的支付流程更稳健
Batch V1.1 本身不会改变日常的 XRP 转账，因为它的价值更为具体：应用程序可以链接多个必需的指令，避免将部分完成的支付或交易视为已完成。如果修正案完成其激活期，开发者可以开始将 Batch 添加到实时的 XRP Ledger 服务中。
本文仅提供信息目的，不构成财务或投资建议。验证者支持和修正案状态可能会发生变化。
