Bitcoin Forum
January 23, 2018, 08:22:06 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 [779] 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2556504 times)
tubexc
Hero Member
*****
Offline Offline

Activity: 500


View Profile
July 17, 2017, 01:25:57 PM
 #15561

I think everything is fine
I do not think there is any conflict between nodes adopters of segwit and nodes not adopters
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1516695726
Hero Member
*
Offline Offline

Posts: 1516695726

View Profile Personal Message (Offline)

Ignore
1516695726
Reply with quote  #2

1516695726
Report to moderator
1516695726
Hero Member
*
Offline Offline

Posts: 1516695726

View Profile Personal Message (Offline)

Ignore
1516695726
Reply with quote  #2

1516695726
Report to moderator
1516695726
Hero Member
*
Offline Offline

Posts: 1516695726

View Profile Personal Message (Offline)

Ignore
1516695726
Reply with quote  #2

1516695726
Report to moderator
Meuh6879
Legendary
*
Offline Offline

Activity: 1498



View Profile
July 17, 2017, 01:46:29 PM
 #15562

I'm a BIP148 follower and i run a complet node+P2Pool with a forced +BIP148 command line (switch activate automaticly on 1st August).

I don't care about the activity on the 1st August (on this full node, i plan to not use it before september), but if the local blockchain rollback every 2-4 hours ... what the shares of P2Pool do at this moment ?
LevinSwe
Newbie
*
Offline Offline

Activity: 10


View Profile
July 17, 2017, 10:21:30 PM
 #15563

Warning: (from bitcoind) Warning: Unknown block versions being mined! It's possible unknown rules are in effect.

Version: 16.0,
bitcoincore: 14.2
What to do? :/

40TH house heating system.
Meuh6879
Legendary
*
Offline Offline

Activity: 1498



View Profile
July 17, 2017, 10:48:52 PM
 #15564

Nothing.
Keep mining until the 1st august.

https://bitcointalk.org/index.php?topic=2027108.msg20197321#msg20197321

This idiotic china industrial mining sector ... build others versions of "revision" of Block and Bitcoin Core don't understand this versions : https://bitcointalk.org/index.php?topic=2027513.0

That's why, we have BIP ... but no, they even don't follow the integrated rules in the Bitcoin Core. Roll Eyes
valid BIP that Bitcoin Core recognize : https://bitcoincore.org/en/bips/

In the past, Bitcoin XT already use this phantom menace (build unknown block version).
That's why i mine on P2Pool ... i use the regular and planned rules of the Bitcoin network.
M8BWNNRFMNdak68c
Sr. Member
****
Offline Offline

Activity: 369


View Profile
July 18, 2017, 08:07:34 AM
 #15565

