[~32 TH] HHTT - Selected Diff/Stratum/PPLNS/Paid Stales/High Availability/Tor

[spiccioli]

Lot of things today!

a new happy soul with 1 TH/s deployed has joined our ranks!

Every hash counts, so 1 TH counts a lot

spiccioli

[spiccioli]

So fireduck has an asic... 1FdkASiCe5Tkueouk2mZHfnDPGwtYFYFRW   

and he just found a block!

Which gives three in the last half day

spiccioli

[spiccioli]

6 TH/s right now 

spiccioli

[fireduck]

fireduck was here

I mean, a second address appeared tonight (UTC+2) under pool funds... so someone had to add it and it wasn't me

spiccioli

Yeah, I would out of town and a power outage at home took some things down.  I wasn't home to bring the encypted filesystems back up so needed to pay people from a separate pool of bitcoin for a little while.

I've seen moved a few of those backend tasks to AWS so that shouldn't be a problem again.

[fireduck]

Given that fireduck, owner of HHTT pool, is away since a few weeks now and the original thread title shows a wrong speed I've decided to wait until the original thread went pushed down to page 2 before opening this new topic to cover the HHTT pool and to be able to update pool's speed.

spiccioli

Much thanks for making a thread and updating it.  I haven't been on bitcointalk much, the interface makes me a little crazy.

If someone needs to reach me, the easiest way is to email me directly (fireduck@gmail.com), post a question to reddit.com/r/hhtt.

I can also be reached on Bitmessage: BM-2D91jXnixXu5rFZGFVHSUEfEVNTnNi6NnE

This week I just added another server, NRT (Tokyo) and improved some alarming to know about potential problems.

[spiccioli]

Given that fireduck, owner of HHTT pool, is away since a few weeks now and the original thread title shows a wrong speed I've decided to wait until the original thread went pushed down to page 2 before opening this new topic to cover the HHTT pool and to be able to update pool's speed.

spiccioli

Much thanks for making a thread and updating it.  I haven't been on bitcointalk much, the interface makes me a little crazy.

If someone needs to reach me, the easiest way is to email me directly (fireduck@gmail.com), post a question to reddit.com/r/hhtt.

I can also be reached on Bitmessage: BM-2D91jXnixXu5rFZGFVHSUEfEVNTnNi6NnE

This week I just added another server, NRT (Tokyo) and improved some alarming to know about potential problems.

Great news fireduck and thanks for keeping the pool going!

spiccioli

[spiccioli]

It is becoming ugly... we need moar hashing power, there really is no other solution for this "problem".

spiccioli

[spiccioli]

I'd like to quote gigavps of the semi-private pool because I couldn't have said it better:

Runs of bad luck are never fun, but please remember that this stuff turns in a blink of an eye. If you leave a pool after having bad luck, you ultimately doom yourself to less revenue.

spiccioli

[Polyatomic]

This block had 200 BTC in transactions fees. http://blockchain.info/tx/4ed20e0768124bc67dc684d57941be1482ccdaa45dadb64be12afba8c8554537

[spiccioli]

This block had 200 BTC in transactions fees. http://blockchain.info/tx/4ed20e0768124bc67dc684d57941be1482ccdaa45dadb64be12afba8c8554537

It came from here https://bitcointalk.org/index.php?topic=279249.msg3025285#msg3025285

holy sh...

spiccioli

[techwtf]

3 issues:

1 "ERROR Failed to contact the origin." for user-details page. user-details-json seems work better.

2 fix the calculation of "Profit and loss measured in blocks", since the current bad luck ...

3 any chance for NMC merged mining (add another address in username?)

[spiccioli]

3 issues:

1 "ERROR Failed to contact the origin." for user-details page. user-details-json seems work better.

2 fix the calculation of "Profit and loss measured in blocks", since the current bad luck ...

3 any chance for NMC merged mining (add another address in username?)

see here https://bitcointalk.org/index.php?topic=269042.msg3005269#msg3005269

spiccioli

[techwtf]

3 issues:

1 "ERROR Failed to contact the origin." for user-details page. user-details-json seems work better.

2 fix the calculation of "Profit and loss measured in blocks", since the current bad luck ...

3 any chance for NMC merged mining (add another address in username?)

see here https://bitcointalk.org/index.php?topic=269042.msg3005269#msg3005269

spiccioli

mid to low priority, so I prefer not to nudge him directly since nothing is interrupted.

[spiccioli]

Right now we're around 1% of the full bitcoin network, so we should expect around 1.4 blocks a day, which we're doing...

It's just difficulty going up so fast that we don't have time to get accustomed to the lower income and we start thinking we're unlucky... which is not true.

We need to find more miners for the pool...

spiccioli

[JorgePasada]

Hey Guys, introduced myself at the orig thread over here.

Good to meet y'all. Ideas for growing the pool and reducing our variance?

[spiccioli]

Hey Guys, introduced myself at the orig thread over here.

Good to meet y'all. Ideas for growing the pool and reducing our variance?

Hi Jorge,

to grow the pool we need more miners which would also reduce our variance, while to reduce your variance you can spread your hashing power to two or three pools, see the link I've posted a couple of messages back, but doing so you would increase our variance since the pool would have less miners...

Truth is a lot of miners should leave the bigger pools and point their gear here or on p2pool or on the other small pools.

spiccioli

ps. how went the date? 

[fireduck]

It would make my life easier if people mining at something close to a TH/s would pick a difficulty of at least around 2048.

In general, being around a share every 5 seconds or higher would be good.  This will greatly reduce the database load.  I am trying to get away with using an AWS RDS small.

[JorgePasada]

It would make my life easier if people mining at something close to a TH/s would pick a difficulty of at least around 2048.

In general, being around a share every 5 seconds or higher would be good.  This will greatly reduce the database load.  I am trying to get away with using an AWS RDS small.

I just finished rewiring a bunch of stuff, flashing firmware and setting everything to 2048 later today.

Anyone know who 1E8xjHavR1NwVv6tWTC6pX7Z93MWmMmPTx is?

[JorgePasada]

Well, I wonder if this will actually work...

https://blockchain.info/tx/942f79f17ffc1987895adc99463b099f8bc88547b6aaefb4647df81f71c37e44

I haven't been on bitcointalk much, the interface makes me a little crazy.

It's insanely hard to extract the useful information from this seething mass of blabber.

ps. how went the date? 

It went well :-)

[fireduck]

Well, I wonder if this will actually work...

https://blockchain.info/tx/942f79f17ffc1987895adc99463b099f8bc88547b6aaefb4647df81f71c37e44

Looks like it worked just fine one way or another.