Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 79. (Read 1514767 times)

You're right, thanks for pointing it out.

Is it 249 or 250 blocks solved now?

Restart complete; mine on!

Damn thats one hell of a share   divide that by 3 and still able to hit 3 blocks out of it LOL

https://btc.com/00000000000000000001b7eb66dd7092971dae0688e099503d381377f7e8f622

I mean since we can turn lead into gold nowadays that seems reasonably plausible.

Because the BM1385 and the BM1580 are the same chip and they just overclocked the balls out of 29 less chips (that they manually ripped off the boards with ViceGrips) in the V9 to get the same results as an S7, right?  

V9 not s9

Dude, everyone knows they are just really overclocked s5's!! 

In all of the usual anti-Bitmain FUD places 

And just *where* is this 'everyone' to be found?
The s7 and s9/T9/V9 use entirely different chips.

anyone know if i can put the s7 firmware into a v9? since everyone is claiming they a refurb. s7's anyways

WOW only 33% reject rate! trade ya

Pool   URL   User   Status   Diff   GetWorks   Priority   Accepted   Nonce#   DiffA#   DiffR#   DiffS#   Rejected   Discarded   Stale   LSDiff   LSTime
0   stratum+tcp://solo.ckpool.org:443   12k3f1gNV2#########th2TSnCtcLL9K6c   Alive   4K   201   0   2,489   0   9,956,000   9,372,000   0   2,343   2,611   0   4,000   0:00:05

Ok, so I will just ignore the rejected ones.
Thank you for the information!

The shitmain drivers are broken. They forked their driver off an ancient version of cgminer. My guess is they are confusing other messages from the pool as being rejected shares - if you can read the console output it will probably say something like rejected untracked share when it fact it's a ping from the pool. If your accepted share rate is fine then you can basically ignore the rejected shares.

For someone more adept than me and may mean nothing but why the warnings?

Last lines of the Kernel Log

Jun 15 23:24:11 (none) local0.notice cgminer[28431]: every_chain_restore_PIC16F1704_voltage_new
Jun 15 23:24:11 (none) local0.err cgminer[28431]: cgminer time error total_secs = 1529105051.660402 last_total_secs = 1.000000
Jun 15 23:24:12 (none) local0.warn cgminer[28431]: Pool 0 stratum+tcp://pool.ckpool.org:3333 alive, testing stability
Jun 15 23:24:12 (none) local0.warn cgminer[28431]: Switching to pool 0 stratum+tcp://pool.ckpool.org:3333
Jun 15 23:24:17 (none) local0.warn cgminer[28431]: API running in IP access mode on port 4028 (7)
Jun 15 23:24:32 (none) local0.notice cgminer[28431]: set_PIC16F1704_voltage_new ok, voltage = 0x80
Jun 15 23:24:32 (none) local0.notice cgminer[28431]: every_chain_restore_PIC16F1704_voltage_new Chain 0 voltage 128
Jun 15 23:24:33 (none) local0.notice cgminer[28431]: set_PIC16F1704_voltage_new ok, voltage = 0x80
Jun 15 23:24:33 (none) local0.notice cgminer[28431]: every_chain_restore_PIC16F1704_voltage_new Chain 1 voltage 128
Jun 15 23:24:33 (none) local0.notice cgminer[28431]: set_PIC16F1704_voltage_new ok, voltage = 0x80
Jun 15 23:24:33 (none) local0.notice cgminer[28431]: every_chain_restore_PIC16F1704_voltage_new Chain 2 voltage 128

Delete post if no value

My V9 does exactly the same 

CKpool & CKSolo with the same results with a lot of rejected shares, about 33% to be exact, and no Best Share shown

Stats on the CK pools show that I'm producing however

Other pools can have next to no rejected shares, but still no Best Share

My miner in in the garage connected to an Amped wireless extender but I tried it indoors directly connected yo the router with the same results

I'm assuming the V9 has some quirks esp. at the price point

The V9 also came with the latest firmware from the factory

I'll stick with the CK pools however 

If I check the Best Share on solo.ckpool.org, everything seems normal.

{
 "hashrate1m": "4.07T",
 "hashrate5m": "3.93T",
 "hashrate1hr": "2.58T",
 "hashrate1d": "3.26T",
 "hashrate7d": "1.33T",
 "lastshare": 1529162379,
 "workers": 1,
 "shares": 384240083,
 "bestshare": 3735381569.939564,
 "bestever": 3735381569,
 "worker": [
  {
   "workername": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
   "hashrate1m": "4.07T",
   "hashrate5m": "3.93T",
   "hashrate1hr": "2.58T",
   "hashrate1d": "3.26T",
   "hashrate7d": "1.33T",
   "lastshare": 1529162379,
   "shares": 384240083,
   "bestshare": 3735381569.939564,
   "bestever": 3735381569
  }
 ]
}

I can't even fathom how you have 900+ accepted shares in an hr and a best share of 0, so I'm thinking your miner is wonkey.

Hi all,

I have pointed my miner to solo.ckpool.org respectively de.ckpool.org.

But as you can see in the screenhot the rejected value is extreme high:
https://ibb.co/e4yxvJ

If I point my miner to viaBTC (also in solo mode) the rejected value is zero:
https://ibb.co/mFJahy

Is this normal on ckpool.org or is there something I can do about it?

Thank you in advance!