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?
Topic: Tumbler Service Transaction Process & Functionality (Read 694 times)
Jump to: