Author

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

legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
He also released a fork of core with just the big blocks patched. that's the version I'll be running.
Sort of.  There is a code base with only the big block bits, with some caveats:

[...] the program you get by compiling that branch calls itself Bitcoin Core, even though it isn't. Distributing a program that uses the brand name of that project whilst including changes the developers disagree with seems kind of like a dick move to me; and if Bitcoin Core was a trademark it'd also cause legal issues.
So that's why Bitcoin XT has a separate brand.
Now, that problem can be easily resolved by inventing yet another new name, adapting the XT rebranding patch, and then setting up that new alternative brand with its own website, etc. But it turns out to be a lot of work to do that, especially if you want builds for every platform, gitian reproducibility, code signing etc. I don't have the energy to do it all twice over. If someone else wants to though, go for it.

[- Mike Hearn]

Hmm. Wonder what's involved in the rebranding. I'd probably be willing to share but I hadn't thought of the rebranding and it would be Linux only (probably).
hero member
Activity: 686
Merit: 500
FUN > ROI
He also released a fork of core with just the big blocks patched. that's the version I'll be running.
Sort of.  There is a code base with only the big block bits, with some caveats:

[...] the program you get by compiling that branch calls itself Bitcoin Core, even though it isn't. Distributing a program that uses the brand name of that project whilst including changes the developers disagree with seems kind of like a dick move to me; and if Bitcoin Core was a trademark it'd also cause legal issues.
So that's why Bitcoin XT has a separate brand.
Now, that problem can be easily resolved by inventing yet another new name, adapting the XT rebranding patch, and then setting up that new alternative brand with its own website, etc. But it turns out to be a lot of work to do that, especially if you want builds for every platform, gitian reproducibility, code signing etc. I don't have the energy to do it all twice over. If someone else wants to though, go for it.

[- Mike Hearn]
legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
Just keep in mind that the default code base and the released binaries of XT include more than just the block size changes.  'Voting for' XT is a vote in favor of all changes, not just the block size ones.

He also released a fork of core with just the big blocks patched. that's the version I'll be running.
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
So the Mac binary for XT is pretty poorly put together... it's not even an app, it's just a compiled tarball with some executables in it.  I might have to rectify that.  Of course, I'll have to get by the configure file claiming I don't have BDB, even though I do - and it's in the standard location - and can compile Core without issue.

Compilation from source on Ubuntu went flawlessly.

I will probably test this out on my node... but won't get to it today.
legendary
Activity: 1258
Merit: 1027
1. I have been testing P2Pool with BitcoinXT on my development node, it works as expected with really no performance differences at all.

2. In the next couple weeks(TM) I'll be releasing Chain Query (alpha: http://chainquery.com) on Github, once thats done I plan to rewrite my P2Pool node front end to use Chain Query and MySQL (the core P2Pool code does not need to be altered) and will relaunch http://minefast.CoinCadence.com on BitcoinXT with the new front end. I will release the full source for the new front end on Github.

The switch to XT is a personal decision, and shows my support for scaling Bitcoin. I believe it is the right path.

...

Is stratum+tcp://minefast.CoinCadence.com:9332 or stratum+tcp://minefast2.CoinCadence.com:9332 on XT yet? I'm getting a few people on my reddit/r/bitcoin and reddit/r/bitcoinxt threads who want to join my XT node, and I'd like to give them other options too.

https://www.reddit.com/r/Bitcoin/comments/3h6nh0/toomim_bros_bitcoin_mining_concern_supports/
https://www.reddit.com/r/bitcoinxt/comments/3h6lk8/toomim_bros_supports_democracy_and_bitcoin_xt/
It's not up yet, still core. I'll post here when it's up and running...
hero member
Activity: 818
Merit: 1006
1. I have been testing P2Pool with BitcoinXT on my development node, it works as expected with really no performance differences at all.

2. In the next couple weeks(TM) I'll be releasing Chain Query (alpha: http://chainquery.com) on Github, once thats done I plan to rewrite my P2Pool node front end to use Chain Query and MySQL (the core P2Pool code does not need to be altered) and will relaunch http://minefast.CoinCadence.com on BitcoinXT with the new front end. I will release the full source for the new front end on Github.

The switch to XT is a personal decision, and shows my support for scaling Bitcoin. I believe it is the right path.

...

Is stratum+tcp://minefast.CoinCadence.com:9332 or stratum+tcp://minefast2.CoinCadence.com:9332 on XT yet? I'm getting a few people on my reddit/r/bitcoin and reddit/r/bitcoinxt threads who want to join my XT node, and I'd like to give them other options too.

