Search content
Sort by

Showing 20 of 174 results by aneutronic
Post
Topic
Board Armory
Re: ArmoryDB doesn't scan blocks, no errors in log
by
aneutronic
on 01/08/2020, 16:02:13 UTC
1) Check port 15000 isn't in use.
2) Check ArmoryQt is actually trying to connect to localhost:15000
3) Start ArmoryDB manually if you have to, give it the proper port.

1) Yes, did that using tcpview.

2) ArmoryQT never connects to 15000 even when running properly, only 8223.
At least that's what tcpview showed.

3) Tried this again and it works only if you start armorydb manually first then launch armoryqt.
I haven't tried any transactions yet but everything looks normal.
I guess it's ok as a temporary solution but still would like to know why armoryqt freezes and won't start armorydb on it's own.
Also I noticed that if you launch armoryqt first then start armorydb manually it won't connect to the db and tcpview fills up with system processes using port 9001.
Post
Topic
Board Armory
Re: ArmoryDB doesn't scan blocks, no errors in log
by
aneutronic
on 31/07/2020, 23:13:50 UTC
Yes, I'm using windows 10 and nice trick! Modifying the AmoryUtils.py does work to change the port number to 15000 but armoryqt still freezes, won't start armorydb and I still get the same fcgi error in the rapidly growing armorycpplog.txt.

Code:
Log file opened at 16:23:20.000: D:\armory\armorycpplog.txt
-ERROR - 16:23:32.469: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - 16:23:32.485: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version

armorylog.txt
Code:
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1164 - C++ block utilities loaded successfully
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1281 -
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1282 -
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1283 -
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1284 - ************************************************************
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1285 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=D:\armory --dbdir=D:\armory\databases --satoshi-datadir=D:\bitcoin\blocks
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1286 - ************************************************************
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1287 - Loading Armory Engine:
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1288 -    Armory Version        : 0.96.5
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1289 -    Armory Build:         : 8730390989
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1290 -    PyBtcWallet  Version  : 1.35
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1291 - Detected Operating system: Windows
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1292 -    OS Variant            : 10-10.0.18362--Multiprocessor Free
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1293 -    User home-directory   : C:\Users\me\AppData\Roaming
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1294 -    Satoshi BTC directory : D:\bitcoin
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1295 -    Armory home dir       : D:\armory
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1296 - Detected System Specs    :
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1297 -    Total Available RAM   : 15.88 GB
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1298 -    CPU ID string         : Intel64 Family 6 Model 142 Stepping 9, GenuineIntel
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1299 -    Number of CPU cores   : 4 cores
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1300 -    System is 64-bit      : True
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1301 -    Preferred Encoding    : cp1252
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1302 -    Machine Arch          : amd64
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1303 -    Available HDD (ARM)   : 3340 GB
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1304 -    Available HDD (BTC)   : 3340 GB
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1305 -
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1306 - Network Name: Main Network
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1307 - Satoshi Port: 8333
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1308 - Do wlt check: True
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1309 - Named options/arguments to armoryengine.py:
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     force_segwit    : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     nettimeout      : 2
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rescan          : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     force_fcgi      : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     ignoreAllZC     : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rescanBalance   : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     disableModules  : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     port            : None
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     interport       : 8223
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     coverageOutputDir: None
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     forceWalletCheck: False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     regtest         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rebuild         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     thread_count    : -1
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     datadir         : D:\armory
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     clearMempool    : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     offline         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     armoryDBDir     : D:\armory\databases
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     armorydb_port   : 15000
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     satoshiPort     : DEFAULT
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     disableConfPermis: False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     useTorSettings  : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     netlog          : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     keypool         : 100
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     coverageInclude : None
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     forceOnline     : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     disableWalletCheck: False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     redownload      : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rpcBindAddr     : 127.0.0.1
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     armorydb_ip     : 127.0.0.1
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     multisigFile    : DEFAULT
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     ram_usage       : -1
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     ignoreZC        : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     logDisable      : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     settingsPath    : D:\armory\ArmorySettings.txt
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     language        : en
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     db_type         : DB_FULL
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     doDebug         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     enableDetSign   : True
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     mtdebug         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     testnet         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rpcport         : DEFAULT
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     satoshiHome     : D:\bitcoin\blocks
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     satoshiRpcport  : DEFAULT
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     logFile         : D:\armory\ArmoryQt.exe.log.txt
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     verbosity       : None
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1312 - Other arguments:
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1315 - ************************************************************
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1720 - C++ block utilities loaded successfully
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:3578 - Using settings file: D:\armory\ArmorySettings.txt
2020-07-31 16:23:20 (ERROR) -- ArmoryUtils.py:3735 - Unsupported language  specified. Defaulting to English (en)
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:3738 - Using Language: en
2020-07-31 16:23:20 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2020-07-31 16:23:20 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background. 
2020-07-31 16:23:20 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2020-07-31 16:23:20 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for
2020-07-31 16:23:20 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2020-07-31 16:23:22 (INFO) -- ArmoryUtils.py:3578 - Using settings file: D:\armory\ArmorySettings.txt
2020-07-31 16:23:28 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2020-07-31 16:23:28 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2020-07-31 16:23:28 (INFO) -- ArmoryQt.py:2195 - Loading Multisig Lockboxes
2020-07-31 16:23:28 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1513 - URL-register action: AskUser
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2020-07-31 16:23:32 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1

Any ideas on what else could be tripping the fcgi error? The only thing that changed on my pc since the last successful run was windows updates.
Post
Topic
Board Armory
Re: ArmoryDB doesn't scan blocks, no errors in log
by
aneutronic
on 30/07/2020, 22:25:11 UTC
yes sir, with or without quotes makes no difference.
Post
Topic
Board Armory
Re: ArmoryDB doesn't scan blocks, no errors in log
by
aneutronic
on 30/07/2020, 19:04:11 UTC
Thanks for the quick reply!

I get the same results and errors whether port is specified on cmd line or config files.

Code:
2020-07-30 14:02:02 (ERROR) -- ArmoryQt.py:1830 - Failed to start Armory database: in method 'BlockDataManagerConfig_hasLocalDB', argument 2 of type 'string const &'
Traceback (most recent call last):
  File "ArmoryQt.py", line 1796, in startArmoryDBIfNecessary
TypeError: in method 'BlockDataManagerConfig_hasLocalDB', argument 2 of type 'string const &'

It looks like the same "TypeError:" on line 1796 carcinogen is getting.


The problem stems from my Windows 10 installation which already has an Intel service listening on 9001.

I initialize armorydb.exe --fcgi-port=9002 --satoshi-datadir="F:\Bitcoin" and it appears to sync up properly.

Then I run armoryqt.exe --armorydb-port=9002 --satoshi-datadir="F:\Bitcoin" and it fails to go online with the following log:

Code:
2020-07-13 17:24:54 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1513 - URL-register action: AskUser
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:566 - Usermode: Advanced
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1699 -    From: Advanced
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1707 -      To: Advanced
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2020-07-13 17:24:56 (ERROR) -- ArmoryQt.py:1830 - Failed to start Armory database: in method 'BlockDataManagerConfig_hasLocalDB', argument 2 of type 'string const &'
Traceback (most recent call last):
  File "ArmoryQt.py", line 1796, in startArmoryDBIfNecessary
TypeError: in method 'BlockDataManagerConfig_hasLocalDB', argument 2 of type 'string const &'
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 0
2020-07-13 17:24:58 (INFO) -- ArmoryQt.py:5477 - BDM is safe for clean shutdown
2020-07-13 17:24:58 (INFO) -- SDM.pyc:465 - Called stopBitcoind
2020-07-13 17:24:58 (INFO) -- SDM.pyc:471 - ...but bitcoind is not running, to be able to stop
2020-07-13 17:24:58 (INFO) -- ArmoryQt.py:5490 - Attempting to close the main window!

I have also tried supplying "F:\Bitcoin\blocks" as the satoshi datadir with the same result.

I have also attempted to run Armory by itself without arguments so that it spawns the DB, but the program simply freezes and writes infinitely to armorycpplog.txt the following error:

Code:
-ERROR - 17:31:11.625: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version

I assume this has something to do with port 9001 being unavailable because no such error appears when the term --armorydb-port=9002 is supplied.

The problem with changing port number is only in armoryqt.exe as I can run armorydb.exe with a port number specified on the cmd line and it appears to work ok.
Post
Topic
Board Armory
Re: ArmoryDB doesn't scan blocks, no errors in log
by
aneutronic
on 30/07/2020, 16:09:13 UTC

I have also attempted to run Armory by itself without arguments so that it spawns the DB, but the program simply freezes and writes infinitely to armorycpplog.txt the following error:

Code:
-ERROR - 17:31:11.625: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version

I assume this has something to do with port 9001 being unavailable because no such error appears when the term --armorydb-port=9002 is supplied.

I'm getting the same program freeze while starting Armory with the same error and rapidly growing armorycpplog.txt file.

Everything worked fine the last time I ran Armory about a month ago so I assume some windows update caused the issue.

Port 9001 is also being shown used by some unknown windows system process on my pc.

Also getting the same python refusing to read the string error when using the --armorydb-port= cmd line option.

Is there a work around for this or can it only be fixed with an Armory update?
Post
Topic
Board Pools
Re: [4300 TH] BTC Guild - Pays TxFees+Orphan+NMC, Stratum, Private Servers
by
aneutronic
on 02/02/2014, 20:39:42 UTC
I use opendns, I hate my isp.  Sad

this is weird. I changed to google's dns and it worked then switched back to opendns again and still working.  Huh

dead rat in the pipe?    Grin

I dunno but it's good now, thanks very much for your help.

Here's a great utility to help you find the best DNS resolver for your location.

https://www.grc.com/dns/benchmark.htm

thanks, I'll give it try.
Post
Topic
Board Pools
Re: [4300 TH] BTC Guild - Pays TxFees+Orphan+NMC, Stratum, Private Servers
by
aneutronic
on 02/02/2014, 18:47:15 UTC
I use opendns, I hate my isp.  Sad

this is weird. I changed to google's dns and it worked then switched back to opendns again and still working.  Huh

dead rat in the pipe?    Grin

I dunno but it's good now, thanks very much for your help.
Post
Topic
Board Pools
Re: [4300 TH] BTC Guild - Pays TxFees+Orphan+NMC, Stratum, Private Servers
by
aneutronic
on 02/02/2014, 11:06:23 UTC
just tried with my phone, tmobile, and I can bring up the site and login ok.
not a great solution but still no go through my ISP.
 Huh
Post
Topic
Board Pools
Re: [4300 TH] BTC Guild - Pays TxFees+Orphan+NMC, Stratum, Private Servers
by
aneutronic
on 02/02/2014, 09:20:38 UTC

What error do you see when trying to load?  Is it an actual error page, or is it a generic browser error?

generic - mostly a blank page, chromium just timeouts and gives this message:

Quote
This webpage is not available

will this traceroute result help?
Code:
~ $ traceroute www.btcguild.com
traceroute to www.btcguild.com (162.159.241.90), 30 hops max, 60 byte packets
 1  myrouter (192.168.0.1)  2.174 ms  2.164 ms  2.147 ms
 2  dynamic-acs-*-*-*-*.myISP (*.*.*.*)  8.991 ms  12.365 ms  17.741 ms
 3  static-acs-*-*-*-*.myISP (*.*.*.*)  19.903 ms  19.911 ms  19.898 ms
 4  dynamic-acs-*-*-*-*.myISP (*.*.*.*)  19.899 ms  19.874 ms  19.847 ms
 5  xe-3-2-1.mpr4.phl2.us.above.net (208.185.145.149)  28.561 ms  28.573 ms  28.553 ms
 6  ae2.mpr3.phl2.us.above.net (64.125.31.25)  31.281 ms  26.602 ms  26.581 ms
 7  ae4.cr1.lga5.us.above.net (64.125.31.34)  29.527 ms  25.601 ms  29.983 ms
 8  ae1.cr2.lga5.us.above.net (64.125.29.38)  31.546 ms  30.626 ms  30.588 ms
 9  xe-0-2-1.er2.lga5.us.above.net (64.125.30.210)  23.680 ms  27.580 ms  34.830 ms
10  paix.xe-5-3-0.cr1.nyc2.us.nlayer.net (198.32.118.91)  31.931 ms  22.232 ms  26.172 ms
11  vlan-78.ar2.ewr1.us.nlayer.net (69.31.34.127)  32.929 ms  36.634 ms  32.918 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Post
Topic
Board Pools
Re: [4300 TH] BTC Guild - Pays TxFees+Orphan+NMC, Stratum, Private Servers
by
aneutronic
on 02/02/2014, 08:43:49 UTC
I'm getting blocked from www.btcguild.com. the miner seems to be connecting still but I can't get to the dashboard or graphs to check anything.

No problems here. Probably a problem at your closest CloudFlare server. Nothing I can do about that other than wait.  CloudFlare is only used for website access. The mining servers are completely separate.

thanks for the quick reply.
It's been blocked for ~11hrs so I'm having doubts if it will come back on it's own.
http://www.isitdownrightnow.com/btcguild.com.html shows it's working for others.
anything else I can try?
Post
Topic
Board Pools
Re: [4300 TH] BTC Guild - Pays TxFees+Orphan+NMC, Stratum, Private Servers
by
aneutronic
on 02/02/2014, 08:08:51 UTC
I'm getting blocked from www.btcguild.com. the miner seems to be connecting still but I can't get to the dashboard or graphs to check anything.
Post
Topic
Board Hardware
Re: Avalon ASIC users thread
by
aneutronic
on 01/02/2014, 23:13:34 UTC
iirc the wiki recommends to not flash via the command line.
telnet in:

Code:
telnet 192.168.1.1 -l root
mount_root
mtd -r erase rootfs_data

now you should be able to get the web gui at 192.168.0.100 again.

Post
Topic
Board Hardware
Re: Avalon ASIC users thread
by
aneutronic
on 01/02/2014, 10:26:17 UTC
I went and did something stupid I guess because my box will not respond. I re-flashed the box and forgot to unchecked the settings box. I could not reach the box and it would not ping. I did a reset of the board, changed my nic and plugged  the miner into my notebook. Still no ping. Powered down and back up still no ping. It just sits there in idle mode...yellow and green leds lit and a slow 1 sec. pulse coming from the on-board nic.

Is there a way to force flash these things without using the web interface? Googled a for a while but did not find the answer.

Thanks ahead of time for any info or
a finger point in the right direction...

search this thread for "failsafe".

Post
Topic
Board Hardware
Re: [ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING***
by
aneutronic
on 31/01/2014, 12:10:11 UTC
What in the heck are you guys thinking?!? Have you ever even tried the currency exchange game?

Please explain to me how spending say 110 in the past say for a BFL single to have it mine maybe 10 or say 15 btc over it's lifetime EVER EVER going to be a profit?! Why is mining better than buying and holding on to the coins? The only way mining will ever be worth it is if you paid with fiat. Then and only then you are truly betting on the exchange rate of btc -ie you are long BTC to use trader speak. So if the exchange rate keeps on going up and up even if the hardware only mines less than what your fiat bought you in btc terms at the time you purchased the hardware then you are still IN PROFIT IN FIAT terms, but then that begs the question why did you even do that. Why not just keep btc that you bought with fiat at whatever price and go long btc. You would've had MORE overall had you not spent it on some digital gold digger that will likely mine less than what you put into it!

Let's be honest here. The main reason we do this is because:

a) we enjoy playing with the technology
b) we have some fetish about mining
c) we are fools cause we think we will actually make a profit in btc terms
d) we are too gutless to trade btc
e) we don't have enough fiat cash to buy hardware so we reinvest or invest btc instead
f) we enjoy making the ASIC mining companies rich

The reality is that you will be outgunned by people with more money than you when it comes to mining.



+10

nailed it!
Post
Topic
Board Hardware
Re: Avalon ASIC users thread
by
aneutronic
on 31/01/2014, 10:37:08 UTC
the fried capacitor is 4.7uF/16V|SMD ceramic capacitors|C8, C17, C146|CAPC2012L|3|4.7uF/16V/X7R| from the BOM.
this should work for a replacement: http://www.mouser.com/ProductDetail/TDK/CGA4J3X7R1C475K125AB/?qs=sGAEpiMZZMs0AnBnWHyRQEWjzA2rN6H9lzWbV9EGTp4%3d

the larger cap next to it would be 22uF/16V|SMD ceramic capacitors|C6, C7|CAPC3225L|2|22uF/16V/X7R|
http://www.mouser.com/ProductDetail/TDK/C3225X7R1C226K250AC/?qs=sGAEpiMZZMs0AnBnWHyRQEWjzA2rN6H938yxxtUSLGM%3d
I would replace it also.

you will have to check for board damage after removing the caps to determine if it can be repaired. if not you can remove the connector to disable the bad section.

changing the miner count won't help as this miner section is not on the end of the board.

I would also recommend replacing the thermal interface material with a quality compound such as arctic cooling as5 or mx4.
you can search back in this thread for tips on doing this.
Post
Topic
Board Hardware
Re: HashFast announces specs for new ASIC: 400GH/s
by
aneutronic
on 29/01/2014, 21:43:25 UTC
this^
even if hf ships 1600 ghs mpp at the end of Feb (lol) he will still only get ~6BTC per machine in 6 months, not even close to the 61BTC he could have bought for the usd cost of each machine. I'm no investment expert but a 90% loss is not a good investment no matter which way you try to paint it.
I feel sorry for those that don't understand this.   Sad

Not quite.

Not buying something is not the same as taking a loss.


*facepalm*

yes, quite, just as the last 2 posts state.

I'm not a day trader, I believe in BTC and I'm invested for the long term.
I lost my ass in BTC betting on 2 scamming miner manufacturers, and I use that term very loosely, and now I'm done.
I've contributed all I can afford to the security of the network so no more miners for me, I will buy BTC whenever possible and hodl.

Post
Topic
Board Hardware
Re: HashFast announces specs for new ASIC: 400GH/s
by
aneutronic
on 29/01/2014, 19:53:22 UTC
Indeed, very nice, congratulations! What a pity the HashFuck people obliterated all these planings, preparations, dreams and anticipation by delivering inferior products 3 months late, thus destroying your investment in them to maybe a tenth.

I paid in USD. And I sell the coins I make for USD. I feel sorry for those that paid in BTC.

Its not only a problem of having paid in BTC or not, its more about how much coins will these miners mine in their rational lifespan. I hope you make more than 50% of your investment back, honestly.

this^
even if hf ships 1600 ghs mpp at the end of Feb (lol) he will still only get ~6BTC per machine in 6 months, not even close to the 61BTC he could have bought for the usd cost of each machine. I'm no investment expert but a 90% loss is not a good investment no matter which way you try to paint it.
I feel sorry for those that don't understand this.   Sad

http://thegenesisblock.com/mining/a/1242f44435
http://thegenesisblock.com/mining/a/15b1795a9f


btw joshv06

All the People who paid in BTC and saw an opportunity in an indirect investment Lawyered up.

if anyone was opportunistic in this cluster-fuck of a trainwreck it would be the liars who tried to build a company by deceiving customers with over-priced 90 day late delivered miners that were slower and used considerably more power than promised.
that tends to piss off rationally thinking people who are less than thrilled about a 90% loss.
many of the people that paid in BTC decided to discourage such unethical scamming lying so called businesses and "lawyer up".
or you could just choose to bend over and capitulate and keep enabling scammers like bfl, avalon, and hf.
good luck with your expected profits.   Roll Eyes
Post
Topic
Board Group buys
Re: [**OPEN**]R2B:HashFast + Host, Dbl. HashRate Upgrade, $43, 10-13GH/s MPP
by
aneutronic
on 29/01/2014, 13:47:49 UTC

[trimmed]  Smiley

I'm not sure what more you'd have me to as I'm in the most Red out of anyone for the reasons above. I put a lot of money down to be able to deliver you guys these at-cost deals, and I continue to put money down, along with the rest of the leaders, to try to get legal recourse to get full BTC refunds which is what the majority wanted overwhelmingly.

There isn't/wasn't a better GB setup/value on the forums available at that time and everything would've been peachy if they had just simply delivered on time or even a little late. HashFast tricked fucked us, but what pisses me off even more is how they've turned miners against other miners.


+1 for your response.  FTFY a bit.   Grin

All of us were dealt an extremely shitty hand here and I feel that DZ has handled it very well... kudos!

I'm rooting for all the legal action from all miners involved against these scammers as this has indeed become a disturbing trend in BTC mining and this is the best way to stop it.

imho the miners who rolled over and cheerfully accepted a screwing from scamfast just keep enabling this type of unethical behavior.
why can't they understand that a better investment would have been to buy BTC and hodl instead of buying an overpriced and a 3 month late delivered miner.   Huh




Post
Topic
Board Hardware
Re: HashFast announces specs for new ASIC: 400GH/s
by
aneutronic
on 25/01/2014, 15:06:09 UTC
Seems like it would be more efficient to just buy Bitcoin than rent an asic farm.

Always was (since Avalon batch #1), always will be.

^THIS

we will never be able to compete with this trend:

http://www.coindesk.com/coinseed-5m-investment-bitfury-mining/
Post
Topic
Board Hardware
Re: HashFast announces specs for new ASIC: 400GH/s
by
aneutronic
on 23/01/2014, 12:59:15 UTC
For those who want to re-instate their orders... I have been told this is the process:

Quote
Thanks for your email.

For any customer that DOES NOT want their refund check & wants their order to be placed back in the queue, please instruct them to mail the checks back to:

HashFast Technologies

c/o: Erin or Cara

100 Bush Street

Suite 650

San Francisco, Ca. 94104

and to have them email refunds@hashfast.com & erin@hashfast.com to advise me that this has been done.

Hope that helps someone...

What a joke.

Yeah, mail it back with a screenshot of this:

Quote
Received: by 10.194.138.199 with SMTP id qs7csp90853wjb;
        Fri, 16 Aug 2013 16:38:36 -0700 (PDT)
X-Received: by 10.236.45.102 with SMTP id o66mr196684yhb.13.1376696316262;
        Fri, 16 Aug 2013 16:38:36 -0700 (PDT)
Return-Path: <bitpaysupport@hashfast.com>

Hi Jim,
Thank you so much for your patience while I got the answer for you, I greatly appreciate it.

The answer is if you buy Baby Jet for 51 BitCoins today and it does not ship, you will be refunded the 51 BitCoins you paid.

I hope that helps and hope you have a good weekend!

Thanks,
Cara

+1

just don't hold your breath waiting for them to do the right thing.