Privacy - Revision history

CoinWallet: /* Coin Wallet */

2026-04-28T13:59:09Z

Coin Wallet

← Older revision		Revision as of 13:59, 28 April 2026
Line 897:		Line 897:
	This multi-platform approach ensures users can access Coin Wallet securely whether through Tor browser using onion addresses or through dedicated applications with Tor VPN connectivity, providing flexible privacy options for different use cases.		This multi-platform approach ensures users can access Coin Wallet securely whether through Tor browser using onion addresses or through dedicated applications with Tor VPN connectivity, providing flexible privacy options for different use cases.

	Main article [[~~Coinwallet~~]]		Main article [[Coin Wallet]]

	== Examples and case studies ==		== Examples and case studies ==

CoinWallet: /* Coin Wallet */

2026-02-10T14:23:29Z

Coin Wallet

← Older revision		Revision as of 14:23, 10 February 2026
Line 896:		Line 896:

	This multi-platform approach ensures users can access Coin Wallet securely whether through Tor browser using onion addresses or through dedicated applications with Tor VPN connectivity, providing flexible privacy options for different use cases.		This multi-platform approach ensures users can access Coin Wallet securely whether through Tor browser using onion addresses or through dedicated applications with Tor VPN connectivity, providing flexible privacy options for different use cases.

			Main article [[Coinwallet]]

	== Examples and case studies ==		== Examples and case studies ==

CoinWallet: /* Existing privacy solutions */

2025-12-10T15:37:13Z

Existing privacy solutions

← Older revision		Revision as of 15:37, 10 December 2025
Line 888:		Line 888:

	In addition to Bitcoin, Unstoppable Wallet is a multi-coin wallet that supports other cryptocurrencies, offering the same high standards of privacy and control for various digital assets.		In addition to Bitcoin, Unstoppable Wallet is a multi-coin wallet that supports other cryptocurrencies, offering the same high standards of privacy and control for various digital assets.

			=== Coin Wallet ===

			'''Coin Wallet''' is a self-custodial, open-source cryptocurrency wallet that provides comprehensive [[Tor]] integration across multiple platforms. The wallet is accessible via a web interface through onion addresses, ensuring anonymous access directly through the Tor network.

			In addition to the web version, Coin Wallet offers native desktop and mobile applications that can be connected to Tor VPN, allowing users to route all application traffic through the Tor network for enhanced privacy and IP address protection.

			This multi-platform approach ensures users can access Coin Wallet securely whether through Tor browser using onion addresses or through dedicated applications with Tor VPN connectivity, providing flexible privacy options for different use cases.

	== Examples and case studies ==		== Examples and case studies ==

Acl1970: /* Bad privacy example - Receiving donations spied on with mystery shopper payments */ I think the new version has the intended meaning.

2025-02-09T17:11:37Z

Bad privacy example - Receiving donations spied on with mystery shopper payments: I think the new version has the intended meaning.

← Older revision		Revision as of 17:11, 9 February 2025
Line 1,042:		Line 1,042:
	# The adversary now has a good idea of your total donation income.		# The adversary now has a good idea of your total donation income.

	Lesson: [[Mystery_shopper_payments\|mystery shopper payments]] can be used to spy on people, even ~~then~~ they avoid [[address reuse]]. Be mindful of what is being revealed with the [[common-input-ownership heuristic]].		Lesson: [[Mystery_shopper_payments\|mystery shopper payments]] can be used to spy on people, even if they avoid [[address reuse]]. Be mindful of what is being revealed with the [[common-input-ownership heuristic]].

	=== Real life example - Bitcoin-stealing malware using static addresses ===		=== Real life example - Bitcoin-stealing malware using static addresses ===

Acl1970: /* Example - Receiving donations privately */ Address 1addrF was the same in Casino2 and Futures Exchange. Corrected.

2025-02-09T16:35:09Z

Example - Receiving donations privately: Address 1addrF was the same in Casino2 and Futures Exchange. Corrected.

