XRP Ledger 批量功能正式上线，支持打包交易

XRP Ledger's main network officially activated the batch trading function, and 30 verification nodes voted in favor.

XRP Ledger (XRPL) has launched its "Batch" function on the main network. This feature is supported by 30 verification nodes, allowing users to package two to eight transactions into one operation for execution.

According to XRPScan data, in the BatchV1_1 vote, 30 verification nodes supported and 5 nodes opposed. This result brought the approval rate to approximately 85.7%. According to the XRPL amendment process, the proposal must maintain the required super majority support of verification nodes for two consecutive weeks before the rules can officially take effect. Currently, after a two-week verification node approval period, BatchV1_1 has been confirmed to be active on the main network.

Core Mechanism and Execution Mode

According to the official documents of XRPL, batch transactions include an outer transaction and 2 to 8 inner transaction lists. The execution mode chosen determines whether these operations are interdependent or can be completed independently. The official specification provides four execution options:

• All or Nothing: The entire batch transaction is completed only if all operations in the list are successful. If any of these transfers fails, other transactions within the group will not be able to be executed independently.
• Only One: allows only one operation to succeed and applies to a range of alternatives without requiring the entire set to complete.
• Until Failure: The operations are processed in order until a failure is encountered. In this mode, previously successful steps will be retained.
• Independent: Attempts to execute the contained operations separately, and each operation is not required to be successful.

It is worth noting that in the "all-or-nothing" model, fees for bulk transactions will still be deducted even if internal transactions fail and lead to an overall rollback. In addition, the specification prohibits nesting one batch transaction within another batch transaction, and does not allow duplicate inner transactions. For bulk transactions involving multiple accounts, participating accounts must jointly approve the set of transactions, and signature rules bind approval rights to bundling operations, preventing one party from treating another party's transfer as a separately authorized payment.

Application Scenarios and Developer Ecosystem

XRPL Verification Node Representative Vet pointed out that this feature is of great significance to institutional users and retail developers. He listed potential application scenarios, including over-the-counter trading (OTC), debt-against-money (DVP) settlement, NFT swaps, and those whose execution relies on other actions.

Vet said: "This is a major functional breakthrough for XRP Ledger, opening the door to critical use cases for institutional and retail builders." He believes that there is a vast space for developers to develop around this feature, which is called a "huge unlocking point."

Previously, crypto.news reported that developers had fixed 11 software issues before the latest approval process. RippleX said commercial projects using batch capabilities have been contracted or are under development. Examples include token swaps between two users and pairing customer payments with platform fees. RippleX's account describes the project under development, but did not disclose the specific company name.

Security Updates and Emergency Patches

Due to security sensitivity, XRPL released the emergency software version fixBatchV1_2 on September 25. The v3.4.1 version notice issued by the XRPL Foundation urges operators to upgrade as soon as possible, and expects the activation date of the security amendment to be October 9, provided that it continues to receive support from verification nodes.

The XRPL tutorial reminds application developers that the outer results of batch transactions show success, but there is no guarantee that all internal transactions have been successful. Developers should check the results of each transaction and verify the account balance.

XRPL Loan Agreement Amendment: Introduction of closed treasury and cash-based accounting

In addition to bulk transactions, XRPL's Lending Protocol V1_1 amendment introduces closed-ended vaults and cash-based accounting. These changes are included in the release notes for the network v3.4.0 release.

According to the software version instructions released on September 16, this software distribution itself does not directly activate the amendment. Under the new loan design, the treasury has a clear subscription period, investment period and redemption period:

• Subscription period: Depositors can deposit or withdraw assets.
• Investment period: Deposits and withdrawals are stopped, and the funds become available for loans.
• Redemption period: After the investment period ends, depositors can recover their shares after the loan matures.

In the newly created treasury, new accounting rules stipulate that interest income is recognized when the borrower pays interest, rather than recording all planned interest at the beginning of the loan. According to documents, after the V1.1 amendment is activated, the old treasury will retain its existing accounting model.

Evernorth's NASDAQ listing plan exposes U.S. shareholder positions

For U.S. stock market investors, the news of Evernorth's plans to list on NASDAQ constitutes another related corporate development trend. The company disclosed the plan in an October 6 filing with the U.S. Securities and Exchange Commission.

According to Evernorth, its transaction with Armada Acquisition Corp. II is expected to close on October 9, subject to regular closing conditions and Nasdaq listing requirements. The company said it expects to hold approximately 473 million XRPs when the transaction closes.

Armada shareholders approved the business combination at the extraordinary shareholders meeting on September 30. Previously, Evernorth's XRPN debut, originally scheduled for October 8, was postponed to October 12 due to administrative delays.