1

In general what makes two or more operations part of an operation group?

And as an example, why are these operations all in the same operation group? https://tzkt.io/ooyynpmcUE1wPUWatxZxqk3Nnwao7NxteZZfnPW2YRkEWeQMQyj

2

You can call those batch operations.

When you create a manager operation, it can contain multiple sub-operations of the following kinds (transaction, origination, delegation, reveal). The limits of that operation are defined by gas and storage limits.

Why is that useful?

  • You can inject more operations per second;
  • It is cheaper;
4
  • ah okay, thanks! And my understanding is if a contract creates a transfer, both of those (the original contract call, and contract-initiated transfer) are also part of the same operation group. Are there other ways operations can be part of the same operation group?
    – Darius
    Jun 24 at 1:06
  • 1
    contract-initiated (transfers, originations, and delegations) are internal calls of sub-operations, and you can consider them as sub-sub-operations. Jun 24 at 7:40
  • 2
    An operation group is a list of operations that are all signed by the same implicit account. The main points of these groups are that: Jun 24 at 9:31
  • 2
    - atomicity: either all the operations in the batch succeed or none is applied - efficiency: the whole batch is signed only once so it is much more efficient to check, hence it requires much less gas - usability: the whole batch only increments the counter of the implicit account signing it by one; for this reason it is easier for tools to provide sending several operations per blocks using operation batches than tracking counter changes. Jun 24 at 9:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.