15:07:06 <br-m> <jpk68:matrix.org> @rucknium:monero.social: Should this be added to the meeting agenda?
15:07:06 <br-m> <jpk68:matrix.org> https://github.com/monero-project/monero/issues/11586
15:14:10 <br-m> <ofrnxmr> Prob nwlb meeting
15:42:39 <br-m> <rucknium> @jpk68:matrix.org: @jeffro256:monero.social: ^ Should it?
15:49:51 <br-m> <ofrnxmr> I think its less of a discussion of if we should, but more about what it would look like
15:50:38 <br-m> <ofrnxmr> Because proofs still use the keys, so you cant just get rid of them. And its not a privacy issue in most situations (like, if the recipient/public doesnt know your primary address)
15:50:47 <br-m> <ofrnxmr> And its not related to the carrot issue
15:51:48 <br-m> <ofrnxmr> Its more of an edge case that gives reason for people should migrate to using proper proofs instead of using _tx_key and accidentally hitting a leak
15:53:52 <br-m> <ofrnxmr> Currently most / all external services ask for tx keys instead of proofs (bisq's auto, explorers, etc). Deprecating would just be deleting the endpoints afaict, and then getting every wallet to provide proofs in their place (cake, monfluo, probably gui, feather, monerujo and every other wallet display they key on the tx details)
15:57:15 <br-m> <ofrnxmr> Its also probably less of a leak than if you provide a view balance key 🙃
15:57:37 <br-m> <ofrnxmr> (Sorry, poking the bear)
15:58:39 <br-m> <ofrnxmr> My main point with that comment, is that the key shouldnt be used for providing proofs to other people, proofs should be. The key should remain private, unless you want to reveal secrets ofc
16:03:01 <br-m> <ofrnxmr> The related carrot issue is that every legacy keyed wallet (so stessnet) leaks the change amount passively