{"type":"rich","version":"1.0","author_name":"npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet","author_url":"https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2018-01-23\n📝 Original message:On Mon, Jan 22, 2018 at 8:00 PM, Peter Todd via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e Most transactions don't have change?! Under what circumstance? For most\n\u003e use-cases the reverse is true: almost all all transactions have change, because\n\u003e it's rare for the inputs to exactly math the requested payment.\n\nIt's quite easy to get no change with a not-dumb algorithm selecting\ncoins if you have a decent number of outputs well under the value\nyou're paying.\n\nThe number of ways n choose m combines grows exponentially, and you\nonly need to get close enough over the right value so that you're\npaying excess fees equal or less than the cost of the change (which\nshould include the current cost output itself as well as estimated\ncost of the future signature to spend it).\n\nAchow101 and Murch have code to implement an efficient algorithm for\nfinding these solutions for Bitcoin core which will hopefully get in\nsoon."}