patientsendpayment

[AdamISZ]

... should be added to scripts/

Current script here

To implement an algo of (be a maker for a while until coins run out or) (after delay, switch to taker to send coins) will require starting the Maker protocol, using a monitor loop and when/if times out, shut down as maker and restart Taker protocol. Haven't really looked into this much yet.

This algo is particularly desirable to have, at least in theory (hasn't been used much yet), so as enhancements go, this one should be high priority I think.

[kristapsk]

Had a thought about this recently - wouldn't this mode be also useful for tumbler, as it waits between individual coinjoins anway? Also, as tumbler now does round amount coinjoins from time to time, possibility of round amount patientsendpayment matching some taker in reasonable amount of time has increased.

[chris-belcher]

Note that using fidelity bonds to resist sybil attacks implies that scripts like patientsendpayment won't work.

It's been more than 2 years since patientsendpayment stopped being included in joinmarket, and to my knowledge nobody has ever complained that it's missing. We can explain this from the economics; coinjoin fees are so low that very little money is saved by using patientsendpayment, you'd have to really value your time very low to trade several hours for maybe 200 satoshi.

[delbonis]

Not to go against the grain here but I'd appreciate this being readded if at all possible.

you'd have to really value your time very low to trade several hours for maybe 200 satoshi

It's less about valuing my own time low and more for cases like "I don't care if the coins move now or in a week from now".

[dmp1ce]

Another vote here for patient send. It could be a way to migrate from wrapped segwit to native segwit for makers. For that matter, "patient send" or custom outputs could be integrated into the yield-generator scripts.

I was thinking a custom file with "address, amount" could be specified in a filed like yg-custom-outputs.csv and when a join is crafted, one of those address could be used, instead of the internal wallet addresses. For example:

yg-custom-output.csv

bc1xxx1,0.1
bc1xxx2,500000
bc1xxx3,-
bc1xxx4,-
bc1xxx5,-

I was thinking - could be used for amount to send as much as possible to the address for the coinjoin. If the amount cannot be satisfied then the next address is used or an internal wallet address is used, same as default.