Skip to main content
deleted 1 character in body
Source Link
kenshi84
  • 2.5k
  • 1
  • 14
  • 33

No.

Given an output pubkey P in a new transaction with its tx pubkey being R, you can recognize it as your incoming transfer by using your private viewkey a by, looking upfor P - Hs(a*R)*G in your hashtable and finding an entry recoding the sub-address's index j. Its private key P=x*G is obtained as x = Hs(a*R) + b + Hs(a || j). So you need both of the original private view and spend keys for receiving funds transferred to sub-addresses and disposable addresses.

No.

Given an output pubkey P in a new transaction with its tx pubkey being R, you can recognize it as your incoming transfer by using your private viewkey a by looking up P - Hs(a*R)*G in your hashtable and finding an entry recoding the sub-address's index j. Its private key P=x*G is obtained as x = Hs(a*R) + b + Hs(a || j). So you need both of the original private view and spend keys for receiving funds transferred to sub-addresses and disposable addresses.

No.

Given an output pubkey P in a new transaction with its tx pubkey being R, you can recognize it as your incoming transfer by using your private viewkey a, looking for P - Hs(a*R)*G in your hashtable and finding an entry recoding the sub-address's index j. Its private key P=x*G is obtained as x = Hs(a*R) + b + Hs(a || j). So you need both of the original private view and spend keys for receiving funds transferred to sub-addresses and disposable addresses.

Source Link
kenshi84
  • 2.5k
  • 1
  • 14
  • 33

No.

Given an output pubkey P in a new transaction with its tx pubkey being R, you can recognize it as your incoming transfer by using your private viewkey a by looking up P - Hs(a*R)*G in your hashtable and finding an entry recoding the sub-address's index j. Its private key P=x*G is obtained as x = Hs(a*R) + b + Hs(a || j). So you need both of the original private view and spend keys for receiving funds transferred to sub-addresses and disposable addresses.