Latest posts of: kerogre256

Show Posts
Pages: [1] 2 3 4 5 6 7 8 9 »

Bitcoin / Armory / Re: Please Help Test Armory 0.91-beta!

on: March 22, 2014, 08:25:10 PM

Ok its working now look like problem was with old 32 bit bitcoin-qt client 8.5 after removing it from C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe armory started to scan DB.

Bitcoin / Armory / Re: Please Help Test Armory 0.91-beta!

on: March 22, 2014, 08:14:26 PM

Any help ?

Bitcoin / Armory / Re: Please Help Test Armory 0.91-beta!

on: March 22, 2014, 08:12:50 PM

2014-03-22 19:56 (INFO) -- ArmoryQt.py:585 - Usermode: Expert 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1343 - Changing usermode: 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1344 - From: Expert 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1352 - To: Expert 2014-03-22 19:56 (INFO) -- SDM.pyc:772 - Creating proxy in SDM: host=127.0.0.1, port=8332 2014-03-22 19:56 (INFO) -- ArmoryQt.py:5444 - Dashboard switched to auto-InitSync 2014-03-22 19:56 (INFO) -- ArmoryQt.py:4878 - Switching Armory state text to Mgmt:Auto, State:InitializingLongTime 2014-03-22 19:56 (INFO) -- ArmoryQt.py:4878 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo 2014-03-22 19:56 (INFO) -- ArmoryQt.py:4820 - Switching Armory functional mode to "Offline" 2014-03-22 19:56 (INFO) -- ArmoryQt.py:6293 - Another Armory instance just tried to open. 2014-03-22 19:56 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible 2014-03-22 19:56 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.90.99.4&id=98dbb36b 2014-03-22 19:56 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.90.99.4 2014-03-22 19:56 (WARNING) -- SDM.pyc:650 - bitcoind exited, bitcoind STDOUT: 2014-03-22 19:56 (WARNING) -- SDM.pyc:652 - 2014-03-22 19:56 (WARNING) -- SDM.pyc:653 - bitcoind exited, bitcoind STDERR: 2014-03-22 19:56 (WARNING) -- SDM.pyc:655 - 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (ERROR) -- ArmoryQt.py:5400 - BitcoindNotAvailable: should not happen... 2014-03-22 19:56 (INFO) -- ArmoryQt.py:4820 - Switching Armory functional mode to "Offline"

Bitcoin / Armory / Re: Please Help Test Armory 0.91-beta!

on: March 22, 2014, 08:12:01 PM

2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:919 - C++ block utilities loaded successfully 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1009 - 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1010 - 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1011 - 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1012 - ********************************************************** 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1014 - ******************************************************** 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1015 - Loading Armory Engine: 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1016 - Armory Version : 0.90.99.4 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1017 - PyBtcWallet Version : 1.35 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1018 - Detected Operating system: Windows 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1019 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1020 - User home-directory : C:\Users\x\AppData\Roaming 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1021 - Satoshi BTC directory : C:\Users\x\AppData\Roaming\Bitcoin\ 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1022 - Armory home dir : C:\Users\x\AppData\Roaming\Armory\ 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1023 - Detected System Specs : 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1024 - Total Available RAM : 7.94 GB 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1025 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1026 - Number of CPU cores : 4 cores 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1027 - System is 64-bit : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1028 - Preferred Encoding : cp1252 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1029 - 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1030 - Network Name: Main Network 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1031 - Satoshi Port: 8333 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1032 - Named options/arguments to armoryengine.py: 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - maxOpenFiles : 0 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - nettimeout : 2 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rescan : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - leveldbDir : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - ignoreAllZC : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - port : None 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - interport : 8223 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - coverageOutputDir: None 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rebuild : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - datadir : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - offline : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - noWalletCheck : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiPort : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - netlog : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - keypool : 100 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - coverageInclude : None 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - forceOnline : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - skipAnnounceCheck: False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - redownload : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - disableTorrent : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - testAnnounceCode: False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - mtdebug : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - skipVerCheck : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - settingsPath : C:\Users\x\AppData\Roaming\Armory\ArmorySettings.txt 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - verbosity : None 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - doDebug : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - testnet : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rpcport : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiHome : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiRpcport : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - logDisable : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - logFile : C:\Users\x\AppData\Roaming\Armory\ArmoryQt.exe.log.txt 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1035 - Other arguments: 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1038 - ********************************************************** 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1386 - C++ block utilities loaded successfully 2014-03-22 19:56 (INFO) -- BDM.pyc:1420 - Using the asynchronous/multi-threaded BlockDataManager. 2014-03-22 19:56 (INFO) -- BDM.pyc:1421 - Blockchain operations will happen in the background. 2014-03-22 19:56 (INFO) -- BDM.pyc:1422 - Devs: check TheBDM.getBDMState() before asking for data. 2014-03-22 19:56 (INFO) -- BDM.pyc:1423 - Registering addresses during rescans will queue them for 2014-03-22 19:56 (INFO) -- BDM.pyc:1424 - inclusion after the current scan is completed. 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:3006 - Using settings file: C:\Users\x\AppData\Roaming\Armory\ArmorySettings.txt 2014-03-22 19:56 (INFO) -- announcefetch.pyc:83 - Reading files in fetcher directory: 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - announce : 88f1e5b41f0a828a1ae440c0490e4136a848b4fc79fa4d41809d309eefc87712 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - bootstrap : 0c68367a6126ed922c90fd06f6b3dc2217248b595adf5c6a1832cdeb4a3ae0b7 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - changelog : d4072bb5c0037ad4bd551dec85601ed8ef1eae04780c08e69e28d62932900441 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - downloads : cec3a5c4381a82860162d9d7d913bda75d88f7b531d6d528620a5464c0020b3d 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - notify : 20aa6e8a9d1f947c08f1b21a4c24d53e29b68c2d37b936a082d88192b2513fea 2014-03-22 19:56 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.90.99.4&id=98dbb36b 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2211 - loadWalletsAndSettings 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2269 - Loading wallets... 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2318 - Number of wallets read in: 2 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2323 - Wallet (2vrvaaUvT): "Piotr " (No Encryption) 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2323 - Wallet (tNKjfKT5): "Offline (Watch) " (No Encryption) 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1758 - Setting up networking... 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1810 - Internet connection is Available: True 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1811 - Bitcoin-Qt/bitcoind is Available: 0 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1812 - The first blk*.dat was Available: True 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1813 - Online mode currently possible: 0 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1932 - startBitcoindIfNecessary 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1972 - setSatoshiPaths 2014-03-22 19:56 (INFO) -- SDM.pyc:264 - Total size of files in C:\Users\x\AppData\Roaming\Bitcoin\blocks is approx 14.8 GB 2014-03-22 19:56 (INFO) -- SDM.pyc:299 - Found bitcoind in the following places: 2014-03-22 19:56 (INFO) -- SDM.pyc:301 - C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe 2014-03-22 19:56 (INFO) -- SDM.pyc:301 - C:\Program Files\Bitcoin\daemon\bitcoind.exe 2014-03-22 19:56 (INFO) -- SDM.pyc:303 - Using: C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe 2014-03-22 19:56 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file 2014-03-22 19:56 (INFO) -- SDM.pyc:480 - Setting permissions on bitcoin.conf 2014-03-22 19:56 (INFO) -- SDM.pyc:483 - Setting permissions on bitcoin.conf 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['icacls', 'C:\\Users\\x\\AppData\\Roaming\\Bitcoin\\bitcoin.conf', '/inheritance:r', '/grant:r', 'x:F'] 2014-03-22 19:56 (INFO) -- SDM.pyc:486 - icacls returned: 2014-03-22 19:56 (INFO) -- SDM.pyc:547 - Called startBitcoind 2014-03-22 19:56 (INFO) -- SDM.pyc:264 - Total size of files in C:\Users\x\AppData\Roaming\Bitcoin\blocks is approx 14.8 GB 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['C:\\Program Files (x86)\\Bitcoin\\daemon\\bitcoind.exe', '-datadir=C:\\Users\\x\\AppData\\Roaming\\Bitcoin\\'] 2014-03-22 19:56 (INFO) -- SDM.pyc:607 - PID of bitcoind: 3424 2014-03-22 19:56 (INFO) -- SDM.pyc:608 - PID of armory: 3760 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['.\\guardian.exe', '3760', '3424'] 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1076 - setupUriRegistration 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1144 - Armory already registered for current user. Done! Here is log can go online.....

Bitcoin / Armory / Re: Please Help Test Armory 0.91-beta!

on: March 22, 2014, 07:42:14 PM

I have Now wallet error found and armory fail to initiate bitcoin engine.

Bitcoin / Armory / Re: Please Help Test Armory 0.91-beta!

on: March 22, 2014, 07:39:08 PM

I just installed this version and Armory don't want go in to online mode, show armory offline mode and noting happend.

Bitcoin / Bitcoin Discussion / scan.co.uk accept bitcoin !!!!

on: February 12, 2014, 11:04:48 PM

scan.co.uk one of the biggest uk electronics selling web page quiet start accepting bitcoin ...

Bitcoin / Development & Technical Discussion / Re: Maximum number of Bitcoins (21million)

on: February 10, 2014, 04:52:14 PM

Quote from: Bitcoi2n2n on February 10, 2014, 04:50:08 PM Quote from: Gator-hex on February 10, 2014, 04:48:21 PM Quote from: Bitcoi2n2n on February 10, 2014, 04:43:56 PM The amount of the Bitcoins that are being generated is very linear. So it should be possible to calculate when we will reach the maximum 21 million BTC to be in circulation. Did anyone calculate this yet? When will the last Bitcoin be mined? It's not linear, it's curved. It's 2140 when the last bitcoin can be earned! And each coin has 8 decimal places so there are 2.1 Quadrillion Satoshi currency units! So this is not linear for you? https://blockchain.info/charts/total-bitcoins lol man just read legend under chart

Bitcoin / Press / Re: 2014-01-23 Bloomberg: Lew calls bitcoin place to hide shares Dimon's Incredulity

on: January 24, 2014, 12:08:35 PM

Quote from: Peter R on January 24, 2014, 04:33:56 AM Quote from: FeedbackLoop on January 23, 2014, 03:08:03 PM Also, lol at the terrorism FUD. So discrediting... A good friend of mine has a theory of how we use "negative entropy" sources to help us more easily get things done. An example of a "negative entropy" source are words that create a strong emotional response, like "terrorism." His theory is that we will use these words (negentropy) to dump entropy into until we've extracted all of the useful work from that source. At this point, these words actually begin to have the opposite effect on the public as they once did. I think we are nearing that point already. Whenever I hear "terrorist," "drugs," "money laundering," or "child porn" my instant emotional response is against the person who is trying to use these words to advance their agenda. This is interesting because I react exactly the same when person use "terrorist," "drugs," "money laundering," or "child porn" in debate or as argument for something, person lose for me all credibility straight away.

Bitcoin / Bitcoin Discussion / Re: Trading Bitcoin without risking a fortune

on: January 21, 2014, 11:28:37 AM

This is fastest way to lose the money, you will have no money and no bitcoin. Don't touch spread betting you will always be on lose position, gambling is more profitable then spread betting.

Bitcoin / Armory / Re: Armory - Discussion Thread

on: December 04, 2013, 03:19:11 PM

Quote from: goatpig on December 04, 2013, 02:20:32 PM It's possible you ran into a n² computation issue rather than actual corruption. If it happens next time, give it 30 minutes and see if it completes. As for the scanning, how many wallets do you use at the same time and do you use imported private keys? These could be the cause of the multiple transaction scans. I have only 2 wallets, keys were not imported.

Bitcoin / Armory / Re: Armory - Discussion Thread

on: December 04, 2013, 02:07:09 PM

Quote from: goatpig on December 04, 2013, 01:50:30 PM Quote from: kerogre256 on December 04, 2013, 01:10:40 PM Quote from: etotheipi on November 30, 2013, 11:12:20 PM Kerogore, Is Armory crashing every time you type in your password? We have a known wallet corruption problem, but it's easy to fix if you have a backup. If not we, can also perform a recovery of the wallet file, which is usually successful. See the following page for more info ("Armory crashes every time I type in my password"): https://bitcoinarmory.com/download/troubleshooting/ I installed 90.-beta version and encrypted wallet, after that was not able send any bitcoin armory client crash, I unencrypted wallet and try it again, 90.-beta crash again, i re-installed version 89.14-beta was able send bitcoin, I encrypted wallet again and after thad armory crash (89.14-beta) when I try send bitcoin, I unencrypted wallet and now was able send it again, I dont know what to do now. Can wallet by corrupted to the point then i will not able recovery private key or print copy of offline wallet ? Was Armory crashing (as in closes on its own) or hanging (stopped responding but didn't close itself)? If you can access your wallet I strongly suggest you create a paper backup for now. You can then write down your experience (with as much details as possible) to contact@bitcoinarmory.com It "stopped responding but didn't close itself" windows notification(Application is not responding Close/Wait I did close) I notice also transaction scanig behave strange, sometime it start scan transaction show 1% scaned jump to 99% back to 1% and again 99% and then 100% and its take only 1-2 minutes oposit to assume "normal" scanig abaut 10min.

Bitcoin / Armory / Re: Armory - Discussion Thread