← Older revision		Revision as of 16:35, 9 February 2025
Line 967:		Line 967:

	Wallet Casino1 Altcoin Exchange Casino2 Futures Exchange Wallet		Wallet Casino1 Altcoin Exchange Casino2 Futures Exchange Wallet
	1btc -> 1addrA 1btc -> 1addrB 0.1btc -> 1addrE 0.1btc -> 1addrG 0.4btc -> ~~1addrH~~ 0.25btc		1btc -> 1addrA 1btc -> 1addrB 0.1btc -> 1addrE 0.1btc -> 1addrG 0.4btc -> 1addrI 0.25btc
	-> 1addrC 0.2btc -> 1addrF 0.9btc -> ~~1addrF~~ 0.6btc -> ~~1addrI~~ 0.25btc		-> 1addrC 0.2btc -> 1addrF 0.9btc -> 1addrH 0.6btc -> 1addrJ 0.25btc
	-> 1addrD 0.7btc -> ~~1addrJ~~ 0.25btc		-> 1addrD 0.7btc -> 1addrK 0.25btc
	-> ~~1addrK~~ 0.25btc		-> 1addrL 0.25btc

	As before the [[full node]] wallet allows your wallet to learn its own history privately, while Tor broadcasting hides your IP address used when sending a [[transaction]]. Using many different amounts stops [[#Amount correlation\|amount correlation]] from providing clues that can ruin your privacy. Using multiple bitcoin websites means a single website which co-operates with the adversary won't be enough to completely ruin your privacy. There is custodial risk as each website has the power to steal your money, but in this example the bitcoin amount is relatively low so the risk is acceptable.		As before the [[full node]] wallet allows your wallet to learn its own history privately, while Tor broadcasting hides your IP address used when sending a [[transaction]]. Using many different amounts stops [[#Amount correlation\|amount correlation]] from providing clues that can ruin your privacy. Using multiple bitcoin websites means a single website which co-operates with the adversary won't be enough to completely ruin your privacy. There is custodial risk as each website has the power to steal your money, but in this example the bitcoin amount is relatively low so the risk is acceptable.

Ddadybayo: /* Existing privacy solutions */

2024-10-17T12:30:14Z

Existing privacy solutions

← Older revision		Revision as of 12:30, 17 October 2024
Line 878:		Line 878:

	Main article: [[MercuryWallet]]		Main article: [[MercuryWallet]]

			=== Unstoppable Wallet ===

			'''Unstoppable Wallet''' is a '''privacy-focused''', open-source, non-custodial mobile wallet that provides unmatched control over your Bitcoin. Designed with privacy at its core, it integrates seamless [[Tor]] support, ensuring all network traffic is routed through the Tor network, keeping your IP address hidden from prying eyes. The wallet avoids address reuse by generating new addresses for each transaction, safeguarding users against linking attacks.

			With transaction input/output shuffling and [[UTXO]] control, Unstoppable Wallet allows users to manually select which UTXOs to use for each transaction, offering on-demand privacy fine-tuning for sensitive use cases. This advanced feature is ideal for Bitcoin users seeking precise control over their transaction history.

			The wallet also includes a duress mode to help users safely navigate coercive situations, protecting their Bitcoin discreetly. Built with [[SPV]] (Simplified Payment Verification) capabilities, it delivers a trust-minimized experience, allowing users to verify their Bitcoin transactions directly without relying on third-party servers.

			In addition to Bitcoin, Unstoppable Wallet is a multi-coin wallet that supports other cryptocurrencies, offering the same high standards of privacy and control for various digital assets.

	== Examples and case studies ==		== Examples and case studies ==

NotATether: add silent payments

2024-06-24T09:28:31Z

add silent payments

← Older revision		Revision as of 09:28, 24 June 2024
Line 656:		Line 656:

	If PayJoin [[transaction]]s became even moderately used then it would make the [[common-input-ownership heuristic]] be completely flawed in practice. As they are undetectable we wouldn't even know whether they are being used today. As [[transaction surveillance company\|transaction surveillance companies]] mostly depend on that heuristic, as of 2019 there is great excitement about the PayJoin idea<ref>https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-August/016340.html</ref>.		If PayJoin [[transaction]]s became even moderately used then it would make the [[common-input-ownership heuristic]] be completely flawed in practice. As they are undetectable we wouldn't even know whether they are being used today. As [[transaction surveillance company\|transaction surveillance companies]] mostly depend on that heuristic, as of 2019 there is great excitement about the PayJoin idea<ref>https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-August/016340.html</ref>.

			=== Silent Payments ===
			'''Silent Payments''' are a method for people to privately send transactions to each other created by Ruben Somsen<ref>https://github.com/bitcoin/bips/blob/master/bip-0352.mediawiki</ref>. It works by creating a reusable address that exists outside of the blockchain, and is therefore not a blockchain address. The sender can use this off-chain address to generate a Taproot address by using their private key and the receiver's public key. Once the address is created, it can be used to send a regular bitcoin transaction. A typical Silent Payment address looks like this:

			<code>sp1qqttuwe3e5mqqw0lpftpewrrtq4cq6lmjn0wgfqvnee9p7g0cjjs9cq6d848qqw37pzflk6c26k84ry96mlhh85s907al62gm6fl0xf8fusvktrxj</code>

			The receiver of the silent payment uses their private key and the sender's public key to scan for the transaction in each block. This exploits the fact that both combinations of private and public keys generate the same resulting public key, and ultimately the same address.

			Silent payments are non-interactive, allowing the sender to create a transaction without the receiver being online. They are also undetectable to anyone except for the sender and the receiver. It also does not use any extra transaction space on the blockchain.

			As of 2024, Silent Payments are supported by [https://cakewallet.com/ Cake Wallet], [https://app.silentium.dev/ Silentium Wallet], and [https://seedsigner.com/ SeedSigner], as beta functionality.

	=== CoinSwap ===		=== CoinSwap ===

NotATether: /* Centralized mixers */

2024-06-24T09:03:23Z

Centralized mixers

← Older revision		Revision as of 09:03, 24 June 2024
Line 615:		Line 615:
	This is an old method for breaking the [[#Transaction graph\|transaction graph]]. Also called "tumblers" or "washers". A user would send bitcoins to a [[Bitcoin mixer\|mixing service]] and the service would send different bitcoins back to the user, minus a fee. In theory an adversary observing the blockchain would be unable to link the incoming and outgoing [[transaction]]s.		This is an old method for breaking the [[#Transaction graph\|transaction graph]]. Also called "tumblers" or "washers". A user would send bitcoins to a [[Bitcoin mixer\|mixing service]] and the service would send different bitcoins back to the user, minus a fee. In theory an adversary observing the blockchain would be unable to link the incoming and outgoing [[transaction]]s.

	There are several downsides to this. The mixer it must be trusted to keep secret the linkage between the incoming and outgoing transactions. Also the mixer must be trusted not to steal coins. This risk of stealing creates reputation effects; older and more established mixers will have a better reputation and will be able to charge fees far above the marginal cost of mixing coins. Also as there is no way to sell reputation, the ecosystem of mixers will be filled with occasional exit scams.		There are several downsides to this. The mixer it must be trusted to keep secret the linkage between the incoming and outgoing transactions. Also the mixer must be trusted not to steal coins. This risk of stealing creates reputation effects; older and more established mixers will have a better reputation and will be able to charge fees far above the marginal cost of mixing coins. Also as there is no way to sell reputation, the ecosystem of mixers will be filled with occasional exit scams. Additionally, the usage of mixers by criminals has caused law enforcement to seize or sanction several mixers in recent times.

	There is a better alternative to mixers which has essentially the same privacy and custody risks. A user could deposit and then withdraw coins from any regular bitcoin website that has a hot wallet. As long as the bitcoin service doesn't require any other information from the user, it has the same privacy and custody aspects as a centralized mixer and is also much cheaper. Examples of suitable bitcoin services are bitcoin casinos, bitcoin poker websites, tipping websites, altcoin exchanges or online marketplaces<ref>https://gist.github.com/chris-belcher/00255ecfe1bc4984fcf7c65e25aa8b4b#worked-example-for-tumbler-replacement</ref>.		There is a better alternative to mixers which has essentially the same privacy and custody risks. A user could deposit and then withdraw coins from any regular bitcoin website that has a hot wallet. As long as the bitcoin service doesn't require any other information from the user, it has the same privacy and custody aspects as a centralized mixer and is also much cheaper. Examples of suitable bitcoin services are bitcoin casinos, bitcoin poker websites, tipping websites, altcoin exchanges or online marketplaces<ref>https://gist.github.com/chris-belcher/00255ecfe1bc4984fcf7c65e25aa8b4b#worked-example-for-tumbler-replacement</ref>.

NotATether: Schnorr was enabled in the Taproot upgrade (need to create page for Taproot)

2024-06-24T08:59:27Z

Schnorr was enabled in the Taproot upgrade (need to create page for Taproot)

← Older revision		Revision as of 08:59, 24 June 2024
Line 587:		Line 587:
	Instantiating [Scriptless] 2P-ECDSA: Fungible 2-of-2 MultiSigs for Today's Bitcoin. https://www.youtube.com/watch?v=3mJURLD2XS8&t=3623 https://diyhpl.us/wiki/transcripts/scalingbitcoin/tokyo-2018/scriptless-ecdsa/</ref>. It doesn't need any consensus changes because bitcoin already uses [[Elliptic Curve Digital Signature Algorithm\|ECDSA]].		Instantiating [Scriptless] 2P-ECDSA: Fungible 2-of-2 MultiSigs for Today's Bitcoin. https://www.youtube.com/watch?v=3mJURLD2XS8&t=3623 https://diyhpl.us/wiki/transcripts/scalingbitcoin/tokyo-2018/scriptless-ecdsa/</ref>. It doesn't need any consensus changes because bitcoin already uses [[Elliptic Curve Digital Signature Algorithm\|ECDSA]].

	'''[[Schnorr]]''' is a digital signature scheme which has many benefits over the status-quo [[Elliptic Curve Digital Signature Algorithm\|ECDSA]]<ref>https://medium.com/cryptoadvance/how-schnorr-signatures-may-improve-bitcoin-91655bcb4744</ref><ref>https://bitcoincore.org/en/2017/03/23/schnorr-signature-aggregation/</ref>. One side effect is that any N-of-N<ref>https://blockstream.com/2018/01/23/musig-key-aggregation-schnorr-signatures/</ref> and M-of-N [[multisignature]] can be easily made to look like a single-sig when included on the blockchain. Adding [[Schnorr]] to bitcoin requires a [[Softfork]] consensus change. ~~As of 2019~~ a ~~design for the signature scheme has been proposed<ref>https://github.com/sipa/bips/blob/bip-schnorr/bip-schnorr.mediawiki</ref>. The required~~ [[softfork]] ~~consensus change is still in the design stage~~ as of ~~early-2019~~.		'''[[Schnorr]]''' is a digital signature scheme which has many benefits over the status-quo [[Elliptic Curve Digital Signature Algorithm\|ECDSA]]<ref>https://medium.com/cryptoadvance/how-schnorr-signatures-may-improve-bitcoin-91655bcb4744</ref><ref>https://bitcoincore.org/en/2017/03/23/schnorr-signature-aggregation/</ref>. One side effect is that any N-of-N<ref>https://blockstream.com/2018/01/23/musig-key-aggregation-schnorr-signatures/</ref> and M-of-N [[multisignature]] can be easily made to look like a single-sig when included on the blockchain. Adding [[Schnorr]] to bitcoin requires a [[Softfork]] consensus change. In 2021, the Bitcoin network underwent a [[softfork]] to enable Schnorr signatures as part of the [[Taproot]] upgrade.

	'''[[Scriptless scripts]]''' are a set of cryptographic protocols which provide a way of replicating the logic of [[script]] without actually having the script conditions visible, which increases privacy and scalability by removing information from the blockchain<ref>https://bitcoinmagazine.com/articles/scriptless-scripts-how-bitcoin-can-support-smart-contracts-without-smart-contracts/</ref><ref>https://download.wpsoftware.net/bitcoin/wizardry/mw-slides/2017-03-mit-bitcoin-expo/slides.pdf</ref><ref>https://joinmarket.me/blog/blog/flipping-the-scriptless-script-on-schnorr/</ref><ref>https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-April/001221.html</ref>. This is generally aimed at protocols involving [[Hash Time Locked Contracts]] such as [[Lightning Network]] and [[CoinSwap]].		'''[[Scriptless scripts]]''' are a set of cryptographic protocols which provide a way of replicating the logic of [[script]] without actually having the script conditions visible, which increases privacy and scalability by removing information from the blockchain<ref>https://bitcoinmagazine.com/articles/scriptless-scripts-how-bitcoin-can-support-smart-contracts-without-smart-contracts/</ref><ref>https://download.wpsoftware.net/bitcoin/wizardry/mw-slides/2017-03-mit-bitcoin-expo/slides.pdf</ref><ref>https://joinmarket.me/blog/blog/flipping-the-scriptless-script-on-schnorr/</ref><ref>https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-April/001221.html</ref>. This is generally aimed at protocols involving [[Hash Time Locked Contracts]] such as [[Lightning Network]] and [[CoinSwap]].

NotATether: add bip324

2024-06-24T08:00:18Z

add bip324

← Older revision		Revision as of 08:00, 24 June 2024
Line 504:		Line 504:
	[[Bitcoin Core]] and its forks use an algorithm known as trickling when relaying unconfirmed transactions, with the aim of making it as difficult as possible for sybil attackers to find the source IP address of a [[transaction]]. For each peer, the node keeps a list of transactions that it is going to [[Network#Messages\|inv]] to it. It sends [[Network#Messages\|inv's]] for transactions periodically with a random delay between each [[Network#Messages\|inv]]. Transactions are selected to go into the [[Network#Messages\|inv]] message somewhat randomly and according to some metrics involving fee rate. It selects a limited number of transactions to [[Network#Messages\|inv]]. The algorithm creates the possibility that a peered node may hear about an unconfirmed transaction from the creator's neighbours rather than the creator node itself<ref>https://bitcoin.stackexchange.com/questions/83018/transaction-relay-and-trickling-in-bitcoin</ref><ref>https://github.com/bitcoin/bitcoin/issues/13298</ref><ref>https://github.com/bitcoin/bitcoin/pull/7125</ref><ref>https://github.com/bitcoin/bitcoin/pull/7840</ref>. However adversaries can still sometimes obtain privacy-relevant information.		[[Bitcoin Core]] and its forks use an algorithm known as trickling when relaying unconfirmed transactions, with the aim of making it as difficult as possible for sybil attackers to find the source IP address of a [[transaction]]. For each peer, the node keeps a list of transactions that it is going to [[Network#Messages\|inv]] to it. It sends [[Network#Messages\|inv's]] for transactions periodically with a random delay between each [[Network#Messages\|inv]]. Transactions are selected to go into the [[Network#Messages\|inv]] message somewhat randomly and according to some metrics involving fee rate. It selects a limited number of transactions to [[Network#Messages\|inv]]. The algorithm creates the possibility that a peered node may hear about an unconfirmed transaction from the creator's neighbours rather than the creator node itself<ref>https://bitcoin.stackexchange.com/questions/83018/transaction-relay-and-trickling-in-bitcoin</ref><ref>https://github.com/bitcoin/bitcoin/issues/13298</ref><ref>https://github.com/bitcoin/bitcoin/pull/7125</ref><ref>https://github.com/bitcoin/bitcoin/pull/7840</ref>. However adversaries can still sometimes obtain privacy-relevant information.

	Encrypting messages between peers as in [https://github.com/bitcoin/bips/blob/master/bip-0151.mediawiki BIP 151] would make it harder for a passive attacker such as an ISP or Wifi provider to see the exact messages sent and received by a bitcoin node.		Encrypting messages between peers as in [https://github.com/bitcoin/bips/blob/master/bip-0151.mediawiki BIP 151] and [https://github.com/bitcoin/bips/blob/master/bip-0324.mediawiki BIP 324] would make it harder for a passive attacker such as an ISP or Wifi provider to see the exact messages sent and received by a bitcoin node. BIP 324 transport is enabled by default in Bitcoin Core 27.0 and later versions.

	==== Tor and tor broadcasting ====		==== Tor and tor broadcasting ====