Imagine I have 20 different unspent outputs, ranging in value from 0.0001 BTC - 1.0 BTC.

Now, supposing I need to create and send 0.01 BTC in a raw transaction. I'm wondering how you guys choose what unspent outputs to use.

Obviously any unspent output >= 0.01 can be used, but is there a preferred way of doing this?

listunspent -> pick an unspent output that has the most confirmations and is >= 0.01.
listunspent -> pick any unspent output as long as it's >=0.01.
etc.

I've got a fully functioning web service working with my bitcoin daemon, which I'm pretty happy with. When a withdrawal is requested, I'm doing the following -

settxfee =  16 satoshis / per byte (this seems pretty safe, however I may switch to using 'estimatefee 6')
sendtoaddress (I'm terrified about attempting rawtransactions)

I'm now thinking how to best handle fees so that they won't eat in to any potential profits. Sending to many isn't an option at this point. Withdrawals will come from warm storage.

• Would it make more sense to utilize sendFrom, and then specify a minimum confirmation of ~6? I believe this should reduce fees.
• Is there anything I can do with my warm storage funds, in terms of organising unspent outputs, that will help increase their priority etc and therefore reduce fees?
• In the client it's possible to deduct the transaction fee from the sending amount, is this possible through the daemon?
• Are there any other practices or recommendations I'm missing?

I'm still thinking how to best handle things. Should I eat the tx fees or pass them on. Should I deduct a static fee from all withdrawals or a tiny percentage.

Thanks fbueller.

I think the take-away from your post is to wait for a few confirmations before making any commitments, and use a combination of multi-sig and cold/hot wallets to limit damage from an attack. These are things I'll certainly be implementing!

Standard enough situation, I'm using -walletnotify to call gettransaction, in order to monitor incoming payments.

My plan is to iterate through all outputs and

• only check outputs that have 'category = receive'
• only check outputs that include an address I have presented to a user I.e. stored in my database

Does this sound ok to implement or am I missing something?

Thanks Greg, appreciate all the work you guys have been doing!

I am setting up a Bitcoin shop and I have a couple of questions as follows -

• When using the bitcoind daemon, if I modify/delete the bitcoin.conf file, are there are repercussions doing this?
• More specifically, if I use 'keypool=1000', and then in a few months time decide I need a larger number of addresses, can I simply change this to 100000 and restart the daemon? Will the previous wallets/addresses be removed?

Thanks

Thought I would chime in as I printed off these ducts/covers many months ago, using our office printer  

I have done some testing with a combination of the stock fan, and 2 Scythe fans. I have tried with and without the Ducts also.

Long story short, the best set-up is to only use the stock fan in Push. Adding 1 Scythe to Pull, actually made things worse. And using the 2 Scythes in Push/Pull wasn't anywhere near as effective as the stock! Atleast 5 degrees in the difference if I can remember right.

The Top/Bottom covers are great, and will probably make a noticeable difference.
As for the Ducts, because I'm only using the Stock fan to push, I only have the front Duct mounted. It does improve cooling quite a bit!

If the noise of the stock fan really is a killer, then you can get away with the 2 Scythes in Push/Pull, and also use both front and rear ducts.

Curious to see what these S3 0.5 Silvers are going for.

I bought it a couple of years back. It's currently ungraded, but I have a good inkling it will be in the region of MS68-70 as it looks perfect to me. (Stored in a capsule, never removed)

What is the going rate for these at the moment? Ballpark would suffice. Can upload some photo's later to get a more accurate idea.

Interested in buying a couple of these off you if they still work. Will drop you a PM =)

EDIT - My mistake, I got completely mixed up with 2012/2013 coins. I guess spotcoins.com isn't reliable either as it lists this address as All-Silver.

Ok, let's not get heated about this.

I presumed that these particular 2012 Casascius coins were either All Silver (of which ~1300 exist) OR All Silver w/ Gold Trim (Gold edge + Gold BTC) (of which ~483 exist)

If the coin is indeed the latter, I have learned something new and I apologise. But it doesn't explain why it is listed as All-Silver on various sites.
Otherwise, I would argue it is modified, as it is no longer All-Silver, as provided by Casascius...

Fair question, fair answer I didn't realise people modified their coins.

For clarification, this is an All-Silver round, not an All-Silver with Gold Trim round.

Some people might be mislead by this.

Edit - I'm wrong, it is All-Silver with Gold Trim, and not modified. I got mixed up with 2013/2012 Gold Trim coins

Not to cause a stir or anything, but shouldn't this coin be All-Silver?

I've searched spotcoins + uberbills, both suggest it's an All-Silver coin, not Silver / Gilt.

Sent PM

1.0 BTC

I will be well and truly asleep when this auction finishes, so I've listed my bid above, which is my final bid.

Goodluck to others/iamsterdam if you would like to out-bid.

0.89BTC

That's a pretty good idea. I guess it is useful if users did this upon registering or something. Not useful for older accounts, as the person staking an address could have already compromised it etc.


Anyways....back to my situation...is Theymos the only one that could help me? Any other mods?  

EDIT - I just replied from the account I have actually been using on my laptop until today. Doh

I've been running my S5 for about 6 months now, pointing it at Antpool the entire time.

Before the crazy Hash Rate increase, I was probably averaging 10-12 mBtc/day, which has roughly halved now.

However, the 24Hr earnings stat on the main Dashboard, recently shows anywhere from 15-20 mBtc, which is obviously incorrect, given my daily payout.

This has been going on like this for a couple of weeks now.

Anyone else experience this?

0.85

0.7

I presume you made a typo - your PGP set includes a 2013 0.5 btc, and not a tenth?

Sent you a PM also.