With regards to my Titan, the 4.17 build appears to either fixed or introduced bugs in the validation of hashes using the CPU. The perspective just depends on if I want to believe I've possibly damaged my Titan.

The 4.17 build reports a bad GPU hash about once every 30-45 seconds while the 4.14 build never reported a single one. This is using the exact same startup parameters (-l 294x2 -C 0 -i 0). The rejected rate from 4.14 also matches with p2pool. I also briefly tried -C 1, -C 2 incase they might have any performance impact but I didn't see anything noticeable.

I was hoping it was just a 32 vs. 64bit issue with cudaminer. But that driver issue is unfortunate. I'll have to look into TCC or running linux.

Ah, so if you're using the full scratchpad space right now do you have an idea why I can't use any launch configurations that go over 2.8GB? The program says there isn't enough memory, but according to the calculation there should be. I'm wondering if there is an integer overflow comparison somewhere?

Following the computation on total memory used, what is the reason that not even half of the memory available on the Titan is being used? Up until the last release today (4/14) autotune has always picked a configuration of 300-307x2 (now 263x2) which comes out to about 2.5GB of used memory at most. Since scrypt is a space/computation tradeoff algorithm isn't there potential for almost a doubling in hash performance if the full 6GB could be used?

Btw, the lastest work has been fantastic. My card hashes at a much more consistent rate and about 30khash/s more than previous builds. Fixing the Ctrl-C is just a nice usability improvement.

I only have the one titan, but I've been having similar issues. First run of cudaminer (4/14) and I get a stream of messages saying the CPU could not verify the block. Second run it seems to work, but because of the crash I can't get the cock speed to return to normal levels and it runs at 512Mhz (should be boosted to 1167MHz).

I tried going back to 4/13 but it seems to have issues as well. Prior to this I had only started and used 4/13 once for about a continuous day of hashing with no issues. Now it has been running for half a day and had 0 shares where as I had 9+ in the same period before. I also get the CPU not verifying the hash fairly often, about once a minute yet I can run the card with games or stressing benchmarks for hours and never see an issue.

Edit: The latest release with the Ctrl-C fix seems to have fixed the problem with the core being stuck at 512MHz. Now to see if I get any shares at a reasonable pace.

Guess thats good know that I'm just finding out the behavior of the card more. Is there any reason the titan can't benefit from the advances for the other kernels though? Shouldn't it be using the best kernel not compiled for compute 3.5 until it is understood why the nvcc compiler seems to break 3.5?

Using a titan with texture cache enabled it seems to be performing with more luck. Granted I may not understand all the metrics on P2Pool but I believe the efficiency metric guages the rate at which I share vs. the expected rate and for 2/3 of a day I've been sitting at 120% whereas with the previous 4/09 build it was a little under 100% with the same time.

My hash rate average didn't change much but the variance did. I used to be 150khash/s to 290khash/s with a mean of 22xkhash/s. The gpu has never been consistently 100% utilized and my cpu sits at about 60% utlization. My hash rates now jumps between 350khash/s and 100khash/s settling with an average of 224khash/s.

Your simple solution doesn't work like bdamm outlined. The blockchain is a ledger and unless you have the private key of the account you can't initiate the transaction to reclaim those keys. It is a design intent of bitcoin that currency will be lost, just like our real commodities and currencies are never 100% recycled.

Biometrics devices are expensive toys so far. There hasn't been a serious easy of use device made yet that uses biometrics for authorization. Especially something that you carry around with you at all times, like when you're out at the bar scene, in a concert venue, or a freezing night.

The real hurdle to mass option is consumer protection. That is what made paypal big and until the average joe has confidence they can reclaim funds from an entity who didn't perform their side of the deal cryptocurriences will be backroom currency.

I'm not so sure they'll be able to free up the lost bitcoins. What heuristic can you use to determine it lost and not just being saved? Bitcoin is supposed to be anonymous afterall, so you shouldn't be able to tell that this address belongs to a person who died and will never use those coins.

One thing that will need to happen though is some way for the blockchain to be truncated. It is growing exponentially and it won't be long, a year or so and you'll have to spend $100 or more in storage space to have the chain. Not to mention personal pcs don't particularly like having dbs with that much data in them.

For the avalon ASICs, who is going to spend 75 BTC for one that will be delivered months from now. It feels like the opportunity has passed considering the starting price was just $1300.

Most people are not patient. Like how I'll most likely have moved on and forgotten about trying to help the cudaminer application work on Titan graphics cards.