right.. but if i unterstood it correctly: several partys ( inculding seg2x and UASF ) will reject blocks without BIP141 soon.
even though i might add this fix ( https://github.com/p2pool/p2pool/pull/327 ) to my p2pool node, chances are high, that an "old" p2pool node could find our p2pool bitcoin block.
this block will then be oprhaned ( which is very bad for our luck. )

so my advice is to stop mining p2pool now. a high fraction of the shares could be worthless.
we need a reliable solution to this problem. ( but this probably can only be found after august )
tubexc
Hero Member
*****
Offline Offline

Activity: 500


View Profile
July 18, 2017, 09:02:59 AM
 #15566

More Ph/s and P2pool will find a block before the end
of July, that's for sure  Cool
veqtrus
Member
**
Offline Offline

Activity: 107


View Profile WWW
July 18, 2017, 05:56:59 PM
 #15567

even though i might add this fix ( https://github.com/p2pool/p2pool/pull/327 ) to my p2pool node, chances are high, that an "old" p2pool node could find our p2pool bitcoin block.
Even then my patch activates only after 95% of p2pool upgrades. I suppose when activation of segwit in bitcoin becomes certain my PR will be merged.

P2Pool donation button | Bitrated user: veqtrus.
windpath
Legendary
*
Offline Offline

Activity: 1232


View Profile WWW
July 18, 2017, 07:37:55 PM
 #15568

From Matt Corallo (aka TheBlueMatt)

Quote
Hey y'all,

Please keep in mind that neither James' segsignal nor Jeff's btc1 have
any logic to ensure they connect to other BIP 91 nodes. Because such
nodes are very few, and because other nodes will *not* relay blocks
which are not their best chain, it is very possible that your nodes will
not receive notifications of new blocks on the BIP 91 chain.

This means that any time a miner mines a block which does meet the BIP
91 requirements, the fork block which does will take a longer amount of
time to reach your nodes, if you see it at all!

Please, please make absolutely sure that your BIP 91-enforcing nodes
have connections (via -addnode=$NODE or addnode $NODE add) too other BIP
91 miners.

Additionally, the public FIBRE nodes will be adapted later today to
relay all blocks which they receive which are recent. This should be
sufficient to solve the issue as well.

In conclusion, MAKE SURE you are connected to the public FIBRE network
as well as other miners BEFORE the BIP 91 activation takes place. Keep
in mind that bitcoind is limited to 8 addnodes (this limit is separate
from the outbound connections limit).

Thanks and good luck,
Matt

Duce
Full Member
***
Offline Offline

Activity: 175


View Profile
July 19, 2017, 03:38:04 PM
 #15569

Questions:
Running bitcoin 14.2 with the -addnode=.location.fibre.bitcoinrelaynetwork.org, is this correct? I have been whitelisted.

Running 16.0-4-gde 1be30, is there another version I should be running for BIP 91?

If not then what is the version as I would like to add the BIP 91 nodes as stated above.

If these have been answered can you please provide the links? I have search here and the web and can’t seem to put my finger on it.
kol4in
Newbie
*
Offline Offline

Activity: 11


View Profile
July 19, 2017, 04:23:07 PM
 #15570

Hi.Welcom p2pool dashcoin algo X11 stratum+tcp://95.59.72.81:7903
sawa
Legendary
*
Offline Offline

Activity: 1204



View Profile
July 19, 2017, 06:24:21 PM
 #15571

Hi.Welcom p2pool dashcoin algo X11 stratum+tcp://95.59.72.81:7903
http://95.59.72.81:7903/fee
50.0 fee Shocked

Meuh6879
Legendary
*
Offline Offline

Activity: 1498



View Profile
July 19, 2017, 07:17:50 PM
 #15572

Ah ... We have news players.

jtoomim
Hero Member
*****
Offline Offline

Activity: 794


View Profile WWW
July 19, 2017, 09:42:21 PM
 #15573

I just finished a beta version of a merge of veqtrus's SegWit code with my 1mb_hardforked+lowmem code. I've also added a couple of things that should improve the likelihood of it working with altcoins. I'm testing with Bitcoin right now. I'll try to have the testing done and the Bitcoin code ready for others to use within a couple of days, and then I'll work on the altcoin stuff and test it with Litecoin.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
Xantus
Jr. Member
*
Offline Offline

Activity: 42


View Profile
July 19, 2017, 09:51:13 PM
 #15574

Questions:
Running bitcoin 14.2 with the -addnode=.location.fibre.bitcoinrelaynetwork.org, is this correct? I have been whitelisted.

Running 16.0-4-gde 1be30, is there another version I should be running for BIP 91?

If not then what is the version as I would like to add the BIP 91 nodes as stated above.

If these have been answered can you please provide the links? I have search here and the web and can’t seem to put my finger on it.

my question is nearby,

is there a way to see the aktual sign/bits for bip´s my node / my miner has set ?
And can i change this for my miner or for my p2pool node or is that p2pool wide fixed ? and if yes how can i do that ?

my wich is to support PIB91 (perhaps to late for 91 but i could switch in that case to BIP141)

p.s. hi there ;-)
jtoomim
Hero Member
*****
Offline Offline

Activity: 794


View Profile WWW
July 19, 2017, 10:28:44 PM
 #15575

is there a way to see the aktual sign/bits for bip´s my node / my miner has set ?
And can i change this for my miner or for my p2pool node or is that p2pool wide fixed ? and if yes how can i do that ?
Using a web browser, navigate to your node's status page, and click on one of the links in My Shares. Then look for a section that looks like this:

Code:
Header

Version (dec): 536870930

Version (hex): 20000012
(I recently switched my node over to btc1 too.)

The bitcoind version you're using (Unlimited/Core/btc1/etc) will include a version bits suggestion which gets passed to your p2pool node in the getblocktemplate response. Depending on which version of the p2pool code you're using, your p2pool node may either use the version bits it receives from bitcoind, or it may override it (see https://github.com/jtoomim/p2pool/blob/lowmem/p2pool/work.py#L386 for an example -- I've never liked that max() line, but haven't changed it in my branch yet). If you want to force particular version bits even though the bitcoind you're using doesn't make those version bits, you can do so by editing that line in your p2pool source code. Each p2pool node can use different version bits, so the final block version bits that you see depends on which p2pool node actually mined the block.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
windpath
Legendary
*
Offline Offline

Activity: 1232


View Profile WWW
July 19, 2017, 11:50:56 PM
 #15576

I just finished a beta version of a merge of veqtrus's SegWit code with my 1mb_hardforked+lowmem code. I've also added a couple of things that should improve the likelihood of it working with altcoins. I'm testing with Bitcoin right now. I'll try to have the testing done and the Bitcoin code ready for others to use within a couple of days, and then I'll work on the altcoin stuff and test it with Litecoin.

Awesome!

veqtrus
Member
**
Offline Offline

Activity: 107


View Profile WWW
July 20, 2017, 10:25:09 AM
 #15577

I just finished a beta version of a merge of veqtrus's SegWit code with my 1mb_hardforked+lowmem code. I've also added a couple of things that should improve the likelihood of it working with altcoins. I'm testing with Bitcoin right now. I'll try to have the testing done and the Bitcoin code ready for others to use within a couple of days, and then I'll work on the altcoin stuff and test it with Litecoin.

My patch is already running successfully on vertcoin's p2pool. In fact after segwit's activation p2pool's hashrate rose so much that the devs made a second network for smaller miners.

P2Pool donation button | Bitrated user: veqtrus.
TierNolan
Legendary
*
Offline Offline

Activity: 1162


View Profile
July 20, 2017, 12:08:48 PM
 #15578

Each p2pool node can use different version bits, so the final block version bits that you see depends on which p2pool node actually mined the block.

Are you planning to enforce BIP-91 for p2pool (assuming it locks in)?

If someone produces a share without the segwit bit set, then that share is effectively worthless (at least until segwit is locked in).

An easy rule would be that the bit must be set until August 1st and then while at least 750 of the last 1000 blocks have it set.  That saves you needing to add code to figure out if segwit has been locked in.

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
jtoomim
Hero Member
*****
Offline Offline

Activity: 794


View Profile WWW
July 20, 2017, 01:06:14 PM
 #15579

Are you planning to enforce BIP-91 for p2pool (assuming it locks in)?
This is a complicated question. Currently, there's an incompatibility between p2pool and BIP91 in that p2pool will mine a transaction-free block on top of the longest chain seen if p2pool hears about a new block but bitcoind does not inform p2pool about this block. While I think this is the correct behavior during normal operation, it is clearly incorrect behavior during chainsplit conditions, so it will need to be disabled for the next month or so. I will be including that change in the new branch I'm working on that merges SegWit and large block generation capability.

Quote
If someone produces a share without the segwit bit set, then that share is effectively worthless (at least until segwit is locked in).
I am not convinced that this is the correct action to take. P2pool generally does not validate the blocks that other nodes are trying to mine except to ensure that the payouts are fair. I'm not sure that we should start now. On one hand, it serves as an added incentive for people to ensure that they are BIP91 compatible. On the other hand, it disincentivizes miners using p2pool as a tool to vote their conscience. I tend to believe that the latter objective is generally more important, but I'm not sure in this particular case. It may be that people would want to exploit p2pool to mine minority-chain blocks while still getting paid on the majority chain, which could be a problem. Perhaps the best solution is just to fork the share chain again, and let anyone who wants to disobey BIP91 do so on their own minority sharechain. However, that approach would require the most work of any.

Quote
An easy rule would be that the bit must be set until August 1st and then while at least 750 of the last 1000 blocks have it set.  That saves you needing to add code to figure out if segwit has been locked in.
That would actually be a difficult rule, since p2pool does not store a copy of the blockchain anywhere, and is unable to evaluate whether 750 of the last 1000 blocks have it set.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
TierNolan
Legendary
*
Offline Offline

Activity: 1162


View Profile
July 20, 2017, 01:47:38 PM
 #15580

While I think this is the correct behavior during normal operation, it is clearly incorrect behavior during chainsplit conditions,

If BIP-91 goes into effect, then BTC1 connectivity is going to be an issue, agreed.

Even nodes with the btc1 client aren't safe, since they could be surrounded by non-BIP-91 nodes and not get the updated block (since it counts as a tie).

Quote
so it will need to be disabled for the next month or so. I will be including that change in the new branch I'm working on that merges SegWit and large block generation capability.

How will that work?  You can't build non-empty blocks if your local bitcoin node doesn't have the tip block. 

You could poll the local node.  If it has it, then it might send it even if it isn't the longest chain (as far as it is concerned).

I think BIP-91 nodes will preferentially connect to at least a few BIP-91 other nodes (or maybe they didn't bother with that).  That means that if the local node is btc1, then you would be ok.

Quote
I am not convinced that this is the correct action to take. P2pool generally does not validate the blocks that other nodes are trying to mine except to ensure that the payouts are fair.

That is because p2pool cannot verify without lots of overhead (distribute the full block for each share).

If BIP-91 locks in, then it is guaranteed that blocks which don't flag segwit are invalid and that info is in the header which (I assume) is shared between p2pool nodes.

Quote
I'm not sure that we should start now

It would definitely be an emergency fix and has a risk/reward profile.  Network-wise, it is a soft fork.

Quote
On one hand, it serves as an added incentive for people to ensure that they are BIP91 compatible.

Shares which are invalid are basically draining the network of earning potential.  They get paid, but provide nothing.

Quote
On the other hand, it disincentivizes miners using p2pool as a tool to vote their conscience.

I am not suggesting that you should force people to vote for BIP-91.

However, if BIP-91 does lock in, then that counts as a soft fork and a change to the bitcoin rules.

You would be enforcing the (new/soft forked) Bitcoin protocol. 

Quote
Perhaps the best solution is just to fork the share chain again, and let anyone who wants to disobey BIP91 do so on their own minority sharechain. However, that approach would require the most work of any.

You could soft fork it.  If 75% agree, then activate the change.  As you say, it is a judgement call.  Maybe people would like to preserve the ability to create their own blocks.

Quote
That would actually be a difficult rule, since p2pool does not store a copy of the blockchain anywhere, and is unable to evaluate whether 750 of the last 1000 blocks have it set.

Fair enough.  You could just make it time based (all blocks from now until 15 August).

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
Pages: « 1 ... 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 [779] 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 »
  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!