The Bitcoin Forum

ikolu: can you try changing that line from
if tracker.items[self.share_data['previous_share_hash']] and tracker.items[self.share_data['previous_share_hash']].naughty:
to
if self.share_data['previous_share_hash'] and tracker.items[self.share_data['previous_share_hash']].naughty:
and tell me if ...

jtoomim,
It is still giving the error about the key.

2018-03-29 12:26:04.589426 GOT SHARE! ikolu.1 5878eeec prev xxxxxxxx age 110.86s
2018-03-29 12:26:04.591264 > Share check failed: 36dc4f8946784eb7126bc68b40990f9c6f614d9e65a8a9bd245e2bf55878eeec ...

Ok... So I commented out the lines where it was giving the error so I could get some share in... Then I uncommented them and fired it up again and now the shares are coming in.

Don't know if you want to fix it for good, but it is working here!

Thank you,

Forgot to push to github, sorry. Check again.

Thank you!
Now I get this:
Share check failed: bfadcebc2e0a9c47c0ceecf77386a6251a66f6fcd1db4b1dc6c416fc3a91b18d -> 0000000000000000000000000000000000000000000000000000000000000000
Traceback (most recent call last):
File "/home/ialmeida/p2poolSolo ...

exceptions.ValueError: segwit transaction included before activation

... trying to make it work as a solo mining for LTC

I have merged the feechecking branch into 1mb_segwit and added a commit to 1mb_segwit that should address your issue. The issue is that v16 shares do not support Segwit ...

jtoomim,
Curiosity..
I checked out the feechecking branch and was trying to make my p2pool node to “solo mine”

I changes the network file with new Identifier and Prefix hex and persist to False.

It loads and it doesn’t download shares as expected. But if I try to connect a worker it throws this ...

I have pushed changes to feechecking that allow it to work with Litecoin Core 0.15.1. These changes will probably also add support for Bitcoin Core 0.15 and later, but I haven't tested that.

I just tried it and ...
2018-03-25 09:49:46.849461 p2pool (version 15.0-99-gb6e6c2d)
2018-03-25 09:49:46 ...

@jtoomim what happens when I connect many workers with the same payout address?
Does each worker works on its own share with the specific share diff or p2pool splits the share diff between them and they mine all together towards the same share?

Example:
3 miners with same payout address mining at a ...

Search found 8 matches

Re: P2pool: Decentralized, DoS-resistant, trustless, censorship-resistant pool.

Re: P2pool: Decentralized, DoS-resistant, trustless, censorship-resistant pool.

Re: P2pool: Decentralized, DoS-resistant, trustless, censorship-resistant pool.

Re: P2pool: Decentralized, DoS-resistant, trustless, censorship-resistant pool.

Re: P2pool: Decentralized, DoS-resistant, trustless, censorship-resistant pool.

Re: P2pool: Decentralized, DoS-resistant, trustless, censorship-resistant pool.

Re: P2pool: Decentralized, DoS-resistant, trustless, censorship-resistant pool.

Re: P2pool: Decentralized, DoS-resistant, trustless, censorship-resistant pool.

about bitcoin.com

You Must Know

Social Links