Looking for feedback/comments/outright rejections:
# `ICRC-4`: Batch Transfers
| Status |
|:------:|
| Draft |
## Abstract
`ICRC-4` is an extension of the base `ICRC-1` standard.
`ICRC-4` specifies a way for an account owner to transfer tokens to multiple addresses in one ledger call in order to drastically reduce the latency of multi account transactions.
The ICRC-4 interface is a generalized interface for submitting multiple transactions in one Internet computer call to an ICRC-1 ledger. It makes no guarantees about the atomicity of the execution of the items, but does outline convinience parameters and the data return in such away that the caller can self verify the results of the transactions.
The interface allows a principle to supply a set of transactions that move tokens from one of their sub accounts to another account. There is no restrictions on which subaccounts, or how many sub accounts can be used, but it is assumed that the principal has the rights to all the sub accounts provided.
## Motivation
Many contracts provide multiplarty transactions or settlment processes tht may move tokens from any accounts owned by a principal to many other accounts. With the ICRC-1 standard, each of these transactions must be submitted seperatelay and incure both call cylce charge(more if a subnet boundry is crossed) and a latency charge as a contract cannot blindly submit unlimited transactions without awaiting due to cycle limits.
This interface enables new application capabilities:
show original
Use case: We need to send multiple transactions when an Origyn NFT sells. This can take a while. Having a batch transfer will help reduce latency and improve the atomicity of payments.
I’d assume ICRC5 after this would be batch approvals and transferFroms to complement ICRC2.
7 Likes