We are upgrading the server, will be down for a little bit...
Need more HD space
Edit: back up and running...
Need more HD space
Edit: back up and running...
noticed that. thx for the fast update
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 167. (Read 2591920 times)
July 05, 2015, 01:56:21 PM
noticed that. thx for the fast update
July 05, 2015, 12:57:37 PM
We are upgrading the server, will be down for a little bit...
Need more HD space
Edit: back up and running...
Need more HD space
Edit: back up and running...
July 04, 2015, 05:27:01 PM
When you refer to "Assemble a new BTC block with the MM information in the coinbase and push it out." - how does one do that with p2pool? Or is it even possible?
Can't help on this one unfortunately, I've never used p2pool so I don't have any idea how it assembles work, same with merged mining via p2pool. Different drives for the coins is definitely one good way to split the load when new blocks hit though.
Does anyone know if it's possible to do what eleuthria suggests above with p2pool?
July 04, 2015, 05:24:27 PM
When you refer to "Assemble a new BTC block with the MM information in the coinbase and push it out." - how does one do that with p2pool? Or is it even possible?
Can't help on this one unfortunately, I've never used p2pool so I don't have any idea how it assembles work, same with merged mining via p2pool. Different drives for the coins is definitely one good way to split the load when new blocks hit though.
Does anyone know if it's possible to do what eleuthria suggests above with p2pool?
July 04, 2015, 03:19:53 PM
It actually had nothing to do with failure to upgrade or not.
They (as well as F2Pool) were/are not checking that blocks are valid before they mine on top of them.
The repercussions are that they will extend invalid blockchains, deceiving SPV nodes with false confirmations and losing the mined bitcoins.
I figured they would eventually lose those bitcoin"s I was wondering if there users are going to be the end or will the problem go further than that? As far as extending invalid block chains will that do anything more that use up space?
They (as well as F2Pool) were/are not checking that blocks are valid before they mine on top of them.
The repercussions are that they will extend invalid blockchains, deceiving SPV nodes with false confirmations and losing the mined bitcoins.
I figured they would eventually lose those bitcoin"s I was wondering if there users are going to be the end or will the problem go further than that? As far as extending invalid block chains will that do anything more that use up space?
July 04, 2015, 02:52:02 PM
Well, compared to certain other pools, our change over went very smoothly I think......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
Bitmain got caught with their pants down on Antpool it seems. They neglected to upgrade. Maybe now their users will realize Antpool isn't close to what Bitmain advertises it to be?
M
What are the repercussions for them failing to upgrade properly?
They (as well as F2Pool) were/are not checking that blocks are valid before they mine on top of them.
The repercussions are that they will extend invalid blockchains, deceiving SPV nodes with false confirmations and losing the mined bitcoins.
July 04, 2015, 02:49:36 PM
Well, compared to certain other pools, our change over went very smoothly I think......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
Bitmain got caught with their pants down on Antpool it seems. They neglected to upgrade. Maybe now their users will realize Antpool isn't close to what Bitmain advertises it to be?
M
What are the repercussions for them failing to upgrade properly?
July 04, 2015, 10:44:06 AM
I just saw a V2 block rejected in my home bitcoind log ... so it would seem the V3 switch over has happened.
I posted this comment coz I thought it was clearly of interest to p2pool and the late change over, to know when V3 happened.Antpool explanation:
https://bitcointalksearch.org/topic/m.11789555
July 04, 2015, 08:11:45 AM
Well, compared to certain other pools, our change over went very smoothly I think......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
Bitmain got caught with their pants down on Antpool it seems. They neglected to upgrade. Maybe now their users will realize Antpool isn't close to what Bitmain advertises it to be?
M
Yeah, I saw that too - but I'm not at all surprised either, if their history is anything to go by. I'm sure it won't be the last time either......
July 04, 2015, 08:07:18 AM
Well, compared to certain other pools, our change over went very smoothly I think......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
Bitmain got caught with their pants down on Antpool it seems. They neglected to upgrade. Maybe now their users will realize Antpool isn't close to what Bitmain advertises it to be?
M
July 04, 2015, 07:45:34 AM
Well, compared to certain other pools, our change over went very smoothly I think......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
Just waiting for a glut of complaints from those who didn't upgrade yet.......
July 04, 2015, 02:52:27 AM
Was this the first P2Pool version 3 block found?
https://blockchain.info/block/000000000000000015358ae1131062fa83081797bb4cec4df0b1e5a5d01c1936
Nice!
https://blockchain.info/block/000000000000000015358ae1131062fa83081797bb4cec4df0b1e5a5d01c1936
Nice!
July 03, 2015, 11:58:33 PM
We are now exclusively switched to v14.0. All v13 miners have been excluded following BIP66 taking effect.
The fact that we came so close to 95% in a less than a week speaks volumes...
Thank you Forrest for your work!
July 03, 2015, 11:56:48 PM
We are now exclusively switched to v14.0. All v13 miners have been excluded following BIP66 taking effect.
July 03, 2015, 09:17:39 PM
I just saw a V2 block rejected in my home bitcoind log ... so it would seem the V3 switch over has happened.
Quote
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
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.
July 03, 2015, 09:06:31 PM
I just saw a V2 block rejected in my home bitcoind log ... so it would seem the V3 switch over has happened.
July 03, 2015, 05:06:38 PM
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
I got cryptoglance working with it now though - had the wrong setting, I did
July 03, 2015, 04:23:45 PM
Hiya JB,
Regarding kanos latest firmware:
....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 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.
. 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
July 03, 2015, 04:19:33 PM
Hiya JB,
Regarding kanos latest firmware:
....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 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.
. 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
July 03, 2015, 04:00:24 PM
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://bitcointalksearch.org/topic/m.11783543 Jump to: