windpath
Legendary
 Offline
Activity: 1258
Merit: 1027
|
 |
July 04, 2015, 04:58:33 AM |
|
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! |
|
|
|
|
|
|
|
|
|
|
|
|
|
Even if you use Bitcoin through Tor, the way transactions are handled by the network makes anonymity difficult to achieve. Do not expect your transactions to be anonymous unless you really know what you're doing.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
p3yot33at3r
|
|
July 04, 2015, 12:45:34 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.......  |
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
July 04, 2015, 01:07:18 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....... 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 |
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me! |
|
|
|
p3yot33at3r
|
|
July 04, 2015, 01:11:45 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....... 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......  |
|
|
|
|
kano
Legendary
Offline
Activity: 4494
Merit: 1808
Linux since 1997 RedHat 4
|
|
July 04, 2015, 03:44:06 PM |
|
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://bitcointalk.org/index.php?topic=1088425.msg11789555#msg11789555 |
|
|
|
|
luthermarcus
|
|
July 04, 2015, 07: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....... 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? |
Donate Bitcoin
1Mz7ZHxPhoH1ZK2yQvo62NdHvvsS2quhzc
Donate TRX
TB3WiLEj6iuSBU5tGUKyZkjB4vqrBDvoYM
|
|
|
Luke-Jr
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
July 04, 2015, 07: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....... 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? 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. |
|
|
|
|
luthermarcus
|
|
July 04, 2015, 08: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?
|
Donate Bitcoin
1Mz7ZHxPhoH1ZK2yQvo62NdHvvsS2quhzc
Donate TRX
TB3WiLEj6iuSBU5tGUKyZkjB4vqrBDvoYM
|
|
|
|
p3yot33at3r
|
|
July 04, 2015, 10: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?  |
|
|
|
|
Luke-Jr
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
July 04, 2015, 10: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? Uh, sure. Just get N hard drives, and put each altcoin on a dedicated one... |
|
|
|
windpath
Legendary
Offline
Activity: 1258
Merit: 1027
|
|
July 05, 2015, 05:57:37 PM
Last edit: July 05, 2015, 06:43:34 PM by windpath |
|
We are upgrading the server, will be down for a little bit... Need more HD space Edit: back up and running... |
|
|
|
|
yslyung
Legendary
Offline
Activity: 1500
Merit: 1002
Mine Mine Mine
|
|
July 05, 2015, 06:56:21 PM |
|
We are upgrading the server, will be down for a little bit... Need more HD space Edit: back up and running... noticed that. thx for the fast update |
|
|
|
|
|
Duce
|
|
July 05, 2015, 10:33:14 PM |
|
Does anybody know what is going on with P2P today with the high latency? It is causing my bitcoind to drop connectivity and my SP's to drop as well (the S5 seems to drop as well looking at my node). It has been up/down for the last six hours. I looked at other pools and some seem to have the same problem as well. I am running the current 13.4-83-gb07b1e3 P2P version and 0.10.1 core.
|
|
|
|
|
|
p3yot33at3r
|
|
July 05, 2015, 10:36:36 PM |
|
I am running the current 13.4-83-gb07b1e3 P2P version and 0.10.1 core.
Current is v14 & 0.10.2 |
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1023
Mine at Jonny's Pool
|
|
July 05, 2015, 10:37:16 PM |
|
Does anybody know what is going on with P2P today with the high latency? It is causing my bitcoind to drop connectivity and my SP's to drop as well (the S5 seems to drop as well looking at my node). It has been up/down for the last six hours. I looked at other pools and some seem to have the same problem as well. I am running the current 13.4-83-gb07b1e3 P2P version and 0.10.1 core.
That's your problem right there. Try joining us on version 14.0... you're mining invalid work. |
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
|
jedimstr
|
|
July 05, 2015, 10:51:57 PM |
|
Does anybody know what is going on with P2P today with the high latency? It is causing my bitcoind to drop connectivity and my SP's to drop as well (the S5 seems to drop as well looking at my node). It has been up/down for the last six hours. I looked at other pools and some seem to have the same problem as well. I am running the current 13.4-83-gb07b1e3 P2P version and 0.10.1 core.
Well... First, you may want to get OFF 13.4-83-gb07b1e3 which is on the wrong side of a hardfork. Please see the first post in the thread (and the last few days worth of posts) and upgrade to 14.0 or you wont get any payout the next time we find a block since any version lower than 14 has been cut off. |
|
|
|
|
Duce
|
|
July 05, 2015, 11:09:18 PM |
|
That was the last pull from GitHub. Heck I thought I was up to speed great.
So I can't just perform a pull but need to delete this version and start with the new one I see.
|
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
July 05, 2015, 11:15:11 PM |
|
I just checked my node, as it was showing down. It looks like it's hyper trying to retrieve shares from multiple places: 2015-07-05 19:06:16.252636 Requesting parent share 66033bd7 from 74.82.233.205:9333
2015-07-05 19:06:17.357663 Requesting parent share 66033bd7 from 149.210.228.165:9333
2015-07-05 19:06:18.809206 Requesting parent share 66033bd7 from 80.60.85.169:9333
2015-07-05 19:06:19.088368 Requesting parent share 37dddcee from 74.82.233.205:9333
Notice it requested the same parent share from four nodes within 4 seconds. That's not very efficient, and I assume that's why it's having a hard time keeping up with the shares. It's doing this regularly. M |
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me! |
|
|
|
p3yot33at3r
|
|
July 05, 2015, 11:20:26 PM |
|
I just checked my node, as it was showing down. It looks like it's hyper trying to retrieve shares from multiple places: 2015-07-05 19:06:16.252636 Requesting parent share 66033bd7 from 74.82.233.205:9333
2015-07-05 19:06:17.357663 Requesting parent share 66033bd7 from 149.210.228.165:9333
2015-07-05 19:06:18.809206 Requesting parent share 66033bd7 from 80.60.85.169:9333
2015-07-05 19:06:19.088368 Requesting parent share 37dddcee from 74.82.233.205:9333
Notice it requested the same parent share from four nodes within 4 seconds. That's not very efficient, and I assume that's why it's having a hard time keeping up with the shares. It's doing this regularly. M I've been seeing this the last few days too, but put it down to the forking & old nodes still not being updated - but maybe it's something else.....? |
|
|
|
|
|
