15:59:09 <m-relay> <f​:monero.social> Documentation says that `--tx-notify` triggers for incoming transactions. Does that include triggering for change received by outgoing transactions?
16:00:27 <sech1> If you receive non-zero change, yes. Or if you churn an input, also yes.
16:02:46 <m-relay> <f​:monero.social> Okay that will create an edge-case for when the change happens to be zero. The use case is to export key images every time an outgoing transactions happens (to keep a live watch-only wallet updated).
16:02:58 <m-relay> <f​:monero.social> Okay that will create an edge-case for when the change happens to be zero. The use case is to export key images every time an outgoing transaction happens (to keep a live watch-only wallet updated).
16:05:31 <sech1> IIRC, the zero change output doesn't even have to go to your address because it's zero. I'm not sure if wallet2 sends it back to your address, or just somewhere into the void
16:08:04 <m-relay> <f​:monero.social> A first idea would be to always force some amount-to-self, but I would actually be surprised if I was the first to need this and there weren't any better options yet ...
19:33:24 <m-relay> <f​:monero.social> I just used feather to do a coin-controlled spend to avoid any change. The monitoring RPC logs a `W Spent money: ...` (upon inclusion in a block), but it indeed does not trigger `--tx-notify`.
19:37:07 <m-relay> <f​:monero.social> I figure having `--tx-notify` straight-out regard both types would make more sense - given that it's triggering most spends anyway.
19:37:33 <m-relay> <f​:monero.social> on*