https://www.reddit.com/r/Bitcoin/comments/3h6nh0/toomim_bros_bitcoin_mining_concern_supports/
https://www.reddit.com/r/bitcoinxt/comments/3h6lk8/toomim_bros_supports_democracy_and_bitcoin_xt/
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Just keep in mind that the default code base and the released binaries of XT include more than just the block size changes.  'Voting for' XT is a vote in favor of all changes, not just the block size ones.
... and just using it is a vote in favour of it ...
Which is why I made the drug dealer reference.
It's not just "try it to see that it's OK" since there is nothing to see, it's: "try it and thus you may not realise it but you are voting for it"
Trying it is voting to use it.
So people should decide that before trying it - since you won't see anything by trying it.
legendary
Activity: 1258
Merit: 1027
Just keep in mind that the default code base and the released binaries of XT include more than just the block size changes.  'Voting for' XT is a vote in favor of all changes, not just the block size ones.

True, here's Mike's list:
Code:
    Bigger blocks
    Double spend relaying
    Better DoS attack defences
    BIP 65 / getutxos support
    DNS seed list refresh

https://groups.google.com/forum/#!topic/bitcoin-xt/_YeEuaUu3Xk
hero member
Activity: 686
Merit: 500
FUN > ROI
Just keep in mind that the default code base and the released binaries of XT include more than just the block size changes.  'Voting for' XT is a vote in favor of all changes, not just the block size ones.
legendary
Activity: 1258
Merit: 1027
Sounds like a drug dealer Smiley
... come on ... you can change your mind later ... just try it ... it wont do anything ...
Um, if it does nothing, why bother?

Drug dealer? Really?

Quote
right now it's 0 risk and a way to support a block size increase.

And that's essentially what it is. A vote with hash power.
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
XT or Core ... whichever works best i go.

ah ha & a BLOCK !
hero member
Activity: 818
Merit: 1006
Toomim Bros operates two p2pool nodes. We are planning on switching one of those nodes to use Bitcoin XT soon, and leave the other one on Bitcoin Core. That way, our customers can choose whichever node they want in order to make their own vote for how Bitcoin should be run. I'll let you know when we make those changes. Everyone is welcome to use these nodes, though you won't have great mining efficiency unless you're inside our datacenter.

We also will probably be changing our IP address for these nodes soon. I'll publish details about the new IP and which node will be using XT once we're ready to make the changes.

So far, Bitcoin Core (and consequently all Bitcoin protocol) development has progressed on a consensus model. All of the main developers have to agree to a change in order for it to take effect. For any important change, there will always be some people who are unhappy about it, so consensus only works for making important changes in oligarchies, and even in oligarchies, it doesn't work well. We at Toomim Bros think that decisions about how Bitcoin should operate ought to be democratized. As such, we support the existence of Bitcoin XT and think that all miners should have the option to choose which version they wish to support and use.

Toomim Bros also thinks that 1 MB is way too small, and that the network can and should support larger blocks. We think that one goal for Bitcoin should be minimizing the real cost per transaction. Currently, that cost is supported primarily by the block subsidy, and runs at about 65 kWh per transaction. (300 MW mining network, 1.27 transactions per second.) That's about $4 per transaction. Increasing the transaction volume would not directly require any significant increase in the mining network power consumption, so it would reduce the real cost per transaction. Our facility spends about 80x as much on electricity as it does on internet connectivity. We do not think large blocks will present a large burden on smaller bitcoin miners like us.

As such, we will be putting the miners owned by Toomim Bros (the company) and the Toomim brothers (the individuals) on XT soon.

Edit: We're running XT on our p2pool node 74.82.233.205:9334, and Core on our p2pool node 74.82.233.205:9332.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Sounds like a drug dealer Smiley
... come on ... you can change your mind later ... just try it ... it wont do anything ...
Um, if it does nothing, why bother?
legendary
Activity: 1258
Merit: 1027
Unless the changes forrestv recently made to support BIP66 also include support for BIP101 and the far larger block size, even if you are using an XT node, wouldn't you still be restricted?  Also, assuming the p2pool code does indeed support the larger blocks... what happens when any p2pool node on XT happens to find a block that is too large for inclusion on the blockchain?  Wouldn't the rest of the network reject it?

Hey JB, the switch (fork) wont happen until Jan 2016 if, and only if, 75% of all blocks mined come from XT, right now it's 0 risk and a way to support a block size increase.

BitcoinXT and Bitcoin Core both share the same data directories and block files, you can switch between XT and Core today with the same data directory with no problem at any time.

Download and fire up XT for a few minuets, it is largely the same as QT (there is a diff on git), with the exception of the scheduled fork in Jan 2016 (if 75% of mined blocks vote for it) and a couple other things outlined on the git repo.

