1 2016-11-23 20:00:05 <adiabat> Hi, question on coinbase txs: can they have multiple inputs?
 2 2016-11-23 20:02:35 <adiabat> txin[0] is the coinbase field, where you commit to the height, give shoutouts to your friends, etc
 3 2016-11-23 20:02:49 <adiabat> but can you have a txin[1] that spends stuff in the first tx in a block?
 4 2016-11-23 20:03:02 <sipa> nope
 5 2016-11-23 20:03:07 <sipa> (unfortunately)
 6 2016-11-23 20:04:11 <adiabat> ok, didn't think so but wasn't sure.  Actually sortof fortunately for my use
 7 2016-11-23 20:04:47 <adiabat> tx[0] can never spend utxos so can be ignored which helps a bit
 8 2016-11-23 23:29:43 <rusty> Anyone thought about removing the dust limit?  In a feemarket world, it seems a little useless, and for things like lightning it complicates things (we have to always keep everything above the dust limit otherwise risk holding a non-standard tx).
 9 2016-11-23 23:43:18 <molz> rusty, most of the devs are in #bitcoin-core-dev channel
10 2016-11-23 23:44:09 <rusty> molz: thanks, repasted there.  It's a bit wider than core, but that's a start I guess.
11 2016-11-23 23:45:05 <molz> np :)
12 2016-11-23 23:56:31 <sipa> rusty: i think no rational wallet would ever produce dust, even without the rule
13 2016-11-23 23:56:58 <sipa> rusty: as the mempool feerate is always higher than the relay feerate, and the relay feerate is used to compute the dust limit
14 2016-11-23 23:57:28 <sipa> you shouldn't create outputs that cost more to spend than they're worth
15 2016-11-23 23:57:49 <rusty> sipa: too bad if fee rates change between creating them and spending them :(
16 2016-11-23 23:58:28 <rusty> sipa: which is a big problem.
17 2016-11-23 23:58:41 <rusty> (for lightning)
18 2016-11-23 23:58:50 <sipa> rusty: maybe the relay feerate changes, but it's an order of magnitude lower (and should be, imho) than the mempool feerate
19 2016-11-23 23:59:01 <sipa> so i can't imagine this is a big problem in practice