Quote from: d5000 on September 11, 2017, 12:49:44 PM

if I remember right - watch addresses

I posted the original output from the dry run of the coinpunk patch:

https://gist.github.com/gjhiggins/4d97eeb24d0eca5de77a92d3996e91e3

for which the below is the corresponding commit:

https://github.com/slimcoin-project/Slimcoin/commit/a8a9e698a320a04cc5cf0e98ce61bc8e3a87d99d

Note the complete absence of any changes in the src/qt folder. This testifies that the GUI is oblivious to the changes made elsewhere and cannot distinguish between an address for which it has a pubkey but not a privkey (the definition of watch address) and a normal address for which it has both a pub and a priv key. Transactions for watch addresses seamlessly intermingle with the user's transactions and there's no visual distinction between them in the GUI.

The watch address patch code was intended for use with the JSON-RPC API and a headless daemon. This seems consonant with the main use case, AIUI. Watch address tx really should not appear in the GUI, or if they do, they should be differentiated and separately presented.

I'll have another go at watching something other than the burn address because it seemed to me that tx associated with the watched addresses were included in at least part of the stake calculations, at least judging by the report of a total of 5000-odd tx, 100% thread use and eventually thrashing so hard that the GUI stopped responding and the process had to be terminated from the command line. I know of only one circumstance in which this happens - stake calculations. I need to go through the code and instrument the staking process so that it reports the addresses of the tx for which it is calculating stake weight.

Some work required, still.

Cheers

Graham