gigq

An even smarter criminal would have "mined" the Ripple give away using EC2, there are still people paying for those instances as we speak so surely they would be more profitable than litecoin mining (assuming you sell them right away).

https://www.computingforgood.org/

https://ripple.com/forum/viewtopic.php?f=18&t=4382

Makes you wonder why the criminal didn't launch g2.2xlarge instances which would get 185 kH/s per instance. In fact for awhile there litecoin mining was profitable at spot prices.

http://www.completefusion.com/profitable-litecoin-mining-on-...

One cc2.8xlarge instance will give you 85 kH/s so 20 instances would give 1700 kH/s which only nets about $18 at current market prices / difficulty. So over 2 days he would have made off with a whopping $36.

Yes please do, I'd also contribute.

I believe to claim the reward you have to reproduce the issue, there is already a patch out for the F_FULLFSYNC change.

https://code.google.com/p/leveldb/issues/attachmentText?id=1...

Yep, that's the only way to do it with zero risk. But since btcchina.com is consistently higher than the other top exchanges you'll eventually have to move CNY out of there and bitcoin in. Moving bitcoin there is trivial (which shows how great bitcoin is) but moving CNY out and converting it to USD for the other exchanges is trickier (need a Chinese bank account for example) so I would expect the lag in price to continue.

From an Amazon review:

You can return it to Amazon or Call Sony @ 1(800)345-7669 to schedule a replacement. Mine is broken like everyone elses.

If your console light turns white (and doesn't get stuck at pulsating blue), it could be the HDMI cable or connection issue. Fix with a pin (see Kotaku's article).

If it stays blue and pulsates, try safe mode (turn off system completely, then hold down power for 10 sec and wait till you hear beeps). From here Sony can help you troubleshoot if you wanted to call in. If it wont even boot to safe mode, it's bricked. You can try to troubleshoot on your own if you're adventurous: 1. Hold down power button until the unit powers off and the light goes out. This took about 10 seconds. 2. From power off, enter Safe Mode by holding down the power button until you hear beeps. Release power button after the second beep. The Safe Mode menu will appear with a list of options. 3. Select Option 4 to restore PS4 to factory defaults. Once it's done, the system will restart. 4. In our case, after the reboot, the PS4 automatically entered Safe Mode. This time, they had us select Option 6 to Initialize the PS4. Note that by doing this, you will lose profiles and settings so just be aware that you are basically starting over. Once it's done, the system will restart. 5. When the PS4 comes back up, it will take you through the initial setup again as if it's being booted for the first time.

If you can't get the PS4 to boot into safe mode, it's not your HDMI port. it's an internal issue and you'll have to send it to Sony to be fixed.

There appears to be multiple issues going on that are probably all being filed under the console being bricked. HDMI seems to be causing problems where the console won't show a picture but everything internally is still working. There is also a safe mode you can go into that is fixing the issue for some. And finally there are some that are really just bricked which is probably accurate to the 0.4% rate that Sony claimed.

Also FWIW I received one from Amazon and everything worked fine out of the box.

Will you guys be supporting the previous app for people that have already downloaded it? Or at least not making any API changes that will break it?

The point in the article was that if you sent the coins to an address that never spent any coins (like the reference client does where it will always create a new "change" address for left over coins from a transaction) then the public key of the address that holds your coins will never be seen on the network.

That sounds pretty useful, something I would love to see open sourced as I've thought about making a distributed LevelDB based DB as well.

Any word on how it handles the distribution? Are we talking a quorum based system like Cassandra/Dynamo or are we talking more like a master / key range type system like HBase.

From what I can tell it's not just legacy systems that are the problem. I just tried the system for the first time today and there are multiple form issues (errors like "Error: id" with no further explanation) and broken links (a link to https://www.healthcare.gov/help/how-do-i-choose-marketplace-... for more info results in a 404).

There are only 3600 BTC per day being generated. They can't just generate a few million bitcoins. At best they could do a 51% attack and double spend bitcoin, which would cause problems but it's been done in other digital currencies and the currencies have still survived.

If they did amass a large volume of bitcoins and dumped them on the market the market would drop but like every other drop it would probably be temporary as people love buying cheap BTC when the market crashes (look at the crash after DPR was arrested, bounced back in hours).

I would think it's a pretty safe assumption he already had multiple copies of the wallet/private keys stored before he got arrested.

Just from a redundancy standpoint you don't want one copy of your wallet in one location as it could get corrupted or destroyed in a disaster.

Bitcoin does have the ability to store this kind of information in the actual blockchain, but blockchain.info decided it was not worth the bloat.

http://bitcoin.stackexchange.com/questions/7864/is-a-public-...

Isn't this what http://betsofbitco.in does?

Ah, good to know that functionality was added. I haven't used Cassandra since the 0.6.x days so my knowledge of what's possible there is rusty.

It wasn't really mentioned in the article but if you do both {X1,Y1} and {X2,Y2} as full row updates then no you can't end up with a mixed row.

http://www.datastax.com/dev/blog/row-level-isolation

It's worth noting that HBase has the same method of using LWW on column level updates. While this usually is what you want and like Cassandra it gives you the ability to do fast blind writes there are sometimes that you need to make sure you aren't having conflicting writes.

The solution that HBase employs is to have checkAndPut functionality. Basically what this lets you do is write a value and only successfully save the update if a given column is the value you expect.

So for example you could have a "records" table that has a column called "check" whenever you update a record you pull the old one, do whatever processing you want to do on it, set the "check" column to a new UUID and then save it with a checkAndPut where you specify the "check" column in hbase has to be the old check value you read. If any other process wrote to this row then it would have updated the check value with a new UUID and so this checkAndPut will fail thereby detecting the conflict. Now you can repull the row and handle any conflict resolution without blindly overwriting the changes.

I also have an RX1 and it really is a fantastic camera.

I bet the OP was talking about the rumored full frame interchangeable lens camera (possibly a full frame NEX) that Sony is supposed to be announcing soon.

The company I work for had a similar experience with Cassandra. We were running it back in the 0.6 days. Once any of our nodes got around 500GB on them the performance would tank.

It seems that they later fixed the performance in 1.2 (http://www.datastax.com/dev/blog/performance-improvements-in...) but by that time we moved our data over to HBase and haven't had any regrets.

In practice it doesn't seem to matter. For example btc-e.com who accepts both bitcoin and litecoin for trading makes you wait 3 confirmations for bitcoin and 6 confirmations for litecoin. So you are correct that 1 litecoin transaction is not as reliable as 1 bitcoin transaction but they are not making you wait 12 litecoin transactions.

Given that btc-e has a lot to lose on double spend attacks I think it's a good measure of how these two currencies are playing out in the market.

There is the concept of green addresses (https://en.bitcoin.it/wiki/Green_address) to solve this. Basically if customers use a wallet that the merchant trusts not to commit a double spend then they can safely accept a zero confirmation transaction. MtGox and Bridgewalker (https://www.bridgewalkerapp.com) support this so if you trust them and your customer uses them then you can accept the transaction immediately.

Of course for something like a cup of coffee or even a purchase for $80 worth of clothes I think most companies would be fine with accepting a zero confirmation transaction and taking the risk as it will be far less of a cost then shoplifting and will be less than the 2% they currently pay on every credit card transaction. If you are buying a $1000 laptop then maybe they make you hang out while they explain the features and wait for a single confirmation.

Is anyone else surprised that the creator of Litecoin needed to take a job? Given that the market cap of Litecoin is 53 million I would have expected the creator to have mined a good amount of that in the early days.

Of course he may have just wanted to take the job and not needed it but I would have assumed he would have worked on something for the Litecoin ecosystem.

Unfortunately this idea was patented 13 years ago:

http://www.google.com/patents/US6124583

Makes you realize why there are no commercial implementations of this and why patents are terrible.

Good point, changed the title to hit and run accident.

He said useful not ubiquitous.

As someone that uses hbase in production, I'd be interested in hearing the setting you are talking about.

Back when I bought my jalapenos they were only $150 and I chose not to do the upgraded pricing to 7GH/s for $100. The speedup I was referring to was simply a bump in the base model from the original 4.5GH/s specs to what the units I received actually ran at.

Given that the units have almost paid for themselves in one week it's hard to be upset about any lost income. On the other hand I still have only received part of my order and am waiting on multiple 60GH/s units that are just now starting to ship to people who ordered in June 2012. Depending on how long it takes them to get to my order I may have some regrets I didn't just order all jalapenos instead.

As someone who ordered back in August 2012 and received his 2 jalapenos a week ago I can say I'm still very happy with my order. I wouldn't advise someone to buy into it now as this article doesn't do enough to explain the geometric rise in difficulty will most likely make it difficult to recoup costs on the hardware by the time an order made today ships. BFL estimates they will clear the backlog of orders by September of this year, but their estimates are notoriously bad so take that with a grain of salt.

These units don't perform worse than what I originally ordered, in fact they hash at a rate that is 24% higher than what I ordered (5.6GH/s vs 4.5GHs). While it is true to say they use more power than promised as they were originally going to use 5 watts and instead use 30 watts saying they perform worse AND use more power is misleading.