on: December 04, 2013, 01:10:40 PM

Quote from: etotheipi on November 30, 2013, 11:12:20 PM Kerogore, Is Armory crashing every time you type in your password? We have a known wallet corruption problem, but it's easy to fix if you have a backup. If not we, can also perform a recovery of the wallet file, which is usually successful. See the following page for more info ("Armory crashes every time I type in my password"): https://bitcoinarmory.com/download/troubleshooting/ I installed 90.-beta version and encrypted wallet, after that was not able send any bitcoin armory client crash, I unencrypted wallet and try it again, 90.-beta crash again, i re-installed version 89.14-beta was able send bitcoin, I encrypted wallet again and after thad armory crash (89.14-beta) when I try send bitcoin, I unencrypted wallet and now was able send it again, I dont know what to do now. Can wallet by corrupted to the point then i will not able recovery private key or print copy of offline wallet ?

Bitcoin / Armory / Re: Armory - Discussion Thread

on: November 30, 2013, 10:31:56 PM

Armory is very unstable, (Windows 7 64 bit 4GB) anything except 89.99.14-beta crashing every time I want to send bitcoin, and what is purpose of transaction scanning and why it take so long??? I like offline wallet but how much unstable it is scary.

Bitcoin / Armory / Armory crashing

on: November 30, 2013, 10:00:07 PM

Armory crashing all the time cant send bitcoin whit version .90 beta

Bitcoin / Bitcoin Discussion / Re: Cracking the Code

on: November 28, 2013, 01:44:08 PM

Quote from: AnonyMint on November 28, 2013, 11:44:50 AM Quote from: kerogre256 on November 28, 2013, 11:32:05 AM Quote from: AnonyMint on November 28, 2013, 11:13:20 AM Quote from: kerogre256 on November 28, 2013, 11:09:28 AM As soon you start insult people because they don't agree with you, you lose argument Logic doesn't have an ego. I lose the attention of the Bitards who would prefer to remain in blissful delusion. Perfect. I see the Bitcoin Wiki is incorrect: https://en.bitcoin.it/wiki/Attacks#Attacker_has_a_lot_of_computing_power Quote The attacker can't: * Change the number of coins generated per block * Create coins out of thin air Can you try explain to me how they will able produce more coins? Refer also to my immediately prior post. Only miners can add coins with the coinbase transaction that is placed in each new mined block of the block chain. If an attacker controls > 50% of the hashrate, the attacker will always have the longest block chain. So the attacker decides what is acceptable in the blocks. The honest miners will reject any block chain which has more new coins in the coinbase transaction than was specified in Satoshi's whitepaper. However, if the attacker has the longest chain, then the honest miners can ignore all they want, they will still have the shorter chain. The entire double-spend security rests on the fact that only the longest block chain is valid. So the only thing the honest miners and honest non-mining nodes could do would be to fork the block chain. But the attacker can then attack the forked chain. And so on and so on. There is no escape. Checkmate. You accept the new coins. P.S. If the honest miners try to blacklist the attacker by IP, he can send to the network from innumerable IP addresses employing a $100 botnet rental. Once you go down that road, the entire network has to be blacklisted, so lights out. Checkmate. You accept the new coins. I get it now you won the race you have 50% bitcoin network power you produce block and inside block is messag 'I'm with stupid' now you have block chain. Bitcoin transaction block,Bitcoin transaction block,Bitcoin transaction block,'I'm with stuppid',Bitcoin transaction block,Frank was here,Bitcoin transaction block,Bitcoin transaction block. Longest chain won.

Bitcoin / Bitcoin Discussion / Re: Cracking the Code

on: November 28, 2013, 12:50:41 PM

Quote from: seriouscoin on November 28, 2013, 11:54:08 AM Quote from: AnonyMint on November 28, 2013, 11:44:50 AM Quote from: kerogre256 on November 28, 2013, 11:32:05 AM Quote from: AnonyMint on November 28, 2013, 11:13:20 AM Quote from: kerogre256 on November 28, 2013, 11:09:28 AM As soon you start insult people because they don't agree with you, you lose argument Logic doesn't have an ego. I lose the attention of the Bitards who would prefer to remain in blissful delusion. Perfect. I see the Bitcoin Wiki is incorrect: https://en.bitcoin.it/wiki/Attacks#Attacker_has_a_lot_of_computing_power Quote The attacker can't: * Change the number of coins generated per block * Create coins out of thin air Can you try explain to me how they will able produce more coins? Refer also to my immediately prior post. Only miners can add coins with the coinbase transaction that is placed in each new mined block of the block chain. If an attacker controls > 50% of the hashrate, the attacker will always have the longest block chain. So the attacker decides what is acceptable in the blocks. The honest miners will reject any block chain which has more new coins in the coinbase transaction than was specified in Satoshi's whitepaper. However, if the attacker has the longest chain, then the honest miners can ignore all they want, they will still have the shorter chain. The entire double-spend security rests on the fact that only the longest block chain is valid. So the only thing the honest miners could do would be to fork the block chain. But the attacker can then attack the forked chain. And so on and so on. There is no escape. Checkmate. You accept the new coins. P.S. If you try to blacklist the attacker by IP, he can send to the network from innumerable IP addresses employing a $100 botnet rental. Once you go down that road, the entire network has to be blacklisted, so lights out. Checkmate. You accept the new coins. Hey dumb ass a node doesnt have to be a miner to be counted as a node. Having >50% hashing power doesnt mean >50% of network node. Welcome to my ignore list retard, Ok you have control > 50% you add 1000 bitcoin to new address and release the block you won race now how network will react to new chain whit additional 1000 bitcoin in only your chain ?

Bitcoin / Bitcoin Discussion / Re: Cracking the Code

on: November 28, 2013, 11:32:05 AM

Quote from: AnonyMint on November 28, 2013, 11:13:20 AM Quote from: kerogre256 on November 28, 2013, 11:09:28 AM As soon you start insult people because they don't agree with you, you lose argument Logic doesn't have an ego. I lose the attention of the Bitards who would prefer to remain in blissful delusion. Perfect. I see the Bitcoin Wiki is incorrect: https://en.bitcoin.it/wiki/Attacks#Attacker_has_a_lot_of_computing_power Quote The attacker can't: * Change the number of coins generated per block * Create coins out of thin air Can you try explain to me how they will able produce more coins?

Bitcoin / Bitcoin Discussion / Re: Cracking the Code

on: November 28, 2013, 11:09:28 AM

Quote from: AnonyMint on November 28, 2013, 06:05:03 AM Quote from: megastacks on November 28, 2013, 05:57:35 AM Quote from: AnonyMint on November 28, 2013, 05:51:11 AM Because mathematically you need to know the prior block hash before you can compute the next one. And unless you have > 50% of the total network hash rate, then you can't permanently compute the next hash faster than the network can. Note you can with declining probability P (< 1) compute the next hash faster than the network with less than 50% of the hash rate. Since probability is multiplicative, then doing this for two consecutive blocks is P x P, e.g. 0.1 x 0.1 = 0.01 so from 1 in 10 for one block rises to 1 in 100 chance for two blocks. Ditto for N consecutive blocks, e.g. for four blocks then 0.1 x 0.1 x 0.1 x 0.1 = 1 in 10,000 chance. Anony, thanks for the explanation. So if someone has over 50% of the total network hash rate is that something to be concerned about? Do you think it will ever happen? My pleasure. Yes very worried because it means they can control the network and even modify the protocol to make it a fiat, create a zillion coins, etc.. Some argue that they can't do that because the Bitcoiners will fork to a new chain. But these Bitards forget that the masses don't care about Bitcoiner idealism. They just want to buy their pizza. See my Transactions Withholding Attack thread for more explanation on that. Once the masses are already using one fork, they won't switch. The controller could run the fork well enough that the masses are happy, even while creating more coins, etc. Exactly like fiat. We go right back where we started. In my (opinionated) analysis it is very likely to happen (when coin rewards diminish near to 0) with Bitcoin, because of a flaw in the design (transaction fees should be zero instead). https://bitcointalk.org/index.php?topic=344154.msg3745513#msg3745513 https://bitcointalk.org/index.php?topic=342848.msg3745458#msg3745458 Or another attack which gives up control of the network. Dig, dig, dig into the rabbit hole: https://bitcointalk.org/index.php?topic=349096.msg3744842#msg3744842 https://bitcointalk.org/index.php?topic=222998.msg3745278#msg3745278 https://bitcointalk.org/index.php?topic=336816.msg3745161#msg3745161 As soon you start insult people because they don't agree with you, you lose argument

Bitcoin / Development & Technical Discussion / Re: How can I use Bitcoin as validation engine?

on: November 27, 2013, 10:42:55 PM

I'm not developer but I wold build a layer on top of Bitcoin you don't need a lot of bitcoin to do it you can send one between parties and just pay transaction fee.

Pages: [1] 2 3 4 5 6 7 8 9 »