Auditing incoming transactions in Monero
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
It is said that a view key can expose incoming transactions.
1. Is the view key enough to prove ownership of an incoming transaction?
The stealth address is calculated with
H(Ra)G + B
, so I guess the public spend key must also be given?
2. Can sharing the view key also expose the incoming amounts? Aren't they all blinded with external blinding (mask) factors, so the view key will not be enough?
viewkey stealth-address auditing
add a comment |Â
up vote
1
down vote
favorite
It is said that a view key can expose incoming transactions.
1. Is the view key enough to prove ownership of an incoming transaction?
The stealth address is calculated with
H(Ra)G + B
, so I guess the public spend key must also be given?
2. Can sharing the view key also expose the incoming amounts? Aren't they all blinded with external blinding (mask) factors, so the view key will not be enough?
viewkey stealth-address auditing
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
It is said that a view key can expose incoming transactions.
1. Is the view key enough to prove ownership of an incoming transaction?
The stealth address is calculated with
H(Ra)G + B
, so I guess the public spend key must also be given?
2. Can sharing the view key also expose the incoming amounts? Aren't they all blinded with external blinding (mask) factors, so the view key will not be enough?
viewkey stealth-address auditing
It is said that a view key can expose incoming transactions.
1. Is the view key enough to prove ownership of an incoming transaction?
The stealth address is calculated with
H(Ra)G + B
, so I guess the public spend key must also be given?
2. Can sharing the view key also expose the incoming amounts? Aren't they all blinded with external blinding (mask) factors, so the view key will not be enough?
viewkey stealth-address auditing
viewkey stealth-address auditing
edited 40 mins ago
knaccc
5,193415
5,193415
asked 1 hour ago
oleiba
355
355
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Yes, the view key proves that outputs were destined for a particular wallet address. It cannot be proven whether these outputs were subsequently spent, but it can be guessed that they have been spent if the outputs are referenced in a transaction that creates a change output that is also destined for that same wallet (which someone with the private view key would be able to detect).
Yes, because both the output amounts and the blinding factors are encrypted using the shared secret H(aR) and included as part of the transaction data.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Yes, the view key proves that outputs were destined for a particular wallet address. It cannot be proven whether these outputs were subsequently spent, but it can be guessed that they have been spent if the outputs are referenced in a transaction that creates a change output that is also destined for that same wallet (which someone with the private view key would be able to detect).
Yes, because both the output amounts and the blinding factors are encrypted using the shared secret H(aR) and included as part of the transaction data.
add a comment |Â
up vote
2
down vote
accepted
Yes, the view key proves that outputs were destined for a particular wallet address. It cannot be proven whether these outputs were subsequently spent, but it can be guessed that they have been spent if the outputs are referenced in a transaction that creates a change output that is also destined for that same wallet (which someone with the private view key would be able to detect).
Yes, because both the output amounts and the blinding factors are encrypted using the shared secret H(aR) and included as part of the transaction data.
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Yes, the view key proves that outputs were destined for a particular wallet address. It cannot be proven whether these outputs were subsequently spent, but it can be guessed that they have been spent if the outputs are referenced in a transaction that creates a change output that is also destined for that same wallet (which someone with the private view key would be able to detect).
Yes, because both the output amounts and the blinding factors are encrypted using the shared secret H(aR) and included as part of the transaction data.
Yes, the view key proves that outputs were destined for a particular wallet address. It cannot be proven whether these outputs were subsequently spent, but it can be guessed that they have been spent if the outputs are referenced in a transaction that creates a change output that is also destined for that same wallet (which someone with the private view key would be able to detect).
Yes, because both the output amounts and the blinding factors are encrypted using the shared secret H(aR) and included as part of the transaction data.
answered 43 mins ago
knaccc
5,193415
5,193415
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%2f10294%2fauditing-incoming-transactions-in-monero%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