5c0b9eb Remove txfee_default: used as user estimation for initial tx_fee estimate, but removing this option and replacing it by the existing estimation (using tx_fee config setting) makes more sense. (AlexCato)
Tree-SHA512: 47790b27ba81e0e4b832a739bafde936852c6e85158dc06bcb7aa1117f7c8ee9a97df45c7c6e7b6050e33135e93457f705ab67f77f3008735f70f6112ebde3af
0ab5b65 Redefine cli-option --txfee: Treat it as txfee to be used in the JM TX's instead of just for preliminary estimations. Now it is a way to temporarily override the tx_fees setting in joinmarket.cfg and behaves exactly the same way as describes there. (AlexCato)
Tree-SHA512: 9343bfbd3bf016de24d7e1cb74bf8aa50f0ad4921c1376f4ca8744f572b4e5393ad39b104d80bc3227b2a109dd7edf6a02f1737106f14e71dab961ac2941671f
in the JM TX's instead of just for preliminary
estimations. Now it is a way to temporarily override
the tx_fees setting in joinmarket.cfg and behaves
exactly the same way as describes there.
cf54789 Set txfee threshold to 1000 instead of 144 (chris-belcher)
Tree-SHA512: dd6f162f3b6a65ef38929b2037274cbb74dc406ce4ba8623587f91f623c796899cf9103dc264ba595d3b5c97cc96ff3763ffc011d1618b0dbba3023ec52956e7
Introduces WalletService object which is in control of
blockchain and wallet access.
The service manages a single transaction monitoring loop,
instead of multiple, and allows updates to the wallet from
external sources to be handled in real time, so that both Qt
and other apps (yg) can respond to deposits or withdrawals
automatically.
The refactoring also controls access to both wallet and
blockchain so that client apps (Taker, Maker) will not need
to be changed for future new versions e.g. client-side filtering.
Also updates and improves Wallet Tab behaviour in Qt (memory
of expansion state).
Additionally, blockchain sync is now --fast by default, with
the former default of detailed sync being renamed --recoversync.
This refactors YieldGeneratorBasic a bit. In particular, we move things
that custom algorithms will most likely want to change to separate
functions. That way, it is easy to define the behaviour of inputs
and outputs for the join without the need to duplicate the other, more
general logic of create_my_orders and oid_to_order.
This adds simple unit tests for the core functionality of
YieldGeneratorBasic in the new file jmclient/test/test_yieldgenerator.py.
The tests verify that offer creation, reannouncement of offers when a
change is made to the maxsize and translation of offers to orders works
as it should.
remove unused import
This reverts commit 4b4f8c97f4.
Due to a flawed assumption where sometimes importing addresses does
take a significant amount of time. For example on machines with HDD
importing 1-2 addresses can last a second or two, and importing 60
addresses lasts about 30 seconds. The commit makes running a maker
impossible on such a machine.
Prior to this commit, if an invalid destination address
was entered on the command line for the tumbler script,
the invalidity would cause a crash at the time a transaction
was built with this destination (during the run).
After this commit, all destination addresses entered on
startup are checked immediately and the program quits with
this information if a specific address is invalid.
In commit 22467f4 a bug was introduced whereby detailed
sync was used instead of fast sync, but with only one
iteration, in Joinmarket-Qt, in certain circumstances,
leading to incorrect wallet reporting/display. This commit
reverts that change (except for function name change).
There may still be edge cases for large wallets doing
recovery in Qt but this will be dealt with later.
c9bf1c6 Update documentation: Replace links to instructions in original Wiki with updated and corrected instructions within USAGE.md. Add YIELDGENERATOR.md to docs/ with updated and corrected instructions from original wiki. (AdamISZ)
Replace links to instructions in original Wiki with updated
and corrected instructions within USAGE.md.
Add YIELDGENERATOR.md to docs/ with updated and corrected
instructions from original wiki.