P2Pool Server List

[RandomQ]

RandomQ has taken GreenBTC too far. You have to draw the line somewhere dude. 

That is too funny...

[1715108499]

1715108499

[1715108499]

1715108499

[Ed]

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

[zvs]

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!

[zvs]

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!

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!

[rjk]

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.

[zvs]

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.

really?  oh, that's better then.

i guess i could manually send them out. 

i set that up on a whim, it seems like p2pool isn't very efficient, anyway

[Smoovious]

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!

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!

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

[zvs]

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

What exactly does the 'efficiency' rating indicate? 

it has me bumpuzzled

[Krak]

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.

[zvs]

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

[Smoovious]

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.

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

[zvs]

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.

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

Would there be less stales if less transactions were included?  I'm guessing some people have slow connections, etc..

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?

[Smoovious]

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

[zvs]

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

Yeah, and 213kb is a lot more than 4kb.

 

[Smoovious]

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

Yeah, and 213kb is a lot more than 4kb.

 

Like... (counts on fingers)... almost twice as big!

-- Smoov

[zvs]

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

Yeah, and 213kb is a lot more than 4kb.

 

Like... (counts on fingers)... almost twice as big!

-- Smoov

 

The point being: if all these transactions weren't included, it'd reduce the stale rate and make it less likely to have orphaned shares/blocks.

Sorry that you missed it earlier.

[Smoovious]

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

Yeah, and 213kb is a lot more than 4kb.

 

Like... (counts on fingers)... almost twice as big!

-- Smoov

 

The point being: if all these transactions weren't included, it'd reduce the stale rate and make it less likely to have orphaned shares/blocks.

Sorry that you missed it earlier.

Didn't miss it at all...

The point being: mining's purpose is to process transactions and get them into the block chain... not mining for the reward at the expense of that purpose.

Anyways, way to miss a joke.

-- Smoov

[zvs]

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

Yeah, and 213kb is a lot more than 4kb.

 

Like... (counts on fingers)... almost twice as big!

-- Smoov

 

The point being: if all these transactions weren't included, it'd reduce the stale rate and make it less likely to have orphaned shares/blocks.

Sorry that you missed it earlier.

Didn't miss it at all...

The point being: mining's purpose is to process transactions and get them into the block chain... not mining for the reward at the expense of that purpose.

Anyways, way to miss a joke.

-- Smoov

Yeah, but the fee is supposed to make them worthwhile to process. 

Anyway, is it possible for a peer joining to send you out of sync data or something?

I've been giving this a go for 12 hrs or so, and noticed this:



I ended up just shutting it down and reloading, now back to 1-2%.

[zvs]

great googly moogly, peers keep sending me blocks

[ThiagoCMC]

Hi!

 I'm running my own Bitcoin / Litecoin P2Pool node for months, but just now I decide to announce it... So, here we go!

 The server hardware and software configuration is:

 Hardware:
 Dell Powered 840
 CPU: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
 RAM: 8G
 HD: 6T hardware RAID5

 Plus:
 NoBreak 1.5 KVA - 1 hour
 80 KVA Diesel Generator

 Software:
 Ubuntu Server 12.04 - 64 Bits

 Bitcoin P2Pool Node Details:
 Linux KVM
 Ubuntu Server Minimal Virtual Machine 12.04 - 64 Bits
 CPU: 2~4 Cores (flags copied from host)
 RAM: 2G~3G
 HD: 50G (1 logical volume of 50G at host as /dev/vda)

 Litecoin P2Pool Node Details:
 Linux KVM
 Ubuntu Server Minimal Virtual Machine 12.04 - 64 Bits
 CPU: 2~4 Cores (flags copied from host)
 RAM: 2G~3G
 HD: 50G (1 logical volume of 50G at host as /dev/vda)


---

 NOTE: There is 2 VPS running at this server, the Bitcoin and Litecoin P2Pool nodes.

 If there is demand, I can rise up the resources allocated to it.

---

 Special Note:

 I'm using two fiber line Internet connections, total of 200Mb down and 30Mb up.

 This is great deal for brazillian users of ISP called Telefônica, using the ADSL service called "Speedy Fibra", even using regular Speedy services (not fiber) through telephone lines (ADSL), this services is good for you! Because we are close to each other!

---

 Bitcoin Brazillian P2Pool Node:

Bitcoin (0.6.3):

Server: http://200.204.162.44:9332
Username: your bitcoin address
Password: anything

More Info: http://200.204.162.44:9332/static/
Graphs: http://200.204.162.44:9332/static/graphs.html
Fee: 0.5%

CGMiner CMD line:

Code:

cgminer -o http://200.204.162.44:9332 -u YOUR_BITCOIN_ADDRESS -p abc123

---

Litecoin Brazillian P2Pool Node:

Litecoin (latest source):

Server: http://200.204.161.215:9327
Username: your bitcoin address
Password: anything

More Info: http://200.204.161.215:9327/static/
Graphs: http://200.204.161.215:9327/static/graphs.html
Fee: 0.5%

Pooler's CPUMiner CMD line:

Code:

minerd -o http://200.204.161.215:9327 -O YOUR_LITECOIN_ADDRESS:abc123

Reaper Litecoin GPU configuration file "litecoin.conf" (for ATI 5XXX):

NOTE: Need to test this!! I have no experience with Reaper at all.

Code:

host 200.204.161.215
port 9327
user YOUR_LITECOIN_ADDRESS
pass abc123

protocol litecoin

worksize 256
aggression 18
threads_per_gpu 1
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 6144

---

South America:

São Paulo/SP::Brazil::200.204.162.44:9332::0.3::BTC::Electra Bitcoin P2Pool Node::ThiagoCMC
São Paulo/SP::Brazil::200.204.161.215:9327::0.5::LTC::Electra Litecoin P2Pool Node::ThiagoCMC

My Bitcoin P2Pool node have enabled merged mining for the following alt-coins: NMC/IXC

But I'm keeping those coins for me because I don't know how to do the accounting...  :-/

---

Good luck!!

Cheers!
Thiago