Pages:
Author

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

newbie
Activity: 8
Merit: 0
Hey people,

is there an overview or an way to see all blockfounds of on pool ?
Somethink like p2pool fiund block on date Y  and on date Y.

all i found is the mined blocks of the last few hours.


yes you can check:
https://www.blocktrail.com/BTC/pool/p2pool
hero member
Activity: 818
Merit: 1006
^ jtoomimnet BTC block. This was p2pool's biggest block yet, at 1288.919 kB. It only brought in 0.07 BTC of fee revenue, though.
hero member
Activity: 818
Merit: 1006
newbie
Activity: 43
Merit: 0
Hey people,

is there an overview or an way to see all blockfounds of on pool ?
Somethink like p2pool fiund block on date Y  and on date Y.

all i found is the mined blocks of the last few hours.
legendary
Activity: 1308
Merit: 1011
full member
Activity: 142
Merit: 100
chrismaster...You actually have a rock solid pool right now. Advertise in your post above and more will show up.   I see both my miners mining with you together with other BCH miners.
More hash on its way in a day or 2

thx for support ;-)
hero member
Activity: 726
Merit: 504
chrismaster...You actually have a rock solid pool right now. Advertise in your post above and more will show up.   I see both my miners mining with you together with other BCH miners.
More hash on its way in a day or 2
full member
Activity: 142
Merit: 100
How do i mine with more workers on a p2pool ?

same address for all workers ? Is that a problem ?
full member
Activity: 933
Merit: 175
Hi guys,

I would like to setup p2pool for FTO (Futurocoin). It's fork of Dash. Which p2pool source code should I use for that?
full member
Activity: 124
Merit: 251
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.

p2pool.io has been moved back to forrestv's p2pool/p2pool@master branch. (The original P2Pool)
hero member
Activity: 818
Merit: 1006
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
legendary
Activity: 1308
Merit: 1011
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
full member
Activity: 932
Merit: 100
arcs-chain.com
Where is documentation for downloading and configuring jtoomin p2pool node?
legendary
Activity: 1308
Merit: 1011
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.
hero member
Activity: 818
Merit: 1006
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.
Pages:
Jump to: