Question about incoming/outgoing merging of transaction identity
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I have a few more questions about sub-addresses, sorry to bother you guys with it, but it's just a bit new to me to get used to the new features.
People said that "accounts" are just user selected groupings of addresses, and have also said that there is no link between individual addresses without any common transactions first.
Now I have a question about 2 possible scenarios:
1) Incoming merger
Suppose you put A,B,C,D in account 1, which represents 1 contextual identity. I assume there is no link here between a secondary account that has no common transactions with it. Althought people have pointed out that there can be linkage between A,B,C,D if we repeatedly receive from the same trading partner multiple transactions on A or B. Obviously if we give them both A,B on the same IP address ,that already links the two, but from what I understood, even if they don't know that A,B are owned by the same person, by repeatedly receiving money to both addresses from the same person, can decode the missing puzzle pieces and see that the 2 accounts are correlated.
2) Outgoing merger
Now suppose there is a 2nd account also owned by the same person, but represending a different contetual identity with addresses E,F,G,H.
Now if we sweep all balances from account 1 and account 2, would that link the 2 accounts together?
What about sweeping just account 1, would that link A,B,C,D together?
( this question was copied from a reddit q&a)
sub-address output-selection output
add a comment |Â
up vote
3
down vote
favorite
I have a few more questions about sub-addresses, sorry to bother you guys with it, but it's just a bit new to me to get used to the new features.
People said that "accounts" are just user selected groupings of addresses, and have also said that there is no link between individual addresses without any common transactions first.
Now I have a question about 2 possible scenarios:
1) Incoming merger
Suppose you put A,B,C,D in account 1, which represents 1 contextual identity. I assume there is no link here between a secondary account that has no common transactions with it. Althought people have pointed out that there can be linkage between A,B,C,D if we repeatedly receive from the same trading partner multiple transactions on A or B. Obviously if we give them both A,B on the same IP address ,that already links the two, but from what I understood, even if they don't know that A,B are owned by the same person, by repeatedly receiving money to both addresses from the same person, can decode the missing puzzle pieces and see that the 2 accounts are correlated.
2) Outgoing merger
Now suppose there is a 2nd account also owned by the same person, but represending a different contetual identity with addresses E,F,G,H.
Now if we sweep all balances from account 1 and account 2, would that link the 2 accounts together?
What about sweeping just account 1, would that link A,B,C,D together?
( this question was copied from a reddit q&a)
sub-address output-selection output
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have a few more questions about sub-addresses, sorry to bother you guys with it, but it's just a bit new to me to get used to the new features.
People said that "accounts" are just user selected groupings of addresses, and have also said that there is no link between individual addresses without any common transactions first.
Now I have a question about 2 possible scenarios:
1) Incoming merger
Suppose you put A,B,C,D in account 1, which represents 1 contextual identity. I assume there is no link here between a secondary account that has no common transactions with it. Althought people have pointed out that there can be linkage between A,B,C,D if we repeatedly receive from the same trading partner multiple transactions on A or B. Obviously if we give them both A,B on the same IP address ,that already links the two, but from what I understood, even if they don't know that A,B are owned by the same person, by repeatedly receiving money to both addresses from the same person, can decode the missing puzzle pieces and see that the 2 accounts are correlated.
2) Outgoing merger
Now suppose there is a 2nd account also owned by the same person, but represending a different contetual identity with addresses E,F,G,H.
Now if we sweep all balances from account 1 and account 2, would that link the 2 accounts together?
What about sweeping just account 1, would that link A,B,C,D together?
( this question was copied from a reddit q&a)
sub-address output-selection output
I have a few more questions about sub-addresses, sorry to bother you guys with it, but it's just a bit new to me to get used to the new features.
People said that "accounts" are just user selected groupings of addresses, and have also said that there is no link between individual addresses without any common transactions first.
Now I have a question about 2 possible scenarios:
1) Incoming merger
Suppose you put A,B,C,D in account 1, which represents 1 contextual identity. I assume there is no link here between a secondary account that has no common transactions with it. Althought people have pointed out that there can be linkage between A,B,C,D if we repeatedly receive from the same trading partner multiple transactions on A or B. Obviously if we give them both A,B on the same IP address ,that already links the two, but from what I understood, even if they don't know that A,B are owned by the same person, by repeatedly receiving money to both addresses from the same person, can decode the missing puzzle pieces and see that the 2 accounts are correlated.
2) Outgoing merger
Now suppose there is a 2nd account also owned by the same person, but represending a different contetual identity with addresses E,F,G,H.
Now if we sweep all balances from account 1 and account 2, would that link the 2 accounts together?
What about sweeping just account 1, would that link A,B,C,D together?
( this question was copied from a reddit q&a)
sub-address output-selection output
edited Aug 6 at 13:52
neversleep
446416
446416
asked Aug 6 at 11:18
Ginger Ale
4,50721038
4,50721038
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
Accounts are groupings of subaddresses for presentation purposes. There is also the side effect that when you spend out of an account, any outputs received at any subaddresses within that account may be combined. This is purely wallet logic.
Funds cannot usually be spent across subaddresses which span multiple accounts because of wallet logic. The wallet requires you transfer funds between accounts (which automatically gives you one level of churn if you do so).
Note that neither subaddresses nor accounts ever appear on the blockchain, because outputs simply appear to have random one-time public keys. You only need to worry about linkage if the same person (or colluding parties) gave outputs to you via many of those subaddresses, and are now observing the blockchain to see if those outputs are ever referenced together in a transaction. Third parties cannot make sense of anything.
Any kind of combination of outputs across subaddresses (whether from the same account or different accounts) will risk linking those subaddresses together, only in the eyes of someone that knows about outputs given to you at those particular subaddresses. There is no such thing as linking accounts together, only linking particular subaddresses together.
So the bottom line is, if you spend outputs together in the same transaction, and those outputs spanned several subaddresses, then those subaddresses are at risk of being linked regardless of whether those subaddresses were all from the same account or from multiple accounts. And again, the risk is only there if someone knows of outputs sent to each of those subaddresses, because only one-time output public keys are written into the blockchain, and addresses/subaddresses are never written into the blockchain.
Finally, if there is no prior suspicion that subaddresses may be linked, then someone is going to have to send multiple outputs per subaddress to you on multiple occasions in order to know whether they're observing random references to outputs or a real pattern. This greatly reduces the threat.
Think of it like this: every time there is a transaction, fresh notes with fresh random serial numbers are given to the recipient. Any time someone spends notes in a transaction, the whole world (via the blockchain) is told about the new random serial numbers generated, as well as the serial numbers of notes that are spent together in that transaction. In addition to the serial numbers of the actual notes being spent, the transaction also includes the serial numbers of lots of other notes that are randomly chosen from the blockchain as decoys. This means no one can be sure which notes are really being spent, but coincidences can be spotted under very particular circumstances by people that gave out particular notes to a particular person whose real identity they know. That's pretty much all the knowledge you need to be able to directly reason about the threat involved.
( answer originally provided by knaccc )
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Accounts are groupings of subaddresses for presentation purposes. There is also the side effect that when you spend out of an account, any outputs received at any subaddresses within that account may be combined. This is purely wallet logic.
Funds cannot usually be spent across subaddresses which span multiple accounts because of wallet logic. The wallet requires you transfer funds between accounts (which automatically gives you one level of churn if you do so).
Note that neither subaddresses nor accounts ever appear on the blockchain, because outputs simply appear to have random one-time public keys. You only need to worry about linkage if the same person (or colluding parties) gave outputs to you via many of those subaddresses, and are now observing the blockchain to see if those outputs are ever referenced together in a transaction. Third parties cannot make sense of anything.
Any kind of combination of outputs across subaddresses (whether from the same account or different accounts) will risk linking those subaddresses together, only in the eyes of someone that knows about outputs given to you at those particular subaddresses. There is no such thing as linking accounts together, only linking particular subaddresses together.
So the bottom line is, if you spend outputs together in the same transaction, and those outputs spanned several subaddresses, then those subaddresses are at risk of being linked regardless of whether those subaddresses were all from the same account or from multiple accounts. And again, the risk is only there if someone knows of outputs sent to each of those subaddresses, because only one-time output public keys are written into the blockchain, and addresses/subaddresses are never written into the blockchain.
Finally, if there is no prior suspicion that subaddresses may be linked, then someone is going to have to send multiple outputs per subaddress to you on multiple occasions in order to know whether they're observing random references to outputs or a real pattern. This greatly reduces the threat.
Think of it like this: every time there is a transaction, fresh notes with fresh random serial numbers are given to the recipient. Any time someone spends notes in a transaction, the whole world (via the blockchain) is told about the new random serial numbers generated, as well as the serial numbers of notes that are spent together in that transaction. In addition to the serial numbers of the actual notes being spent, the transaction also includes the serial numbers of lots of other notes that are randomly chosen from the blockchain as decoys. This means no one can be sure which notes are really being spent, but coincidences can be spotted under very particular circumstances by people that gave out particular notes to a particular person whose real identity they know. That's pretty much all the knowledge you need to be able to directly reason about the threat involved.
( answer originally provided by knaccc )
add a comment |Â
up vote
3
down vote
Accounts are groupings of subaddresses for presentation purposes. There is also the side effect that when you spend out of an account, any outputs received at any subaddresses within that account may be combined. This is purely wallet logic.
Funds cannot usually be spent across subaddresses which span multiple accounts because of wallet logic. The wallet requires you transfer funds between accounts (which automatically gives you one level of churn if you do so).
Note that neither subaddresses nor accounts ever appear on the blockchain, because outputs simply appear to have random one-time public keys. You only need to worry about linkage if the same person (or colluding parties) gave outputs to you via many of those subaddresses, and are now observing the blockchain to see if those outputs are ever referenced together in a transaction. Third parties cannot make sense of anything.
Any kind of combination of outputs across subaddresses (whether from the same account or different accounts) will risk linking those subaddresses together, only in the eyes of someone that knows about outputs given to you at those particular subaddresses. There is no such thing as linking accounts together, only linking particular subaddresses together.
So the bottom line is, if you spend outputs together in the same transaction, and those outputs spanned several subaddresses, then those subaddresses are at risk of being linked regardless of whether those subaddresses were all from the same account or from multiple accounts. And again, the risk is only there if someone knows of outputs sent to each of those subaddresses, because only one-time output public keys are written into the blockchain, and addresses/subaddresses are never written into the blockchain.
Finally, if there is no prior suspicion that subaddresses may be linked, then someone is going to have to send multiple outputs per subaddress to you on multiple occasions in order to know whether they're observing random references to outputs or a real pattern. This greatly reduces the threat.
Think of it like this: every time there is a transaction, fresh notes with fresh random serial numbers are given to the recipient. Any time someone spends notes in a transaction, the whole world (via the blockchain) is told about the new random serial numbers generated, as well as the serial numbers of notes that are spent together in that transaction. In addition to the serial numbers of the actual notes being spent, the transaction also includes the serial numbers of lots of other notes that are randomly chosen from the blockchain as decoys. This means no one can be sure which notes are really being spent, but coincidences can be spotted under very particular circumstances by people that gave out particular notes to a particular person whose real identity they know. That's pretty much all the knowledge you need to be able to directly reason about the threat involved.
( answer originally provided by knaccc )
add a comment |Â
up vote
3
down vote
up vote
3
down vote
Accounts are groupings of subaddresses for presentation purposes. There is also the side effect that when you spend out of an account, any outputs received at any subaddresses within that account may be combined. This is purely wallet logic.
Funds cannot usually be spent across subaddresses which span multiple accounts because of wallet logic. The wallet requires you transfer funds between accounts (which automatically gives you one level of churn if you do so).
Note that neither subaddresses nor accounts ever appear on the blockchain, because outputs simply appear to have random one-time public keys. You only need to worry about linkage if the same person (or colluding parties) gave outputs to you via many of those subaddresses, and are now observing the blockchain to see if those outputs are ever referenced together in a transaction. Third parties cannot make sense of anything.
Any kind of combination of outputs across subaddresses (whether from the same account or different accounts) will risk linking those subaddresses together, only in the eyes of someone that knows about outputs given to you at those particular subaddresses. There is no such thing as linking accounts together, only linking particular subaddresses together.
So the bottom line is, if you spend outputs together in the same transaction, and those outputs spanned several subaddresses, then those subaddresses are at risk of being linked regardless of whether those subaddresses were all from the same account or from multiple accounts. And again, the risk is only there if someone knows of outputs sent to each of those subaddresses, because only one-time output public keys are written into the blockchain, and addresses/subaddresses are never written into the blockchain.
Finally, if there is no prior suspicion that subaddresses may be linked, then someone is going to have to send multiple outputs per subaddress to you on multiple occasions in order to know whether they're observing random references to outputs or a real pattern. This greatly reduces the threat.
Think of it like this: every time there is a transaction, fresh notes with fresh random serial numbers are given to the recipient. Any time someone spends notes in a transaction, the whole world (via the blockchain) is told about the new random serial numbers generated, as well as the serial numbers of notes that are spent together in that transaction. In addition to the serial numbers of the actual notes being spent, the transaction also includes the serial numbers of lots of other notes that are randomly chosen from the blockchain as decoys. This means no one can be sure which notes are really being spent, but coincidences can be spotted under very particular circumstances by people that gave out particular notes to a particular person whose real identity they know. That's pretty much all the knowledge you need to be able to directly reason about the threat involved.
( answer originally provided by knaccc )
Accounts are groupings of subaddresses for presentation purposes. There is also the side effect that when you spend out of an account, any outputs received at any subaddresses within that account may be combined. This is purely wallet logic.
Funds cannot usually be spent across subaddresses which span multiple accounts because of wallet logic. The wallet requires you transfer funds between accounts (which automatically gives you one level of churn if you do so).
Note that neither subaddresses nor accounts ever appear on the blockchain, because outputs simply appear to have random one-time public keys. You only need to worry about linkage if the same person (or colluding parties) gave outputs to you via many of those subaddresses, and are now observing the blockchain to see if those outputs are ever referenced together in a transaction. Third parties cannot make sense of anything.
Any kind of combination of outputs across subaddresses (whether from the same account or different accounts) will risk linking those subaddresses together, only in the eyes of someone that knows about outputs given to you at those particular subaddresses. There is no such thing as linking accounts together, only linking particular subaddresses together.
So the bottom line is, if you spend outputs together in the same transaction, and those outputs spanned several subaddresses, then those subaddresses are at risk of being linked regardless of whether those subaddresses were all from the same account or from multiple accounts. And again, the risk is only there if someone knows of outputs sent to each of those subaddresses, because only one-time output public keys are written into the blockchain, and addresses/subaddresses are never written into the blockchain.
Finally, if there is no prior suspicion that subaddresses may be linked, then someone is going to have to send multiple outputs per subaddress to you on multiple occasions in order to know whether they're observing random references to outputs or a real pattern. This greatly reduces the threat.
Think of it like this: every time there is a transaction, fresh notes with fresh random serial numbers are given to the recipient. Any time someone spends notes in a transaction, the whole world (via the blockchain) is told about the new random serial numbers generated, as well as the serial numbers of notes that are spent together in that transaction. In addition to the serial numbers of the actual notes being spent, the transaction also includes the serial numbers of lots of other notes that are randomly chosen from the blockchain as decoys. This means no one can be sure which notes are really being spent, but coincidences can be spotted under very particular circumstances by people that gave out particular notes to a particular person whose real identity they know. That's pretty much all the knowledge you need to be able to directly reason about the threat involved.
( answer originally provided by knaccc )
answered Aug 6 at 11:18
Ginger Ale
4,50721038
4,50721038
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmonero.stackexchange.com%2fquestions%2f9938%2fquestion-about-incoming-outgoing-merging-of-transaction-identity%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password