rippled lets vault and lending transactions run inside a Batch, behind the LendingProtocolV1_2 amendment

Victoria Shinder06 October 2026, 09:221 min read

The XRP Ledger's reference server, rippled, merged pull request #8244 on 6 October. It allows Single Asset Vault and Lending Protocol transactions to run as inner transactions of a Batch, once the LendingProtocolV1_2 amendment is enabled.

What changes. Batch already applied its inner transactions through the normal transaction pipeline, but explicitly rejected every Vault and Lending transaction type. The pull request makes that restriction depend on the amendment: without it, these transactions stay invalid inside a Batch; with it, they are allowed.

The signing detail. A LoanSet normally carries a CounterpartySignature. Inside a Batch, both parties sign the outer Batch instead, and the change verifies that authorisation flow.

What the tests cover. The test plan shows what becomes possible:

• a full vault lifecycle in one Batch — create, deposit, withdraw, delete;
• a loan lifecycle from vault creation through LoanSet and LoanPay, in one Batch on an open-ended vault or in two Batches on a closed-ended vault, because deposits and loans are valid in different phases;
• arbitrage under tfAllOrNothing: borrow, buy on the DEX, sell, repay, with a case where the sell cannot fill and nothing persists;
• rollback of a LoanSet when a later inner transaction fails, and tfIndependent chains where a failing inner does not stop the ones after it.

The change touches libxrpl and adds about 990 lines across seven files, five of them in the test tree. Nothing changes on the network until the LendingProtocolV1_2 amendment is enabled.