Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/concepts/transactions/batch-transactions.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ status: not_enabled

XRPL Batch Transactions let you package multiple [transactions](/docs/concepts/transactions) together and execute them as a single unit. It eliminates the risk of partial completion and unexpected outcomes, giving you a more reliable and predictable experience for complex operations. Up to eight transactions can be submitted in a single batch.

{% amendment-disclaimer name="Batch" /%}
{% amendment-disclaimer name="BatchV1_1" /%}

## XRPL Batch Use Cases

Expand Down
7 changes: 4 additions & 3 deletions docs/references/protocol/transactions/types/batch.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ seo:
labels:
- Transaction Sending
- Other Transactions
requiredAmendment: Batch
requiredAmendment: BatchV1_1
status: not_enabled
txIcon: other
---
Expand All @@ -13,7 +13,7 @@ txIcon: other

Submit up to eight transactions as a single [batch](../../../../concepts/transactions/batch-transactions.md). The transactions in the batch are executed atomically in one of four modes: All or Nothing, Only One, Until Failure, or Independent.

{% amendment-disclaimer name="Batch" /%}
{% amendment-disclaimer name="BatchV1_1" /%}


## Example {% $frontmatter.seo.title %} JSON
Expand Down Expand Up @@ -140,7 +140,7 @@ Each inner transaction:

### BatchSigners

This field operates similarly to multi-signing on the XRPL. It is only needed if multiple accounts' transactions are included in the `Batch` transaction; otherwise, the normal transaction signature provides the same security guarantees.
This field operates similarly to multi-signing on the XRPL. It is only needed if multiple accounts' transactions are included in the `Batch` transaction; otherwise, the normal transaction signature provides the same security guarantees. The entries must be sorted by `Account` in ascending order and must be unique.

| Field | JSON Type | [Internal Type][] | Required? | Description |
|:----------------|:----------|:------------------|:----------|:------------|
Expand Down Expand Up @@ -173,6 +173,7 @@ A transaction is considered successful if it receives a `tesSUCCESS` result.
| Error Code | Description |
|:--------------------------|:--------------------------------------------------|
| `temARRAY_EMPTY` | The batch transaction contains zero or one inner transaction. You must submit at least two inner transactions. |
| `temBAD_SIGNER` | The `BatchSigners` array isn't sorted by `Account` in ascending order, or it contains a duplicate entry. |
| `temINVALID_INNER_BATCH` | - An inner transaction is malformed.<br>- You are attempting to submit a lending or vault-related transaction, which are currently disabled. Invalid transactions include: `LoanBrokerCoverClawback`, `LoanBrokerCoverDeposit`, `LoanBrokerCoverWithdraw`, `LoanBrokerDelete`, `LoanBrokerSet`, `LoanDelete`, `LoanManage`, `LoanPay`, `LoanSet`, `VaultCreate`, `VaultSet`, `VaultDelete`, `VaultDeposit`, `VaultWithdraw`, and `VaultClawback`. |
| `temSEQ_AND_TICKET` | The transaction contains both a `TicketSequence` field and a non-zero `Sequence` value. A transaction can't include both fields, but must have at least one. |

Expand Down