|
For future reference, I received my refund in less then 24 hours.
|
|
|
|
Important News:First of all we would like to thank everyone for believing in this project and supporting us. But as clearly evident, the ICO has performed well under anybody's expectations with only about 14 BTC raised so far. We are not sure what went wrong but we clearly messed it up somewhere and want to rectify our mistakes and hence we will be cancelling this ICO and relaunching it after collecting feedback from the community on what did we do wrong. We wanted to still go ahead with the launch and that was the first choice of the team but this decision has been taken keeping in mind the interests of hundreds of people who enrolled for our bounty campaigns and those few people that have backed us in this ICO. Since with only 14 BTC raised in the ICO, the bounties are worth almost nothing and so are the WiC of the investors, we believe relaunching the ICO with new plans is in the best interests of all the stakeholders. We have also received emails from some investors who are demanding refunds.ICO Investors:We will be emailing all the investors the procedure for refunds but you could also send us an email (with the contact email you used for the ICO) at cryptowi@tuta.io with your BTC refund address to claim your BTC back. We value your backing us at this stage and will have some extra bonuses for our current investors in the next ICO. Bounty campaign participants:Unfortunately the bounty campaign has been paused until we can assess what went wrong and relaunch the ICO. The shares you earned up till now will be valid when we launch the new campaign and your hard work will be rewarded. Lastly we would like to thank the community who has been very very positive and appreciative of the project, the investors who believed in us and also the several people who enrolled in our bounty campaign and help spread the word. We know its a set back for the CryptoWi project but we ensure you that we will be back very soon with a new improved plan. We hope you can give us a second chance and we would like to get your very valuable feedback on what we need to improve and where did we go wrong. Please fill up this form and help us asses the situation: https://docs.google.com/forms/d/1c8r9P56ewWc3VhaJWX9PooqE3o2_G2lGxhJ3vNg34RAWe will also be keeping this thread open and will be posting constant updates. We are not going anywhere and are definitely going to be launching WiC and CryptoWi very soon. This is just a delay, not the end. Sorry to hear it is delayed. I will fill in the form soon. I send and email to request the refund, how long do you think before it is processed? |
|
|
|
I understand that quite a few people are surprised by the low ICO investment and so are we. There are a few people emailing us about the same as well. There is something definitely that went wrong here and rest assured we will rectify it. Expect more announcements in about a day.
With everything going on with Bitfinex and the high prices and the ico being open to the end of next month (24th) it is unsure what the BTC price will be by then. Ok granted it is always unsure, but when things go south with Bitfinex debacle they will go south deep and that $10-$100-$1000 people put into it now might just be less worth then the bonuses give some extra. I mean, I took that into account for myself but maybe I'm the only one? |
|
|
|
|
I'm in, hope I'm still on time for the bonus
|
|
|
|
Still awaiting response from you!
this is your fault. and maybe you lost your money. they have sent your payment to the bitcoin wallet address, which was used to send your bet and you can not control this wallet address What is my fault. Would you take a moment to explain it. I don't think it's an error from my end. Dude it is easy. You use address A to send to the address B of secondstrade. If you win secondtrade returns the winning to address A So you send this transaction: https://blockchain.info/tx/45ee3d5b0040ed94be0bad1cc5fb1545a2ff95d1d4bdefdbcc011b80dd4403c6from adress: 1JmnUTj3kyoHAkNpeX4vuVSbxSWpxQL5yW Unless you did send to 18 address at once and own (as in have the privkeys of) that address it clearly looks like a shared wallet from LBC. but you won so the winnings are send back: https://blockchain.info/tx/a9f4523e3c620bd427b28b98b4e65642bbbaebd505e2b1a211b46577da4f044fto adress: 1JmnUTj3kyoHAkNpeX4vuVSbxSWpxQL5yW I guess you have to take that up with LBC (BTW if you send to multiple different addresses from second trade at once all the btc will only be used for one bet at the first address they receive; you send to both GBPUSD Up and GBPUSD Down in one tx... and you are just "lucky" GBPUSD DOWN won with the total of the two bets, that is if you can fix that with LBC of course) |
|
|
|
|
Did anyone tried it with 14.1 yet?
|
|
|
|
Please put instruction for begginers how to buy this ICO. What to do step by step.
Yes this will help alot. Hey, let me try and explain the instructions: 1) On April 22, 2017 at 6PM EST, the escrow team will post a BTC address which is held by them in a multi signature wallet. 2) Anybody who wants to invest will need to send BTC to that address. 3) After sending the BTC, he/she will need to fill the form here: https://docs.google.com/forms/d/1eGp9d49UwoID9N-S-VmzTpobrZbH-p4Xza-xAd13Skk4) After the ICO ends and WiC launches, investors will need to email us their WiC address and claim the ICO coins. In this way we have made the entire process as simple as possible and have eliminated the need to register or make accounts to invest. I will try and make a video about the process for convenience of new investors. I hope these instructions were clear. Let me know if you need more help. Thanks a lot for taking interest! Interesting project. I might join a little. If you make a video try to include how new investors obtain a WiC address |
|
|
|
|
Anaheim Ducks 3 - 0 Edmonton Oilers
|
|
|
|
we are checking it.. but it will take some hours. thank you . Received payment. Thanks |
|
|
|
Hi, since I've updated to Bitcoin Core 0.14.0 the db keeps giving this message every 40 seconds or so: -ERROR - 1489323791: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323791: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323791: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node this is the db log Log file opened at 1489323546: C:\Users\----\AppData\Roaming\Armory\dbLog.txt
-INFO - 1489323546: (..\main.cpp:23) Running on 8 threads
-INFO - 1489323546: (..\main.cpp:24) Ram usage level: 4
-INFO - 1489323546: (..\BlockUtils.cpp:1338) blkfile dir: D:\Bitcoin\blocks
-INFO - 1489323546: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\-----\AppData\Roaming\Armory\databases
-INFO - 1489323546: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1489323547: (..\BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1489323547: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1489323547: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1489323547: (..\BDM_Server.cpp:797) registered bdv: f87d2e25504ce328de4f
-INFO - 1489323549: (..\DatabaseBuilder.cpp:208) Found 456916 headers in db
-INFO - 1489323551: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1489323552: (..\DatabaseBuilder.cpp:477) Found next block after skipping 504928bytes
-INFO - 1489323553: (..\DatabaseBuilder.cpp:268) parsed block file #800
-DEBUG - 1489323553: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1489323553: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 1.419s
-INFO - 1489323553: (..\DatabaseBuilder.cpp:106) scanning new blocks from #456902 to #456905
-INFO - 1489323553: (..\BlockchainScanner.cpp:650) scanned from height #456902 to #456905
-INFO - 1489323553: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.216s
-INFO - 1489323553: (..\DatabaseBuilder.cpp:160) init db in 6.488s
-INFO - 1489323553: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-ERROR - 1489323608: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323608: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323608: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323669: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323669: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323669: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323730: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323730: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323730: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323791: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323791: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323791: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323852: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323852: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323852: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323913: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323913: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323913: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
and the armory log 2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1137 - C++ block utilities loaded successfully
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1247 -
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1248 -
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1249 -
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1250 - ************************************************************
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:\Bitcoin
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1252 - ************************************************************
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1253 - Loading Armory Engine:
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1254 - Armory Version : 0.95.1
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1255 - Armory Build: : 374672b751
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1256 - PyBtcWallet Version : 1.35
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1257 - Detected Operating system: Windows
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1258 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1259 - User home-directory : C:\Users\-----\AppData\Roaming
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1260 - Satoshi BTC directory : D:\Bitcoin
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1261 - Armory home dir : C:\Users\-----\AppData\Roaming\Armory\
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1262 - Detected System Specs :
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1263 - Total Available RAM : 15.93 GB
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1264 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1265 - Number of CPU cores : 8 cores
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1266 - System is 64-bit : True
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1267 - Preferred Encoding : cp1252
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1268 - Machine Arch : amd64
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1269 - Available HDD (ARM) : 146 GB
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1270 - Available HDD (BTC) : 334 GB
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1271 -
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1272 - Network Name: Main Network
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1273 - Satoshi Port: 8333
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1274 - Do wlt check: True
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1275 - Named options/arguments to armoryengine.py:
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - thread_count : -1
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - rescan : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - ignoreAllZC : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - rescanBalance : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - disableModules : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - port : None
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - interport : 8223
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - skipStatsReport : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - forceWalletCheck: False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - regtest : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - rebuild : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - nettimeout : 2
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - datadir : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - clearMempool : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - offline : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - coverageOutputDir: None
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - armoryDBDir : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_port : 9001
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - satoshiPort : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - useTorSettings : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - netlog : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - keypool : 100
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - coverageInclude : None
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - forceOnline : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - skipAnnounceCheck: False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - redownload : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_ip : 127.0.0.1
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - multisigFile : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - ram_usage : -1
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - testAnnounceCode: False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - mtdebug : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - logDisable : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - settingsPath : C:\Users\-----\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - db_type : DB_FULL
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - doDebug : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - enableDetSign : True
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - disableConfPermis: False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - testnet : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - rpcport : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - satoshiHome : D:\Bitcoin
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - satoshiRpcport : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - logFile : C:\Users\-----\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - verbosity : None
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1278 - Other arguments:
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1281 - ************************************************************
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1684 - C++ block utilities loaded successfully
2017-03-12 13:56 (INFO) -- BDM.pyc:367 - Using the asynchronous/multi-threaded BlockDataManager.
2017-03-12 13:56 (INFO) -- BDM.pyc:368 - Blockchain operations will happen in the background.
2017-03-12 13:56 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2017-03-12 13:56 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2017-03-12 13:56 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:3597 - Using settings file: C:\Users\-----\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2608 - Loading Multisig Lockboxes
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1530 - URL-register action: AskUser
2017-03-12 13:56 (INFO) -- ArmoryQt.py:546 - Usermode: Expert
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1709 - From: Expert
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1717 - To: Expert
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-12 13:56 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="FTDLTZaFd5vqTfHqWLBzK91YoDSkR8WYpHbrE8H5fTNc"', u'--satoshi-datadir="D:\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\-----\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\-----\\AppData\\Roaming\\Armory\\databases"']
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-12 13:56 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-12 13:56 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-12 13:58 (INFO) -- ArmoryQt.py:6366 - BDM state is scanning -- force shutdown BDM
2017-03-12 13:58 (INFO) -- SDM.pyc:588 - Called stopBitcoind
2017-03-12 13:58 (INFO) -- SDM.pyc:594 - ...but bitcoind is not running, to be able to stop
2017-03-12 13:58 (INFO) -- ArmoryQt.py:6386 - Attempting to close the main window!
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1137 - C++ block utilities loaded successfully
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1247 -
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1248 -
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1249 -
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1250 - ************************************************************
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:\Bitcoin
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1252 - ************************************************************
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1253 - Loading Armory Engine:
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1254 - Armory Version : 0.95.1
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1255 - Armory Build: : 374672b751
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1256 - PyBtcWallet Version : 1.35
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1257 - Detected Operating system: Windows
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1258 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1259 - User home-directory : C:\Users\-----\AppData\Roaming
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1260 - Satoshi BTC directory : D:\Bitcoin
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1261 - Armory home dir : C:\Users\-----\AppData\Roaming\Armory\
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1262 - Detected System Specs :
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1263 - Total Available RAM : 15.93 GB
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1264 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1265 - Number of CPU cores : 8 cores
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1266 - System is 64-bit : True
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1267 - Preferred Encoding : cp1252
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1268 - Machine Arch : amd64
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1269 - Available HDD (ARM) : 146 GB
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1270 - Available HDD (BTC) : 334 GB
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1271 -
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1272 - Network Name: Main Network
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1273 - Satoshi Port: 8333
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1274 - Do wlt check: True
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1275 - Named options/arguments to armoryengine.py:
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - thread_count : -1
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - rescan : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - ignoreAllZC : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - rescanBalance : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - disableModules : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - port : None
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - interport : 8223
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - skipStatsReport : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - forceWalletCheck: False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - regtest : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - rebuild : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - nettimeout : 2
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - datadir : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - clearMempool : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - offline : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - coverageOutputDir: None
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - armoryDBDir : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_port : 9001
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - satoshiPort : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - useTorSettings : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - netlog : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - keypool : 100
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - coverageInclude : None
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - forceOnline : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - skipAnnounceCheck: False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - redownload : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_ip : 127.0.0.1
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - multisigFile : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - ram_usage : -1
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - testAnnounceCode: False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - mtdebug : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - logDisable : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - settingsPath : C:\Users\-----\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - db_type : DB_FULL
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - doDebug : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - enableDetSign : True
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - disableConfPermis: False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - testnet : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - rpcport : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - satoshiHome : D:\Bitcoin
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - satoshiRpcport : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - logFile : C:\Users\-----\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - verbosity : None
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1278 - Other arguments:
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1281 - ************************************************************
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1684 - C++ block utilities loaded successfully
2017-03-12 13:58 (INFO) -- BDM.pyc:367 - Using the asynchronous/multi-threaded BlockDataManager.
2017-03-12 13:58 (INFO) -- BDM.pyc:368 - Blockchain operations will happen in the background.
2017-03-12 13:58 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2017-03-12 13:58 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2017-03-12 13:58 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:3597 - Using settings file: C:\Users\-----\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-12 13:58 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2017-03-12 13:58 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2608 - Loading Multisig Lockboxes
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1530 - URL-register action: AskUser
2017-03-12 13:59 (INFO) -- ArmoryQt.py:546 - Usermode: Expert
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1709 - From: Expert
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1717 - To: Expert
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-12 13:59 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-12 13:59 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="BMA8coF2js6PSn1AGtq7WukybjnYTSDL18pZ87deE3zk"', u'--satoshi-datadir="D:\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\-----\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\-----\\AppData\\Roaming\\Armory\\databases"']
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-12 13:59 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-12 13:59 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2886 - Current block number: 456905
2017-03-12 14:07 (INFO) -- ArmoryQt.py:4024 - Log saved to C:/Users/-----/Desktop/armorylog_20170312_1407.txt
Log file opened at 1480191063: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1480191121: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1480193992: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1480320551: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1480320743: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
-ERROR - 1480320743: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1480321940: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1480322061: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1480322186: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1480331726: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1480334931: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1480425759: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1481270669: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1482609187: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1482786751: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483042311: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483045028: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483052315: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483053886: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483133221: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483189468: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483281107: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483285553: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483291195: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483299834: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483366683: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483647966: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483727714: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483818976: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483906647: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484046465: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484073963: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1484075731: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1484078389: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1484080635: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
-ERROR - 1484080635: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1484080643: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484082887: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1484085444: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1484085467: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1484085599: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1484085660: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484085667: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484088951: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484089032: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484089081: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484130979: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484154629: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484162710: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484215947: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484216054: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484220135: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484297027: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484302559: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484339516: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484384155: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484491464: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484558186: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484591486: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484913666: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484995269: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485099093: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485116867: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1485116886: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1485117250: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485120544: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1485120633: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1485121265: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485283114: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485534680: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485640126: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1485640145: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1485640462: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485642079: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485765749: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485814169: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485978322: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486287544: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1486287563: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1486290523: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1486293646: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1486293657: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486381490: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486458264: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486629459: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486915604: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486939664: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486976206: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486976397: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486976741: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486979143: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486981467: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1487186040: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1487435332: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1487435350: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1487435832: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1487544196: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1488741920: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1488741939: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1488742042: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1488749048: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1488970297: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1488987113: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489047143: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489047533: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489047645: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
-ERROR - 1489047645: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1489047655: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489048422: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489048440: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1489048554: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489315279: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489315377: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1489318882: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489320121: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1489320128: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489320725: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489323360: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489323510: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1489323530: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
is this nothing to worry about (but it does prevent broadcasting txs sometimes) or can i solve this somehow? EDIT: I should have read a couple of posts above me  |
|
|
|
|
HT: Liverpool 1 - 0 Chelsea
FT: Liverpool 1 - 2 Chelsea
|
|
|
|
|
Yes I remember clearly as it was a good learning curve at that moment.
For my first transaction I bought a coin, pretty huge for just testing it out now that I look back at it.
I checked everything multiple times, like reading the whole address and so. New to this I figured out it would take approximately 10 minutes before I got my coin as the average blocktime was 10 minutes. So I waited 10 minutes....
nothing....
waited some more....
nothing....
started sweating and recheck the address in my wallet and on the site I bought it, they were the same.
was I scammed?
still waiting...
nothing...
Something wrong with how do you call it the blockchain?
browsing... no news
still waiting...
confused...
Did I do something wrong?
still waiting.....
it took 97 minutes before next block was mined... and immediately i had my coin in my wallet... sigh the longest 97 minutes in my btc experience. Ok I had to wait longer on confirmations but back then I didn't no anything, so yeah I will never forget my first transaction.
|
|
|
|
|
Insert Quote
HT: Liverpool 1 - 1 Southampton
FT: Liverpool 2 - 1 Southampton
|
|
|
|
|
Eibar 0 v 2 Barcelona
Eibar 1 v 4 Barcelona
|
|
|
|
The tx fee of 0.0002 ate all your profits and more. |
|
|
|
|
Pittsburgh 19 - 21 Kansas City
|
|
|
|
|
Show Posts
