Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 48. (Read 2591916 times)

TROLL?
You'll see the cartoons that you're already late.

What I said was accurate. You just made some stuff up. LOL Good job troll.

I was mining litecoins at your xpool.net site and now it's stopped
I will loose all my shares???

That is a good question for jtoomim

And you sound opportunist
Now bitcoin wants to run the way miners live
Not good  

It seems to me that your earlier statement is the problem.

You sound lazy.

Anyone, tell, please when it will be compiled on Windows.

It appears that the litecoin side of p2pool was not set up to support segwit. I do not have the time to get it working and am not sure to what extent the code changes will be. It may be as simple as comparing the BTC side of /networks/bitcoin.py to litecoin.py and adding:


...but I have not tried at all.

Anyone know of a good LTC pool?

Edit: I apologize in advance for talking about anything other than Bitcoin in this thread but whatever.

(c)http://p2pool.e-pool.net:5758/static/

Thats is good, but the person who will force me to use Linux, or compile under FreeBSD or Windows programs for this OS, has not yet been born.

What can i do? Core is latest, p2pool is official 16.0

I made a p2pool for ltc with support for SegWit.
If you want, you can try installing from the repository https://github.com/ilsawa/p2pool-ltc

I started getting this message with the main p2pool source (not jtoomim) today starting at around 9am pacific. Nothing I do will get it to work. Anyone have it working?

Edit: Made sure I was running the latest version of litecoind and https://github.com/p2pool/p2pool

Worked out many days. But today i see it:



 
 

 

I haven't tested on Windows before. That looks like it might be a Windows-specific error. I'll see if I can reproduce it.

2017-05-10 20:50:20.355000 P2Pool: 0 shares in chain (0 verified/8607 total) Peers: 6 (0 incoming)
2017-05-10 20:50:20.355000  Local: 0H/s in last 0.0 seconds Local dead on arrival: Expected time to share:
2017-05-10 20:50:23.507000 Processing 57 shares from 208.84.223.121:9333...
2017-05-10 20:50:23.507000 > Share check failed: 0000000000000024677fb883b7adf4d0005b9de313b8d5a6a7f305047533bff5 -> 00000000000000d388b15e1aca14c569e6d6a2b748469a847ea10c167a05ba96
2017-05-10 20:50:23.522000 > Traceback (most recent call last):
2017-05-10 20:50:23.522000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 134, in download_shares
2017-05-10 20:50:23.522000 >     self.handle_shares([(share, []) for share in shares], peer)
2017-05-10 20:50:23.522000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 47, in handle_shares
2017-05-10 20:50:23.522000 >     self.node.set_best_share()
2017-05-10 20:50:23.522000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 293, in set_best_share
2017-05-10 20:50:23.522000 >     best, desired, decorated_heads, bad_peer_addresses = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2017-05-10 20:50:23.538000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 486, in think
2017-05-10 20:50:23.538000 >     if self.attempt_verify(share):
2017-05-10 20:50:23.538000 > --- ---
2017-05-10 20:50:23.538000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 464, in attempt_verify
2017-05-10 20:50:23.538000 >     share.check(self)
2017-05-10 20:50:23.538000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 323, in check
2017-05-10 20:50:23.553000 >     if self.timestamp > int(time.mktime(time.gmtime()) - time.mktime(time.gmtime(0))) + 300:
2017-05-10 20:50:23.553000 > exceptions.OverflowError: mktime argument out of range
2017-05-10 20:50:23.553000 > Share check failed: 00000000000000d388b15e1aca14c569e6d6a2b748469a847ea10c167a05ba96 -> 000000000000001d67b2dbc2e3979ece6983117c25d8041e61f69d810f784d2e
2017-05-10 20:50:23.553000 > Traceback (most recent call last):
2017-05-10 20:50:23.553000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 134, in download_shares
2017-05-10 20:50:23.553000 >     self.handle_shares([(share, []) for share in shares], peer)
2017-05-10 20:50:23.553000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 47, in handle_shares
2017-05-10 20:50:23.569000 >     self.node.set_best_share()
2017-05-10 20:50:23.569000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\node.py", line 293, in set_best_share
2017-05-10 20:50:23.569000 >     best, desired, decorated_heads, bad_peer_addresses = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2017-05-10 20:50:23.569000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 486, in think
2017-05-10 20:50:23.569000 >     if self.attempt_verify(share):
2017-05-10 20:50:23.569000 > --- ---
2017-05-10 20:50:23.569000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 464, in attempt_verify
2017-05-10 20:50:23.585000 >     share.check(self)
2017-05-10 20:50:23.585000 >   File "C:\Users\ppif\Documents\GitHub\p2pool\p2pool\data.py", line 323, in check
2017-05-10 20:50:23.585000 >     if self.timestamp > int(time.mktime(time.gmtime()) - time.mktime(time.gmtime(0))) + 300:
2017-05-10 20:50:23.585000 > exceptions.OverflowError: mktime argument out of range

https://github.com/jtoomim/p2pool/tree/1mb_hardforked has new code. This should fix the sync issues that people have been having. It also includes a few bootstrap nodes to make it easier for people to connect to the jtoomimnet p2pool.

To set up and run my fork, you will need to do the regular steps for installing p2pool, except that instead of getting the regular github.com/p2pool/p2pool repository, you will do:


If anyone continues to have trouble connecting to jtoomimnet, please let me know.

Thanks for the info. It does seem that there may be something wrong with that commit. It's a pretty important commit, though. Without it, in my early testing, I was getting about 60% of my shares orphaned due to transmission failures. I think that orphan rate mostly applies to the first share after a new block, so the orphan rate is likely to be lower in a production environment. However, it will still cost you money if you try to run completely without it.

The purpose of that commit was to fix a problem in which transaction hashes that were part of a stratum job could not be dereferenced into full transactions for share propagation. To fix it, that commit does a few things:

1. It keeps a separate record of transactions that were most recently received by bitcoind in a getblocktemplate vs. transactions that were most recently handed out to miners.
2. It uses a Python namespace hack to keep the transactions in memory in a separate variable in case #1 above doesn't work
3. If share transmission doesn't work due to missing transactions, it queues additional attempts with a delay.

It looks like the problem was with the share retransmission logic (#3). I don't think the retransmission logic is necessary any more, so I made a branch that excludes just that part and see if it fixes the problems that people have been having. I'm testing it now. Looks good so far; I'll post again once testing is finished.

We need to know which two pools you are referring to.

Any ideas why my backup pool has different numbers for everything?  And why did the backup pool output 2 different lines with "New work?"  The second line has the same share difficulty as my main instance, but the difficulty, block value and number of transactions aren't the same.  Both nodes to show the same number of shares in the chain and the same pool hash rate and stale rate.

OK so I went onto the Russian "how to".
I cant read a word of Russian but can understand the code.

I used this :-

git clone -b 1mb_hardforked https://github.com/jtoomim/p2pool.git p2pool

And now im working. Must have been trying the Git Clone wrong.
Ill let this run, its downloading and processing the share chain and see what happens.