joinmarket-clientserver
joinmarket-clientserver copied to clipboard
Bitcoin CoinJoin implementation with incentive structure to convince people to take part
Currently it is really slow. Likely some optimizations are possible even without adding new data to wallet file, but ultimate solution IMHO is caching. For wallet with around 1000 transactions...
Fresh installs of 9.5, 9.10 and git head repro on first run after setting new joinmarket.cfg 's rpc info. If I print the exception: > User data location: /home/user/.joinmarket/ >...
Our current defaults are [here](https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/7aebed728b6427158b330af0471a280e9c921dc2/jmclient/jmclient/configure.py#L182). Here is a newly proposed one: ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222 We could add more to this page over time. "Stopgap": because, the only realistic solution I think, over...
Wasabi Wallet has a feature that at transaction preview before sending transaction will suggest changing send amount little bit if that allows to avoid having change. It would be useful...
See https://github.com/dennisreimann/joinmarket-log-parser. It's a tool that analyzes JoinMarket log files and extracts structured data from them. It would make sense to store that data in structured manner by JoinMarket itself....
It there a reason to ask user a question to enable or not enable fidelity bond support when creating new wallets instead of always enabling it?
It would be extremely useful to be able to get the created tx ids from `wallet/{walletname}/taker/direct-send` and `/wallet/{walletname}/taker/coinjoin` REST API calls. Is this possible?
When there is try to send privmsg to an unavailable message channel, user gets errors like this: ``` [ERROR] Tried to communicate on this message channel but failed: onion-network [ERROR]...
It's bad to have different functions for the same thing, `coins_to_satoshi()` were already used in some tests.