public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Weigl <Daniel.Weigl@mycelium.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] On-going work: Coin Selection Simulation
Date: Thu, 22 Sep 2016 11:33:18 +0200	[thread overview]
Message-ID: <1aa41a90-2cc6-36c8-d9c5-67d52befabbe@mycelium.com> (raw)
In-Reply-To: <358752cc-48f6-eef8-ae9a-e17a0651ed52@murch.one>

Hi,

Is your simulation code available somewhere?

I was just wondering why mycelium generates a very big UTXO set for <1000sat, because change outputs will never be smaller than 
5460sat (=TransactionUtils.MINIMUM_OUTPUT_VALUE). If the change would be lower, it simply is skipped and added to the miner fee:
	-> https://github.com/mycelium-com/wallet/blob/master/public/bitlib/src/main/java/com/mrd/bitlib/StandardTransactionBuilder.java#L334

Does your simulation account for that?

It might also be that the small UTXO came from external tx and we never spend them, bec. of pruning/privacy. Not sure how we could optimize that.

Cheers,
Daniel

On 2016-09-21 14:58, Murch via bitcoin-dev wrote:
> Hi,
> 
> I'm currently compiling my Master's thesis about Coin Selection and my
> presentation proposal to Scaling Bitcoin has been accepted.
> 
> For my thesis, I have analyzed the Coin Selection problem, created a
> framework to simulate wallet behavior on basis of a sequence of
> payments, and have re-implemented multiple coin selection strategies of
> prominent Bitcoin wallets (Bitcoin Core, Mycelium, Breadwallet, and
> Android Wallet for Bitcoin).
> 
> As the Scaling Bitcoin site suggests that research should be made
> available to this mailing list, I would like to invite you to have a
> look at:
> 
> http://murch.one/wp-content/uploads/2016/09/CoinSelection.pdf
> 
> The PDF (176 kB) contains a two page description of my on-going work,
> including preliminary simulation results, and three figures showing the
> simulated wallets' UTXO compositions at the end of the simulation.
> 
> I can provide further information as requested, and would welcome any
> feedback.
> 
> →→ If anyone has another sequence of incoming and outgoing payment
> amounts at hand that I could run my simulation on, I'd love to hear
> about it.
> 
> Regards
> 
> Murch
> 
> 
> 
> 
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 


  parent reply	other threads:[~2016-09-22  9:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 12:58 [bitcoin-dev] On-going work: Coin Selection Simulation Murch
2016-09-21 15:02 ` Andreas Schildbach
2016-09-21 22:40   ` Chris Priest
2016-09-22  9:33 ` Daniel Weigl [this message]
2016-09-23  9:11   ` Murch
2016-09-23  9:35     ` Daniel Weigl
2016-10-21 14:09     ` Murch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1aa41a90-2cc6-36c8-d9c5-67d52befabbe@mycelium.com \
    --to=daniel.weigl@mycelium.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox