The URL issue is not related to your case in any way.
I'm thinking of 2 possible culprits:
1) You are trying to broadcast a transaction with no fee. Starting 11.1 or 11.2 (can't remember which version), Core will essentially not relay 0 fee transactions anymore.
2) Your current DB is somehow corrupt. It doesn't see some of the spends and is trying to spend invalid TxOuts. A rescan would fix that issue.
If it's neither one nor the other, I'll need to look at your log files.
So the URL issue is a known bug or something? Can you PM an email address I can forward you my logs to? Thanks. |
|
|
|
I'm not mining really with S3's anymore. Costs more than profits. But they are good heaters.
Thats what my buddy does with his KnC cubes; put em in corners of house to heat it up a little. For my "at home rig" (some SP20's) I did the same as well. When it was cold; turned them to blow into the house. When it got hot; turn em back to blow out the window again. To get them hot though you need to mining- then the electricity goes up. |
|
|
|
Cat heater.  That kitten is like, this shit is mine and I know I'm cute as hell...so let me take a nap. |
|
|
|
Set up my first S7 B9 (or B8 if they're the same) with the preinstalled 03 December 2015 firmware and a EVGA 1600w T2 (Titanium) power supply. I asked earlier what the settings should be if I wanted the draw at the wall 1,250watts max. Here's what I've found on 230v. Freq. 606.25M and fans at 32% (3,120rpm fan 01 and 3,000rpm fan 03). Ambient room temp. about 70 degrees F. S7 temps showing 61 degrees C. Kill-A-Watt showing 1,249 watts at the wall on 230v (this includes a NZXT Sentry LX fan controller and 5 additional case fans which uses about 20-25w). Getting above 4,080+ GH/S(avg) at 0.0000% HW errors so far. I don't condone setting the fans so low, just posting this to show what kind of wattage the S7 pulls at the wall at these settings. Dropping to 600M cuts about 14watts (4,020 GH/S). Does anyone know the make and model number of the fan? Want to find out what the CFM is at 3,000 rpm. Has anyone tried to switch the fans like we were doing with the S3+ with the Silverstone FHP141 that moved 171 CFM at 2,000rpm? http://www.silverstonetek.com/product.php?pid=366&area=enI believe these are the stock fans. These babies use 39 watts. Jet Blasters. For the size of the fan, they sure do move lots of air. I'm a big Noctua believer, but when Jet Blasters are installed no need to worry at all about temperatures. http://www.nidecpg.com/fanpdfs/va450dcf.pdf |
|
|
|
Did you pay a fee on these transactions?
If the default transaction fee was selected could the network deny the transaction somehow and make things look weird? The BTC address I sent the coins to indicates a 0 balance, but the wallet I sent the coins to still has the coins in them. I may have selected the default transaction fee. If that may make things look a little odd that would explain "some" of the issues. Still not sure why Armory isn't letting me know there is an updated Core. I can directly send you my log if that may make it easier to check? Little hard to decipher the log if not a developer. I can re-generate the URL issue at will by hitting check update button. I don't want to blindly just reinstall/update. I'd rather try to see why these things are happening, to avoid them later. Thank you. 2016-01-18 20:06 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt2016-01-18 20:06 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible 2016-01-18 20:06 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt2016-01-18 20:06 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt2016-01-18 20:15 (INFO) -- announcefetch.pyc:389 - Forcing announce data fetch 2016-01-18 20:15 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt2016-01-18 20:15 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible 2016-01-18 20:15 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt2016-01-18 20:15 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt2016-01-18 20:15 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown 2016-01-18 20:15 (INFO) -- SDM.pyc:683 - Called stopBitcoind 2016-01-18 20:15 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect... 2016-01-18 20:15 (INFO) -- ArmoryQt.py:6805 - Attempting to close the main window! |
|
|
|
You will see this message when your own Bitcoin node fails to relay the transaction Armory broadcasted back to it.
This is the Armory broadcast process:
1) Armory is connected to your local Bitcoin node as a peer.
2) You create a tx with Armory. Armory broadcasts it to your local node (and only your local node) through the P2P Bitcoin protocol. As far as your node is concerned, it received a tx from another node.
3) Armory, still through the P2P protocol, asks your node for that transaction it just broadcasted by hash.
4.a) If your node returns that tx, Armory considers the tx has been broadcasted succesfully and will display it in your GUI.
4.b) If your node fails to return that tx, Armory will keep polling your local node for that tx for a few seconds. If it runs out of attempts, it will prompt you with that message, which summarizes what I just explained: Armory tried to broadcast the tx but failed to verify the broadcast was successful.
However if any of the steps fail prior to 4) fails, you will get the same message.
The more significant marker of a failure a step 4) is getting a message from Armory that it lost its connection to your local node after you get the failure message. Baring that, the issue is somewhere between 1) and 3).
A failure at step 4) indicates the tx is invalid in some way, a failure somewhere else means something is wrong with your setup.
The only changes I have made was moving the monster DB to a 120GB SSD drive. Using the special startup switch satoshi-datadir. I just ran Armory, loads up just fine. Indicates "online". If I click "Check for Updates" tells me announcements are up-to-date, but still indicates 11.1 core. This is me loading up Armory, letting it go online and sync, trying to check for an update then shutting down. When I get some food in me I'll look into BTC weirdness. I'll gather up the BTC addresses in the log for the past few days, since I only made 2 transmits and check them against the blockchain. My math is telling me 4 BTC vanished, but I have to look further. 2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1076 - C++ block utilities loaded successfully
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1186 -
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1187 -
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1188 -
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1189 - ************************************************************
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1190 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=J:\Armory
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1191 - ************************************************************
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1192 - Loading Armory Engine:
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1193 - Armory Version : 0.93.3
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1194 - Armory Build: : e59e10d38c
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1195 - PyBtcWallet Version : 1.35
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1196 - Detected Operating system: Windows
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1197 - OS Variant : 8-6.2.9200--Multiprocessor Free
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1198 - User home-directory : C:\Users\ME\AppData\Roaming
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1199 - Satoshi BTC directory : J:\Armory
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1200 - Armory home dir : C:\Users\ME\AppData\Roaming\Armory\
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1201 - Detected System Specs :
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1202 - Total Available RAM : 63.90 GB
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1203 - CPU ID string : Intel64 Family 6 Model 63 Stepping 2, GenuineIntel
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1204 - Number of CPU cores : 12 cores
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1205 - System is 64-bit : True
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1206 - Preferred Encoding : cp1252
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1207 - Machine Arch : amd64
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1208 - Available HDD (ARM) : 226 GB
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1209 - Available HDD (BTC) : 5 GB
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1210 -
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1211 - Network Name: Main Network
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1212 - Satoshi Port: 8333
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1213 - Do wlt check: True
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1214 - Named options/arguments to armoryengine.py:
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - nettimeout : 2
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - rescan : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - ignoreAllZC : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - enableSupernode : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - disableModules : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - port : None
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - interport : 8223
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - skipStatsReport : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - forceWalletCheck: False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - rebuild : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - datadir : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - clearMempool : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - offline : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - coverageOutputDir: None
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - armoryDBDir : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - satoshiPort : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - useTorSettings : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - netlog : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - keypool : 100
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - coverageInclude : None
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - forceOnline : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - skipAnnounceCheck: False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - redownload : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - multisigFile : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - disableTorrent : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - testAnnounceCode: False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - mtdebug : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - logDisable : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - settingsPath : C:\Users\ME\AppData\Roaming\Armory\ArmorySettings.txt
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - verbosity : None
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - doDebug : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - enableDetSign : True
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - testnet : False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - rpcport : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - satoshiHome : J:\Armory
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - satoshiRpcport : DEFAULT
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - logFile : C:\Users\ME\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1216 - disableConfPermis: False
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1217 - Other arguments:
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1220 - ************************************************************
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:1620 - C++ block utilities loaded successfully
2016-01-18 19:02 (INFO) -- BDM.pyc:418 - Using the asynchronous/multi-threaded BlockDataManager.
2016-01-18 19:02 (INFO) -- BDM.pyc:419 - Blockchain operations will happen in the background.
2016-01-18 19:02 (INFO) -- BDM.pyc:420 - Devs: check TheBDM.getState() before asking for data.
2016-01-18 19:02 (INFO) -- BDM.pyc:421 - Registering addresses during rescans will queue them for
2016-01-18 19:02 (INFO) -- BDM.pyc:422 - inclusion after the current scan is completed.
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:3531 - Using settings file: C:\Users\ME\AppData\Roaming\Armory\ArmorySettings.txt
2016-01-18 19:02 (INFO) -- announcefetch.pyc:95 - Reading files in fetcher directory:
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - announce : 96f5d5f4253bac5528333c4fef3afd5fa0e931816bfd4c4c8b43d85cee002bb9
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - bootstrap : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - changelog : 1c01304b876de3e75672c8b13d9a00157556b86612afac1c88ffc40a8d7dfb90
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - downloads : 28efee8047ee0a2c26ac9f785d93566fb5a45c20a794da6f972aa48db50ec35a
2016-01-18 19:02 (INFO) -- announcefetch.pyc:104 - notify : 87fa1adcd555be83a71b4f5935a6d4f85178ccbf5043531fdd71432b57d127ca
2016-01-18 19:02 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=8&os=win&ver=0.93.3&id=b00fe8a1
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2736 - loadWalletsAndSettings
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2790 - Loading wallets...
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2849 - Number of wallets read in: 1
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2854 - Wallet (26X1pw3LB): "Primary Wallet Armory " (Encrypted)
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2863 - Loading Multisig Lockboxes
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2298 - Setting up networking...
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2327 - Internet status: 0
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2442 - startBitcoindIfNecessary
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2491 - setSatoshiPaths
2016-01-18 19:02 (INFO) -- SDM.pyc:282 - Total size of files in J:\Armory\blocks is 52.5 GB
2016-01-18 19:02 (INFO) -- SDM.pyc:415 - Found Bitcoin-Qt link on desktop: C:\Program Files (x86)\Armory
2016-01-18 19:02 (INFO) -- SDM.pyc:415 - Found Bitcoin-Qt link on desktop: C:\Program Files\Bitcoin
2016-01-18 19:02 (INFO) -- SDM.pyc:321 - Found bitcoind in the following places:
2016-01-18 19:02 (INFO) -- SDM.pyc:323 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2016-01-18 19:02 (INFO) -- SDM.pyc:323 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2016-01-18 19:02 (INFO) -- SDM.pyc:325 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2016-01-18 19:02 (INFO) -- SDM.pyc:496 - Reading bitcoin.conf file
2016-01-18 19:02 (INFO) -- SDM.pyc:515 - Setting permissions on bitcoin.conf
2016-01-18 19:02 (INFO) -- SDM.pyc:524 - Setting permissions on bitcoin.conf
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: [u'icacls', u'J:\\Armory\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'ME:F']
2016-01-18 19:02 (INFO) -- SDM.pyc:530 - icacls returned:
2016-01-18 19:02 (INFO) -- SDM.pyc:597 - Called startBitcoind
2016-01-18 19:02 (INFO) -- SDM.pyc:282 - Total size of files in J:\Armory\blocks is 52.5 GB
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=J:\\Armory']
2016-01-18 19:02 (INFO) -- SDM.pyc:669 - PID of bitcoind: 4324
2016-01-18 19:02 (INFO) -- SDM.pyc:670 - PID of armory: 9692
2016-01-18 19:02 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: ['.\\guardian.exe', '9692', '4324']
2016-01-18 19:02 (INFO) -- SDM.pyc:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1582 - Armory already registered for current user. Done!
2016-01-18 19:02 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1810 - Changing usermode:
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1811 - From: Expert
2016-01-18 19:02 (INFO) -- ArmoryQt.py:1819 - To: Expert
2016-01-18 19:02 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-01-18 19:02 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt?osvar=8&os=win&ver=0.93.3&id=b00fe8a1
2016-01-18 19:02 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2016-01-18 19:02 (INFO) -- ArmoryQt.py:5887 - Dashboard switched to auto-InitSync
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2525 - loadBlockchainIfNecessary
2016-01-18 19:02 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 1
2016-01-18 19:02 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-01-18 19:02 (INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
2016-01-18 19:02 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-01-18 19:02 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-01-18 19:02 (INFO) -- Networking.pyc:157 - Version: 70002
2016-01-18 19:02 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-01-18 19:02 (INFO) -- Networking.pyc:159 - TimeStamp: 1453161769
2016-01-18 19:02 (INFO) -- Networking.pyc:160 - StartHeight: 393937
2016-01-18 19:02 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
2016-01-18 19:02 (INFO) -- ArmoryQt.py:3148 - Current block number: 393937
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6238 - New Block! : 393938
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6246 - Current block number: 393938
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6238 - New Block! : 393939
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6246 - Current block number: 393939
2016-01-18 19:03 (INFO) -- Networking.pyc:215 - Received new block. 000000000000000002914d619f82f9becd9cdbca341cd4ddb9ab2f4f0e4efc9a
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6238 - New Block! : 393940
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6246 - Current block number: 393940
2016-01-18 19:03 (INFO) -- Networking.pyc:215 - Received new block. 0000000000000000074078c4a5e95c260c00ed3dd55ee43268b659b69c258187
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6238 - New Block! : 393941
2016-01-18 19:03 (INFO) -- ArmoryQt.py:6246 - Current block number: 393941
2016-01-18 19:04 (INFO) -- announcefetch.pyc:389 - Forcing announce data fetch
2016-01-18 19:04 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt
2016-01-18 19:04 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-01-18 19:04 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt
2016-01-18 19:04 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2016-01-18 19:04 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown
2016-01-18 19:04 (INFO) -- SDM.pyc:683 - Called stopBitcoind
2016-01-18 19:04 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-01-18 19:04 (INFO) -- ArmoryQt.py:6805 - Attempting to close the main window!
|
|
|
|
Screenshot of the error? Can you post the logs?
I didn't want to initially randomly post the logs due to security issues. Here is what I have so far. Looks like Armory is not letting me know there is a new version of core (11.2) out there. Still says 11.1 on the dashboard. I have a small balance in my wallet, so I may try to send that out. Before I post more information I want to make sure my pending transaction confirms. If I search the log for "Bitcoins Sent" or "ArmoryQt.py:6662" there isn't even an entry for the coins I sent yesterday but they are in my other wallet. I just emptied out my Armory wallet and will wait for more confirmations. Something doesn't look right. Obvious errors about notifying me about the new core version isn't working. Line 13767: 2016-01-18 17:47 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible Line 13768: 2016-01-18 17:47 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt?osvar=8&os=win&ver=0.93.3&id=b00fe8a1 Line 13807: 2016-01-18 18:17 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible Line 13808: 2016-01-18 18:17 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt Line 13820: 2016-01-18 18:22 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible Line 13821: 2016-01-18 18:22 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt |
|
|
|
Can a new thread be opened for the cheerleader squad and just keep this one pool related? Trying to blow through 20 pages of voodoo and chicken wings to find out pool related info gets more and more difficult. I try to keep up and my usual disclaimer, not trying to offend anyone. A good alternative for cheerleading type posts is Twitter. What is was designed for. Maybe use that for the chicken food and celebration tweets and leftovers will be all detailed pool related. Remember, some of us can't get on the forums daily and I would like to keep up to date on things but sometimes I can't because of 20 pages of "we will get this block" or "have some chicken". While it is crazy funny wacky stuff us old guys read slower and can't keep up so fast. If I'm the only one that thinks this way, then stuff me right back down the hole from which I came.
Thank you.
4 d sake of saving tym & spAc it iz nu requirement 2 Lern SMS TXT LINGO. frm DIS tym 4ward. evry1 must only post n SMS LINGO - n lng h& allowD. pix wiL rEzlt n permenant BAN Hammer. Don't feck w DIS. I had a bad day there. Apologize for the rant. |
|
|
|
bad karma comes to those that get posts' deleted when they speak the truth  .. I agree it was OT but its an issue that needs addressed towards this pool and its operators! You didnt forget BTC is decentralized right. thats what gives it its strength.. You and f2pool are a security issue for BTC whether you want to see it or not.. The free market will be the deciding factor who is right and who was wrong in the end. Sorry if i offended you with truth! Best Regards d57heinz I posted something, can't even remember but was probably the truth and opinionated. Was it deleted? |
|
|
|
It has been such a rat race I've pretty much gave up on keeping exact track on my balances. More or less a hobby, but having lots of buys like this has been nice. I bought my first Bitcoins for under $20 when there weren't any public facing sites out there. I still visit the deep web. Way before kiddy sites like Coinbase ever existed. I may sell 5 or 6 perfectly running S5's, but I'm pretty cheap these days. I'd want a favorable offer. I'd even throw in a couple ATX power supplies. I thought there would be a buy/sell area in the mining area but can't seem to find it.
Try posting here https://bitcointalk.org/index.php?board=75.0Sounds so weird. "Computer Hardware". Maybe when the new forum comes around, if it ever does they will re-organize some of these areas. Perfect place to buy/sell mining hardware would be a sub-forum in the mining forum area. That's where I was looking, thanks. |
|
|
|
|
I'm updated with the latest core and Armory version. Armory indicated "online" and I tried to send some Bitcoin to an address and Armory came up with a snag screen saying it could not send the coin and gave me the transaction URL to check the blockchain. Took me 5 attempts and one transaction finally made it. Anyone else see this? I'm asking before I start dumping time into spending time on checking logs.
|
|
|
|
I bought Batch 1 S7's and yes, buying BTC would have been a better investment. But i had the BTC not the fiat. However: 1. Bitcoin would be worthless if noone "mines it" and processes the transactions. This also applies to the pools mining blocks and including no transactions. 2. I have not had to turn on my furnace yet this year, buying BTC would not keep my house warm. (Last couple of days it has been in the 30's F here and the house @ 75+F with a couple windows partially open. I hope noone takes this the wrong way. I mostly am trying to make myself feel better about spending 8+ BTC on something selling for 2.4 BTC only 4 months later. I will most likely be ordering another S7 soon.  LOL. I've calculated it over and over again hundreds of times since they announced the price of the batch 1 S7 and in like 90% of the models it just doesn't make sense to buy a S7 for me. Even now at BTC2.4 it still doesn't make financial sense to get one but damn it I ordered one anyway and I'm still considering getting another one as well! I'll never understand this. There's actually proof you will lose money or not make it back and people still literally throw money out the door. If you really have an urge to knowingly lose money I can give you my mailing address. Send me a check.  |
|
|
|
guys I know its frustrating to order and then the price drops, but welcome to Bitmaintech I suppose. I recommend only ordering what ships RIGHT AWAY, everything else is pre-order and the price is bound to change for the best or the worse.
You mean "welcome to Bitcoin". |
|
|
|
I believe that it was Xian01 who instead of buying a S7 bought BTC with fiat for the amount that the S7 cost when it first came out. I think he's probably pretty happy about his choice now but I could be wrong since the price had dropped a bit.
I think it was the other way around. He bought BTC at the yearly highs of around $475 on Coinbase instead of buying an S7. There is a photo of his transaction somewhere on this thread. So its shows how doing either can go either way. I think you might be right. I didn't spend too much time trying to find that post and I couldn't recall BTC prices around that time. I guess we'd have to compare his BTC vs the amount of profit mined from the batch 1 S7 plus the potential resale value of the S7. Interesting price adjustment from Bitmain. Decided to do this again instead of buying an S7  Good luck everyone. Boy did I pick a bad day to buy or what ? *sighs* Had another urge to buy a miner. A Batch 3 S7. Decided to do this again, instead.  PACMiC v4 looks to be a loser. Good luck everyone. And the buy button just went live, despite the large expense, I wonder how long until they sell out of batch #1?
Good luck to everyone buying these ! Looks like some great gear, but this time around, instead of buying a fancy new miner, I did the following and will HODL.  Lets see which will be the better investment 9 months down the road. Thanks for sharing. I love mining and will continue to do it. But you do show a track record of pretty good investment's which I applaud you for. Are there any losers you have not shown? It seems like you could have not been right 100 percent of time? It has been such a rat race I've pretty much gave up on keeping exact track on my balances. More or less a hobby, but having lots of buys like this has been nice. I bought my first Bitcoins for under $20 when there weren't any public facing sites out there. I still visit the deep web. Way before kiddy sites like Coinbase ever existed. I may sell 5 or 6 perfectly running S5's, but I'm pretty cheap these days. I'd want a favorable offer. I'd even throw in a couple ATX power supplies. I thought there would be a buy/sell area in the mining area but can't seem to find it.  |
|
|
|
|
Can a new thread be opened for the cheerleader squad and just keep this one pool related? Trying to blow through 20 pages of voodoo and chicken wings to find out pool related info gets more and more difficult. I try to keep up and my usual disclaimer, not trying to offend anyone. A good alternative for cheerleading type posts is Twitter. What is was designed for. Maybe use that for the chicken food and celebration tweets and leftovers will be all detailed pool related. Remember, some of us can't get on the forums daily and I would like to keep up to date on things but sometimes I can't because of 20 pages of "we will get this block" or "have some chicken". While it is crazy funny wacky stuff us old guys read slower and can't keep up so fast. If I'm the only one that thinks this way, then stuff me right back down the hole from which I came.
Thank you.
|
|
|
|
|
Pool wars once again. Why don't pools just let each other operate and if your pool is that good people will join your pool. The kicker is everyone will bad mouth Antpool and bitch, bitch, bitch, but drop $10k on Antminers on the other hand. Confuses me.
|
|
|
|
Pool 1
URL: stratum.kano.is:3333
Worker: <USERNAME>.worker
Password: x
That is it.
Sorry, forgot to say thanks. I think he is connected ok. |
|
|
|
PEBKAC. (opentoe, is that you?)Armory works fine. Armory users host their own blockchain for the maximum level of security. Security <--------|--------> Convenience Feel free to move the slider as you see fit. It sounds to me like you are more interested in convenience. Here, let me help you: https://blockchain.info/ What the heck are you talking about? |
|
|
|
Windows 10 completely fucked all my computers. It's unstable as fuck under the gui. I nuked that shit and went back to 7.
Not sure why you're experiencing such instability, I have Windows 10 since its release with Armory working fine, maybe you should give it a go again Ditto. I've switched over to Windows 10 Pro version on my Windows boxes and have no issues. I run loads of services and programs that were made for Windows 7 with no problems. On a few of them I do have to run in compatibility mode for them to work correctly. I also made sure to install Windows 10 CLEAN from the USB stick. I don't care what anyone says, if you just perform an "upgrade" on top of a Windows 7 box it is like meshing two operating systems into one. I did try a "upgrade" and had lots of issues. Performed clean install, no issues. |
|
|
|
|
Anyone have a screen shot of an S5/S7 config page filled out with registered user for this pool? I'm not home and can't access my network. Trying to help a friend configure his rigs for here and he's having a problem connecting.
Anyway, Happy New Year. Stay safe.
|
|
|
|
|
Show Posts
