I'm losing hope here... we lost 100 users which certainly isn't helping variance.
Any idea why that is?
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 434. (Read 2591964 times)
January 31, 2014, 11:30:05 PM
Any idea why that is?
January 31, 2014, 10:40:53 PM
I'm losing hope here... we lost 100 users which certainly isn't helping variance.
January 31, 2014, 09:11:15 PM
Had a nice conversation on irc about multiple payment address support in the share chain, and I can see why that might not be a good thing to support in a generalized way.
However I do want to suggest that the node fee be handled like donation with a special line in the share chain. It would only add 1 address to the share chain per share mined at a node with a fee, but the advantage is a node can't lie about the fee they are charging, and it reduces node and miner variance.
However I do want to suggest that the node fee be handled like donation with a special line in the share chain. It would only add 1 address to the share chain per share mined at a node with a fee, but the advantage is a node can't lie about the fee they are charging, and it reduces node and miner variance.
It would be nice to see the -fee system work based on bitcoins mined instead of shares. And it would be nice to specify if you only want the -fee to be applied to certain miners instead of the whole network. This way you don't need to worry about your own miner(s) having to pay the same fee.
Would also be nice to see more information on the minters, such as a estimate time to payout and the payout itself.
January 31, 2014, 08:53:34 PM
Had a nice conversation on irc about multiple payment address support in the share chain, and I can see why that might not be a good thing to support in a generalized way.
However I do want to suggest that the node fee be handled like donation with a special line in the share chain. It would only add 1 address to the share chain per share mined at a node with a fee, but the advantage is a node can't lie about the fee they are charging, and it reduces node and miner variance.
However I do want to suggest that the node fee be handled like donation with a special line in the share chain. It would only add 1 address to the share chain per share mined at a node with a fee, but the advantage is a node can't lie about the fee they are charging, and it reduces node and miner variance.
January 31, 2014, 06:13:46 PM
Is there any other front ends other than the extended front end for P2Pool?
I've seen a few. None that are like official public "download here" interfaces that I know of. For example here are a couple variations:
http://p2pool.etyd.org:9171/static/ (comes from http://sleipnir.syari.net/pool/)
http://q30.qhor.net:9171/static/
Edit: Found another one, with source.
https://github.com/johndoe75/p2pool-node-status
as used on:
http://bitcoin.p2pool.fr:9332/static/
Edit: Apparently the default extended inteface has some bugs, fixed by this version: https://github.com/blixnood/P2PoolExtendedFrontEnd
January 31, 2014, 05:45:28 PM
Is there any other front ends other than the extended front end for P2Pool?
January 31, 2014, 05:29:13 PM
To add support for multiple address shares, it'd basically be converting share_data.payout_addrress to a list (of addresses and amounts) and reflecting it correctly in block.gentx.coinbase as well. At least from my quick glance at the code so far. Does this sound right? Then of course handling the payout_address list properly in all spots.
There wouldn't seem to be a way to make this compatible with older nodes, so it'd have to be one of those features that doesn't activate until 95% of the nodes are on the minimum version that supports it.
There wouldn't seem to be a way to make this compatible with older nodes, so it'd have to be one of those features that doesn't activate until 95% of the nodes are on the minimum version that supports it.
January 31, 2014, 04:37:20 PM
hehe no problem, i think it is clear now. i havnt found enough shares then. so to get a payout of 1% of the shares i have to submit no less than 100 valid shares from this node. thank you very much! :-)
It's possible it's random, I don't know having not looked at the source code. So it might be every share has a 1% chance to go to the pool, or it might be every 100th share.
I looked it up, it is random. I play a card game where packs have a 1% chance of giving you a better card so I'm quite familiar with how much variance that can result in. So it's possible you might find 200-300 shares with no operator fee, or sometimes the node will find 100 shares and pay the node much more than 1%.
I wonder how difficulty it'd be for p2pool to support shares with multiple payment addresses. As I mentioned in an earlier way too long post, that could be used to both help address the variance of smaller miners and pay the operator exactly 1% of the shares found with less variance to the miners or the node operator.
January 31, 2014, 04:07:27 PM
hehe no problem, i think it is clear now. i havnt found enough shares then. so to get a payout of 1% of the shares i have to submit no less than 100 valid shares from this node. thank you very much! :-)
It's possible it's random, I don't know having not looked at the source code. So it might be every share has a 1% chance to go to the pool, or it might be every 100th share.
January 31, 2014, 03:41:12 PM
thank you both for your answer but i am not sure if i understand you correctly. i am mining on the node since 5 days or the last three blocks were found and this could be a to short timeframe? because the 1% is calculated on the whole p2pool submited shares and not 1% of my miners shares?
I guess it depends on how many total shares your node has found. That's the % that relates to node fee payment. For example, if in the last 5 days you found 200 shares, then about 2 of them should be in the node's name and 198 in the miner's name. Apologies for sometime saying "pool" instead of "node", I tend to think of nodes as pools, but that is confusing.
hehe no problem, i think it is clear now. i havnt found enough shares then. so to get a payout of 1% of the shares i have to submit no less than 100 valid shares from this node. thank you very much! :-)
January 31, 2014, 03:27:08 PM
thank you both for your answer but i am not sure if i understand you correctly. i am mining on the node since 5 days or the last three blocks were found and this could be a to short timeframe? because the 1% is calculated on the whole p2pool submited shares and not 1% of my miners shares?
I guess it depends on how many total shares your node has found. That's the % that relates to node fee payment. For example, if in the last 5 days you found 200 shares, then about 2 of them should be in the node's name and 198 in the miner's name. Apologies for sometime saying "pool" instead of "node", I tend to think of nodes as pools, but that is confusing.
January 31, 2014, 03:22:16 PM
Anybody care to answer my question?
i've setup my node and iam hashing with two ants and everything went well execpt my fee setting doesnt seem to work.
the address mentioned is on its own wallet, the income from the ants goes to another wallet. so it can not be an wallet feature. :-)
what iam doing wrong?
i've setup my node and iam hashing with two ants and everything went well execpt my fee setting doesnt seem to work.
Code:
python run_p2pool.py --fee 1.0 --address 18SeaFycUrSprGT7VejWTNhRaRP4Nf5Mgx
the address mentioned is on its own wallet, the income from the ants goes to another wallet. so it can not be an wallet feature. :-)
what iam doing wrong?
Remember that p2pool isn't set up to pay the fee on a per-block basis. What happen is 1% of your pool's shares will be paid in full to that address, and 99% of the pool's shares will go to the miner's address. If you just recently started it up, is it possible you haven't found enough shares for the 1% to end up in the pool's name yet?
thank you both for your answer but i am not sure if i understand you correctly. i am mining on the node since 5 days or the last three blocks were found and this could be a to short timeframe? because the 1% is calculated on the whole p2pool submited shares and not 1% of my miners shares?
January 31, 2014, 03:10:22 PM
Anybody care to answer my question?
i've setup my node and iam hashing with two ants and everything went well execpt my fee setting doesnt seem to work.
the address mentioned is on its own wallet, the income from the ants goes to another wallet. so it can not be an wallet feature. :-)
what iam doing wrong?
i've setup my node and iam hashing with two ants and everything went well execpt my fee setting doesnt seem to work.
Code:
python run_p2pool.py --fee 1.0 --address 18SeaFycUrSprGT7VejWTNhRaRP4Nf5Mgx
the address mentioned is on its own wallet, the income from the ants goes to another wallet. so it can not be an wallet feature. :-)
what iam doing wrong?
Remember that p2pool isn't set up to pay the fee on a per-block basis. What happen is 1% of your pool's shares will be paid in full to that address, and 99% of the pool's shares will go to the miner's address. If you just recently started it up, is it possible you haven't found enough shares for the 1% to end up in the pool's name yet?
January 31, 2014, 03:09:32 PM
Anybody care to answer my question?
i've setup my node and iam hashing with two ants and everything went well execpt my fee setting doesnt seem to work.
the address mentioned is on its own wallet, the income from the ants goes to another wallet. so it can not be an wallet feature. :-)
what iam doing wrong?
i've setup my node and iam hashing with two ants and everything went well execpt my fee setting doesnt seem to work.
Code:
python run_p2pool.py --fee 1.0 --address 18SeaFycUrSprGT7VejWTNhRaRP4Nf5Mgx
the address mentioned is on its own wallet, the income from the ants goes to another wallet. so it can not be an wallet feature. :-)
what iam doing wrong?
Nothing you must wait. Be patient
January 31, 2014, 03:05:04 PM
Anybody care to answer my question?
i've setup my node and iam hashing with two ants and everything went well execpt my fee setting doesnt seem to work.
the address mentioned is on its own wallet, the income from the ants goes to another wallet. so it can not be an wallet feature. :-)
what iam doing wrong?
i've setup my node and iam hashing with two ants and everything went well execpt my fee setting doesnt seem to work.
Code:
python run_p2pool.py --fee 1.0 --address 18SeaFycUrSprGT7VejWTNhRaRP4Nf5Mgx
the address mentioned is on its own wallet, the income from the ants goes to another wallet. so it can not be an wallet feature. :-)
what iam doing wrong?
January 30, 2014, 09:33:01 PM
Is the opening of ports 9333 and 9332 on the firewall only TCP or does UDP need to be open as well?
No, just TCP
Then I am not sure why the bitcoin graph on one of my miners doesn't update when the miner is outside my network, but it does update when the miner is inside the network. The hashing graph works while the miner is inside and or outside the network?
Almost certainly some other kind of network configuration problem. Firewall still not right, bad gateway, netmask, etc.
Well all I can think of is that there is some extra port that needs to be opened for the traffic to be allowed in as it works inside the LAN, but only hashing works from the outside, not the bitcoin graph which is supposedly related to shares according to someone else on github, if that's the case than why would miner get shares inside the network but not from the outside connection?
January 30, 2014, 08:43:07 PM
Is the opening of ports 9333 and 9332 on the firewall only TCP or does UDP need to be open as well?
No, just TCP
Then I am not sure why the bitcoin graph on one of my miners doesn't update when the miner is outside my network, but it does update when the miner is inside the network. The hashing graph works while the miner is inside and or outside the network?
Almost certainly some other kind of network configuration problem. Firewall still not right, bad gateway, netmask, etc.
January 30, 2014, 08:34:13 PM
Is the opening of ports 9333 and 9332 on the firewall only TCP or does UDP need to be open as well?
No, just TCP
Then I am not sure why the bitcoin graph on one of my miners doesn't update when the miner is outside my network, but it does update when the miner is inside the network. The hashing graph works while the miner is inside and or outside the network?
January 30, 2014, 07:46:40 PM
Is the opening of ports 9333 and 9332 on the firewall only TCP or does UDP need to be open as well?
No, just TCP
January 30, 2014, 06:56:51 PM
Is the opening of ports 9333 and 9332 on the firewall only TCP or does UDP need to be open as well?
Jump to: