|
I heard this from a trusted person on IRC: Apparently someone posed as a potential buyer for the 20GB data. Instead of getting anything in response from the supposed blackmail thief, they began receiving phishing e-mail claiming to be from Bitcoin companies with trojaned payloads in attachments.
|
|
|
|
|
Can you please see if the same bug exists in Bitcoin 0.9 rc2?
|
|
|
|
|
Bitcoin OMG10 has all the bug fixes that were in Bitcoin-Qt 0.8.6. It is fully compatible with the data and wallet of the standard Bitcoin-Qt. That being said you should always make backups of wallet.dat on a regular basis.
|
|
|
|
I am Warren Togami. https://bitcointalk.org/index.php?action=profile;u=81508;sa=showPosts;start=0I am a developer of both Bitcoin and Litecoin, management consultant and engineer. My previous career was as a Linux Software Engineer followed by MBA and a bit of law school. You can see from my post history that I have been involved in major bug fixes in Bitcoin during 0.8.x and 0.9 and have contributed to related projects like p2pool in both code and fund raising. I also consult for <various Bitcoin companies> on business and engineering issues. I met theymos late 2013 the day of the major security breach. I initially served as an emergency security consultant, mainly in locking down the replacement server to get the forum back up and running as quickly as possible. The site remains a bit crippled today (i.e. no uploading of avatars) because of paranoid server security configurations and shared agreement that the current SMF is not worthwhile to improve. Upgrading to the SMF-2.x would be too much work to port and validate weird custom features (starting with Satoshi years ago and other administrators through the years) while the user experience wouldn't be much of an improvement. Theymos studied the other forum software alternatives and was dissatisfied with all of them. James Wang is one of the most experienced and versatile engineers that I know. He has done iOS and Android apps, desktop applications, and highly scalable web and database apps. Other engineers at his company are similarly talented. He long had a desire to implement a better communications framework, and he was very excited when he learned that someone wanted a new forum where the end product would be open source as all of his past work was forced to be hidden within proprietary software companies. His vision for the new forum is to not only do forum-like communications better, but to also reuse the same framework to do what Freenode does in a better way. This could be a compelling new product that is useful for projects, open and closed teams and communities far beyond Bitcoin. Theymos was late in getting help to achieve the stated goals for the forum, and it is too easy for people to criticize due to that tardiness. Now I can say with confidence that there are professionals working on not only engineering but also protecting the forum as a defensible legal entity. Shortly pieces of working code will be revealed to the community and be placed in production in auxiliary functions of the current forum. A bit after initial portions go live the engineering firm will be directly engaging with the community for feedback on the new forum design. I believe the community will be surprised and pleased with what comes next. The purpose of all this work is more ambitious and goes beyond a mere medium of communication. |
|
|
|
DPR Seized Coins owner, SEND US THE COINS!!!Andrian Lep < andrian_blockchain@yahoo.com> Sat, Feb 22, 2014 at 4:33 AM Reply-To: Andrian Lep < andrian_blockchain@yahoo.com> To: " wtogami@example.com" < wtogami@example.com> Hello, Mr Togami. We've EVIDENCE that you are the owner of this BTC address (DPR Seized Coins ) now. It's really very lucky to have 144,341.5246317 BTC. We WILL contact the FBI and post on the bitcointalk.org at February 24.
Please send us more than 8,000 btc and at least 16,000ltc.BTC: 1MRTW5uQf9sh8TAhQqFEEYSDRL3ir6zcXo
1PHCPQi3mhMdaYADAqfdUp2agCHhgHUESV
1BVVs5i35mrerWNV8EdMb3yEpM2urntU1V
1PvXWDwV3CfMnrEUDG73MAvzBunxrkt7WT
LTC: LV9xKPUFkvoinG5WNdpSuVkSDXP5VTh37S
Have a good night! I admit it. This unaltered* screenshot was made by me. I tried to pay the blackmail but the client fails when I click on send. What do I do? I have less than one day to pay or I am exposed. Help! * The screenshot is real ... of Bitcoin-Qt patched to demonstrate watch-only addresses support which is not yet in the standard Bitcoin-Qt client.. |
|
|
|
Any idea how to contact that person? They are very late in delivery. |
|
|
|
|
People. Calm down. Litecoin and Bitcoin OMG regularly backports bug fixes and features for the purpose of testing. Various bug fixes in 0.8.3 through 0.8.6 and master were directly or indirectly influenced by our work. Much of it was not directly written by us but was the result of a collaborative effort. Most of the credit goes to the Bitcoin devs.
|
|
|
|
Conditions
The bounty may be awarded under the following conditions.
Document how anyone can consistently reproduce the data corruption.
Explain why it happens.
Write a code fix that is acceptable to the Bitcoin core developers and merged into Bitcoin git master.
The Bitcoin developers have ultimate deciding power of how to apportion the bounty award(s) based upon the merit of the contributions This may encourage collaboration that may lead to a fix rather than hoarding of information. Non-developers may be able to figure out #1.
These terms may be changed at any time for any or no reason. These were the original bounty conditions. After consulting with core Bitcoin devs, it turns out "into Bitcoin git master" was a bad idea. What was shipped in 0.8.6 was correct and needed for Bitcoin users as quick as possible. There is a desire to be far more deliberate in testing the code that goes into git master for what will eventually become Bitcoin 0.9. For this reason we are exercising the "These terms may be changed at any time for any or no reason." clause. The final term will be changed, s/merged into Bitcoin git master/merged into Bitcoin/. The apportionment of the bounty to split to different contributors involved in fixing the issue will be the decision of Bitcoin devs including myself, Gavin, laanwj and others. Depending on the country where the various contributors are located tax forms may be required to make payments. If they refuse to do required tax forms then they may opt for their portion to be instead directed at a Bitcoin-accepting charitable organization like the FSF or EFF. |
|
|
|
I feel like OMG is not thought of as an addition or bleading edge thing, but tries to get people away from the official reference client?
Dia
Actually the litecoin core development team actually listens to the users, instead of themselves. Instead of trying to implement other protocols that are broken in a Beta client  Please be respectful to the Bitcoin devs. We are all in this together. |
|
|
|
I feel like OMG is not thought of as an addition or bleading edge thing, but tries to get people away from the official reference client?
Dia
Please do not feel alarmed. This is merely a decentralized variation of the reference client that is intended to help improve the 0.8.x and master branches. OMG testing has directly contributed to the selection of patches that went into 0.8.6. OMG was also very helpful in testing various candidate patches for the MacOS leveldb corruption issue as shipped in 0.8.6. wumpus also points out that we caught the deleteLater issue with Coin Control thanks to OMG. Bitcoin OMG was published because a ton of work was put into testing the backport patches shipped in Litecoin 0.8.x and it was not much more effort to repackage those patches into a Bitcoin client. Users want features like Coin Control and through many months of testing and some of feedback to cozz it has improved to a point where I personally feel comfortable using it in these 0.8 backports. As far as client security goes, OMG has its own gitian.sigs where random members of the public are invited to help verify with their own GPG-signed gitian sigs. |
|
|
|
I like Cozz's version. Good to have alternatives, but I will also give bitcoin OMG a try.
Bitcoin OMG *is* Cozz's version. |
|
|
|
Just read the Brainstorming document. Some great plans.
Fee on each share is a smart idea, I didn't realise the payout per share is value/difficulty weighted as things are now. I now see the wisdom in larger miners upping their share diff threshold.
Trustless Accumulator (both variants) would be vital, infrequent dusty payouts to those with relatively small hashing power is a real barrier.
Multi-threaded share propagation is potentially good, and could work very well with the per-peer Statistical Tracking (as mentioned). Even though it does little in practical over-time terms to alter the payouts, it would increase user perception of "less wasted work" in the system as a whole. Although I'm not sure whether this won't just have the effect of increasing the effective granularity of stales, as there will still be the same number of shares in the chain.
Per-peer Statistical Tracking in it's own right is great for encouraging the kind of miner who uses professional hosting, and so contributes to a perception of a professionalism. Gives those miners a perceived high worth status, even if it's only in terms of the stratification of connections. And of course orphans could be less prevalent.
Glad to see someone clearly understands the issues involved. =) |
|
|
|
|
Status Update: OMG10 already has all bug fixes that were included in 0.8.6. OMG will be rebased on "0.8.6" only after we have substantive fixes or new features to make a new release worthwhile.
|
|
|
|
|
The Litecoin Dev team did contract with Peter Todd to do all the work necessary to implement pruning and to have it submitted to Bitcoin github for code review. This includes pruning and various supporting code that has been proposed by others. For example, "archive nodes" would store a full copy of the blockchain. "Fully verifying nodes" no longer need the entire blockchain, but for the network to be healthy and capable of syncing new clients they need to keep subsets of the blockchain. There also needs to be a way to tell peers what ranges of blocks you have available.
While it would be bad to allow peers to have less than a full blockchain, this is a balancing act. With the rapid growth of the blockchain the quantity of listening nodes on the network has been continually shrinking. Perhaps fully verifying nodes that store subsets of the blockchain would allow more listening nodes to exist comfortably on the global network.
|
|
|
|
|
OMG10 already has all bug fixes in 0.8.6rc1. The minor fee related rule changes will be included in 0.8.6-OMG after 0.8.6 is released.
|
|
|
|
|
Show Posts
