Skip to main content
I polished grammar, style, word choice of this worthy question.
Source Link

When constructing a change output, mustdoes it have to be destined forsent to the main public address?

I was thinking about how the behavior of spending Monero from the same wallet over time inducesintroduces the risk of eventually linking change outputs when they are later combined and spent. Can this be avoided?

It occurred to me that the wallet will prefer to spend from within particular subaddresses (citation could be useful here), so I was thinking that one way to prevent future linking of change outputs would be to address them to various subaddresses.

Back to the title, is it possible for change outputs to be addressedsent to subaddresses? Does thesuch functionality exist in the code now? Ignoring the obvious downside where an actively used wallet would quickly have an issue with a plethora of difficult-to-manage subaddresses, is it possible and does the idea have merit?

When constructing a change output, must it be destined for the main public address?

I was thinking about how the behavior of spending Monero from the same wallet over time induces the risk of eventually linking change outputs when they are later combined and spent. Can this be avoided?

It occurred to me that the wallet will prefer to spend from within particular subaddresses (citation could be useful here), so I was thinking that one way to prevent future linking of change outputs would be to address them to various subaddresses.

Back to the title, is it possible for change outputs to be addressed to subaddresses? Does the functionality exist in the code now? Ignoring the obvious downside where an actively used wallet would quickly have an issue with a plethora of difficult-to-manage subaddresses, is it possible and does the idea have merit?

When constructing a change output, does it have to be sent to the main public address?

I was thinking about how the behavior of spending Monero from the same wallet over time introduces the risk of eventually linking change outputs when they are later combined and spent. Can this be avoided?

It occurred to me that the wallet will prefer to spend from within particular subaddresses (citation could be useful here), so I was thinking that one way to prevent future linking of change outputs would be to address them to various subaddresses.

Back to the title, is it possible for change outputs to be sent to subaddresses? Does such functionality exist in the code now? Ignoring the obvious downside where an actively used wallet would quickly have an issue with a plethora of difficult-to-manage subaddresses, is it possible and does the idea have merit?

Source Link
scoobybejesus
  • 5.5k
  • 20
  • 42

When constructing a change output, must it be destined for the main public address?

I was thinking about how the behavior of spending Monero from the same wallet over time induces the risk of eventually linking change outputs when they are later combined and spent. Can this be avoided?

It occurred to me that the wallet will prefer to spend from within particular subaddresses (citation could be useful here), so I was thinking that one way to prevent future linking of change outputs would be to address them to various subaddresses.

Back to the title, is it possible for change outputs to be addressed to subaddresses? Does the functionality exist in the code now? Ignoring the obvious downside where an actively used wallet would quickly have an issue with a plethora of difficult-to-manage subaddresses, is it possible and does the idea have merit?