Pages:
Author

Topic: [~32 TH] HHTT - Selected Diff/Stratum/PPLNS/Paid Stales/High Availability/Tor - page 13. (Read 29733 times)

newbie
Activity: 14
Merit: 0
I am 1E8xjHav....MmPTx    Grin Grin i'm here
legendary
Activity: 1378
Merit: 1003
nec sine labore
sr. member
Activity: 336
Merit: 250
It seems they keep coming... Wink

spiccioli.

ps. Where are all the new BitFury's/Punin's units ?


Yeah! Three in a row.  1E8xjHav....MmPTx  is having some great luck finding blocks.
I am adding some bitfury hashes to the pool today. Grin
legendary
Activity: 1378
Merit: 1003
nec sine labore

Great!

BTW, 10 blocks in three days Smiley

spiccioli

Nice luck streak before the difficulty adjustment.

It seems they keep coming... Wink

spiccioli.

ps. Where are all the new BitFury's/Punin's units ?
member
Activity: 61
Merit: 10

Great!

BTW, 10 blocks in three days Smiley

spiccioli

Nice luck streak before the difficulty adjustment.
legendary
Activity: 1378
Merit: 1003
nec sine labore
sr. member
Activity: 392
Merit: 251
member
Activity: 61
Merit: 10
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?  Roll Eyes

It went well :-)

member
Activity: 61
Merit: 10
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?

sr. member
Activity: 392
Merit: 251
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.

legendary
Activity: 1378
Merit: 1003
nec sine labore
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?  Roll Eyes
member
Activity: 61
Merit: 10
Hey Guys, introduced myself at the orig thread over here.

Good to meet y'all. Ideas for growing the pool and reducing our variance?
legendary
Activity: 1378
Merit: 1003
nec sine labore
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
full member
Activity: 140
Merit: 100
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 ... Sad

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

see here https://bitcointalksearch.org/topic/m.3005269

spiccioli

mid to low priority, so I prefer not to nudge him directly Smiley since nothing is interrupted.
legendary
Activity: 1378
Merit: 1003
nec sine labore
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 ... Sad

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

see here https://bitcointalksearch.org/topic/m.3005269

spiccioli
full member
Activity: 140
Merit: 100
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 ... Sad

3 any chance for NMC merged mining (add another address in username?)
legendary
Activity: 1378
Merit: 1003
nec sine labore
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.


Smiley

spiccioli
legendary
Activity: 1378
Merit: 1003
nec sine labore
It is becoming ugly... we need moar hashing power, there really is no other solution for this "problem".

spiccioli
Pages:
Jump to: