As part of our scans over at https://mnowatch.org/ I came across this address XvVwJbTFzVd2FCCVFDg89wWiSS5WBy266n what is interesting about it is the inputs. For example, consider these transactions.
When we look at the input side, we see
This is a bunch of inputs (MN rewards) being collated into one UTXO, this is what MNOwatch bots scan for. The owner of this address, must also control all those masternodes in order to be able to spend their rewards.
The above TX shows a privateSend denominate transaction, this MNO is now mixing his coins, but wait, he made one fatal error and that is to combine all his inputs into one new input which then links all those mastenode nodes together.
From MNOwatch bots we were able to determine that this MNO owns the following masternodes and they are now categorised in our database.
So, what did he do wrong? How did he compromise some of his privacy when trying to do the right thing? This MNO likely has his payout addresses on his hardware wallet and is sending the rewards periodically to his desktop QT wallet for mixing. This results in the inputs being combined in this way. The ideal approach is to define/update the masternode to pay to an address (different one for each node!) that is exists in the Desktop QT wallet. That way the payments will arrive in the QT wallet and when he turns on mixing, the algorithm will NEVER combine inputs thus keeping the anonymity of the MNO, and we would never know how many nodes he has. As the mixing progresses, he can then send the mixed inputs back to the hardware wallet or where ever and we will be none the wiser.
Bottom line, when mixing, never combine inputs prior to mixing, doing so proves ownership of all inputs to that transaction and reduces your privacy.
When we look at the input side, we see
This is a bunch of inputs (MN rewards) being collated into one UTXO, this is what MNOwatch bots scan for. The owner of this address, must also control all those masternodes in order to be able to spend their rewards.
The above TX shows a privateSend denominate transaction, this MNO is now mixing his coins, but wait, he made one fatal error and that is to combine all his inputs into one new input which then links all those mastenode nodes together.
From MNOwatch bots we were able to determine that this MNO owns the following masternodes and they are now categorised in our database.
Payout address
XevprsdaprzNQZzjAPWvELsmnx6MoBHkwF
XgX8TULNf9A8jmCKLKuaCNkxtxhuMENsHs
XgzS4YtMY63eVMGsPqfaBbBVk18BwXbJ4X
XinSvdZjEqvPDMPhndr4UEXSsrP2BExbsH
XiZ2tafwbYeNKLVkjb4eiGr2Gc2Z42sUmm
XpejiLrtCttrzMCqHAjocEQD3FJxPpVS9R
Xrjde2tT5JU73BZXJv4Bzf3nur5KxBkzr3
XuuU5MfXNPc6oHfDeuwwj3qbh913QtArUd
XuZU25WEfkRXeCucJ8eGvDGt5vHqiTmUYP
Xwi6LLZD5Ze1ixnCyxQ93981GLjE5dGH5y
So, what did he do wrong? How did he compromise some of his privacy when trying to do the right thing? This MNO likely has his payout addresses on his hardware wallet and is sending the rewards periodically to his desktop QT wallet for mixing. This results in the inputs being combined in this way. The ideal approach is to define/update the masternode to pay to an address (different one for each node!) that is exists in the Desktop QT wallet. That way the payments will arrive in the QT wallet and when he turns on mixing, the algorithm will NEVER combine inputs thus keeping the anonymity of the MNO, and we would never know how many nodes he has. As the mixing progresses, he can then send the mixed inputs back to the hardware wallet or where ever and we will be none the wiser.
Bottom line, when mixing, never combine inputs prior to mixing, doing so proves ownership of all inputs to that transaction and reduces your privacy.