No one that gives half a shi.t about Bitcoin should mine here. Of course Bitmain will mine all their machines here, but no one else should! They are by and far the worst empty block offenders and they'll never do anything to change until the network forces them to, just like they keep running their crappy cgminer fork.
|
|
|
Thought I would chime in as I printed off these ducts/covers many months ago, using our office printer I have a friend with a 3D printer and he's making the ducts for me. I got the S5 over the weekend and hooked it up in my laundry room. It's loud, but it's not as loud as I expected from everything I read. I used some tin foil to cover the bottom of the unit and then some more tin foil at the back to duct most of the hot air out my dryer vent. The laundry room did get a few degrees warmer, but I think once I get the ducts on and get all the hot air to leave through the vent it will be better. I'll try a couple different fans to see what it does for noise, but stock fan is something I can live with and the box runs around 50*C which is great.
|
|
|
The first parts of my 3D printed S5 ducts are complete, just waiting on the second half of them to finish up. My friend has a 3D printer so he's able to make these for me. I look forward to experimenting with them and some different fan combos to see if I can get my S5 a little quieter but still running cool.
|
|
|
That missing 110 ph where is it? I don't know guesses abound we have put up more then Ten ideas.
Let's hope most of the missing hash stays missing.
The thing is, missing or not, that equipment physically exists out there still (unless it burned down or was all "old" gear that got recycled), so it could come back at any time and bump diff again. It's a fun mystery to contemplate, I only wish we could get a definitive answer on what it is.
|
|
|
As a result, the interest rate of Wallet, the flexible interest wallet, will be lowered from the current 3% APR to 2% APR;
So I play around with Epay faucets some times and they will pay 1% on all your faucet earnings. 2% here isn't that appealing, it's not really even noticeable for most deposits. Sure, it's more than 0, but it's getting to the point that it's not worth having any coin stored with HaoBTC.
|
|
|
I would love for us to do 90 days with -0.5% in diff and +20% in price.
I would be much happier with a significant decrease in difficulty. Any negative is nice, but really -0.5% is not noticeable. Let's get some > -10% adjustments and then we're talking. I'd love to see diff get back down below 100G and still maintain a +$400 coin price. I just got an S5 and am considering pointing it here for a chance at the Avalon give away. I'm afraid if I won, though, that I couldn't afford the electricity to run it, lol.
|
|
|
My S3+ solo lottery machine got it's best ever share a couple weeks ago after running almost a year, "bestever": 44,756,831,208. That would have been a block a year ago when I started mining! Over the weekend I just upgraded my solo lottery miner to an S5, so here's to hoping!
|
|
|
Happened to me too just yesterday. Core crashed and I booted it back up and had a corrupted database, so I told it to rebuild and it crashed again. Then it wouldn't get past the loading screen without crashing, so I deleted everything in my \Bitcoin\ directory and reinstalled Core 0.12 and the same thing kept happening, crash at the loading screen. I tried installing my \Bitcoin\ directory on another physical drive and still same thing happened. After deleting and reinstalling about 5 times it finally booted up and started syncing again. I think this is my computer telling me it's too old for this sh.t any more.
So v0.12 is a total bust for me. It crashed once more and I cannot get it to start up no matter what. It sometimes makes it to "checking addresses" on the loading screen, but never any further. Sometimes it crashes as soon as the loading screen appears. I went back to 0.11.2 and it loads just find so it is a bug specific to 0.12. Here are a few of my logs from the crashes, you can see the program just stops with no indication of any sort of error. 2016-02-26 15:14:47 Bitcoin version v0.12.0 (2016-02-17 09:40:03 +0100) 2016-02-26 15:14:47 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2016-02-26 15:14:47 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed 2016-02-26 15:14:48 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2016-02-26 15:14:48 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2016-02-26 15:14:48 Default data directory [editted out] 2016-02-26 15:14:48 Using data directory [editted out] 2016-02-26 15:14:48 Using config file [editted out] 2016-02-26 15:14:48 Using at most 125 connections (2048 file descriptors available) 2016-02-26 15:14:48 Using 2 threads for script verification 2016-02-26 15:14:48 Using wallet wallet.dat 2016-02-26 15:14:48 scheduler thread start 2016-02-26 15:14:48 init message: Verifying wallet... 2016-02-26 15:14:48 CDBEnv::Open: LogDir=[editted out] ErrorFile=[editted out] 2016-02-26 15:14:48 Error: Couldn't open socket for incoming connections (socket returned error An address incompatible with the requested protocol was used. (10047)) 2016-02-26 15:14:48 Bound to 0.0.0.0:8333 2016-02-26 15:14:48 Cache configuration: 2016-02-26 15:14:48 * Using 2.0MiB for block index database 2016-02-26 15:14:48 * Using 32.5MiB for chain state database 2016-02-26 15:14:48 * Using 65.5MiB for in-memory UTXO set 2016-02-26 15:14:48 init message: Loading block index... 2016-02-26 15:14:48 Opening LevelDB in [editted out] 2016-02-26 15:14:48 Opened LevelDB successfully 2016-02-26 15:14:48 Using obfuscation key for [editted out]: 0000000000000000 2016-02-26 15:14:48 Opening LevelDB in [editted out] 2016-02-26 15:14:48 Opened LevelDB successfully 2016-02-26 15:14:48 Using obfuscation key for [editted out]: 72046a1e7622fad5 2016-02-26 15:14:57 LoadBlockIndexDB: last block file = 197 2016-02-26 15:14:57 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=365, size=131274522, heights=330521...330993, time=2014-11-18...2014-11-21) 2016-02-26 15:14:57 Checking all blk files are present... 2016-02-26 15:14:58 LoadBlockIndexDB: transaction index disabled 2016-02-26 15:14:58 LoadBlockIndexDB: hashBestChain=00000000000000001639f0ef7eb082b57e48f33baeb9082a7ab07ef3ef7df130 height=330922 date=2014-11-21 00:37:07 progress=0.450084 2016-02-26 15:14:58 init message: Verifying blocks... 2016-02-26 15:14:58 Verifying last 288 blocks at level 3 2016-02-26 15:15:14 No coin database inconsistencies in last 36 blocks (26535 transactions) 2016-02-26 15:15:14 block index 26188ms 2016-02-26 15:15:14 init message: Loading wallet... 2016-02-26 15:15:15 nFileVersion = 120000 2016-02-26 15:15:15 Keys: 0 plaintext, 265 encrypted, 265 w/ metadata, 265 total 2016-02-26 15:15:15 wallet 281ms 2016-02-26 15:15:15 init message: Activating best chain... 2016-02-26 15:15:16 UpdateTip: new best=000000000000000012e7c144fc1c1038c2e7826033b8c9739e5e690b8bf40b91 height=330923 log2_work=81.519843 tx=51953838 date=2014-11-21 00:49:03 progress=0.450093 cache=0.4MiB(1228tx) 2016-02-26 15:15:19 UpdateTip: new best=00000000000000001acb1484131a0b69c7666e1a9b94e483babae59adf1fe160 height=330924 log2_work=81.519915 tx=51954895 date=2014-11-21 01:02:32 progress=0.450110 cache=15.2MiB(4216tx) 2016-02-26 15:15:22 UpdateTip: new best=000000000000000005357156756d6576017e084a6ad8505fd2721feb79773b6c height=330925 log2_work=81.519987 tx=51956910 date=2014-11-21 01:56:55 progress=0.450152 cache=17.7MiB(8185tx) 2016-02-26 15:15:24 UpdateTip: new best=00000000000000001062194213863dab2ef62cb1f7715329927c6d24dc0dc0fd height=330926 log2_work=81.520059 tx=51957644 date=2014-11-21 01:57:29 progress=0.450160 cache=21.0MiB(9680tx) 2016-02-26 15:15:26 UpdateTip: new best=00000000000000000a99e0837981a3ffb45b20b14a4f30e6be51eb014a69a850 height=330927 log2_work=81.520131 tx=51959086 date=2014-11-21 02:14:09 progress=0.450182 cache=22.4MiB(11784tx) 2016-02-26 15:15:29 UpdateTip: new best=0000000000000000178e4ae780a4e48f28c1cf6e061167b92e3ee1f75e166a37 height=330928 log2_work=81.520203 tx=51960689 date=2014-11-21 02:40:51 progress=0.450210 cache=25.6MiB(14222tx) 2016-02-26 15:15:29 mapBlockIndex.size() = 400090 2016-02-26 15:15:29 nBestHeight = 330928 2016-02-26 15:15:29 setKeyPool.size() = 98 2016-02-26 15:15:29 mapWallet.size() = 307 2016-02-26 15:15:29 mapAddressBook.size() = 64 2016-02-26 15:15:29 init message: Loading addresses... 2016-02-26 15:15:29 torcontrol thread start 2016-02-26 15:15:29 ERROR: Read: Failed to open file [editted out] 2016-02-26 15:15:29 Invalid or missing banlist.dat; recreating 2016-02-26 15:15:29 Loaded 158 addresses from peers.dat 32ms 2016-02-26 15:11:32 Bitcoin version v0.12.0 (2016-02-17 09:40:03 +0100) 2016-02-26 15:11:32 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2016-02-26 15:11:32 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed 2016-02-26 15:11:33 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2016-02-26 15:11:33 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2016-02-26 15:11:33 Default data directory [editted out] 2016-02-26 15:11:33 Using data directory [editted out] 2016-02-26 15:11:33 Using config file [editted out] 2016-02-26 15:11:33 Using at most 125 connections (2048 file descriptors available) 2016-02-26 15:11:33 Using 2 threads for script verification 2016-02-26 15:11:33 Using wallet wallet.dat 2016-02-26 15:11:33 init message: Verifying wallet... 2016-02-26 15:11:33 CDBEnv::Open: LogDir=[editted out] ErrorFile=[editted out] 2016-02-26 15:11:37
2016-02-26 15:11:37 Bitcoin version v0.12.0 (2016-02-17 09:40:03 +0100) 2016-02-26 15:11:37 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2016-02-26 15:11:38 GUI: registerShutdownBlockReason: GetProcAddress for ShutdownBlockReasonCreate failed 2016-02-26 15:11:39 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2016-02-26 15:11:39 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2016-02-26 15:11:39 Default data directory [editted out] 2016-02-26 15:11:39 Using data directory [editted out] 2016-02-26 15:11:39 Using config file [editted out] 2016-02-26 15:11:39 Using at most 125 connections (2048 file descriptors available) 2016-02-26 15:11:39 Using 2 threads for script verification 2016-02-26 15:11:39 Using wallet wallet.dat 2016-02-26 15:11:39 init message: Verifying wallet... 2016-02-26 15:11:39 CDBEnv::Open: LogDir=[editted out] ErrorFile=[editted out] 2016-02-26 15:11:39 scheduler thread start 2016-02-26 15:11:39 Error: Couldn't open socket for incoming connections (socket returned error An address incompatible with the requested protocol was used. (10047)) 2016-02-26 15:11:39 Bound to 0.0.0.0:8333 2016-02-26 15:11:39 Cache configuration: 2016-02-26 15:11:39 * Using 2.0MiB for block index database 2016-02-26 15:11:39 * Using 32.5MiB for chain state database 2016-02-26 15:11:39 * Using 65.5MiB for in-memory UTXO set 2016-02-26 15:11:39 init message: Loading block index... 2016-02-26 15:11:39 Opening LevelDB in [editted out] 2016-02-26 15:11:39 Opened LevelDB successfully 2016-02-26 15:11:39 Using obfuscation key for [editted out]: 0000000000000000 2016-02-26 15:11:39 Opening LevelDB in [editted out] 2016-02-26 15:11:39 Opened LevelDB successfully 2016-02-26 15:11:39 Using obfuscation key for [editted out]: 72046a1e7622fad5 2016-02-26 15:11:48 LoadBlockIndexDB: last block file = 197 2016-02-26 15:11:48 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=365, size=131274522, heights=330521...330993, time=2014-11-18...2014-11-21) 2016-02-26 15:11:48 Checking all blk files are present... 2016-02-26 15:11:48 LoadBlockIndexDB: transaction index disabled 2016-02-26 15:11:48 LoadBlockIndexDB: hashBestChain=00000000000000001639f0ef7eb082b57e48f33baeb9082a7ab07ef3ef7df130 height=330922 date=2014-11-21 00:37:07 progress=0.450085 2016-02-26 15:11:48 init message: Verifying blocks... 2016-02-26 15:11:48 Verifying last 288 blocks at level 3 2016-02-26 15:12:05 No coin database inconsistencies in last 36 blocks (26535 transactions) 2016-02-26 15:12:05 block index 25562ms 2016-02-26 15:12:05 init message: Loading wallet... 2016-02-26 15:12:05 nFileVersion = 120000 2016-02-26 15:12:05 Keys: 0 plaintext, 265 encrypted, 265 w/ metadata, 265 total 2016-02-26 15:12:05 wallet 203ms 2016-02-26 15:12:05 init message: Activating best chain... 2016-02-26 15:12:06 UpdateTip: new best=000000000000000012e7c144fc1c1038c2e7826033b8c9739e5e690b8bf40b91 height=330923 log2_work=81.519843 tx=51953838 date=2014-11-21 00:49:03 progress=0.450095 cache=0.4MiB(1228tx) 2016-02-26 15:12:08 UpdateTip: new best=00000000000000001acb1484131a0b69c7666e1a9b94e483babae59adf1fe160 height=330924 log2_work=81.519915 tx=51954895 date=2014-11-21 01:02:32 progress=0.450111 cache=15.2MiB(4216tx) 2016-02-26 15:12:11 UpdateTip: new best=000000000000000005357156756d6576017e084a6ad8505fd2721feb79773b6c height=330925 log2_work=81.519987 tx=51956910 date=2014-11-21 01:56:55 progress=0.450153 cache=17.7MiB(8185tx) 2016-02-26 15:12:13 UpdateTip: new best=00000000000000001062194213863dab2ef62cb1f7715329927c6d24dc0dc0fd height=330926 log2_work=81.520059 tx=51957644 date=2014-11-21 01:57:29 progress=0.450161 cache=21.0MiB(9680tx) 2016-02-26 15:12:15 UpdateTip: new best=00000000000000000a99e0837981a3ffb45b20b14a4f30e6be51eb014a69a850 height=330927 log2_work=81.520131 tx=51959086 date=2014-11-21 02:14:09 progress=0.450183 cache=22.4MiB(11784tx) 2016-02-26 15:12:17 UpdateTip: new best=0000000000000000178e4ae780a4e48f28c1cf6e061167b92e3ee1f75e166a37 height=330928 log2_work=81.520203 tx=51960689 date=2014-11-21 02:40:51 progress=0.450211 cache=25.6MiB(14222tx) 2016-02-26 15:12:17 mapBlockIndex.size() = 400090 2016-02-26 15:12:17 nBestHeight = 330928 2016-02-26 15:12:17 setKeyPool.size() = 98 2016-02-26 15:12:17 mapWallet.size() = 307 2016-02-26 15:12:17 mapAddressBook.size() = 64 2016-02-26 15:12:17 torcontrol thread start 2016-02-26 15:12:53 I give 0.12 a fail stamp, sorry.
|
|
|
Excuse the noob question, but does the S5 controller need to be extracted from a S5, or does it have "extra" hook ups so you can tie into an already mining S5 with your pod?
I would buy one for <$100, put me on the interested list.
|
|
|
Having issues with my 0.12 node It shut itself down during the night, just booted it up now and it says the block database is corrupted... It's checking blocks now, let's see how this goes. Wierd that this happened after updating and not right away, still trying to figure out what's happening. Happened to me too just yesterday. Core crashed and I booted it back up and had a corrupted database, so I told it to rebuild and it crashed again. Then it wouldn't get past the loading screen without crashing, so I deleted everything in my \Bitcoin\ directory and reinstalled Core 0.12 and the same thing kept happening, crash at the loading screen. I tried installing my \Bitcoin\ directory on another physical drive and still same thing happened. After deleting and reinstalling about 5 times it finally booted up and started syncing again. I think this is my computer telling me it's too old for this sh.t any more.
|
|
|
Nice solar back yard array, I love it! Do you use it for growing primarily? Do you get any other mining or home use out of it? CB radio, ham radio, same thing.
Uh, no, they're completely different frequency bands.
|
|
|
I can't wait any longer, I peeked into a crystal ball and it showed my some magic lines. The lines all converged at:
-2.5% = Mikestang
|
|
|
I looked up the old thread from the guy who made 3D print models for fan ducts and upper/lower case covers for the S5. I downloaded his files and will probably, at the very least, have the top and bottom plates printed up (about $40-$50 total). Makes a lot of sense to me to confine the airflow to the inside of the unit rather than letting it escape out the top and bottom. I'm not sold on his fan ducts, though, mostly because all the printing places I've looked at want $60-$80 just for printing that one part! There's also a guy selling acrylic side panels and includes a bottom panel on ebay, definitely less expensive than ordering the custom 3D printed parts, but probably not as effective.
|
|
|
I have always used Bitcoin core for my wallet.
I have always sent transactions using core's recommended tx fee (whatever it may be when I sent the tx).
I have never once experienced a delayed transaction.
Am I just lucky?
|
|
|
Any particular reason you are using 2 different fans? Which one is push and which one is pull? I tend to lean more to the overclock side of the fence than underclock, but I'll see how this unit is when it arrives and I may UC a little if I have to. I OC'd my S3+ a little, and OC'd my S1 when I used it.
|
|
|
So I just picked up an S5 to run in hot southern California and have a few fan questions to tag onto this thread: Did you use that fan on your S5, Phil? Did you run it as push only, or push/pull? How did it perform? push and pull system with a couple of scythe fans and you'll be fine, I run mine in my office in an apartment and it isn't too noticeable, i am getting 32db if I remember correctly.
Do you have links for the fans you used? 32db sounds too good to be true, I would like to hear more about your fans and the operating temps you saw.
|
|
|
I've ordered a single G839 Noctua NF-F12 Industrial PPC 3000RPM PWM 120mm High Performance Fan to try.
Do you still run your S5? Does it still use this fan? How did it perform? I just picked up an S5 and will be looking to replace the fan with something a bit quieter.
|
|
|
I finally decided to upgrade my S3+ to an S5 because I found one used for about what I paid for my S3+ used. I only run 1 machine at home due to electricity costs, and new hardware is just too expensive for me to justify buying for a hobby.
Question: I've scanned through several threads but cannot find a simple, definitive answer to "the best" fan(s) to use. I want it to be quieter than the 70db stock fan, but I want it to stay cool, too (about 25*C ambient). Could anyone recommend me a fan or push/pull fan combo to use? Thanks.
|
|
|
What would setting S3+ difficulty look like with just an address? do I add it to worker or password? I'm sorry if it has been posted before I did make an effort to look for it, but there's so much to read through.
Go to https://www.kano.is, all the directions are right there, easy to read and follow what to do. To mine your S3+ to just and address, use the following in the miner config page: stratum+tcp://stratum.kano.is:3333 {your BTC address here}_{any worker name here} x You cannot configure difficulty if you only mine to an address and really there is no need, especially with just an S3+, the pool will adjust it for you.
|
|
|
|