Pulp

But it might also be an error, right? E.g., if the directories are actually down or the onions are misspelled. Also, are you sure it actually continues? I.e., It keeps...

> if no other message channels are configured. Exactly, sorry I was taking this for granted. So basically: If we have only onion channels this seems quite important, we cannot...

From a quick profiling, it seems most of the runtime comes from low level `bitcointx` functions and classes. Does it make sense? Maybe there's some more room for caching the...

So, from the README: Output A node in the output graph represents a function and has the following layout: +------------------------------+ | function name | | total time % ( self...

See: https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/f1f3972aa162a9ac844d2a710bac2f7c020f73c0/scripts/obwatch/ob-watcher.py#L86-L87 I.e., `sw0XXXoffer` are for `bc1` addresses. `swXXXoffer` are for `3` addresses.

Both concepts seem useful to me, and AFAIK the code for both is already there but not used (or not used as much). In particular: For `--dry-run` we have this...

Random example to showcase the idea. ``` (jmvenv) $ python3 scripts/tumbler.py --explain FILE.SCHEDULE SCHEDULE ENTRY: 4,0,9,INTERNAL,0.22,16,0 From mixdepth 4, sends amount X minus fee, without rounding, to internal address in...

> As per my understanding of the JoinMarket protocol, takers are the users who select one of the orders made by a maker, which is described in [here](https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/YIELDGENERATOR.md). Correct. >...

> I can think of it as "coinjoin rooms". Each taker can enter one such room, and wait for an undefined time to have other takers join him. Basically "dynamic"...

> Sure, but why not having it as optional? Wouldn't it be better for the users to choose which one is more suitable for them? It seems to me just...