Wallet (console and FFI) should have setting to not choose outputs that reveal the address #4403
Assignees
Comments
stringhandler
pushed a commit
that referenced
this issue
Aug 31, 2022
…reveal the address #4403 (#4516) Description --- #4403 Wallet (console and FFI) should have setting to not choose outputs that reveal the address #4403 Motivation and Context --- Problem Wallets currently will choose the best outputs as inputs when spending, however since a lurking base node can generate a transaction graph of inputs to outputs with relative ease, a wallet may reveal its transaction history by including a (non-stealth address) one-sided payment. For example, an attacker wishing to know the transaction graph of a public key PK_Alice can send a one-sided payment to PK_Alice using the Tariscript Push(PK_Alice). At some point, Alice's wallet spends this transaction without realizing it. Possible solution Could change the wallet to have a config setting, to not include one-sided payments by default when spending How Has This Been Tested? ---
Repository owner
moved this from In Progress
to Done
in Tari Esme Testnet
Aug 31, 2022
jorgeantonio21
pushed a commit
to jorgeantonio21/tari
that referenced
this issue
Aug 31, 2022
…reveal the address tari-project#4403 (tari-project#4516) Description --- tari-project#4403 Wallet (console and FFI) should have setting to not choose outputs that reveal the address tari-project#4403 Motivation and Context --- Problem Wallets currently will choose the best outputs as inputs when spending, however since a lurking base node can generate a transaction graph of inputs to outputs with relative ease, a wallet may reveal its transaction history by including a (non-stealth address) one-sided payment. For example, an attacker wishing to know the transaction graph of a public key PK_Alice can send a one-sided payment to PK_Alice using the Tariscript Push(PK_Alice). At some point, Alice's wallet spends this transaction without realizing it. Possible solution Could change the wallet to have a config setting, to not include one-sided payments by default when spending How Has This Been Tested? ---
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Wallets currently will choose the best outputs as inputs when spending, however since a lurking base node can generate a transaction graph of inputs to outputs with relative ease, a wallet may reveal its transaction history by including a (non-stealth address) one-sided payment.
For example, an attacker wishing to know the transaction graph of a public key
PK_Alicecan send a one-sided payment toPK_Aliceusing the TariscriptPush(PK_Alice). At some point, Alice's wallet spends this transaction without realizing it.Possible solution
The text was updated successfully, but these errors were encountered: