-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Add batch transfers info #6772
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add batch transfers info #6772
Changes from 1 commit
5654b4a
77174f0
3b48315
e7f6cde
3413842
8e0b81a
e9987da
a642196
71dd66a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -90,6 +90,21 @@ Vesting funds are on a release schedule that unlocks a constant number of tokens | |
| (**linear vesting**) or the full amount after a specific block number (**cliff vesting**). In all | ||
| vesting cases, the lock decreases over time until all the funds are transferable. | ||
|
|
||
| ### Batch Transfers | ||
|
|
||
| Batch transfers are transfers that include multiple calls. The `utility` pallet is used to dispatch batched calls, and there are three ways of doing it: | ||
|
filippoweb3 marked this conversation as resolved.
Outdated
|
||
| - `utility.batch()`: stops execution if it encounters an error and emits an event with the number of executed calls and the error of the failed call. | ||
|
filippoweb3 marked this conversation as resolved.
Outdated
|
||
| - `utility.batchAll()`: atomic batch execution, meaning that if a call within the batch fails, everything is rolled back as if nothing happened. | ||
|
filippoweb3 marked this conversation as resolved.
Outdated
|
||
| - `utility.forceBatch()`: All calls before and after one fails will be executed. | ||
|
filippoweb3 marked this conversation as resolved.
Outdated
|
||
|
|
||
| | Function | Stops on Error | Atomic | Events for Debugging | | ||
| |--------|--------|--------|--------| | ||
| | `batch`| Yes | No | Yes | | ||
| | `batchAll`| Yes | Yes | Not needed | | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you explain why it is not needed here?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's an "all or nothing" situation. No need to emit an event, as it will be 100% success or 100% failure
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. added a detailed table about events triggered for each case |
||
| |`forceBatch`| No | No | No | | ||
|
|
||
| For more detailed information about the arguments accepted by each of these calls, see [the Metadata Explorer](../general/metadata.md). | ||
|
|
||
| ## Verifying Extrinsics | ||
|
|
||
| !!!danger | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.