Bitcoin Forum
July 16, 2019, 11:13:20 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Tumbler Service Transaction Process & Functionality  (Read 614 times)
airborne305
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
December 30, 2013, 07:02:47 PM
 #1

I’m seeking feedback, opinions, options, functionality, practical use, and/or any input you may have. My curiosity is on the bitcoin API side, not any programming (PHP, py, java, ajax, etc.)

In regards to tumbling services, it is my understanding that they log balances, mix and join balances, shuffle (or Tumble), then make sure you get the correct output over a period of time and x amount of transactions.
What are some of the ways these are done efficiently? Is there a better way to do this than using [sendfrom], [sendmany], and/or [sendtoaddress]?
Are there other methods that can be used that would add a layer of difficulty of following addresses? What about [sendrawtransaction]?

TLDR: are tumblers just a mixture of [sendfrom], [sendmany], and/or [sendtoaddress]? Any input or complaints on traditional services/functionality?
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!