Aggregate multiple settlement transfers into single transaction #342

Open
opened 2025-12-28 17:19:09 +00:00 by sami · 3 comments
Owner

Originally created by @alexvanin on GitHub (Oct 8, 2021).

During the settlement, alphabet nodes generate many transfer invocations of balance contract. Instead of sending transaction per transfer, Alphabet node can try to group multiple transfers into single transaction.

Originally created by @alexvanin on GitHub (Oct 8, 2021). During the settlement, alphabet nodes generate many transfer invocations of balance contract. Instead of sending transaction per transfer, Alphabet node can try to group multiple transfers into single transaction.
Author
Owner

@fyrchik commented on GitHub (Jan 11, 2022):

This requires some refactoring, as we have multiple clients emdedded in each other.
One way to approach this is to have dummy client which accumulates multiple invoked scripts in a single one and then calculates GAS cost and sign/send tx in another method.
I think this is better to be done after cleaning up code for notary-disabled environment.

@fyrchik commented on GitHub (Jan 11, 2022): This requires some refactoring, as we have multiple clients emdedded in each other. One way to approach this is to have dummy client which accumulates multiple invoked scripts in a single one and then calculates GAS cost and sign/send tx in another method. I think this is better to be done after cleaning up code for notary-disabled environment.
Author
Owner

@roman-khimov commented on GitHub (Dec 25, 2025):

Can be easily aggregated by owner, btw. balance contract can get a list of relevant containers and loop through them, so it's like settleOwnerPayment instead of settleContainerPayment.

@roman-khimov commented on GitHub (Dec 25, 2025): Can be easily aggregated by owner, btw. balance contract can get a list of relevant containers and loop through them, so it's like `settleOwnerPayment` instead of `settleContainerPayment`.
Author
Owner

@roman-khimov commented on GitHub (Dec 25, 2025):

Although owner can have quite a number of containers in which case we could have a problem with system fee.

@roman-khimov commented on GitHub (Dec 25, 2025): Although owner can have quite a number of containers in which case we could have a problem with system fee.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#342
No description provided.