[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 120.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: DonBit on December 08, 2015, 10:29:27 PM

I've configured the stock cgminer in my S7 batch 6 with

Code:

"submit-stale" : true,
"queue" : "1",
"expiry" : "1",
"scan-time" : "1"

and looks like it's now submitting stale shares.

Quote

[2015-12-09 03:27:21] Pool 1 stale share detected, submitting as user requested
[2015-12-09 03:27:21] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
[2015-12-09 03:27:22] opt_bitmain_freq:600 tmp:600
[2015-12-09 03:27:22] Pool 1 stale share detected, submitting as user requested
[2015-12-09 03:27:22] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
[2015-12-09 03:27:23] Pool 1 stale share detected, submitting as user requested

Don't know if it's a bogus submission or if it's really happening but I'm on full speed p2pool

The cgminer default is always to submit stale shares. That entry in your config does nothing on current versions of cgminer. The problem with bitmain's driver is it deletes shares in the driver before even returning them to the main cgminer code in a way you can't configure in cgminer to avoid. These shares don't even show up as being deleted in any logs.

DonBit

member

Activity: 69

Merit: 10

Quote from: jonnybravo0311 on November 24, 2015, 09:29:36 AM

Quote from: wariner on November 24, 2015, 08:19:47 AM

Quote from: -ck on November 24, 2015, 06:44:38 AM

Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...

the problem is only for s7? or even s5 - s3....?

There is a discussion that contains all modified antminer drivers for p2pool?

Quote from: jonnybravo0311 on November 24, 2015, 08:00:48 AM

.. but it certainly isn't the only one

.

Do you think it's just bad luck or other?

The problem is for ALL Antminers unless you have installed the proper binaries from -ck and kano. If you are using any other binaries (Bitmain's, some other forks for extranonce, etc) then you do not have the updated code that submits stale shares. In other words, you are potentially throwing away possible block solutions.

As to your other question regarding luck... yes, I believe it is just poor luck. We are experiencing normal swings in variance. As I initially mentioned, S7s are certainly a potential influencing factor since there are no (to my knowledge, -ck/kano can correct me) updated cgminer binaries for it. However, I don't know how many people currently mining on p2pool are using S7s, so I don't have any reference for how much of an impact it might have

.

I've configured the stock cgminer in my S7 batch 6 with

Code:

"submit-stale" : true,
"queue" : "1",
"expiry" : "1",
"scan-time" : "1"

and looks like it's now submitting stale shares.

Quote

[2015-12-09 03:27:21] Pool 1 stale share detected, submitting as user requested
[2015-12-09 03:27:21] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
[2015-12-09 03:27:22] opt_bitmain_freq:600 tmp:600
[2015-12-09 03:27:22] Pool 1 stale share detected, submitting as user requested
[2015-12-09 03:27:22] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
[2015-12-09 03:27:23] Pool 1 stale share detected, submitting as user requested

Don't know if it's a bogus submission or if it's really happening but I'm on full speed p2pool

windpath

legendary

Activity: 1258

Merit: 1027

Looks like we are at about 25% upgraded, big milestone is 50% when the alert message will be triggered on all nodes to upgrade...

I'll have some time tomorrow to try and reach out to the larger nodes still producing V3 blocks, but if anyone wants to get started today it sure could not hurt Wink

Meuh6879

legendary

Activity: 1512

Merit: 1012

AndreyNag

member

Activity: 88

Merit: 10

Quote from: sawa on December 06, 2015, 04:23:15 PM

I see - very few nodes been updated:
http://poolnode.info/
http://nodes.p2pool.co/

Our node have been updated to.
che2pool.mine.nu:9332
Welcome.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: forrestv on December 06, 2015, 04:34:02 PM

I'm not sure what version number they'll use, but when they release it (and somebody tells me), I will whitelist it and release P2Pool 15.1.

It will be 0.11D (or 0.11.0D, or something like that, depending on how it gets parsed). It should be released pretty soon.

yslyung

legendary

Activity: 1500

Merit: 1002

Mine Mine Mine

thx forrest,

will be updating my node too.

been away for a bit. is anyone mining with s7 on p2p ? how is it doing ?

Meuh6879

legendary

Activity: 1512

Merit: 1012

v15 installed.

wariner

legendary

Activity: 1257

Merit: 1004

pool.sexy

Quote from: lightfoot on December 04, 2015, 01:06:02 PM

Quote from: p3yot33at3r on December 04, 2015, 12:11:52 PM

Quote from: lightfoot on December 04, 2015, 12:06:21 PM

Is some flunkie DOSing the nodes again?

I'm not aware of any p2pool node ever being dos'd. There seems to be something wrong with your setup though - over 4 seconds is rather high - try limiting your connections to 12-14 instead - that should help.

Sorry, I was thinking bitcoind. I've noticed I have been drawing more stupid-fire ever since I brought up a full node, even more than when I started running a tor relay. Simple enough to deal with, still kind of lame.

I'll try limiting the connections some. The proper solution though is to probably fire up a ubuntu system on an old laptop and run a copy of bitcoind inside network peered to the outside one and others. That should bring it back to sub-second responses while allowing the externally facing one to serve as a full bitcoin node and a p2pool node that can supply blocks to others behind nats.

The problem it's RAM.

Use this for reduce use of RAM:

-limitfreerelay= Rate-limit free transactions to *1000 bytes per minute (default: 15)
-minrelaytxfee= Fees smaller than this (in satoshi) are considered zero fee (relaying and mining) (default: 0.00001)
-disablewallet Do not load the wallet and disable wallet RPC calls

maybe fix in bitcoin core 0.12....

jedimstr

hero member

Activity: 798

Merit: 1000

Quote from: forrestv on December 06, 2015, 04:34:02 PM

Quote from: jedimstr on December 06, 2015, 04:31:24 PM

Note the new P2Pool Hardfork version 15 currently does not support the BitcoinXT client (neither the 0.11C nor pre-release 0.11D version) and won't fully startup unless you're running BTCore 0.11.2.

Forest: when BitcoinXT gets the BIP65 pull request merged in, will P2Pool be able to support the resulting BXT version #?

I'm not sure what version number they'll use, but when they release it (and somebody tells me), I will whitelist it and release P2Pool 15.1.

Thanks, I'll shoot a message over once Gavin and Mike have a version with BIP65 available.

forrestv

hero member

Activity: 516

Merit: 643

Quote from: jedimstr on December 06, 2015, 04:31:24 PM

Note the new P2Pool Hardfork version 15 currently does not support the BitcoinXT client (neither the 0.11C nor pre-release 0.11D version) and won't fully startup unless you're running BTCore 0.11.2.

Forest: when BitcoinXT gets the BIP65 pull request merged in, will P2Pool be able to support the resulting BXT version #?

I'm not sure what version number they'll use, but when they release it (and somebody tells me), I will whitelist it and release P2Pool 15.1.

jedimstr

hero member

Activity: 798

Merit: 1000

Note the new P2Pool Hardfork version 15 currently does not support the BitcoinXT client (neither the 0.11C nor pre-release 0.11D version) and won't fully startup unless you're running BTCore 0.11.2.

Forest: when BitcoinXT gets the BIP65 pull request merged in, will P2Pool be able to support the resulting BXT version #?

forrestv

hero member

Activity: 516

Merit: 643

Quote from: sawa on December 06, 2015, 04:23:15 PM

I see - very few nodes been updated:
http://poolnode.info/
http://nodes.p2pool.co/
It would be better to change the values in https://github.com/p2pool/p2pool/blob/master/p2pool/networks/bitcoin.py#L15

Code:

IDENTIFIER = 'fc70035c7a81bc6f'.decode('hex')
PREFIX = '2472ef181efcd37b'.decode('hex')

It was only released two hours ago, so it's not surprising that few nodes have updated. Changing those values would prevent a smooth transition. Everything will be fine, if it goes at all similarly to how the last hardfork did.

sawa

legendary

Activity: 1308

Merit: 1011

Quote from: forrestv on December 06, 2015, 02:28:06 PM

BIP65 will take effect in the next week and in order for P2Pool to continue working without producing invalid blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded before BIP65 takes effect, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.

So, please upgrade to 15.0 now and also tell everyone else to.

I see - very few nodes been updated:
http://poolnode.info/
http://nodes.p2pool.co/
It would be better to change the values in https://github.com/p2pool/p2pool/blob/master/p2pool/networks/bitcoin.py#L15

Code:

IDENTIFIER = 'fc70035c7a81bc6f'.decode('hex')
PREFIX = '2472ef181efcd37b'.decode('hex')

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: forrestv on December 06, 2015, 02:28:06 PM

P2Pool release 15.0 - commit hash: 86bbdac7eaaa03438e71ee9dcb11898c7b2b8bdf

HARDFORK - Upgrade URGENTLY required in the next few days.

Windows binary: http://u.forre.st/u/ovqxauzj/p2pool_win32_15.0.zip
Windows binary signature: http://u.forre.st/u/wynjbvpn/p2pool_win32_15.0.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/15.0
Source tarball: https://github.com/forrestv/p2pool/tarball/15.0

Changes:
* BIP65/block version 4 compatibility
* Requires Bitcoin >=0.11.2 (for BIP65 compatibility)

BIP65 will take effect in the next week and in order for P2Pool to continue working without producing invalid blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded before BIP65 takes effect, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.

So, please upgrade to 15.0 now and also tell everyone else to.

Thank you Forrest!

forrestv

hero member

Activity: 516

Merit: 643

P2Pool release 15.0 - commit hash: 86bbdac7eaaa03438e71ee9dcb11898c7b2b8bdf

HARDFORK - Upgrade URGENTLY required in the next few days.

Windows binary: http://u.forre.st/u/ovqxauzj/p2pool_win32_15.0.zip
Windows binary signature: http://u.forre.st/u/wynjbvpn/p2pool_win32_15.0.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/15.0
Source tarball: https://github.com/forrestv/p2pool/tarball/15.0

Changes:
* BIP65/block version 4 compatibility
* Requires Bitcoin >=0.11.2 (for BIP65 compatibility)

BIP65 will take effect in the next week and in order for P2Pool to continue working without producing invalid blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded before BIP65 takes effect, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.

So, please upgrade to 15.0 now and also tell everyone else to.

sawa

legendary

Activity: 1308

Merit: 1011

Quote from: p3yot33at3r on December 06, 2015, 07:18:29 AM

P2pool has been updated:

https://github.com/p2pool/p2pool

I see forrestv has created a new v15 tag in the repo too - maybe some more updates on the way?

Thanks forrestv

Edit: Hmmm....since updating my system has locked up twice in 30 minutes. I'm not sure yet what the problem is until I get a chance to check the logs.......

After the update, there is no visual changes. My node works without lockings.
This message appears periodically (but it was before updating):

Code:

Unhandled Error
Traceback (most recent call last):
File "/usr/local/lib/pypy2.7/dist-packages/twisted/internet/defer.py", line 501, in _startRunCallbacks
self._runCallbacks()
File "/usr/local/lib/pypy2.7/dist-packages/twisted/internet/defer.py", line 588, in _runCallbacks
current.result = callback(current.result, *args, **kw)
File "/opt/p2pool-btc/p2pool/util/deferral.py", line 256, in gotResult
it(res2)
File "/opt/p2pool-btc/p2pool/util/deferral.py", line 233, in it
res = gen.send(cur) # external code is run here
--- ---
File "/opt/p2pool-btc/p2pool/util/deferral.py", line 284, in _worker
self.func(*self.args, **self.kwargs)
File "/opt/p2pool-btc/p2pool/util/expiring_dict.py", line 109, in
self._expire_loop = expire_loop = deferral.RobustLoopingCall(lambda: self_ref().expire())
exceptions.AttributeError: 'NoneType' object has no attribute 'expire'

notbatman

legendary

Activity: 2212

Merit: 1038

Quote from: Carlton Banks on December 06, 2015, 06:31:55 AM

Quote from: notbatman on December 05, 2015, 05:15:38 PM

blockmaxsize=640000

"640K ought to be enough for anyone" -- Bill Gates

BTClimit=21 000 000

Quote from: satoshi

"21 million coins ought to be enough for everyone" Satoshi Nakamoto

Sensible limit is a sensible limit...

And remember kids, the blocksize limit is exactly that, a limit on the blocksize. Alot of people claim it is a transaction rate limit, 3 tps to be precise. But that's only when using the method of encoding the data that we use currently. Real scaling solutions will expand the use of 1MB until there are no ways left to cram extra tx info into that 1MB (indeed, several angles are already in contention). Then, the blocksize might need increasing. Until then, higher transaction throughput can be achieved a better way (a way that won't have all miners buying new disk drives every year).

mintxfee=0.0005
minrelaytxfee=0.0005

"If you're good at something, never do it for free" -- Joker

p3yot33at3r

sr. member

Activity: 266

Merit: 250

P2pool has been updated:

https://github.com/p2pool/p2pool

I see forrestv has created a new v15 tag in the repo too - maybe some more updates on the way?

Thanks forrestv

Edit: Hmmm....since updating my system has locked up twice in 30 minutes. I'm not sure yet what the problem is until I get a chance to check the logs.......

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: notbatman on December 05, 2015, 05:15:38 PM

blockmaxsize=640000

"640K ought to be enough for anyone" -- Bill Gates

BTClimit=21 000 000

Quote from: satoshi

"21 million coins ought to be enough for everyone" Satoshi Nakamoto

Sensible limit is a sensible limit...

And remember kids, the blocksize limit is exactly that, a limit on the blocksize. Alot of people claim it is a transaction rate limit, 3 tps to be precise. But that's only when using the method of encoding the data that we use currently. Real scaling solutions will expand the use of 1MB until there are no ways left to cram extra tx info into that 1MB (indeed, several angles are already in contention). Then, the blocksize might need increasing. Until then, higher transaction throughput can be achieved a better way (a way that won't have all miners buying new disk drives every year).

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