Bitcoin Forum
December 04, 2016, 10:16:02 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Transaction overhead and doing addr->addr transactions  (Read 522 times)
DariusAsh
Newbie
*
Offline Offline

Activity: 3


View Profile
March 21, 2012, 06:43:49 PM
 #1

So when you do a bitcoin transaction, you typically take a bunch of addresses, as inputs and you have one output. Due to this blend of addresses for input, I would argue (and many others have as well) that this makes a trail that is easy to trace back to many sources that would destroy your anonymity.

Now if each transaction only included one input and one output, and to pay someone you did a series of transactions, this would be extremely difficult to track, especially if the receiver gave you multiple addresses to send to.

So what would be the typical block byte overhead of doing multiple transactions (ignore fees):
addr_a -> addr_A
addr_b -> addr_B
addr_c -> addr_C
addr_c -> addr_D

vs
the typical case of a single transaction:
( addr_a & addr_b & addr_c & addr_d )-> addr_A


(I am using upper case letters for receivers)

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Meni Rosenfeld
Donator
Legendary
*
Offline Offline

Activity: 1890



View Profile WWW
March 21, 2012, 07:13:45 PM
 #2

If everyone did that always, coins would be split but never merged, causing an increasingly large number of transactions required per operation, and a blowup of the overhead.

1EofoZNBhWQ3kxfKnvWkhtMns4AivZArhr   |   Who am I?   |   bitcoin-otc WoT
Bitcoil - Exchange bitcoins for ILS (thread)   |   Israel Bitcoin community homepage (thread)
Analysis of Bitcoin Pooled Mining Reward Systems (thread, summary)  |   PureMining - Infinite-term, deterministic mining bond
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!