|
The arguments of government sometimes are more crackpot than this.
There is no justice or law as basic property of society. The violent means to force your rules and laws upon other people, no matter how crackpot your rules are is all that matters. If some militants had hundreds of thousands armed soldiers, with MBT tanks, jet fighters and nuclear armed submarines, they also could write their own laws and legal system and enforce it upon everyone.
Take example from commies in October revolution. They were illegal, crackpot, but using Mauser pistole and Maxim machine gun they forced everyone to accept their way of organizing society and laws.
|
|
|
|
No matter how difficult is the password, the security breach of computer by trojan keylogger will capture everything that is written to computer. What I did was to encrypt the wallet with an impossible to crack randomly generated password (example: r'WRVJ?G2/=Z/,f\ijAGZ#q$&0GvNB), then put it in a password protected RAR archive using another impossible to crack password and then put it on an external HDD that is connected to my PC (Online). That sounds secure enough, right? The additional password to WinRAR archive is only useful to keep the public addresses secret in case of theft. Receiving addresses are not encrypted by wallet encryption. This might backfire if WinRAR archive format is changed without backward compatibility and You cannot decrypt archive anymore. External HDD's are generally more unreliable than internal drives and having the wallet on external drive that is conected to computer and internet gives no additional security. I believe the only way of someone stealing my coins is to infect my PC with a very smart trojan that can record me entering the password (which I don't plan on doing as I don't intend on spending the coins anytime soon) and stealing the wallet.dat file Even most basic trojans come with keylogger, file browser, remote control and remote file upload and execution functionality. This is how most theft happen. I will create offline wallet on another computer that have no network connection with Armory, print deterministic wallet backup and store it somewhere safe and hidden, create watching only wallet for use on internet connected computer and send most coins to offline wallet on the offline computer. And encrypt harddrive of that offline computer, with decryption password and header key backups written down somewhere safe. Not so hard at all if You know how to use computers. |
|
|
|
Yes, when you have a post count like yours. Smiley The post count is not indication about the intentions of person operating it or the persons ability to pay back. There was sticky warning about it on forum. Probably my longevity and time spent here is the most important that matters. Too bad most of the threads in this forum are from newbies asking for free money I'm surprised if they ever get some money and even more surprised if they return it back. |
|
|
|
|
Money received. This forum really have helpful people here!
|
|
|
|
|
I'm going to have 200$ PayPal to my PayPal account from MoonShadow. Will pay him back 220$ after 65 days from now (at May 17, 2013). This is for public records.
|
|
|
|
Where's the No option? Can you add that?
There isn't No option in original poll here https://bitcointalk.org/index.php?topic=152406.0The No should look more like "The ASIC is all scam and advance fee fraud and no ASIC devices are in production stage past daydreaming" |
|
|
|
|
According to optimistic libertarian predictions it is possible that Bitcoin will end zionist world domination and world population will be set free from jewish banksters. Are jews are adopting Bitcoin just in case it becomes the new gold of computer era or they are unknowingly helping to dig the graves of old system?
|
|
|
|
|
25 years old cipher have flaws no surprise for me.
|
|
|
|
Bitcoin does have much much more at stake than some filesharing network, which is why there should be spec to follow.
For something that my life depend on, I want certainty that it's well understood and tested.
An how would specification prevent what happened yesterday? Document the unknown bugs? Only thorough examination of source code could reveal hidden flaws. I completely agree on the importance of Bitcoin. |
|
|
|
|
If the block size remains unchanged, in far future there will be high transaction costs so no Satoshi Dick style transaction flood will take place. 1M in every 10 minutes are not that much. JewTube videos take at least 10 times as much traffic as Bitcoin under worst conditions.
|
|
|
|
|
The source code is the best specification. No documentation written in human language be complete and unanimous enough to be sure that everything is covered. You cannot compile Hemingway writings into executable code.
Bitcoin with connectivity difficulties would have problems with different Bitcoin clients, but will happily create disconnected network and all sorts of other nasty things.
Bitcoin have much more at stake than Gnutella warez download.
|
|
|
|
MysteryMiner
remote access trojan in every bitcoin install. |
|
|
|
|
False. Different Gnutella implementations had interconnectivity issues in past. Bitcoin did it only once and even then a minor one.
|
|
|
|
|
I expect Satoshi to return to appoint new project leader. Satoshi once made a successful choice, probably no one could do it better.
If Satoshi is alive, is not group of people or Luke-Jr, still have his PGP key and Satoshi is not Gavin himself.
|
|
|
|
As a professional software developer this may be an opportune time to point out that the bitcoin code is an amateur production. Yes it is amateur production. Bitcoin have no closed source, it does not ask for money and have no restrictive EULAs. It is not written by greedy turd. Nevertheless, make no mistakes, the current incarnation of Bitcoin has a lot of ill-conceived design points and implementation weaknesses (as we have seen from the events of the last 24 hours).
Aside from the blunder that just resulted in a blockchain fork, there is a much larger, related issue looming on the horizon, which is the inability of the design to process large numbers of transactions. I see the results of proprietary closed source development every month's second Tuesday. Some vulnerabilities are not publicly known for years and remains unfixed for years afterwards. Most professionals working on closed source software make really bad design choices resulting in complete lack of security when bulletproof security is needed. Compared to small glitches in Bitcoin like recent one. It is ludicrous we have people whining about "Satoshi Dice" creating numerous transactions. I could sit down and write a software component that could easily generate billions of transactions without breaking a sweat once it is deployed to a few thousand boxes, if I so chose, and yet you are concerned about Satoishi Dice generating a few million transactions. The problem of high-volume transaction handling needs to be answered at a new level which is, unfortunately, way above the paygrade of the current development team. You don't understand how Bitcoin transaction fees works. You can create only so much transactions than you have bitcoins to spend. Invalid transactions will not be relayed further. Payment to development team have nothing to do with quality and possibilities of software. Best softwares out there are made by volunteers working on FOSS projects. And I know numerous occasions when developers were paid millions in cash and buggy .net code were deployed that did not even satisfy all requirements. |
|
|
|
|
Satoshi Dice did not cause the forking, but it helped to discover the flaw with the additional transaction volume it generates. So Satoshi Dice somewhat caused forking. Paradox.
|
|
|
|
So Atlas feared the unknown? This fact surely deserved to be dug out of the archives to celebrate his wisdom.
This thread and Atlas still delivers the Lulz! No, he did not fear the unknown, he wanted to be sure that Bitcoin protocol will not change by accident with new database implementation. In original thread Atlas at some unknown point got high on ganja so the proposed solution was not the best. I don't see a hard fork. Majority of 0.7.x and earlier relay users being permanently unable to accept new 0.8 blocks built upon unacceptable one is a hard fork. I see would be orphans which is quite different in both concept and consequences... Orphans happen from time to time as a normal operation. This fork was caused by one database implementation rejecting blocks that was valid in another implementation. |
|
|
|
0.7 refuses good data, 0.8 doesn't put bad data in the blockchain... What is good and bad data is determined by majority of nodes and miners. Basically Atlas was right on spot about new database engine breaking things, even if it broke them by fixing what already was broken... If it works don't fix it! A majority of the hashing power was on 0.8 before they decided to downgrade. By your definition at the moment of the fork the 0.8 version was the good version. Even if it was from standpoint of correctness and majority of miners, the current network was broken... by 0.8.0 fixing previously unknown flaw in database engine. These unforeseen consequences is what Atlas feared, so technically Atlas was right. |
|
|
|
0.7 refuses good data, 0.8 doesn't put bad data in the blockchain... What is good and bad data is determined by majority of nodes and miners. Basically Atlas was right on spot about new database engine breaking things, even if it broke them by fixing what already was broken... If it works don't fix it! And now few of the finest quotes ever! Atlas....who would have thunk! A Broken Clock Is Right Twice A Day
0.8.0: Am I wrong?
0.7.x version: You're not wrong 0.8.0. You're just an asshole.
|
|
|
|
What are people going to say when BFL delivers? I'm happy to be wrong this time. Already made my coins on betsofbitco.in for BFL not delivering till end of 2012. |
|
|
|
|
Show Posts