If you don't like it for some reason, you can switch back to core in a matter of seconds...

legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Unless the changes forrestv recently made to support BIP66 also include support for BIP101 and the far larger block size, even if you are using an XT node, wouldn't you still be restricted?  Also, assuming the p2pool code does indeed support the larger blocks... what happens when any p2pool node on XT happens to find a block that is too large for inclusion on the blockchain?  Wouldn't the rest of the network reject it?
hero member
Activity: 798
Merit: 1000
Just wanted to share a couple things with everyone to maintain transparency:

1. I have been testing P2Pool with BitcoinXT on my development node, it works as expected with really no performance differences at all.

2. In the next couple weeks(TM) I'll be releasing Chain Query (alpha: http://chainquery.com) on Github, once thats done I plan to rewrite my P2Pool node front end to use Chain Query and MySQL (the core P2Pool code does not need to be altered) and will relaunch http://minefast.CoinCadence.com on BitcoinXT with the new front end. I will release the full source for the new front end on Github.

The switch to XT is a personal decision, and shows my support for scaling Bitcoin. I believe it is the right path.

If you don't like the idea of bigger blocks and mine on my node you are welcome to find another that runs Bitcoin Core, or run your own.

My intention is not to start some debate about block size in this thread, there is plenty of that elsewhere.

As P2Pool miners we vote with our hashrate, in the coming months that hashrate on my node will be running off of BitcoinXT.

I hope that many of you (P2Pool node operators) will join me in supporting Bitcoin's growth by voting with your hashrate, I know that some of you will not, and thats your choice.

And that's all I have to say about that. Wink

Cheers.



And that's why you've got my spare mining nodes pointed in your direction...
Let's hope more test the waters soon.  It will take much more than just us few on p2pool to bring mining consensus to BitcoinXT.
legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
...as can be seen, my usage rarely goes above 40kBs download & 34kBs upload, so running one p2pool node & one Bitcoin wallet is not a problem on even the slowest ADSL line. It's simply a case of setting maxconnections on your wallets & making sure your QOS settings are right, no changes to p2pool connections are needed - I use the standard settings. If you are still having bottleneck issues/slowdowns after checking your settings then it's time to buy a new router...... Wink

Edit: The only time you will drown your network is when you sync your wallets/p2pool (ie: restarts etc).

Possibly you are correct. I need to fire up league of legends, watch the ping and do some analysis. I have a very basic setup right now.

To be clear, it's not like the connection is swamped, it's just that gaming is sensitive. I need to take another look at the QOS because turning that on killed my p2p payouts back in the day. But I may have been over-throttling bitcoind.
legendary
Activity: 1512
Merit: 1012
For me, the next month ... i  have activate the pruning mode to restrict the Bitcoin Core installation at 50 Go : https://bitcointalksearch.org/topic/can-the-prune-mode-of-the-011-bitcoin-core-disrupt-the-bitcoin-network-1097636

For the block size, i wait the decision of BIP101 ... and stay at Bitcoin Core.
legendary
Activity: 1258
Merit: 1027

Thanks.

Mike Hearn just published what I think is an awesome article about it here:

https://medium.com/@octskyward/why-is-bitcoin-forking-d647312d22c1

You can get precompiled binaries for XT and more info here:

http://xtnodes.com/

And here is the XT repo:

https://github.com/bitcoinxt/bitcoinxt
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
Just wanted to share a couple things with everyone to maintain transparency:

1. I have been testing P2Pool with BitcoinXT on my development node, it works as expected with really no performance differences at all.

2. In the next couple weeks(TM) I'll be releasing Chain Query (alpha: http://chainquery.com) on Github, once thats done I plan to rewrite my P2Pool node front end to use Chain Query and MySQL (the core P2Pool code does not need to be altered) and will relaunch http://minefast.CoinCadence.com on BitcoinXT with the new front end. I will release the full source for the new front end on Github.

The switch to XT is a personal decision, and shows my support for scaling Bitcoin. I believe it is the right path.

If you don't like the idea of bigger blocks and mine on my node you are welcome to find another that runs Bitcoin Core, or run your own.

My intention is not to start some debate about block size in this thread, there is plenty of that elsewhere.

As P2Pool miners we vote with our hashrate, in the coming months that hashrate on my node will be running off of BitcoinXT.

I hope that many of you (P2Pool node operators) will join me in supporting Bitcoin's growth by voting with your hashrate, I know that some of you will not, and thats your choice.

And that's all I have to say about that. Wink

Cheers.



much thx windpath ! if there's a guide & some explanation of differences or why will be awesome.

i can give it a try to see how things goes.

whereisblock ? hungry !
Jump to: