I[f] You are so worried about P2pool performance why don't you chan[g]e [the] master branch ?
The jtoomimnet code works fine for Bitcoin, but currently does not appear to work with altcoins. P2pool master must support altcoins, so until I make my code work with alts, I will not try to merge my code into master. I intend to address this, but my time is finite, so I haven't done it yet. 
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 23. (Read 2591916 times)
September 04, 2017, 05:56:07 PM
September 04, 2017, 04:16:01 PM
Increasing the new txs size/share limit is sticking your head in the sand about attack vectors. Unless of course your use case is a private pool aided by other hashers.
I do not consider making all users of p2pool receive and transmit up to 1 MB of data every 30 seconds (on average, assuming the attacker has 100% of the hashrate) to be an attack vector. Veqtrus keeps repeating that claim as if 1 MB is a lot of data. It's not.If you have at least 4 Mbps of upstream and downstream bandwidth available that can be used by p2pool during an adversarial attack, then you can easily survive the "DoS attack" that veqtrus is so worried about. 4 Mbps is enough to receive a new 1MB share in about 2 seconds, in theory. It should be enough to allow you to keep up with the network okay if the share download time is 1/15th of the average share interval.
I consider 4 Mbps to be a reasonable minimum HW spec for p2pool, especially if it only applies to adversarial conditions with an attacker controlling nearly 100% of the hashrate. I really don't get why veqtrus is making such a big fuss about it.
For reference, in non-adversarial conditions, my p2pool nodes on jtoomimnet are each currently using around 13.3 KB/s (0.1 Mbps) in each direction, averaged over the last week.
September 03, 2017, 07:22:55 PM
Well that's an unexpected thing for you to imply about p2pool ... ... ...
Of course centralized solutions are more efficient, you don't need jtoomim's fork for that.
You have no one else but you mining on your p2pool?
I hope so, otherwise you are running a centralised p2pool ... controlling all those miners mining on your p2pool ...
September 03, 2017, 06:08:48 PM
In C there only is this folder
https://en.bitcoin.it/wiki/Data_directory
bitcoin.conf must be in the blockchain directory where you has the blocks directory, too (local blockchain).
blockchain directory have wallet.dat, adresses.dat, banlist.dat, etcs ... and bitcoin.conf that you must create (not provide by the setup of Bitcoin Core).
September 03, 2017, 10:38:58 AM
Well that's an unexpected thing for you to imply about p2pool ... ... ...
Of course centralized solutions are more efficient, you don't need jtoomim's fork for that. September 03, 2017, 10:37:03 AM
In the . conf what i have to exactly write? I found several versions.
Where is your blockchain downloaded? September 03, 2017, 10:26:51 AM
Coz he is more worried about the problems with p2pool and doing something about them, rather than sticking his head in the sand.
Increasing the new txs size/share limit is sticking your head in the sand about attack vectors. Unless of course your use case is a private pool aided by other hashers.Your basically scamming people when you say that they'll earn more on p2pool, since they wont for a number of specific reasons including:
1) mining fee of between 0% and 1% (varies per block found and if you run your own node or use someone else's)
2) lost transaction fees since 39% of blocks will average under 1MB, though that's no longer the block size limit on other pools
3) inequalities for all but the largest miner on p2pool - unlike all private pools that don't have their miners battle over submitted shares, no matter the size of the miner
4) current pool size gives an expected share payout based on multiple diff changes - which are 'usually' increasing, though at the moment there appears to be a short term of it dropping
So basically your saying p2pool has an attack vector that implies no one should use p2pool - since either
1) jtoomim's changes that resolve some of the above are dangerous
2) your version ensures poor payouts due to all the above
Well that's an unexpected thing for you to imply about p2pool ... ... ...
September 03, 2017, 10:26:08 AM
In this folder "E:\Program Files\Bitcoin" in which there is bitcoin-qt.exe. But isn't normal that p2pool crashes in so short time always.
P2Pool tells you to create it in "C:\Users\User1\AppData\Roaming\Bitcoin" where your bitcoind data folder is.There isn' t any "C:\Users\User1\AppData\Roaming\Bitcoin".
In the . conf what i have to exactly write? I found several versions.
September 03, 2017, 10:15:43 AM
In this folder "E:\Program Files\Bitcoin" in which there is bitcoin-qt.exe. But isn't normal that p2pool crashes in so short time always.
P2Pool tells you to create it in "C:\Users\User1\AppData\Roaming\Bitcoin" where your bitcoind data folder is. September 03, 2017, 10:09:03 AM
I made the txt saved .conf in the bitcoin core folder.
Where exactly? P2Pool doesn't seem to find it. September 03, 2017, 09:56:55 AM
I made the txt saved .conf in the bitcoin core folder.
Where exactly? P2Pool doesn't seem to find it. September 03, 2017, 09:41:10 AM
i have a problem, i'm using Windows 10. When i open p2pool after less than one second it crashes, sometimes displaying something that i captured with a program. https://ibb.co/ghVFBv
I installed phyton 2.7.13, GCC 4.3.3, WMI-1.4.9.win32, pywin32-218.win32-py2.7, zope and twisted. And i have the latest bitcoin core version updated. I made the txt saved .conf in the bitcoin core folder.
Can someone help me?
Thanks
I installed phyton 2.7.13, GCC 4.3.3, WMI-1.4.9.win32, pywin32-218.win32-py2.7, zope and twisted. And i have the latest bitcoin core version updated. I made the txt saved .conf in the bitcoin core folder.
Can someone help me?
Thanks
September 03, 2017, 08:58:28 AM
Coz he is more worried about the problems with p2pool and doing something about them, rather than sticking his head in the sand.
Increasing the new txs size/share limit is sticking your head in the sand about attack vectors. Unless of course your use case is a private pool aided by other hashers. September 02, 2017, 08:21:29 PM
I don't think he his worried about the problems that divide p2pool.And i can' t find one node with his 1 mb fork that's on the master branch.
you won't ...
September 02, 2017, 07:57:15 PM
These spikes in hashrate are from people renting hashrate from Nicehash, usually to take advantage of merged mining income. As is often the case with Nicehash renters, this person seems to have had high DOA rates (~10%) during his hashing burst, which would subtract from his profitability. My guess is that the DOA rates this miner is getting are higher or equal to the revenue bonus he is getting from the merged mining, which means that he will probably stop after he has re-evaluated his profitability using experimental data instead of his predicted revenue.
If anyone is thinking of doing a Nicehash burst on p2pool, I suggest they let me know first. There are a few configuration changes they can make in order to improve their node performance, and there are also some code changes I've got on my to-do list that will improve fairness for miners with high vs. low hashrate and high vs. low latency.
I You are so worried about P2pool performance why don't you chance to the master branch ?If anyone is thinking of doing a Nicehash burst on p2pool, I suggest they let me know first. There are a few configuration changes they can make in order to improve their node performance, and there are also some code changes I've got on my to-do list that will improve fairness for miners with high vs. low hashrate and high vs. low latency.
September 02, 2017, 07:42:07 PM
These spikes in hashrate are from people renting hashrate from Nicehash, usually to take advantage of merged mining income. As is often the case with Nicehash renters, this person seems to have had high DOA rates (~10%) during his hashing burst, which would subtract from his profitability. My guess is that the DOA rates this miner is getting are higher or equal to the revenue bonus he is getting from the merged mining, which means that he will probably stop after he has re-evaluated his profitability using experimental data instead of his predicted revenue.
If anyone is thinking of doing a Nicehash burst on p2pool, I suggest they let me know first. There are a few configuration changes they can make in order to improve their node performance, and there are also some code changes I've got on my to-do list that will improve fairness for miners with high vs. low hashrate and high vs. low latency.
I You are so worried about P2pool performance why don't you chance to the master branch ?If anyone is thinking of doing a Nicehash burst on p2pool, I suggest they let me know first. There are a few configuration changes they can make in order to improve their node performance, and there are also some code changes I've got on my to-do list that will improve fairness for miners with high vs. low hashrate and high vs. low latency.
September 02, 2017, 07:30:49 PM
These spikes in hashrate are from people renting hashrate from Nicehash, usually to take advantage of merged mining income. As is often the case with Nicehash renters, this person seems to have had high DOA rates (~10%) during his hashing burst, which would subtract from his profitability. My guess is that the DOA rates this miner is getting are higher or equal to the revenue bonus he is getting from the merged mining, which means that he will probably stop after he has re-evaluated his profitability using experimental data instead of his predicted revenue.
If anyone is thinking of doing a Nicehash burst on p2pool, I suggest they let me know first. There are a few configuration changes they can make in order to improve their node performance, and there are also some code changes I've got on my to-do list that will improve fairness for miners with high vs. low hashrate and high vs. low latency.
I You are so worried about P2pool performance why don't you chance to the master branch ? If anyone is thinking of doing a Nicehash burst on p2pool, I suggest they let me know first. There are a few configuration changes they can make in order to improve their node performance, and there are also some code changes I've got on my to-do list that will improve fairness for miners with high vs. low hashrate and high vs. low latency.
September 02, 2017, 06:46:23 PM
OMG
Global hash rate of 666TH...That's EVIL.....
So much reading to catch up...
Sad to see p2 is not more popular...seems to have some serious drawbacks as well.
Global hash rate of 666TH...That's EVIL.....
So much reading to catch up...
Sad to see p2 is not more popular...seems to have some serious drawbacks as well.
September 02, 2017, 05:51:36 PM
... and there are also some code changes I've got on my to-do list that will improve fairness for miners with high vs. low hashrate and high vs. low latency.
I'm eagerly waiting for this one. My two AvalonMiner 741's are bleeding me out with an average DOA rate of around 15% on my PyPy P2Pool node, no thanks to their sluggishness in keeping up with P2Pool's frequent work changes.
September 02, 2017, 12:06:12 PM
jtoomim
what was the pool hashrate before you got jtoomimnet up and running ...
what was the pool hashrate before you got jtoomimnet up and running ...
Jump to: