Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Aggregate transfers in MultiPayment sent to the same recipient
See original GitHub issueCurrently, a MultiPayment transaction can be built with separate payments to the same recipient.
To reduce the number of { recipient, amount } items stored in a MultiPayment transaction (and to save computational power on the node), the crypto package could aggregate separate payments sent to the same recipient in a single MultiPayment in the builder.
Example ( considering [ { recipient: amount } ... ] ):
[ {sameAddress : 1 }, { sameAddress : 2 }, { otherAddress: 5 } ]
Becomes:
[ { sameAddress : 3 }, { otherAddress : 5 } ]
Additionally, an optional parameter could be added to the builder to configure whether the MultiPayment should aggregate payments or not (enabled by default).
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I rather avoid behaviour this. If the user passes in a certain set of data then we will use this as we have to assume that it was his intention, if he wants to aggregate them he can do that but something like that is part preparing your data for signing and not something a library should just do.
The data is permanently stored on the blockchain and us altering any kind of user data is a no go. What they pass in goes on the blockchain.
This issue has been closed. If you wish to re-open it please provide additional information.