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

[ooncan]

hi Jtoomim,

we started to mine in your server since your advice to "kbirand". And also we are starting to test our local node based on jtoomimnet. We took several data from your site and your api codes but we can not find what is the last found block number from jtoomimnet.
"http://crypto.office-on-the.net:9334/recent_blocks" this code does not return it.
we need the learn probability distribution of your pool with this hash rates.
thanks for kindly support and your great job
regards,
Ozgur

[1714196827]

1714196827

[jtoomim]

recent_blocks will return any blocks found in the last 24 or 72 hours (depending on the software version -- I changed it recently). If no blocks have been found in the last 72 hours, then the most recent block is not recent, and it doesn't show up there. Since the expected time per block is currently around 20 days on jtoomimnet and 80 days on mainnet, recent_blocks will usually show nothing at all.

https://blockchain.info/address/1Kz5QaUPDtKrj5SqW5tFkn7WZh8LmQaQi4 is a list of all Bitcoin p2pool blocks found. This includes both jtoomimnet and mainnet.

[kbirand]

recent_blocks will return any blocks found in the last 24 or 72 hours (depending on the software version -- I changed it recently). If no blocks have been found in the last 72 hours, then the most recent block is not recent, and it doesn't show up there. Since the expected time per block is currently around 20 days on jtoomimnet and 80 days on mainnet, recent_blocks will usually show nothing at all.

https://blockchain.info/address/1Kz5QaUPDtKrj5SqW5tFkn7WZh8LmQaQi4 is a list of all Bitcoin p2pool blocks found. This includes both jtoomimnet and mainnet.

So there is no way to filter mainnet and jtoomimnet ..
https://www.blocktrail.com/BTC/pool/p2pool
So this link is also showing both  mainnet and jtoomimnet..

Ohh one other question... The last block was found on the 31st of December... So no blocks both for jtoomimnet and mainnet for the lat 30 days.
Then how does "since the expected time per block is currently around 20 days on jtoomimnet" that apply ?

Thanks,
Koray Birand

[jtoomim]

There's no 100% reliable way to filter mainnet and jtoomimnet. The jtoomimnet blocks have different users and different payment addresses (e.g. the 1GuDN address) than mainnet, so you can do it manually if you'd like.

Ohh one other question... The last block was found on the 31st of December... So no blocks both for jtoomimnet and mainnet for the lat 30 days.
Then how does "since the expected time per block is currently around 20 days on jtoomimnet" that apply ?

It's probabilistic. Luck is involved. Sometimes it takes less than the expected value. Sometimes it takes more. It's the same as how Bitcoin has 10 minute blocks on average, but sometimes it takes an hour between blocks, and sometimes it's only 2 minutes.

https://www.khanacademy.org/math/statistics-probability/random-variables-stats-library/poisson-distribution/v/poisson-process-1

[sawa]

The developers changed the address format to bech32 on BCH version 0.16.2 (https://download.bitcoinabc.org/0.16.2/win/).
jtoomim, will BCH p2pool be able to work with this address format?
If not, then please add the possibility of running p2pool with bech32 address format.

[jtoomim]

I don't have time to give p2pool the ability to parse the new address format right now. Old addresses still work. Internally, Bitcoin (Cash) software converts the address format into a public key, and the pubkey is what is encoded in the transactions. The pubkeys have not changed.

If you tell p2pool to mine to an old-style p2pkh address and are using a wallet that only supports CashAddr addresses, you can use https://cashaddr.bitcoincash.org/ to convert between them.

If someone is able to add CashAddr support in a pull request, I would be most appreciative.

[Tornado_of_Coins]

Jt, your probably tired of sounding like a broken record but I have my S9's configured as such
stratum+tcp://ml.toom.im:9332
stratum+tcp://ml.toom.im:9334
stratum+tcp://ml.toom.im:9336
Is this correct, does it matter? Im still learning and there's no manual that explains the why of things.

[Acejam]

I have updated p2pool.io to use jtoomim's 1mb_segwit fork. p2pool.io:9332 is still based on Bitcoin core.

I have also deployed ltc.p2pool.io:9327 for Litecoin mining using the same fork and have plans to add several more coins very soon.

[jtoomim]

Jt, your probably tired of sounding like a broken record but I have my S9's configured as such

You should not use my nodes (ml.toom.im:933x) for all three pools. If my internet connection goes down and you're only using my nodes, then your machines will stop mining.

[jtoomim]

Someone put about 3.5 PH/s onto the BCH p2pool around 30 hours ago. Current hashrate for BCH is around 4.4 PH/s, with an expected time to block of 3.7 days.

[Tornado_of_Coins]

I have updated p2pool.io to use jtoomim's 1mb_segwit fork. p2pool.io:9332 is still based on Bitcoin core.

I have also deployed ltc.p2pool.io:9327 for Litecoin mining using the same fork and have plans to add several more coins very soon.

Thanks for heads up

[Tornado_of_Coins]

Jt, your probably tired of sounding like a broken record but I have my S9's configured as such

You should not use my nodes (ml.toom.im:933x) for all three pools. If my internet connection goes down and you're only using my nodes, then your machines will stop mining.

Ok, I see. I thought that the each pool was using a set of chips 189/3 for mining for some reason.

[sawa]

jtoomim, I forked and uploaded branch 1mb_segwit of your p2pool on https://github.com/ilsawa/p2pool-jtoomim
This works with the latest versions of the wallets.
I added autodiff & DUMB_SCRYPT_DIFF pathes.
Those who wish can use the pruned blockchain (configuration examples for demons with a pruned blockchain in README.md)

[jtoomim]

Those who wish can use the pruned blockchain (configuration examples for demons with a pruned blockchain in README.md)

The check_block_header function (which uses the getblockheader RPC method) is already compatible with pruned blockchains. It's only the getblock RPC that fails on pruned blockchains. The commit you made to change the initialization routine will allow people to use the wrong daemon at startup (e.g. Bitcoin ABC on the regular BTC network) and is dangerous.

For reference, I added support for pruned mode in this commit, with the fork protection and some renaming done here.

You don't need to change the RPC port in both e.g. ~/.litecoin/litecoin.conf and int p2pool/bitcoin/networks/litecoin.py. Changing it in the latter is probably a bad idea, actually. P2pool already checks litecoin.conf for non-default settings, and if any are present (e.g. RPC password or port changes) p2pool will use the litecoin.conf settings instead of the litecoin.py settings. It's only if the user has not changed the default port that p2pool will use the litecoin.py settings. If that's the case, then litecoin.py should point p2pool to the actual default litecoin ports, which are 9333/9332 not 10333/10332. The same applies for Bitcoin Cash.

[sawa]

Those who wish can use the pruned blockchain (configuration examples for demons with a pruned blockchain in README.md)

The check_block_header function (which uses the getblockheader RPC method) is already compatible with pruned blockchains. It's only the getblock RPC that fails on pruned blockchains. The commit you made to change the initialization routine will allow people to use the wrong daemon at startup (e.g. Bitcoin ABC on the regular BTC network) and is dangerous.

For reference, I added support for pruned mode in this commit, with the fork protection and some renaming done here.

Thank you, I agree. Your method is good.
I'll return it.

[nreal]

Where is documentation for downloading and configuring jtoomin p2pool node?

[sawa]

Those who wish can use the pruned blockchain (configuration examples for demons with a pruned blockchain in README.md)

The check_block_header function (which uses the getblockheader RPC method) is already compatible with pruned blockchains. It's only the getblock RPC that fails on pruned blockchains. The commit you made to change the initialization routine will allow people to use the wrong daemon at startup (e.g. Bitcoin ABC on the regular BTC network) and is dangerous.

For reference, I added support for pruned mode in this commit, with the fork protection and some renaming done here.

I did a more thorough rpc check https://github.com/ilsawa/p2pool-jtoomim/commit/e7d0a252c2401dabc63f29adfd4dbaf9a2f0efc0

You have it will not work with new wallets https://github.com/jtoomim/p2pool/blob/1mb_segwit/p2pool/bitcoin/networks/bitcoin.py#L18

Code:

not (yield bitcoind.rpc_getinfo ()) ['testnet']

I'm interested to hear what you think about this commit: https://github.com/ilsawa/p2pool-jtoomim/commit/342a7bbb9e3a13a2583722811751c5819c033fb3

And please add this commit to your repository:
https://github.com/ilsawa/p2pool-jtoomim/commit/e43f9e295d1c398b056db40bb1cf5736cab44fcd

[jtoomim]

1st block mined on BCH!

https://www.blocktrail.com/BCC/block/00000000000000000242abe408a650a10eaf356f4547bb3e91a3e7033d57b6d2

[sawa]

1st block mined on BCH!

https://www.blocktrail.com/BCC/block/00000000000000000242abe408a650a10eaf356f4547bb3e91a3e7033d57b6d2

Thank you for your work.

[jtoomim]

Hmm, it looks like the coinbase transaction in that BCH p2pool block is causing Electron-cash to crash. Block explorers seem to be fine with it, though. Is anyone else having issues with it? If so, what wallet are you using? Are you able to access that transaction fine? If so, what wallet are you using?

Edit: This has been tracked down to a bug in Electron-cash which, apparently, has been fixed.
https://github.com/fyookball/electrum/issues/542