Bitcoin Forum
June 26, 2017, 07:23:04 AM *
News: Latest stable version of Bitcoin Core: 0.14.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 [695] 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 ... 777 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2323615 times)
lightfoot
Legendary
*
Offline Offline

Activity: 1190

I fix broken miners. And make holes in teeth :-)


View Profile
December 04, 2015, 04:16:31 PM
 #13881

Well Gbt latency seems to be a problem on my node, even after bringing mintxfee to .000whatever2 it's still climbing and requiring a sw reset of bitcoind every day. At the moment it's at 4.72 seconds, with spikes to 15-20 seconds. At that rate I would fail everything with p2pool, correct?

(Mac mini server, 0.11.1 bitcoind, 8gb memory, SSD boot disk and bitcoin block disk)
1498461784
Hero Member
*
Offline Offline

Posts: 1498461784

View Profile Personal Message (Offline)

Ignore
1498461784
Reply with quote  #2

1498461784
Report to moderator
POLONIEX TRADING SIGNALS
+50% Profit and more via TELEGRAM
ALTCOINTRADER.CO
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
windpath
Legendary
*
Offline Offline

Activity: 1120


View Profile WWW
December 04, 2015, 04:28:34 PM
 #13882

Well Gbt latency seems to be a problem on my node, even after bringing mintxfee to .000whatever2 it's still climbing and requiring a sw reset of bitcoind every day. At the moment it's at 4.72 seconds, with spikes to 15-20 seconds. At that rate I would fail everything with p2pool, correct?

(Mac mini server, 0.11.1 bitcoind, 8gb memory, SSD boot disk and bitcoin block disk)


How many connections do you allow to bitcoind?

Had some issues with 0.11.1, running smooth since 0.11.2, might be worth the upgrade...

btcdrak
Legendary
*
Offline Offline

Activity: 1064


View Profile
December 04, 2015, 04:58:36 PM
 #13883

Just a heads up, BIP65 is currently deploying on the network. Miners needs to upgrade to Bitcoin Core 0.11.2 to support BIP65 CHECKLOCKTIMEVERIFY. Once enforcement comes, p2pool version 3 blocks will be rejected by the network so it would be advisable to upgrade asap.

Network stats: bitcoin.sipa.be/ver-2k.png
Last 1000 blocks: data.bitcoinity.org/bitcoin/block_version/5y?c=block_version&r=week&t=a

As far as I can tell al* major pools except one are already producing v4 blocks, leaving just 1 pool and p2pool.
lightfoot
Legendary
*
Offline Offline

Activity: 1190

I fix broken miners. And make holes in teeth :-)


View Profile
December 04, 2015, 05:06:21 PM
 #13884

How many connections do you allow to bitcoind?
Pretty much unlimited. Otherwise if p2pool crashes and restarts it can't get a connection. Besides, this is a nice thing to help the network overall.

Quote
Had some issues with 0.11.1, running smooth since 0.11.2, might be worth the upgrade...
Okies. I tried compiling from source but got a runtime error on launch. Will work on it. Interesting, I just checked the node (not mining) and I see:

Warning: LOST CONTACT WITH BITCOIND for 4.0 minutes! Check that it isn't frozen or dead!

Is some flunkie DOSing the nodes again? Hm. Actually python is running hot at 94% with bitcoind running at 15%.
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
December 04, 2015, 05:11:52 PM
 #13885

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.
windpath
Legendary
*
Offline Offline

Activity: 1120


View Profile WWW
December 04, 2015, 05:36:38 PM
 #13886

Just a heads up, BIP65 is currently deploying on the network. Miners needs to upgrade to Bitcoin Core 0.11.2 to support BIP65 CHECKLOCKTIMEVERIFY. Once enforcement comes, p2pool version 3 blocks will be rejected by the network so it would be advisable to upgrade asap.

Network stats: bitcoin.sipa.be/ver-2k.png
Last 1000 blocks: data.bitcoinity.org/bitcoin/block_version/5y?c=block_version&r=week&t=a

As far as I can tell al* major pools except one are already producing v4 blocks, leaving just 1 pool and p2pool.

A.K.A. OP_HODL! Great BIP, looking forward to it's enforcement Smiley

Actually published a tutorial yesterday about monitoring its deployment Smiley

Monitoring soft fork enforcement using getblockchaininfo
https://chainquery.com/tutorials/monitoring-soft-fork-enforcement-using-getblockchaininfo

lightfoot: I limit my bitcoind to 15 connections on the pool node.

lightfoot
Legendary
*
Offline Offline

Activity: 1190

I fix broken miners. And make holes in teeth :-)


View Profile
December 04, 2015, 06:06:02 PM
 #13887

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.
kano
Legendary
*
Online Online

Activity: 2128


Linux since 1997 RedHat 4


View Profile
December 04, 2015, 11:03:16 PM
 #13888

Yeah there's an issue doing that as per design by current bitcoind

Bitcoin devs say your suggestion is how you should do it, but it's problematic:

Every node running bitcoind core of course fully verifies every block it receives.
However, there's no way to ask a node to pass it's block onto you before it has fully verified it.

e.g. check the hash, versions etc which takes only nanoseconds on a typical CPU, but not the transactions, before passing it on to another node that will also fully verify it before 'using' it.
The reason for this is of course to stop distribution of invalid blocks, but your setup is a perfect example where that simply slows it down for 'almost' every block ever found and thus you'd not want that in your configuration.

So the verification process is repeated every time in every node before it gets to you and you do it again yourself.
That verification is quite slow, but even if it was fast, it will still delay you passing your blocks around your collection of bitcoinds.

So if you have one outward facing node, talking to (all) your other internal, non-outward facing nodes, that doubles the relay (verification) time since it's done effectively twice before each internal node uses the block.

That's called trust, to allow early distribution, which is apparently, according to a bitcoin dev:
"trust settings are black magic that cannot be configured correctly even by experts"

So yeah consider that (double delay) issue of receiving EVERY block change, except blocks your node finds, in your configuration.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
windpath
Legendary
*
Offline Offline

Activity: 1120


View Profile WWW
December 05, 2015, 09:32:51 PM
 #13889


Upgrade Required: Bitcoin Core 0.11.2

Just a heads up that the last large pool started generating version 4 blocks today.

About 70% of the last 1,000 blocks were V4, at 75% transactions including CLTV will be allowed, at 95% version 4 blocks will be REQUIRED.

If you do not upgrade and find a block it will be rejected by the network.


notbatman
Legendary
*
Offline Offline

Activity: 1246



View Profile
December 05, 2015, 10:15:38 PM
 #13890

blockmaxsize=640000

"640K ought to be enough for anyone" -- Bill Gates
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2198


Ruu \o/


View Profile WWW
December 05, 2015, 10:29:45 PM
 #13891

Just a heads up that the last large pool started generating version 4 blocks today.
If you're referring to antpool, they are still producing a mixture of v3 and v4 blocks so it's not quite there yet. That's no reason to stop everyone else from updating though.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at ckpool.org Solo mine at solo.ckpool.org
-ck
Carlton Banks
Legendary
*
Offline Offline

Activity: 1680



View Profile
December 06, 2015, 11:31:55 AM
 #13892

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).

Vires in numeris
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
December 06, 2015, 12:18:29 PM
 #13893

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  Smiley

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.......
notbatman
Legendary
*
Offline Offline

Activity: 1246



View Profile
December 06, 2015, 01:29:02 PM
 #13894

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
sawa
Hero Member
*****
Offline Offline

Activity: 894



View Profile
December 06, 2015, 04:29:29 PM
 #13895

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  Smiley

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
--- <exception caught 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 <lambda>
    self._expire_loop = expire_loop = deferral.RobustLoopingCall(lambda: self_ref().expire())
exceptions.AttributeError: 'NoneType' object has no attribute 'expire'

forrestv
Hero Member
*****
Offline Offline

Activity: 515


View Profile
December 06, 2015, 07:28:06 PM
 #13896

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.

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
windpath
Legendary
*
Offline Offline

Activity: 1120


View Profile WWW
December 06, 2015, 07:51:43 PM
 #13897

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!

sawa
Hero Member
*****
Offline Offline

Activity: 894



View Profile
December 06, 2015, 09:23:15 PM
 #13898

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')

forrestv
Hero Member
*****
Offline Offline

Activity: 515


View Profile
December 06, 2015, 09:26:41 PM
 #13899

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.

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
December 06, 2015, 09:31:24 PM
 #13900

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 #?


Pages: « 1 ... 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 [695] 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 ... 777 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!