[ANN] The First Litecoin PPS Pool (litecoinpool.org)

[powersync]

Burnside is getting hit at the same time.

PS

[1713995827]

1713995827

[1713995827]

1713995827

[1713995827]

1713995827

[burnside]

Burnside is getting hit at the same time.

PS

Yeah, not fun.  Working on shifting the traffic to a larger DDoS setup.

[wndrbr3d]

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

[Nicksasa]

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

You'd probably spend a lot on bandwidth ... I've considered this myself before.

[burnside]

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

I don't want to get too far off topic, this isn't my pool thread.

I have thought about splitting the web services from the poolserver instance.  Two problems:

1) Cost.  an LTC pool doesn't make money and even my full dedicated server has load issues periodically.
2) The attack we were seeing today was icmp flood + http flood + pushpool port flood, so having separate servers wouldn't have helped much.

Cheers.

[wndrbr3d]

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

I don't want to get too far off topic, this isn't my pool thread.

I have thought about splitting the web services from the poolserver instance.  Two problems:

1) Cost.  an LTC pool doesn't make money and even my full dedicated server has load issues periodically.
2) The attack we were seeing today was icmp flood + http flood + pushpool port flood, so having separate servers wouldn't have helped much.

Cheers.

Right, but if you used DNS load balancing you could just map a new IP and update your A-Record.

I mean, unless a DDoS attack does a DNS on each request, I imagine you would suffer minimal downtime. I'm making assumptions though, I've personally never launched a DDoS myself.

[burnside]

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

I don't want to get too far off topic, this isn't my pool thread.

I have thought about splitting the web services from the poolserver instance.  Two problems:

1) Cost.  an LTC pool doesn't make money and even my full dedicated server has load issues periodically.
2) The attack we were seeing today was icmp flood + http flood + pushpool port flood, so having separate servers wouldn't have helped much.

Cheers.

Right, but if you used DNS load balancing you could just map a new IP and update your A-Record.

I mean, unless a DDoS attack does a DNS on each request, I imagine you would suffer minimal downtime. I'm making assumptions though, I've personally never launched a DDoS myself.

DDoS attacks primarily originate from compromised machines serving a botnet.  Thus when a DDoS attack is pointed at a domain name, the attack follows the domain name just as fast as your dns changes reach the compromised machines.

[pooler]

DDoS attack is in progress. Sorry for the inconvenience.

[Simran]

DDoS attack is in progress. Sorry for the inconvenience.

Don't worry, pooler!

[Dagger75]

  Thanks Pooler, was wondering what was up today!!   

[splat44]

I'm glad to server is up and running!

Just in case of further DDos attack, how we set up for solo mining using cpuminer?

I especially want to know the string and where to enter it as command line (while using server:port and userpass)

Oh yes, about public key, what this all about?
Can use we use this in cpuminer and if so, then what the string?

Regards

[pooler]

Just in case of further DDos attack, how we set up for solo mining using cpuminer?

I especially want to know the string and where to enter it as command line (while using server:port and userpass)

To mine solo just tell cpuminer to connect to your local Litecoin daemon, using the local IP of the machine and the RPC username and password defined in your litecoin.conf. The default port is 9332.
If you want to set up failover pools in cpuminer, see this thread.

Oh yes, about public key, what this all about?

At present it's only used for the avatar, you don't need to worry about it.

[pekv2]

Just in case of further DDos attack, how we set up for solo mining using cpuminer?

I especially want to know the string and where to enter it as command line (while using server:port and userpass)

To mine solo just tell cpuminer to connect to your local Litecoin daemon, using the local IP of the machine and the RPC username and password defined in your litecoin.conf. The default port is 9332.
If you want to set up failover pools in cpuminer, see this thread.

This &

https://bitcointalk.org/index.php?topic=83371.0

+

For offline use.
[TUTORIAL] Solo Mining Litecoins Guide--Windows! Offline PDF

[splat44]

Just in case of further DDos attack, how we set up for solo mining using cpuminer?

I especially want to know the string and where to enter it as command line (while using server:port and userpass)

To mine solo just tell cpuminer to connect to your local Litecoin daemon, using the local IP of the machine and the RPC username and password defined in your litecoin.conf. The default port is 9332.
If you want to set up failover pools in cpuminer, see this thread.

This &

https://bitcointalk.org/index.php?topic=83371.0

+

For offline use.
[TUTORIAL] Solo Mining Litecoins Guide--Windows! Offline PDF

Thank and I certainly take note of this!

I also notice mining ltc value has increased and difficulties decreased, Is this good and does it means we earn more?

Regards

[conspirosphere.tk]

Something is strange:
- I am logged in with 2 computers and mining from several hours on http://www.litecoinpool.org/miner, but the shares generated do not appear on my account http://www.litecoinpool.org/account

- I inserted the embeddable miner on a couple of websites of mine with my user.name:pass, but they do not seem to work even if I load the plugin when asked by my browser. The miners are here:
http://webabuser.blogspot.com/p/support.html
http://saveyourassetsfirst.blogspot.com

[pooler]

Something is strange:
- I am logged in with 2 computers and mining from several hours on http://www.litecoinpool.org/miner, but the shares generated do not appear on my account http://www.litecoinpool.org/account

- I inserted the embeddable miner on a couple of websites of mine with my user.name:pass, but they do not seem to work even if I load the plugin when asked by my browser. The miners are here:
http://webabuser.blogspot.com/p/support.html
http://saveyourassetsfirst.blogspot.com

The password you provide on the second page you listed is wrong, please correct it. The embeddable miner on the first page, on the other hand, appears to be working well, and so does the online miner on the pool website. I have briefly tested both of them using your worker's credentials, and shares do show up in your account page.
Please keep in mind that share counts are not updated in real time, but only every minute.

[conspirosphere.tk]

The password you provide on the second page you listed is wrong, please correct it. The embeddable miner on the first page, on the other hand, appears to be working well, and so does the online miner on the pool website. I have briefly tested both of them using your worker's credentials, and shares do show up in your account page.
Please keep in mind that share counts are not updated in real time, but only every minute.

Thank You very much for the prompt and professional support.
+rep to you

[pooler]

litecoinpool.org PPS rate 0.00002833 LTC
coinotron.com PPS rate 0.00046042 LTC

Litecoin pools don't all use the same share difficulty. And of course if the share difficulty is lower shares are "easier" to find, and their value is lower.

[meebs]

litecoinpool.org PPS rate 0.00002833 LTC
coinotron.com PPS rate 0.00046042 LTC

coinotron pps rate = diff 16 shares
litecoinpool pps rate = diff 1 shares

liteocinpool does variable difficulty. When you first fire up a GPU pointed to their pool it'll do a couple hundred shares in seconds than VERY quickly slow down to about 5/minute.

[SyRenity]

Hi.

When new members will be allowed?