Bitcoin Forum
July 06, 2024, 08:19:31 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: How does Armory improve privacy ?  (Read 135 times)
Ratatosk (OP)
Sr. Member
****
Offline Offline

Activity: 263
Merit: 250


View Profile
December 13, 2018, 11:20:17 PM
 #1

I sometimes read that Armory improves the privacy of the user and tx, compared to many/most/all other BTC wallets.

Could you please tell me how, what various tech or methods does it use ?

Thank you  Smiley
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3682
Merit: 1347

Armory Developer


View Profile
December 14, 2018, 07:26:14 PM
 #2

There are some minor pieces of code in place to try and improve privacy, and I have more ideas for that, but the crux of the argument is the full node vs remote service model.

A typical wallet is just a GUI with no blockchain processing capacity. That task is serviced by a remote server operated (99% of the time) by the wallet provider. This creates a situation where a 3rd party (whoever is running that server) knows of all your transaction history past, present and future, for all operations you perform with that wallet software.

Armory does not provide such remote service. Instead, the software package comes with a local service for all things blockchain, and requires that you operate your own Bitcoin node, which is its interface with the Bitcoin network.

Therefor all your Bitcoin operations are contained within your own hardware and software stack, and Armory has no phone home/eavesdropping code, therefor there is no way, short of an adversary infiltrating your system, for anyone (devs included) to know what you're doing with your coins but you.

There's also the non negligible advantage that you get to choose which Bitcoin node code you want to run, which itself has some minor privacy implications.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!