With the huge men pool now, I tried to do this yesterday and even a low fee was 26 bucks and normal fee was over 60 bucks. again due to so many small inputs and thus transaction KB size. Thinking of ways to solve this issue, Since Kano uses our blocks to send out payments, maybe we would be able to select a payout threshold, .25 or .5 or something like that. That would help. Another thought is send it to network with a low standard fee of .0002 and then provide Kano the transaction ID so he can include in our next block, kind of a perk for mining here and getting a faster lane on the congested BTC highway. Again, only for addresses that he has in DB as payment addresses, so no abuse as input addresses need to match pool payment addresses. Anyway, looking for some suggestions with this consolidation issue, I'm sure I'm not the only one, as I have seen others here do the same thing monthly or weekly consolidation into a new address.
well if he did it every other sunday 2x a month with 100 sats per byte it would only affect a few blocks with lower payments.
at 300 sats it is about .0006 per block
at 100 sats it is about .0002 per block
so 2 weeks is about 30 blocks
or .0180 vs .0060
That's not much to give up pool wise to get the ability to bypass the congestion till something is done to resolve it. No real opinion on the solution. I think Kano has said in the past he did not want to allow us to set payment thresholds but back then this congestion problem did not exist. I also believe he does our payments with zero fees since its in our blocks.
he could do it one weekend a month which might make it easy to track.