{
  "id": 6341547,
  "title": "Batch Transaction - QA Test Report",
  "url": "https://urgent.news/2026/09/08/batch-transaction-qa-test-report",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-08T22:39:39.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ripplexdev/batch-transaction-qa-test-report-5g5g"
  },
  "original_language": "en",
  "account": "This report details the outcome of QA testing conducted on Batch (XLS-56) transactions on the XRP Ledger (xrpld). The testing focused on the BatchV1_1 amendment, which enhances the original Batch amendment by strengthening BatchSigner authorization and signing semantics.\n\nThe Batch feature enables an account to bundle up to eight inner transactions into a single outer Batch transaction, which is processed as one atomic unit. The inner transactions can execute in four modes - AllOrNothing, OnlyOne, UntilFailure, or Independent - and can be authorized across multiple accounts through various methods. The report covers the complete Batch surface under the BatchV1_1 amendment and covers the testing of all four execution modes, inner-transaction bounds, fee calculation and tfInnerBatchTxn rules, multi-account and multi-signed BatchSigner authorization, and interaction with other features such as Permission Delegation, Sponsored Fees & Reserves, Confidential MPT, and Tickets.\n\nThe testing was done using multiple types of tests, including functional tests, regression tests, adversarial/security attack scenarios, and cross-feature interactions. A total of 189 tests were executed, with 189 functional tests, 56 adversarial/security tests, and 27 cross-feature interaction tests. The regression tests covered the full xrpld test suite to ensure no existing functionality was broken by the Batch changes.\n\nThe test results show that all security-critical properties were validated, including correct atomic commit/rollback semantics for each execution mode, enforcement of the 2-8 inner-transaction bounds, correct BatchSigner authorization under the hardened BatchV1_1 signing preimage, and accurate reporting of inner-transaction metadata. No Critical Open bugs were found. The Batch feature was introduced in PR #5060 and later replaced by BatchV1_1 in PR #6446.",
  "summary": "Test Report Date : 9/8/2026 Prepared By : sgramkumar Environment : GitLab CI Runner (nix-debian) Network : xrpld devnet + private CI network Overview This report presents the results of QA testing performed on Batch (XLS-56) Transactions across xrpld servers. Coverage targets the BatchV1_1 amendment, which supersedes the original Batch amendment and tightened BatchSigner authorization and signing…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}