Tumbler always uses mixdepth 0 about joinmarket-clientserver HOT 4 CLOSED

Also happens when no --schedulefile. python tumbler.py wallet.json <addr> = same result.

from joinmarket-clientserver.

Yes, for now this is a gap in implementation, and a rather annoying one.

It's quite related to the idea mentioned elsewhere that, the two scripts sendpayment and tumbler really ought to be folded together in this version, since there's some duplication of function; it's better to see tumbler only as a way of generating schedules, nothing else.

The basic sendpayment is now wrongly named since it supports multiple payments and specific schedules can have transactions starting from any mixdepth. But unfortunately, as is noted here the code doesn't currently support starting a tumbler from non-0 mixdepth, only continuing an existing schedule with the --restart option.

Here's one (inferior) way to get round it without code changes: create a tumble schedule normally with python tumbler.py --schedulefile schedule.schedule <tumbler options> wallet.json <addrs> , let it crash as above with No coins error, then edit the schedule.schedule file to increment all the mixdepths (0->1,1->2,..), then run it as a schedule file against sendpayment.py. This option is not good enough though, as it doesn't include the schedule tweaking function which is what makes it more robust.

A better way round it is to create a schedule as above, using one more mixdepth than you actually want, and edit the last value in each entry for mixdepth 0 to 1, which flags it as already complete (for syntax details you've probably already seen this). Then use python tumbler.py --restart --schedule-file schedule.schedule <insert same tumbler options as first start> wallet.json <same addrs>, which should start the tumbler from mixdepth 1 (here assuming that there is no external address in mixdepth 0 payments (that's almost never the case)).

In any case, I should fix this to make it work, apologies.

from joinmarket-clientserver.

I'm not sure why I didn't support this in the initial implementation; the original algo (which was simply ported over here with almost no change) supported an arbitrary start depth and I disabled it; I think it was simply a matter of 'worry about that later'. Now that I have "worried" about it (and tested it in a few different configurations), it works fine. The option is -m as per the help. Implemented in 2424104 ; let me know if there's any problem with it.

from joinmarket-clientserver.

Awesome! Worked perfect.

from joinmarket-clientserver.