[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[yslyung]

yeah i see that too

2015-07-03 00:50:49.745000  Pool: 2163TH/s Stale rate: 14.9% Expected time to block: 1.1 days
2015-07-03 00:50:50.927000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:50.927000
2015-07-03 00:50:50.958000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:50.958000
2015-07-03 00:50:50.983000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:50.984000
2015-07-03 00:50:51.018000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:51.018000
2015-07-03 00:50:51.042000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:51.042000
2015-07-03 00:50:51.066000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:51.066000
2015-07-03 00:50:51.096000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:51.096000
2015-07-03 00:50:52.763000 P2Pool: 17357 shares in chain (17361 verified/17361 total) Peers: 10 (0 incoming)


still got the blanks.

[1714102256]

1714102256

[1714102256]

1714102256

[luthermarcus]

still got the blanks.
[/quote]

I just upgraded and I don't see any off the blanks you guys are getting.

[jtoomim]

Has BIP66 taken effect yet?

[forrestv]

Has BIP66 taken effect yet?

No, not yet. You can watch http://bitcoin.sipa.be/ver-2k.png for the red line crossing 2.95 or run:

Code:

alias b=~/repos/bitcoin/src/bitcoin-cli
((for i in $(seq $(($(b getblockcount)-1000)) $(b getblockcount)) ; do b getblock `b getblockhash $i` | egrep '(\"hash\")|(ver)' | tr '\n' ' ' ; echo ; done ) ) | grep ': 3,'  | wc -l

which will return 950 or higher when BIP66 takes effect.

[p3yot33at3r]

I just upgraded and I don't see any off the blanks you guys are getting.

Are you sure? I still got the blanks too - I think everyone has........

Edit: Oh, hello forrestv - any news on this blank thing? 

[forrestv]

Are you sure? I still got the blanks too - I think everyone has........

Edit: Oh, hello forrestv - any news on this blank thing? 

I think the commit I just pushed should remove them.

Also, we're at 94.7% converted (averaged over the last hour)! Looks like someone big upgraded recently.

[p3yot33at3r]

Are you sure? I still got the blanks too - I think everyone has........

Edit: Oh, hello forrestv - any news on this blank thing? 

I think the commit I just pushed should remove them.

Also, we're at 94.7% converted (averaged over the last hour)! Looks like someone big upgraded recently.

Cool. I'm not sure what info was being missed in the blanks (maybe it was merge mining info - can't remember tbh), but is it possible to show what actual coin block was found/submitted instead of the general "merge mined work"? ie NMC, I0C or whatever?

[yslyung]

Are you sure? I still got the blanks too - I think everyone has........

Edit: Oh, hello forrestv - any news on this blank thing? 

I think the commit I just pushed should remove them.

Also, we're at 94.7% converted (averaged over the last hour)! Looks like someone big upgraded recently.

Cool. I'm not sure what info was being missed in the blanks (maybe it was merge mining info - can't remember tbh), but is it possible to show what actual coin block was found/submitted instead of the general "merge mined work"? ie NMC, I0C or whatever?

it is 

New work for worker! Difficulty: 500.000000 Share difficulty: 5696067.651468 Total block value: 25.026283 BTC including 62 transactions

for other workers, some show some don't.

[windpath]

...
Also, we're at 94.7% converted (averaged over the last hour)! Looks like someone big upgraded recently.

This is great news!

[jonnybravo0311]

Are you sure? I still got the blanks too - I think everyone has........

Edit: Oh, hello forrestv - any news on this blank thing? 

I think the commit I just pushed should remove them.

Also, we're at 94.7% converted (averaged over the last hour)! Looks like someone big upgraded recently.

I upgraded to the latest commit and no longer see the blank spaces.  Forrestv, thanks for the work you've done, both in creating p2pool in the first place and the recent updates to ensure we don't get left behind when BIP66 goes into effect.

I have sent a small donation to the BTC address you have listed in the README.md in the github repo of p2pool.  It isn't much, but it does reflect 1% of the total I've mined on p2pool since I started here early last year.  The TxID is: 237b9a5b1f444274bb8320e1eee04179dd6b4446ddd2e2948002c8b889c3c31d.  I've also added a 1% donation on my node using the --give-author parameter.

Thanks again for your work.

[p3yot33at3r]

Hiya JB,

Regarding kanos latest firmware:

I upgraded my S3s to use this.

....did you manage to get the hash rate stats up on mmonitor/cryptoglance by any chance? If so, what flags are you using?

Thanks.

[jonnybravo0311]

Hiya JB,

Regarding kanos latest firmware:

I upgraded my S3s to use this.

....did you manage to get the hash rate stats up on mmonitor/cryptoglance by any chance? If so, what flags are you using?

Thanks.

Since you asked in both threads... figured I'd reply to you in both .  No, I don't use any monitoring software applications.  You might want to give mdude77 a shout out to see if he's planning to update his app to support the standard APIs (that kano uses with his updated stuff) in addition to the Bitmain ones.  Not sure how much effort it would be on his part, but it's worth asking.  Of course, this is assuming you're using his monitoring app .  If not, check out the threads for those apps and ask the developers.

[p3yot33at3r]

Yeah, posted it in kanos thread by mistake - deleted it as soon as I realized  

[jonnybravo0311]

Yeah, posted it in kanos thread by mistake - deleted it as soon as I realized  

Appears somebody got crypto glance working with kano's patch for the S3.  Check out the post in kano's pool thread here: https://bitcointalk.org/index.php?topic=789369.msg11783543#msg11783543

[mdude77]

Hiya JB,

Regarding kanos latest firmware:

I upgraded my S3s to use this.

....did you manage to get the hash rate stats up on mmonitor/cryptoglance by any chance? If so, what flags are you using?

Thanks.

Since you asked in both threads... figured I'd reply to you in both .  No, I don't use any monitoring software applications.  You might want to give mdude77 a shout out to see if he's planning to update his app to support the standard APIs (that kano uses with his updated stuff) in addition to the Bitmain ones.  Not sure how much effort it would be on his part, but it's worth asking.  Of course, this is assuming you're using his monitoring app .  If not, check out the threads for those apps and ask the developers.

I wasn't aware of any outstanding issues with S3s not monitoring properly in my app.

M

[jonnybravo0311]

Hiya JB,

Regarding kanos latest firmware:

I upgraded my S3s to use this.

....did you manage to get the hash rate stats up on mmonitor/cryptoglance by any chance? If so, what flags are you using?

Thanks.

Since you asked in both threads... figured I'd reply to you in both .  No, I don't use any monitoring software applications.  You might want to give mdude77 a shout out to see if he's planning to update his app to support the standard APIs (that kano uses with his updated stuff) in addition to the Bitmain ones.  Not sure how much effort it would be on his part, but it's worth asking.  Of course, this is assuming you're using his monitoring app .  If not, check out the threads for those apps and ask the developers.

I wasn't aware of any outstanding issues with S3s not monitoring properly in my app.

M

Kano's newly released updated S3 software seems to have broken some monitoring tools for some people because it uses standard cgminer APIs and not Bitmain's altered versions of them.  I'm not sure how your app behaves since I don't use any monitoring apps... I was just letting p3yot33at3r know what kano had written in his thread, hoping to steer him in the right direction.

[p3yot33at3r]

Only the hash rate display isn't working, everything else is fine:



I got cryptoglance working with it now though - had the wrong setting, I did 

[kano]

I just saw a V2 block rejected in my home bitcoind log ... so it would seem the V3 switch over has happened.

[CohibAA]

I just saw a V2 block rejected in my home bitcoind log ... so it would seem the V3 switch over has happened.

2015-07-04 02:09:28 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-07-04 02:09:28 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-07-04 02:09:29 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-07-04 02:09:29 ERROR: invalid header received

There it is.

[forrestv]

We are now exclusively switched to v14.0. All v13 miners have been excluded following BIP66 taking effect.