So about $11 in import tax and $125 in handling fee?  If so, I'll stop using DHL...

DHL showed up today, the 4th of July, with my 2 power supplies, and confirmed my B5 S9s were sitting in the warehouse (well, at least one of them the carrier actually laid eyes on) awaiting import duty payment.

I've been reading this and other threads and apparently duty varies from $10 to $50ish per unit, I had to pay $138 for two units in Missouri - which seems excessive.

Reading that thread next.  Thanks for the information. 

Wish I could have paid the man, but DHL doesn't let them load the packages on the truck until payment has been made.

How about we go with "Random Government taxation"?

Will do, but see no vector that would allow that to change, or that would make it vary by carrier???

Anyone know if import duties vary by US State?

Thanks.... I just paid almost $70 each.

Well... much to my surprise, DHL showed up with the two power supplies (surprised because today is a national holiday in the US and they were not suppose to be working, but apparently the staff is trying to get residential things out - brownie points for them!)

The driver confirmed he found a 3rd package and that when he tried to clear it for delivery was told there was a tax due ($138).  Apparently the text was legit, and I have a receipt for payment of the tax addressed to me and duty_payments@dhl.com.

Hopefully I'll get the actual units tomorrow.

First time for everything I suppose.  I do recall reading somewhere that packages under $2500 were tax free (not worth the processing cost I guess), but of course, (2) S9s is closer to $4000.

I didn't pay anything on my Batch 1 unit, although I only bought one then, and this is two units.

Excuse me for asking basic questions:  But are you USA based, how much was the duty per unit, and were you asked to pay through a Canadian site (dhlmypayument.us which routes to mypayment.dhl.ca)?  I'm particularly concerned that a US Import duty would be paid through a Canadian site...

My B45 order of S9s has hit the United States.  I've been buying miners from Bitmain since the S3, and this is the first time I've had DHL tell me I owe import taxes. Apparently the message is coming DHL Canada, perhaps because its the 4th of July Holiday here in the USA?   I tried calling Customer Support, which is suppose to be open, but got routed to an old DHL Canadian telephone that told me to update my phone records and call 1-855-DHL-SHIP - very strange.

Anybody else having problems today?

Is it normal to have to pay an import duty, or is this likely some type of screwup because DHL Canada appears to be dealing with things today (and Canadians always pay an import duty).

My B45 order of S9s has hit the United States.  I've been buying miners from Bitmain since the S3, and this is the first time I've had DHL tell me I owe import taxes. Apparently the message is coming DHL Canada, perhaps because its the 4th of July Holiday here in the USA?   I tried calling Customer Support, which is suppose to be open, but got routed to an old DHL Canadian telephone that told me to update my phone records and call 1-855-DHL-SHIP - very strange.

Anybody else having problems today?

Well... ideally you should have tcp port 6666 forwarded from your firewall to the machine running the coin daemon.  Doing that, along with the "listen=1" in your configuration file, will make your machine a full node in the network.

I'd also suggest you remove your peers.dat file in the folder with your configuration file.  Peers.dat is the list of all machines your daemon has ever tried to connect to, which it then filters and then randomly tries to connect to (you will see all the attempts in your debug.log if you look in there).  Removing it will cause you to connect to the dnsseeds, and they will communicate who they are connected to.

If your willing, try that.

There appears to be on Trojan node out there at 85.236.188.28, since its running protocol version 80007 of the code, which is about 10,000 versions higher than production.  That is likely causing problems.  I've seen this happen with other coins and can add some code to check for it.

Please make sure your at least connected to the two of the three seeds:  66.128.118.35, 66.128.118.38, and 216.146.251.13.  I will share that .35 currently has 15 connections.

Sad world where people try and scam coins like this.

Update:  Testing the protocol patched version on .35 and had 6 connections in seconds, 11 connections in under a minute.  HIGHLY recommend you run the linux based code if you can.  My linux clients almost always have more connections than Windows version.  Not sure why.

Update 2:  New source pushed to github.  Will try and get a Windows executable built tomorrow.

Coin is running as designed.  Not going to change it just to change it.

Yep.  Just switched and loaded the app this afternoon.  Not quite sure what the bar color code is suppose to mean between my 3 workers, since all three are colored the same.

Thanks.  Alas my S9 unit was shipped with the June 8th firmware, and I'm seeing the same issue on my S7s.  I've asked for help on the #ckpool IRC channel, but so far, no response.

To the previous responder:  I actually do know how to spell my username, and the image shows that as being consistent with my usage on Slush.  As mentioned, the website accepts that spelling as me.

Love to try CKPool, but unable to connect for some reason.  Any suggestions?

Can we have a non-emotional, fact based, discussion about that?  I am open to switching.

Slush is running around 62PH, it has a 2% fee and using a scoring system that seems fair (rewards consistent participation).  Transaction fees are shared.

CKPool is running around 36PH, has a 0.9% fee and uses PPLNSG payouts.  Transaction fees are also shared.

Seems to me, for someone that is running for months, PPLNSG and Slushes scoring system are similar in effect, both avoid block hoppers (are those still a problem?).

Variance based on pool size is not a big deal for either:  both are large enough that a daily payout is reasonable (my personal threshold).

Seems Slush wouldn't make for a very good backup pool, since short term access results in a lower score.  Seems to me that CKPool may be ok for that, although the payouts would be delayed by a day or so.

Bottom line, the fees are the major difference?

BTW - I have CKPool as one of my backup pools as of last night, but all three of my miners are showing the pool as dead.  I'm using a named account.  The doc indicates the worker name will be auto-generated upon first contact, yet I'll never have a first contact if the pool doesn't show up as alive...

Sound report:  Doing the Lowes filter trick raised my temps about 10%.  Removing the fan guard lowered my temps 1-2C and made the unit rather quiet (at least relative to S7s or S4s).

Tried removing the fan guards from the S7s and had very little impact.  Placing a Lowe's filter across the intakes worked great though.  Since I have 2, side by side, I just used one filter and suction is holding it in place.  Temps are up a bit but very inconstant now, varying from 53 to 63 between the 6 boards.  Still that is in line with the S9 temps, so I suspect I'm fine.

Almost at 2 hours now, web page indicateds 13,544.19 GH/S(RT) and 13,6954.32(avg) - just added the "Lowes sound mod" and noticing the temps go up a few degrees - now at 65-67C.

Of interest, Slushpool is crediting my S9 with 14.53TH/s over the past hour:



My units are in a basement "machine room", so thinking of removing the grills to see if that helps.  On my S7s, I found partially blocking the intake worked, but raised temps.  Using a block of 2x3 lumber BEHIND the unit brought the sound under control.  May play a bit more before disabling the safety grills.

Just to add a data point, my S9 B1 arrived today.  Had it up and running in perhaps 20 minutes (and headed to Lowes soon for filter and duct tape!)



It is running about 10C at the PCB level than my S7s, presuming the S7 firmware's temp is a PCB temp.  However they are also higher in the rack, so may have higher temp input air.

I'm seeing a few (like 3 in 30 minutes) hardware errors, and about 97% of the advertised 14TH, so well within the +/-5%.

Cassey

ps:  Mine apparently came with the June 8th firmware I see on the site: