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

[veqtrus]

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.

[1714200060]

1714200060

[Scorpion21]

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

[veqtrus]

I made the txt saved .conf in the bitcoin core folder.

Where exactly? P2Pool doesn't seem to find it.

[Scorpion21]

I made the txt saved .conf in the bitcoin core folder.

Where exactly? P2Pool doesn't seem to find it.

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.

[veqtrus]

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.

[Scorpion21]

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.

In C there only is this folder "C:\Users\User1\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Bitcoin Core" in which i also place the .conf. In this folder there are only 3 links to the other folder in E, because C is the primary partition.

There isn' t any "C:\Users\User1\AppData\Roaming\Bitcoin".

In the . conf what i have to exactly write? I found several versions.

[kano]

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.

Well if you consider than 39% of blocks will be less than 1MB, then p2pool can't compete with any other pool that always mines full blocks ... and that's of course ignoring the other problems he's trying to resolve.

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

[veqtrus]

In the . conf what i have to exactly write? I found several versions.

Where is your blockchain downloaded?

[veqtrus]

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.

[Meuh6879]

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

[kano]

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.

Yep people do it all the time with the main p2pool fork

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

[jtoomim]

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.

[jtoomim]

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.

[uwuplent]

Could I have some help? Blockchain is sync'd, bitcoind is turned on, and this error occurs. (Ports are already open.) https://uwu.s-ul.eu/BOcxTgk8.png

Edit: Now I'm getting 401 Unauthorized. Tried to edit conf file. Here are contents:

Code:

server=1
rpcuser=meme
rpcpassword=meme
rpcallowip=192.168.*

[jtoomim]

Both bitcoind and p2pool read the same configuration file. If you change the ~/.bitcoin/bitcoin.conf file and restart p2pool, then p2pool will be using the new credentials but bitcoind will still be using the old ones. Try restarting bitoind.

[nikoluz123]

I want to know how I calculate my share based on the pool. From what I am understanding, if i am contributing 15gh/s and the pool has for example 60gh/s hashing power, i am paid based on the percentage of my computing power on the total pool. However I see this pool hashing power and "net" hashing power. I see that the net hashing power is bigger than the pool hashing power. Do i divide my hashing power in the pool's hashing power or the net hashing power?

[jtoomim]

It seems you're using the word "share" to mean "portion", but in mining "share" means something different. A share is a data object used to prove that a miner has done some mining work. Mining for shares is the same as mining for blocks with the exception that blocks have a more difficult threshold for the hash. With p2pool right now, it is 196,426 times as difficult to find a Bitcoin block as it is to find a p2pool share.

Some of your hashpower isn't counted as part of the net (or "good") hashpower. Some of everyone else's hashpower isn't counted as part of the good hashpower either. Your percentage equals your good hashpower divided by the pool's total good hashpower.

If a share has been found by another p2pool miner and received by your p2pool node, then any hashes that your hardware does on the old share is considered DOA (dead on arrival) hashes. If you find a share at around the same time as another miner finds a share (both using the same parent share), then only one of those two shares can be included in the share chain, and the other becomes an orphan share. The share chain is what is used to calculate your total portion of the block reward. If there are 8640 shares in the share chain, and if they all have the same difficulty, and if you have 86 shares in the share chain at the moment a block was found, you would get 1% of the block reward.

On the other hand, the hashpower that is used for making blocks is not simply the good hashpower, but all hashpower. If a person finds a DOA share that also meets the Bitcoin block threshold, it still is a valid block even though it isn't a good share, and everyone in p2pool will get paid as a result of it. Same thing for orphan shares -- if a share meets the block difficulty threshold, it will still give payouts even if it doesn't make it into the share chain.

[veqtrus]

I consider 4 Mbps to be a reasonable minimum HW spec for p2pool

Yes, this is indeed a reasonable spec for a private pool.

[jtoomim]

veqtrus, is it your opinion that people should be able to mine on p2pool via ISDN?

Even if that makes p2pool economically unviable for everybody who has something better than ISDN (who can get better profits on a private pool) as well as everyone who *does* have ISDN (who can get better profits with less bandwidth on a private pool)?

[Scorpion21]

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

I create the file in the principal folder i will check if this files are in a subfolder. Now i have to use another computer for 2 days or maybe for months  so i have to redownload the blockchain and everything on the computer that i actually use. When i finish i will try again