The good news:
I managed to make a stratum proxy that works with p2pool.
The bad news:
It looks to me like the S2s can't respond quick enough to the restarts from p2pool. That causes rejects. If the difficulty is too low, it gets out of hand, where the shares coming from the S2s are from prior jobIDs, as many as two or three back.
I'm watching the data flow through real time, and shares submitted 1-5 seconds after the restart request (with the new jobID) are rejected because the jobID is the wrong one.
Other things of note:
- It'd be useful if p2pool returned some indication as to what was wrong when an item is rejected. I'm going to have to track jobIDs myself to visually indicate if it was rejected because of a bad jobid.
- The "id" in the response from p2pool doesn't match the "id" from the sender. The stratum specs are a bit vague, but it seems to me the response "id" should be the same as the sender id. Instead it seems to be an incremental number for that connection.
More to come.
M
So it works like a charm with walletadress/10000000+1024 ? And without those 30s altcoins.. |
|
|
|
|
Pool Luck(?) (7 days, 30 days, 90 days): 185.7%102.4%98.9%
|
|
|
|
Peer =148.251.238.178:18702 is causing bitcoind to go out of sync, 0 hours behind..... lying about blocks
Is there a way to block these getaddr.bitnodes.io:0.1 clients from bitcoind, or do one have to block ip after ip from firewall?
Not sure but, it seems to cause orphan and dead shares while this happens..0 hours behind....
As far as I know, you can only block them by setting up a whitelist of connections to use, so only setting up connections for specific peers. Use "connect" to establish a list of trusted peers, but then you're only locked to those peers which has its pros and cons. -addnode=<ip> Add a node to connect to and attempt to keep the connection open
-connect=<ip> Connect only to the specified node(s)
-seednode=<ip> Connect to a node to retrieve peer addresses, and disconnect
-externalip=<ip> Specify your own public address
-onlynet=<net> Only connect to nodes in network <net> (IPv4, IPv6 or Tor)
-connect method would be nice if I only knew how to connect to p2pool node, not sure what happens if bitcoind is started up witout connect settings and then p2pool brought up - then change the config to connect=specified hosts and reboot bitcoind. It can be that if a block is found it cant be submitted to bitcoind.. Installed and configured iptables and now it stays synced.. |
|
|
|
|
Peer =148.251.238.178:18702 is causing bitcoind to go out of sync, 0 hours behind..... lying about blocks
Is there a way to block these getaddr.bitnodes.io:0.1 clients from bitcoind, or do one have to block ip after ip from firewall?
Not sure but, it seems to cause orphan and dead shares while this happens..0 hours behind....
|
|
|
|
|
It would be nice to have share info after rebooting p2pool node, someone with the skills could do that. Please.
I think it could be easy, but..
f = open("shares.txt","w")
replaced with
f = open("shares.txt","a")
|
|
|
|
What is TRC? *boggle*
isn't that the short for terracoin? It shouldn't be - this is the BTC Pools board. Oh, sorry for mentioning TRC, I tought this is P2pool board. I guess I was wrong then. |
|
|
|
Payout if a block were found NOW: 12.46588235 TRC to 1PDSDTokUdwEakJMryeuMQt2f3P3gbrC3z. Expected after mining for 24 hours: 21.0 TRC per block. Current block value: 20.0015 TRC Expected time to block: 3.7 hours  expecting to get more than block value is... Payout if a block were found NOW: 12.68139146 TRC to 1PDSDTokUdwEakJMryeuMQt2f3P3gbrC3z. Expected after mining for 24 hours: 23.0 TRC per block. Current block value: 20.0025 TRC Expected time to block: 3.7 hours |
|
|
|
|
I dont have s2, but was thinking if it could help at all to put walletaddress/2000000+1024 or walletaddress+1024 as username. Maybe not.
|
|
|
|
"These are the results of the survey. 68% of all unit holders have cast their vote: - Yes, PetaMine should switch over to P2Pool – 96% - No, PetaMine should stay with ghash.io – 3% - No, Petamine should switch to another pool like Eligius or BTCGuild – 1% The result is clear that a big majority of unit holders prefer a switch to p2pool. As we were performing additional tests the past week, we have to inform you that unfortunately the Bitfury systems are not compatible with p2pool. We are currently working on a solution for this and we will switch to p2pool as soon as we are able to fix this problem." Sharedifficulty rising..  I cant wait to see if Peta makes more coins with p2pool then before... |
|
|
|
|
Reservoir Dogs
Nice Guy Eddie: C'mon, throw in a buck!
Mr. Pink: Uh-uh, I don't tip.
Nice Guy Eddie: You don't tip?
Mr. Pink: Nah, I don't believe in it.
Nice Guy Eddie: You don't believe in tipping?
Mr. Blue: You know what these chicks make? They make shit.
Mr. Pink: Don't give me that. She don't make enough money that she can quit.
Nice Guy Eddie: I don't even know a fucking Jew who'd have the balls to say that. Let me get this straight: you don't ever tip?
Mr. Pink: I don't tip because society says I have to. All right, if someone deserves a tip, if they really put forth an effort, I'll give them something a little something extra. But this tipping automatically, it's for the birds. As far as I'm concerned, they're just doing their job.
Mr. Blue: Hey, our girl was nice.
Mr. Pink: She was okay. She wasn't anything special.
Mr. Blue: What's special? Take you in the back and suck your dick?
Nice Guy Eddie: I'd go over twelve percent for that.
|
|
|
|
|
I think Eligius needs more nodes and an option to user to selecet sharedifficulty..
2014-06-27 12:41:08,720 INFO proxy stratum_listener.submit # [219ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:21,693 INFO proxy client_service.handle_event # New job 1403862024 61319 for prevhash f463930d, clean_jobs=False
2014-06-27 12:41:21,694 INFO proxy stratum_listener.submit # [7196ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:21,694 INFO proxy stratum_listener.submit # [7001ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:21,694 INFO proxy stratum_listener.submit # [6523ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:21,694 INFO proxy stratum_listener.submit # [4105ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:21,695 INFO proxy stratum_listener.submit # [3748ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:21,695 INFO proxy stratum_listener.submit # [3031ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:27,165 INFO proxy stratum_listener.submit # [309ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:31,007 INFO proxy stratum_listener.submit # [272ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:39,130 INFO proxy stratum_listener.submit # [213ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:41,496 INFO proxy stratum_listener.submit # [226ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:43,123 INFO proxy stratum_listener.submit # [295ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 511
2014-06-27 12:41:43,209 INFO proxy client_service.handle_event # Setting new difficulty: 255.99609375
2014-06-27 12:41:58,200 INFO proxy client_service.handle_event # New job 1403862054 61320 for prevhash f463930d, clean_jobs=False
2014-06-27 12:41:58,201 INFO proxy stratum_listener.submit # [9988ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 255
2014-06-27 12:41:58,201 INFO proxy stratum_listener.submit # [9407ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 255
2014-06-27 12:41:58,201 INFO proxy stratum_listener.submit # [3549ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (23, u'high-hash', None)
2014-06-27 12:41:58,202 INFO proxy stratum_listener.submit # [2301ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 255
2014-06-27 12:41:58,202 INFO proxy stratum_listener.submit # [1246ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 255
2014-06-27 12:41:59,464 INFO proxy stratum_listener.submit # [224ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' accepted, diff 255
2014-06-27 12:42:05,298 INFO proxy stratum_listener.submit # [387ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (23, u'high-hash', None)
2014-06-27 12:42:13,390 INFO proxy client_service.handle_event # New job 1403862084 61321 for prevhash f463930d, clean_jobs=False
2014-06-27 12:44:59,701 INFO proxy stratum_listener.submit # [15350ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (20, u'unknown-work', None)
2014-06-27 12:44:59,702 INFO proxy stratum_listener.submit # [11741ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (20, u'unknown-work', None)
2014-06-27 12:44:59,702 INFO proxy stratum_listener.submit # [11659ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (20, u'unknown-work', None)
2014-06-27 12:44:59,702 INFO proxy stratum_listener.submit # [10551ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (20, u'unknown-work', None)
2014-06-27 12:44:59,703 INFO proxy stratum_listener.submit # [7057ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (20, u'unknown-work', None)
2014-06-27 12:44:59,703 INFO proxy stratum_listener.submit # [5931ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (20, u'unknown-work', None)
2014-06-27 12:44:59,703 INFO proxy stratum_listener.submit # [5322ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (20, u'unknown-work', None)
2014-06-27 12:44:59,704 INFO proxy stratum_listener.submit # [5241ms] Share from '1KUeBzZEtGdupam6bK4VfEHFXJhk1C7XCn' REJECTED: (20, u'unknown-work', None)
|
|
|
|
I've seen payouts before with the block reporting later. it could just be a delay in the stats?
Hmmm .... maybe Its orphan in p2pool share chain but still its a valid block... |
|
|
|
I tought there was a bug in p2pool, had my username/3000000 , when i took the 3000000 of it didnt go down to 1200000 that webpage was showing - even node reboot didnt calm it down. It stayed at ~1600000 even with 2 erupters 670mh  Had to put username/1000000 and then it started to follow.. |
|
|
|
He does if he wants people to switch on donations again. Anyway, if we can't ensure that future mining hardware is usable with p2pool - it will die - simple as that. The hash rate drop since his spectacular fail of a "statement/moan/bribery attempt" shows which way p2pool is going, it will only get worse as everyone gradually switches off their S1's.......
Copy/Paste of my last received email from Bitmain:
"Hi,
Thanks for the info.
Please kindly provide us compared version of screenshot showing that the different speed when you use the p2pool and other pools. we need to provide more details to engineers to investigate it.
Thanks for your help in advance.
Best Regards
BITMAIN"
As my node is no longer online (stripped down) I am unable to provide these - can anyone chime in with these?
Peace.
Tell them to install one node and test themselves... It isnt too hard i think, for them.. |
|
|
|
Anyone using mining_proxy with p2pool, doesnt work here - Im doing something wrong maybe. It keeps connecting and closing.
They don't work with p2pool - never have. One of the many........ Oh, thats bad.. |
|
|
|
|
Anyone using mining_proxy with p2pool, doesnt work here - Im doing something wrong maybe. It keeps connecting and closing.
|
|
|
|
This seems to work well, mining in the dark  |
|
|
|
|
Sent 10000 FSC to Fjhv8Sk8iC7AF76CTJbKo1zkHLUbTTTBs2
cb96de344bfb6bd769d2a3c5cc3900bbd33c1622d183025c057f6e0414466876 ?
|
|
|
|
How does the peering system work and what do incoming and outgoing peers do?
Are the outgoing peers downloading the sharechain from you because they haven´t got the complete list?
What happens when your node has no ingoing peers?
Does your peernetwork automatically grow with your nodes´online time?
I read somewhere that you can also "force" your node to peer with a certain other node, is there a benefit in that?
Does a bigger peer network mean less orphaned shares? (as the found share should be distributed faster around the p2pool network)
Peers talk to each other 20 peers is enough, but 30 is better... Yes they download the chain if they havent got it up todate. You dont necessarily need incoming peers, but if You can open port 9333 it helps network - all cant do that. Force connect if theres a node you think is working very well and might help with your dead or orphan shares.. |
|
|
|
|
"Just run one... there's no reason to run two instances of Bitcoin Core on same box."
Theres plenty of reasons, but it can be done with just one...
|
|
|
|
|
Show Posts
