Depends on how quickly our found block, propagates through the bitcoin network. Size and complexity of the block can contribute to how long it takes, but being decentralized, we will still expect orphans.
-- Smoov
Topic: P2Pool Server List - page 16. (Read 106702 times)
the rest of the network seems pretty inefficient, w/ 9% stales... so i guess 110% efficiency isn't all that great
i mean, i get 200ms ping times there anyway
That efficiency, relates to the share chain. If your own efficiency, is in line with the whole network's efficiency rate, then you are where you should be as far as getting your average number of shares.i mean, i get 200ms ping times there anyway
With a decentralized network, and the rapid rate shares are generated, ~9% of stale/dead shares isn't unusual.
For example, this is my efficiency right now --> Efficiency: ~75.6% (46-96%)
I restarted p2pool a little while ago, so it doesn't have a lot of shares to give a very accurate efficiency yet, however, the pool's efficiency (100% - stale rate%), of 90.2% (stale rate 9.8%), is within my margin for error, 46-96%, so for now, I'm ok. As I get more shares, that spread will get smaller, narrowing down what my actual efficiency is.
As long as my spread, stays where the pool's efficiency falls within my spread, then my proportion of shares should be ok.
-- Smoov
I also couldn't help but to notice:
https://blockchain.info/block-index/240513/000000000000081b10d5246d813087641b51dcbf1711934ed7cde45164409425
vs
https://blockchain.info/block/000000000000024287811f3979c34b1bc45df06184d276c8998647f46920bae3
so it's sending 200kb of data every time someone finds a share on the network, i guess that would cause a lot of stales?
the rest of the network seems pretty inefficient, w/ 9% stales... so i guess 110% efficiency isn't all that great
i mean, i get 200ms ping times there anyway
That efficiency, relates to the share chain. If your own efficiency, is in line with the whole network's efficiency rate, then you are where you should be as far as getting your average number of shares.i mean, i get 200ms ping times there anyway
With a decentralized network, and the rapid rate shares are generated, ~9% of stale/dead shares isn't unusual.
For example, this is my efficiency right now --> Efficiency: ~75.6% (46-96%)
I restarted p2pool a little while ago, so it doesn't have a lot of shares to give a very accurate efficiency yet, however, the pool's efficiency (100% - stale rate%), of 90.2% (stale rate 9.8%), is within my margin for error, 46-96%, so for now, I'm ok. As I get more shares, that spread will get smaller, narrowing down what my actual efficiency is.
As long as my spread, stays where the pool's efficiency falls within my spread, then my proportion of shares should be ok.
-- Smoov
the rest of the network seems pretty inefficient, w/ 9% stales... so i guess 110% efficiency isn't all that great
i mean, i get 200ms ping times there anyway
i mean, i get 200ms ping times there anyway
well, since you seem to know how this works..
What exactly does the 'efficiency' rating indicate?
it has me bumpuzzled
That measures the percentage of dead/orphan shares you have in comparison to the average of the rest of the network. What exactly does the 'efficiency' rating indicate?
it has me bumpuzzled
That's not how the merged mining works...
Only the primary coin is pooled with the share chain, so computers mining off of your p2pool, can use a specific address, and their address will be injected into the chain, instead of yours, for payouts. Your primary coin would be BTC or LTC depending on the network you set it up for.
All of your --merged mining coins, however, are not pooled. You are strictly solo mining those. You would get the rewards on those. No address gets passed from the miner to the --merged coin.
Anyone mining on your node, would be donating their hash power, towards your solo mining the --merged coin. If you wanted to distribute your --merged coin to the people mining on your node, you have to do that externally, p2pool does not support that.
-- Smoov
well, since you seem to know how this works..Only the primary coin is pooled with the share chain, so computers mining off of your p2pool, can use a specific address, and their address will be injected into the chain, instead of yours, for payouts. Your primary coin would be BTC or LTC depending on the network you set it up for.
All of your --merged mining coins, however, are not pooled. You are strictly solo mining those. You would get the rewards on those. No address gets passed from the miner to the --merged coin.
Anyone mining on your node, would be donating their hash power, towards your solo mining the --merged coin. If you wanted to distribute your --merged coin to the people mining on your node, you have to do that externally, p2pool does not support that.
-- Smoov
What exactly does the 'efficiency' rating indicate?
it has me bumpuzzled
i have one that's just running for no purpose really myself,
it's at 5.9.24.81:9332
username set to whatever your payout address is
uh, it's also set for merged mining with namecoins. although as i understand it, you'd actually have to solve a namecoin block and then you'd get ~50nmc.
fee is 0%
it's located in falkenstein, germany
and i'm running the latest bitcoind, 0.6.3rc1
i think it works!
it's at 5.9.24.81:9332
username set to whatever your payout address is
uh, it's also set for merged mining with namecoins. although as i understand it, you'd actually have to solve a namecoin block and then you'd get ~50nmc.
fee is 0%
it's located in falkenstein, germany
and i'm running the latest bitcoind, 0.6.3rc1
i think it works!
oh, and your namecoin address has to be the same as your bitcoin address
which leads to all sorts of shenanigans, which i'm not going to trifle with!
Only the primary coin is pooled with the share chain, so computers mining off of your p2pool, can use a specific address, and their address will be injected into the chain, instead of yours, for payouts. Your primary coin would be BTC or LTC depending on the network you set it up for.
All of your --merged mining coins, however, are not pooled. You are strictly solo mining those. You would get the rewards on those. No address gets passed from the miner to the --merged coin.
Anyone mining on your node, would be donating their hash power, towards your solo mining the --merged coin. If you wanted to distribute your --merged coin to the people mining on your node, you have to do that externally, p2pool does not support that.
-- Smoov
oh, and your namecoin address has to be the same as your bitcoin address
which leads to all sorts of shenanigans, which i'm not going to trifle with!
No, you as the node operator get all the merged mining profits unless you set up a way to distribute them.which leads to all sorts of shenanigans, which i'm not going to trifle with!
i guess i could manually send them out.
i set that up on a whim, it seems like p2pool isn't very efficient, anyway
oh, and your namecoin address has to be the same as your bitcoin address
which leads to all sorts of shenanigans, which i'm not going to trifle with!
No, you as the node operator get all the merged mining profits unless you set up a way to distribute them. which leads to all sorts of shenanigans, which i'm not going to trifle with!
i have one that's just running for no purpose really myself,
it's at 5.9.24.81:9332
username set to whatever your payout address is
uh, it's also set for merged mining with namecoins. although as i understand it, you'd actually have to solve a namecoin block and then you'd get ~50nmc.
fee is 0%
it's located in falkenstein, germany
and i'm running the latest bitcoind, 0.6.3rc1
i think it works!
it's at 5.9.24.81:9332
username set to whatever your payout address is
uh, it's also set for merged mining with namecoins. although as i understand it, you'd actually have to solve a namecoin block and then you'd get ~50nmc.
fee is 0%
it's located in falkenstein, germany
and i'm running the latest bitcoind, 0.6.3rc1
i think it works!
oh, and your namecoin address has to be the same as your bitcoin address
which leads to all sorts of shenanigans, which i'm not going to trifle with!
i have one that's just running for no purpose really myself,
it's at 5.9.24.81:9332
username set to whatever your payout address is
uh, it's also set for merged mining with namecoins. although as i understand it, you'd actually have to solve a namecoin block and then you'd get ~50nmc.
fee is 0%
it's located in falkenstein, germany
and i'm running the latest bitcoind, 0.6.3rc1
i think it works!
it's at 5.9.24.81:9332
username set to whatever your payout address is
uh, it's also set for merged mining with namecoins. although as i understand it, you'd actually have to solve a namecoin block and then you'd get ~50nmc.
fee is 0%
it's located in falkenstein, germany
and i'm running the latest bitcoind, 0.6.3rc1
i think it works!
Feel free to use my dedicated server without any fee:
location Europe
Kyiv, UA
URL (BTC): http://93.126.88.72:9332/
Username: your bitcoin address
Password: anything
fee 0%
efficiency expected 105%
miner batch example: cgminer -o http://93.126.88.72:9332/ -u "your bitcoin address" -p x
URL (LTC): http://93.126.88.72:9327/
Username: your bitcoin address
Password: anything
fee 0%
efficiency expected 102%
miner batch example: minerd --url http://93.126.88.72:9327/ --userpass "your bitcoin address":x
location Europe
Kyiv, UA
URL (BTC): http://93.126.88.72:9332/
Username: your bitcoin address
Password: anything
fee 0%
efficiency expected 105%
miner batch example: cgminer -o http://93.126.88.72:9332/ -u "your bitcoin address" -p x
URL (LTC): http://93.126.88.72:9327/
Username: your bitcoin address
Password: anything
fee 0%
efficiency expected 102%
miner batch example: minerd --url http://93.126.88.72:9327/ --userpass "your bitcoin address":x
RandomQ has taken GreenBTC too far. You have to draw the line somewhere dude. 
That is too funny...
http://blockexplorer.funkymonkey.org:9335/ updated to 3.1 today.
Had an error after loading the shares the first time starting but the 2nd time starting seems to be fine now.
Had an error after loading the shares the first time starting but the 2nd time starting seems to be fine now.
http://p2pool-cologne.dyndns.org:9332
is already upgraded to 3.1
is already upgraded to 3.1
Probably shaves off at least 2 or 3 minutes off of his pizza delivery times...
-- Smoov
-- Smoov
RandomQ has taken GreenBTC too far. You have to draw the line somewhere dude.
Updated to Version 3.1
I've updated p2pool.stitthappens.com:8336 (BTC + NMC) and p2pool.stitthappens.com:10336 (LTC) to version 3.
Mine have been updated as well.-- Smoov
I've updated p2pool.stitthappens.com:8336 (BTC + NMC) and p2pool.stitthappens.com:10336 (LTC) to version 3.
Jump to: