Bitcoin Forum

HHTT Short list of pros and cons (http://hhtt.1209k.com/):

PROs

• no bells and whistles
• very low fees when mining with difficulty higher than 128 and at difficulty 128 (default one) fees are slightly less than 0.51%
• half of each block's transactions fees are paid to the miner that finds the block lowering fees even more
• rock solid and resilient (http://hhtt.1209k.com/ha.php)
• no registration needed: bitcoin address as username and whatever you like as password.
• if you want to set your difficulty just add it at the end of your username preceeded by an underscore:
  
                        1FDkoGo8o9tmXD4cYpAqBZeWACJiYjMm3x_256
  
  This sets you at difficulty 256.
• TOR mining aka don't let your government know that you're mining...

CONs

• no bells and whistles
• backgound colors can be annoying at times - just reload page for a different combination ;)
• with difficulty growing so fast variance can be felt at times

NEWS

• October 22nd, 2013: easy configuration sample for high availability (http://hhtt.1209k.com/config.php) for cgminer (should work with bfgminer as well)
• October 24th, 2013: as en example of block's fees reducing pool's fee, see here latest block which paid a good 0.15 BTC to the miner who solved it: https://blockchain.info/block-index/429263/00000000000000072089a0adae2b921c93f3d707c1180b7dae1b63ef03e0dd78
• November 8th, 2013: there was no mention of pool's URL... (http://hhtt.1209k.com/) now there are at least two links to it :)
• November 9th, 2013: no other pool gives you a 9.5 BTCs prize for a solved block (https://blockchain.info/block-index/438763/00000000000000018914e17bd674c5d8069ce463e00750cb838b91d3b0ac80c3)!!

This is a Pay Per Last N Shares pool which means that you need to mine here for at least a couple of days before getting your full share (https://bitcoil.co.il/pool_summary.pdf) of each found block.

Oh, don't forget to have a look at the original thread (https://bitcointalk.org/index.php?topic=95378.0) if you want to know how it all began.

spiccioli

Oh well!!!

A good fellow with 800 GH (at least) came back tonight.

Welcome back! Your hashing power is really needed :)

spiccioli

And a bigger fish!  :o

3 TH/s is really serious gear!

I'd say, as an unrequested advice, that with 3 TH/s you can use a much higher difficulty than 256.

I'd try with 2048 at least, lowering your fee to a little less than 0.3%

spiccioli

Hopefully they hang around for a while. We have more hashing power than p2pool ATM.

All fingers crossed.... :)

spiccioli

the mighty miner seems to be here to stay.

with his help HHTT pool is now around 5.5 TH/s sustained.   8)

spiccioli

bitparking have some rejecting issues so I came back... & personally I know the 3TH guy :)

hopefully we could have NMC merge mining in the future, but where is fireduck ...

if the pool goes wrong, with --disable-rejecting, the issue could be solved faster with a lower diff.

I don't think, but I can be wrong, that merge mining NMC makes a lot of difference on the payout.

I don't know where is fireduck, I hope he's enjoying his time and comes back fully recharged to make some changes:

- colors! :)
- bigger blocks, so that who finds a block gets a bigger payout

spiccioli

ps. thanks for coming back !

I'm not following you here... using a higher diff share, p2pool, for example uses 14K right now, gives two advantages:

- one for you, lower fees
- one for the pool, less shares to track, less burden on the servers

spiccioli

Hi,

an error on blockchain.info makes it appear that the pool is out of coins... it already happened in the past :)

http://blockchain.info/address/1HHTTPaz86gcxqntnjZMHbaoF4EvyYZCka

gives


spiccioli

Might have something to do with the vulnerability .  

Blockchain has an app on android ?

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

The mighty miner has gone away...  :'(

We're back to less than 3 TH/s... I wonder why he left.

spiccioli

i have left hhtt,  too low earnings here for my blade

threeedrules,

your earnings depend upon your hashing speed relative to the pool's total one and upon the pool "luck".

on a big pool you'll have frequent but small payments while on a smaller pool less frequent but higher ones.


spiccioli

Congrats to the 10 Gig miner who found a block , how do u feel ?.

Every hash counts, as they say :)

BTW, we even got an orpahan.

spiccioli

The spreadsheet has been updated.

https://lh3.googleusercontent.com/k9VE67Wex32UonOslGkjImJM0VxsldXi6FJe0RZwVc6z-0WZnQSC72xMiendBDspiUj1UhuLHxSbZdboF0tFeudEp4WZ90UX2b6k2uxdWe9Y1dQ1SZkRPZQY

Yeah,

and he now has a bitmessage address...

Bitmessage address of fireduck/HHTT: BM-2D91jXnixXu5rFZGFVHSUEfEVNTnNi6NnE


;)

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

So fireduck has an asic... 1FdkASiCe5Tkueouk2mZHfnDPGwtYFYFRW   

and he just found a block!

Which gives three in the last half day ;)

spiccioli

6 TH/s right now  8)

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.

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

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

spiccioli

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


:)

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

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.

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

Hey Guys, introduced myself at the orig thread over here (https://bitcointalk.org/index.php?topic=95378.msg3041175#msg3041175).

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?  ::)

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?

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

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


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


It went well :-)

Looks like it worked just fine one way or another.

Great!

BTW, 10 blocks in three days :)

spiccioli

Nice luck streak before the difficulty adjustment.

It seems they keep coming... ;)

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

Five yesterday! :)

I am 1E8xjHav....MmPTx    ;D ;D i'm here

Hello!   Keep up the great work finding us blocks!  ;D

Pleased to meet you, can you tell us what kind of hardware you're using?

spiccioli

I have 30 avalon

Holy!!!  That's a lot of Avalons.  ;-)

mybe :) i have avalon 1 2 Batch NO'T 3 Batch

I'm sorry for my English is not very good

No problem on the English, thanks for being a part of the pool and for adjusting your difficulty to 2048.

I just added about 50 Gh/s worth of Bitfury cards to my ID....

Actually flashing my Avalons tonight, I'll probably get about that much additional hash power out of them.

I can confirm this~ ^_^

Nice grow today,

we should be past 8 TH/s if those new hashers stay with us.

spiccioli

Yeah!  Let's solve some blocks.

I think I talked a couple of those guys on to the pool :-) Hope so at least.

In order to make the user details pages load faster I've split out the graph into a 7 day detail graph and a 1 day per data point long term graph.

This should avoid the timeouts people have been sometimes seeing loading the user details page.

It also now gives history beyond 30 days (although at one-day data points).

Very nice!

I was just looking at my miner when I noticed the second graph and I've spent a while wondering why are they "weak" graphs?

What do you mean by "weak" ?

spiccioli

Hey FD - nice to hear from you....

I was making a play on 'week' and that I don't really like that graph package.  It seems to work alright and it isn't a huge pain to use so makes sense to stick with.

Ah ok :)

spiccioli

ps. Do you have time to give some love to the coloring code? Lighter backgrounds or dark ones but with a light foreground color... I'd venture to say... no bleak backgrounds! :)

I think it works pretty well given how silly it is.  You can take a crack at it if you like, I've copied the php file so you can see the source:

http://hhtt.1209k.com/colors.txt

It is always set to no-cache so a quick refresh should get you out of anything especially ugly.

Fireduck,

it probably is that my eyes are becoming old :)

Anyway, here are three examples of what I find too dark to be able to easily read cell contents and visited links.

http://imgur.com/vECoTJv,QH1hhBb,u2Pu79P

I confirm that reloading the page always works.

spiccioli

Thanks.  It looks like it is going too dark for the primary color and the red and blue link colors are always ugly.  I'll see what I can do about that.

Well, I've changed some things.  I'm not sure if I made it better or worse.

I made it so that the sum of red + blue +green has to be at least 400 which should eliminate anything really dark.  It now is not guaranteed to halt (heh) and that change allowed me to open up some color ranges a bit to get single color elements lower.  This means before you could never get a pure primary color, now it is possible.

I've also tweaked the column headers and links a bit.

Now I can't find my link on the main page - everything is just underlined...  No big deal, since I have it bookmarked...

I can make the visited links more obvious which will probably help.

Sorry to keep bothering you, table headers always white would be better, IMHO.

spiccioli

Poxy orphaned block.

Prefer previous spreadsheet colors.

Coloring is better now, I'd say there are very few combinations left which pose some reading problems (to me).

Thanks  :D

spiccioli

There is some problem with the IAD instance.  AWS is showing connectivity issues on their dashboard (http://status.aws.amazon.com/).  I've pulled it from DNS and it is down for now.

Two orpahans in two days!  >:(

WTF?

spiccioli

Yeah, variance is killing me.  Looks like a lot of hash power has dropped off too.   :P

This is not variance, two orpahans in a row is just plain bad luck :/

spiccioli

Even without the Orphans, we should be finding 2-3 blocks a day. no blocks on the 14th, just one today, and that one is  an orphan.  That variance.

8 TH/s at current difficulty are worth around 35 BTCs/day, so less than 1 and a half of a block/day.

spiccioli

Fucking ugly day today, orpahans and a good 1.5 TH/s less of suckers :/

spiccioli

Bit better luck in the last 12 hours. :-)

Sure!

But we're still missing those 1.5 TH/s.

I'd like to know: why did he leave and where has he gone.

I mean, we should know why people leave otherwise in a couple of difficulty jumps mining here and mining solo will mostly be the same...

spiccioli

If it's who I think it is, I might be seeing him tonight, I'll try and coax him back on the pool. Not positive it is though.

People seem to be pretty fickle about jumping hash power when pools get unlucky. I don't understand it, either just split it and keep it split or don't move it. It all averages out and nobody is good at 'picking winners'.

Well, even if he does not come back, I'd like to know why he moved and where he moved :)

We're in a chicken and egg situation, we need moar power to attract people which will add moar power which...

spiccioli

One good today, but one orpahan yesterday...

fireduck, can you verify all is working ok?

I mean, for months we had 1 orpahan/month, our hashing power being more or less the same, in september alone we have 5 blocks plus one on august 31st.  :-\

spiccioli

btw, neither blockchain.info nor blockexplorer can find this block

http://blockchain.info/search?search=0000000000000003d533f6fb39cd86f0f6f83de5ad2a4965593e0a5601b93e89

?

spiccioli

Don't know what block you are looking at.  Don't see that in the last few days of found blocks....

Redacted,

it's the last orpahan.

In march we had 6 orpahan though, so this is not the first time...

spiccioli

Oh well,

I've left a call to arms... (https://bitcointalk.org/index.php?topic=226846.msg3200522#msg3200522)

If it really happens that a sizeable chunks of BitCentury customers points their miners here... well, dreaming costs nothing, doesn't it?

spiccioli

ps. A small pool like this finds it hard to have users joining it one after the other, because new users prefer to point their gears to a bigger one for reduced variance, but if five or ten TH/s (I don't know how many TH/s BitCentury sold) come here all at the same time, it should work, since everyone reduces the variance that the others feel.

It looks like miners have their rigs on rotate.

It seems we're talking about 6 TH/s (https://bitcointalk.org/index.php?topic=226846.msg2387678#msg2387678) which would double us (if they ever come) and make HHTT a little less the size of p2pool.

spiccioli

Three blocks, but another "strange" orpahan, strange in that it is not found on blockchain.info


http://blockchain.info/search?search=00000000000000078b9fc485c97a58595752ef178dedb8ada97eb634212e21f4


it has the same hour of a found block, just a few seconds later, so was it not even submitted to the bitcoin network?

Is it a real orpahan?

spiccioli

I have had the same on my pool which uses the same stratum software as HHTT. I wonder if there's an issue somewhere. I'd get a 'block' with 20 seconds of another which is never submitted to the network.

It looks like Blockchain.info does not update orphaned blocks fast enough "20 SEP" is the last orphan , or it could be here https://blockchain.info/rejected

Here's the discussion on my pool (https://bitcointalk.org/index.php?topic=57148.msg3085964#msg3085964) about the same same short block/orphan issue.

I think one of the causes of orphans is that my bitcoind instances are taking 5-10 seconds to do a getblocktemplate so we end up working on the old block longer than we should.

I've done some testing and this seems to be due to not good disk latency on AWS EC2 instances.  I've done testing with Google Compute Engine and numbers there are much better.

I've setup a test instance, us-central on GCE and am doing some production testing there.  If it goes well, I'll switch everyone over to GCE probably this week.

Are you running the latest bitcoind?  5-10 seconds is a very long time, even for the crappy performance you get with AWS.  GBT is very single-core CPU and HDD intensive, and AWS uses many-cores with relatively slow clock rates, and disk access speeds are always garbage.

Best specs you can get for GBT:  High clock speed modern CPU (E3-1230v2 is beastly for this since it has a 3.7 Ghz turbo, 3.3 baseline), and SSD.  Another alternative is storing the blockchain on a ramdisk, but that's only an option if you've got a dedicated machine with 32GB+ of RAM.

Yep, latest bitcoind.  Yeah, GBT seems to be entirely disk latency based.  I can't really afford the high memory machines for this project.

Anyways, with GCE I am getting 0.05 seconds for getblocktemplate which is quite an improvement for very similar price.

New nodes are up.  stratum.hhtt.1209k.com is pointing to them.

They are:
us-central-1.hhtt.1209k.com
us-central-2.hhtt.1209k.com
eu-west-1.hhtt.1209k.com

Talked with him again this past week. He no longer controls the hashpower is my understanding.

Extremely efficient pool operator that fireduck.

and the you wake up and...

https://bitcointalk.org/index.php?topic=226846.msg3220533#msg3220533

:(

btw, a new fake orpahan did show up yesterday

http://blockchain.info/search?search=0000000000000001ae09ea8b40865bc31a7f8605412b1ace4f5b7a6357d0416e

spiccioli

Yeah, my GCE migration didn't fix everything.  I now added a bunch of logging to SockThing so that I can track down exactly what was happening or not happening.

I saw an instance where two of my nodes didn't see a new block for a over a minute and then eventually learned it.  So I took some steps to improve the p2p network and ensure that my nodes are connected at least to each other to increase coverage.

Good start to the swing.

Well, let's hope 1E8xj fixes his troubles fast... or we're down 2 TH

spiccioli

Yeah, looks like he was sending a bunch of h-not-zero (an odd error message I copied from the pushpoold).  It means the user was submitting shares that didn't match the assigned difficulty.  My guess is some software/firmware update did not go well.

It seems we are way better with orpahans, we still need a massive infusion of hashing power, though.

BTW, given that you're now using a faster virtual server, could you fireduck increase block size?

This would increase fees paid to block's solver which in the end should give people one more reason to join us.

spiccioli

Joined tonight.  We need some more miners!  Throw some hashes this way for super low fees!  Transaction fees are split 50/50 with the miner whom finds the blocks.

Welcome aboard!

spiccioli

Well,

some advertizing should help finding new fellow miners, shouldn't it?

So, why don't we, HHTT miners, put a signature like this


Every one of us with a different color, like HHTT background! :)

To change color you have to change


Using some other color combination.

http://html-color-codes.info/

Let's see how we transform this forum in a rainbow!  :)

spiccioli

I added a new feature to the main web page showing pool luck back 30 days.

Once I have more historical data accumulated I can push it our further.

I prune regular shares from the DB after 35 days so I was only able to build the summary table out 35 days back.

Nice!

In the  last month we've been over 100%

I'm going to change my signature: Mine with us, > 100% luck and no DDOS !! :D

spiccioli

ps two blocks half an hour apart.. very nice!

make it three ;)

spiccioli

Hi guys,

without bitcointalk days become soo long :)

I see several KnC in the wild, is someone with a Saturn/Jupiter unit mining with us?

spiccioli

Yes!

Good to know!  :)

So we're KnC compatible!

Too bad HHTT is not listed on their site as a preconfigurable pool, I wrote them back then, they promised to have a look at the issue, but never fixed it. :(

spiccioli

edit: I wrote to Bitcoinorama about this issue, let's see if it can get sorted out.

I'll talk to them and get it on the preconfigured pool list.

Luck factor at 108.5% for last month  8)

Come joins us, every hash counts !!

spiccioli

ps. You won't even need to fill an admission request... ;)

I have information that indicates the 3rd largest KNC order will be completely on HHTT.

And how much did that order cost you to buy from KnC?   ;D

It wasn't me but it was something like 25 Jupiters.

The 6 I have on teh way seem pretty insignificant by comparison.......   >:(

They won't be insignificant if you point them here instead of BTCG or that private pool... :D

spiccioli

Tattle-tale...  ;)


They have to arrive here, first :)  I've gotten one, but that went to a group-buy that bought it out.  One more on the way that also goes to a group buy.  And THEN I get to have some of them.

Very nice!

It seems pool is warming up to receive them, we just broke the 10 TH/s barrier :)

spiccioli

13.5 TH/s and growing... very nice!


spiccioli

Vote:

Switch all user reported metrics to GH/s rather than MH/s?  (yes/no)

This will include:
- User detail pages
- JSON user pages
- Metrics to AWS

And the votes are in.  One vote in favor (mine).  Motion passes.  Sorry for the people who are about to get alerts about low hash rate as I change the scale.

So I just found a block  8)

But all that is showing in my wallet so far is 0.09 btc.  Is that normal? is that all I get?

Very noob question but i`m excited so much my brain is going wierd....

https://blockchain.info/block-index/425621/00000000000000003c5ea2ad55b138846b026c4ba0687bb013785854a239c6bf

looks like the pool took loads...

Wow, you did find a block.  At your hash rate that is pretty rare.

Anyways, you get half of the transactions fees, which is 0.09404426 plus your PPLNS share for the block (about 0.03).  Including some of the previous recent blocks that is adding up to the 0.08 that you see.

https://blockchain.info/tx/0349dac045e71cc6a671b8a0559fed0eba7d672ae6a7ae90645e0d8637c9cee5

Your user detail page shows expected BTC per day:
http://hhtt.1209k.com/user-details.php?user=1J4Y6MYQtRNs7ZNFgNZ1gNreovhTgPRsGw

You are probably a bit above that including the transaction fees from that block you found.

So the majority of the 25btc found goes to the pool?

It depends on your difficulty, but yeah generally well over 99% of the block goes to the miners on this pool.

It was time, MH/s are like KH/s in 2012... :)

spiccioli

The way I think of its is , Solving a block is like getting a BTC Pie,   The more hashes you contribute the bigger the slice of "pie" you get.  Unless you find  the block, then you get to "lick" the bowl.   ;-)

Ouch!

where has everybody gone?

spiccioli

I know right?

I`m still here and what small amount of hash power i have and will get will be going towards hhtt :)

I guess the guy 1E8xjH..... that was hashing at 6000 GH/s  decided to solo mine. Since he was solving 80% of the blocks the last few weeks anyway.   :'(

I noticed as well.  We hash on!

that mighty miner experienced some high rej problem on HHTT. hopefully it will get resolved soon

One of the nodes is down for maintenance and it was a while before I noticed and pulled it from DNS.  That might be explanation.

Maybe I'll add DNS health checks to my todo list to take care of that automatically.

Hey fireduck glad to see you around the forums again. :)

This is done.  It is somewhat simplistic but seems to work.  Route 53 FTW.

Buhaha!

half the speed twice the blocks!  ;D

Now... if those 2 and a half TH would just come back...

spiccioli

fireduck,

are TOR hidden service URLs still valid now that pdx, iad and dub servers are no more online?

spiccioli

Nice luck last night, 2 blocks  :)

Yes, I need to relabel them.  2/3 should be up right now.  One isn't up because the instance is in zone maintenance but it should be back eventually.

Apparently probability is for quitters and we should just continue finding all the zeros.

"probability is for quitters "

excellent saying

Yeah,

but we should really ask ourselves why are they leaving?

What is making them swith pool? Pool's variance only?

If half of those that mined here for one day were still here, pool would be at 100 TH at least.

I'm starting to think that, apart from variance, the current coloring scheme of pool's home page could be annoying for someone and, worst, everybody has some coloring combination that annoys him and which gets selected randomly during the day.

For example, this one is unbearable for me... http://imgur.com/VW3qlvJ

Now, I don't know if coloring is the real issue, but such violent colors can make your co-workers wonder what you're staring at, for example, which could be annoying in itself :)

So my question is: fireduck do you think that it would be possible to have some way for users to choose a color combination they like and "freeze" it for the future?

What do others here think about this issue?

spiccioli

I'm not sure that colour is the reason.  For me, some of the stumbling block is fees.  I'm more than happy to pay them, but of course they decrease with difficulty increase.  I feel this is innappropriate unless Variable Diff is included in the pool.

 To lower my fees, I put my diff as 130 (ish) but because I have only 25gh/s to my name, it take ages to find even one share, but I pay less fees.  I recently had a go at comparing emc with hhtt, and I'm trying to decide which pool to settle on. (which considering Josh is an A hole should be an easy decision)

If fees were based on the same priciple, but used varidiff instead of 'pick a number and use it' it would be a little fairer in my opinion.

Thanks

Well, with vardiff and a 25GH/s you'd end up with a low difficulty value to keep a certain share-per-minute rate, but a "high" fee.

I think that pool fees are high when difficulty is low mostly because the high availability solution fireduck is using is costing him monies and the more shares a miner sends the more it costs him (amazon message services have a fixed, even if low, cost per message sent).

By the way, you don't have to put your difficulty at 130 given that minimum difficulty used by pool (if not explicitly set by miner) is 128 now.

In any case, adding a fees paid field to user data could be usefull to see how much one is paying in fees at any given time, which does not solve your issue, but at least shows you how much your spending...

spiccioli

Well, pool could set a maximum share per minute and force miners to use the resulting diff. value if the one set by the miner is too low.

This would make fireduck expenses more predictable, btw.

spiccioli

Agreed spiciolli, THanks :)

Hhtt is and will be my 1st choice for pools for the future.

Nahh - I like the colors.  It's part of the fun of being a sucker....

That said, there are color combos I like more than others, and I wouldn't mind freezing my page at a color I particularly like for at least a couple of days....

I've been thinking about that.  My plan is to include in the page somewhere what the value of the base color is and then allow a url parameter to always use that base color but as it is part of the CSS style sheet loaded by the browser it isn't entirely trivial.

Growin Growin Growin
Though one miner's soloing
Keep them suckers hashin Rawhide
...

:)

spiccioli

Got tracking number
All the zeros will be found
Soon more hashes

N-I-C-E !-!

spiccioli

BTW, what are you waiting for KnC or BFSB/Megabigpower or?

spiccioli

I have one KNC jupiter for physical delivery and five more which will be datacenter hosted.

I am also waiting on a BFL Monarch because I am very very stupid and like to punish myself.

I've written up some sample cgminer configs and make some new dns round-robin pools for faster failover:

http://hhtt.1209k.com/config.php (http://hhtt.1209k.com/config.php)

This way cgminer can fail away from a failed node much faster than my health checks will pull it.

I'd like to show an example, mostly to our new fellows, of how block's fees reduce pool's fee that each miner pays to the pool.

This is latest found block: https://blockchain.info/block-index/429263/00000000000000072089a0adae2b921c93f3d707c1180b7dae1b63ef03e0dd78

It paid a good 0.15 BTC to the miner who found it.

spiccioli

I'd suggest putting "0.25% Fees!!!!!!1!one" in the title.

FireDuck,
I have many many more pools setup to ensure I am always mining so I do not think the load balance is an option for me.  To ensure the best fail over should I set these two as my first two pools?

stratum+tcp://set0.hhtt.1209k.com:3333
stratum+tcp://set1.hhtt.1209k.com:3333

Or should I set all of these?  If so, in which order is preferred?

us-central-1a.hhtt.1209k.com - A single node
us-central-1b.hhtt.1209k.com - A single node
us-central-2a.hhtt.1209k.com - A single node
eu-west-1a.hhtt.1209k.com - A single node

Or all 6?  Again which order?

stratum+tcp://set0.hhtt.1209k.com:3333
stratum+tcp://set1.hhtt.1209k.com:3333
us-central-1a.hhtt.1209k.com - A single node
us-central-1b.hhtt.1209k.com - A single node
us-central-2a.hhtt.1209k.com - A single node
eu-west-1a.hhtt.1209k.com - A single node

Thanks!
-Wave

I recommend using just set0 and set1.  The four nodes are in those sets and any new nodes I create will be as well.

You don't want to use individual nodes, I might change them at any time.

Thanks Fireduck!

Come on miners, this is a great pool.  If you have any questions on how to get setup let us know and we will do our best to help.

4 blocks in two days, not bad :)

Anyway, fireduck, do you think you can increase block size? To increase the "lottery" reward for those that find a block.

spiccioli

The block size is a deliberately limited resource.  It's not up to Fireduck to change the Bitcoin blocksize.

Redacted,

in bitcoin.conf you can increase it up to 1 MB right now, I don't know how big it is right now, but from mined blocks I'd say it is at the default value of 250 KB.

If fireduck has enough CPU power edit: and bandwidth at his disposal increasing it could give a nice return to miners here.

spiccioli

Is that really possible???

Sure,

https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments

-blockmaxsize

spiccioli

We have been running with 750k limit since around March.

just added my 80gh technobit bitfury miners :)

Hi fireduck,

I've just controlled all listed found blocks, this is the biggest one (https://blockchain.info/block-index/429263/00000000000000072089a0adae2b921c93f3d707c1180b7dae1b63ef03e0dd78)  at 270KB, a lot of them are at 25-100 KB.

Am I missing something?

spiccioli

Nice! Welcome onboard!

spiccioli

Thats along with my 2 x blades and 10 erupters.  Theoretical max of 103 gh :)

Thanks :)  I`m glad to be a part of a great pool

Sig updated, thanks spiccioli!

-Wave

Like the signature. I feel like most people assume all pool fees are 'about the same'

Nice :)

Just FYI I'd remove a few trailing spaces, on my ipad mini it gets wrapped on a new line near the end.

spiccioli

Could some one maybe make me a code for my sig? as Waves is? I`ve tried for ages to get something to work...

Here is mine.  You can change colors if you like:

Thanks Wave :)

vulgartrendkill,

yours gets cut in half horizontally

http://imgur.com/bpGJuZo

spiccioli

Yeah I know :( not sure why.....

Because tag space has a fixed height

So either you remove one line or try to use a smaller font for the HHTT advertizing line

spiccioli

Thanks Spiccioli, sorted now :)

Hi guys,

I haven't had a pplns owed amount added to my account for 2 days now.  Anything to worry about?

Pool hasn't found a block in last two days...

and

Payouts

Payouts will occur based on the following rules:
If the balance for an address is greater than 0.25 BTC, a payout is done.
If the balance for an address is greater than 0.05 BTC and the last payout was more than 24 hours ago, a payout is done.
If the balance for an address is greater than 0.001 BTC and the last payout was more than 3 days ago, a payout is done.

Payouts are automatic and cannot be requested. These rules are run at the start of each hour.


So, the old ugly variance at work :(

spiccioli

Thanks,

I thought as much!

hrumph

0 percent luck?


o
m
g

 :-[ :-\ ???

Variance, look at 30 and 45 days luck, one day is too little.

The other day we had 4 blocks... it can't be so every day :)

spiccioli

edit: you can have a look at a comparable size pool's luck (http://p2pool.info/) and you will find out that, sadly, at this pool's size it can and it does happen to go a couple of days (and even more) without a block.

Yeah, if you guys could go ahead and find some blocks that would be great.

My 100 gh are trying!!!!

Didn't you get the new cover sheet for the TPS reports, I will send you another one just to make sure.

Nice november start, eh?

spiccioli

Btw, last block had 0.25 transaction fees in it, so who found it got a nice 0.125 BTC prize :)

spiccioli

absolutely. I got 0.4 :)  massive amount compared to what i`m used to in one day (0.09!!!!!)

us-central-1b is down for maintenance for a week.  Once that is back I'll remove us-central-2a since that is going to be deprecated in December.

I've added eu-west-1b to get us back up to four nodes.

Nice growth lately,

we're around 30 TH/s now.

spiccioli

edit: and five blocks so far... we should try not to get accustomed to such a bonanza...  ;D

Maybe we have broken numbers and they don't work correctly anymore.

Keep them as broken as you can, fireduck! :)

Last block (http://blockchain.info/search?search=000000000000000549a71e9ccc7ef1c47796bccad3113eee91475569369b0223) paid a good .25 BTC to its finder!

spiccioli

We are doing great, keep it up gents!

Can't see the pool URL in the first post? :)
Would be great to have it there.

Gosh... you're right!

I've added a couple of links... :)

spiccioli

I like your model.  I am going to point some hashpower your way to test it out!

Congrats to someone
https://blockchain.info/block-index/438763/00000000000000018914e17bd674c5d8069ce463e00750cb838b91d3b0ac80c3

Woooww!

I need to put a link on it on the OP :)

spiccioli

Transaction is:
https://blockchain.info/tx/8e9adefd0608b4525d2d35e80247911516d2afcfee8d6bb121c63197ef275df0?show_adv=true

with 18.7908 BTC fee.

I wonder if it was a poorly constructed transaction by hand or a wonky fee calculator (that transaction is indeed huge).

It's not the first tx of this kind.
Seems like those fees are intentional.

It's been a little dry lately, come on lucky blocks, where you hiding?

Lucky periods, per definition, last a lot less than unlucky ones... you can see a lucky period as a reward for enduring an unlucky one :)

spiccioli

Here we go again!

1bush8 gets 0.27 per block (more or less) and today solving latest block (http://blockchain.info/search?search=0000000000000006d7e70fb3ebac4d0c34b864f02bfaa40863ee5c8c8e36e498) he/she got a nice 0.36 prize!

HHTT is the only pool doing this kind of lottery :)

spiccioli

Support the discouraging of address re-use.


The exchange rate value of everyone's Bitcoins depends on killing the lists. Including you, me, spiccioli, and everyone mining, pooled, decentrally or solo.

spiccioli, please consider using the address re-use de-prioritising mining node. This will be a step along the way to preventing the public blockchain record from being used against us to devalue our Bitcoins.

Everyone at HHTT should familiarise themselves with the forthcoming HD wallets feature, keychains. You can create as many keychains as you wish, just like single addresses. This will let you lock reward payments to a sequence of crytographically determined keychain addresses instead of one address. It is a superior alternative to locking to a static address, you can gain more privacy with the same level of security.

HD wallets will likely be available in the 0.9 Bitcoin client.


Support the discouraging of address re-use.

So whatever this thread spam is aside, I've been thinking about that.

For example, if someone wanted to give me an electrum master public key, I could send payments for them to unused addresses on that chain.  I'd be glad to support any other deterministic schemes I could find software for.

Example (not implemented, stated as an example):
A person mines with a username of an electrum master public key.  In the suckers list and status pages HHTT would show something like HMAC(mpk, 'hhtt').substring(0, 20).  That way, no one would be able to see the who mpk.  Then when doing a payment, I would find an unused address on that mpk chain and send the payment to that.  I would also stop posting transaction IDs to make it harder to figure out who each miner was in the payment transactions.  Still possible, but hard after the fact.  The transactions would of course still be visible, but not how much each miner was paid and which miner is which.

Hey gents, on the main mage we show "Orpahans", it should be Orphans.

-Wave

Wave,

it this pool we say orpahans (https://bitcointalk.org/index.php?topic=95378.msg2634370#msg2634370)... ;)

spiccioli

I guess I couldn't change it now.

I like Orpahans.  You should keep it.

This is going to hurt...

spiccioli

What is going to hurt?

Three days without blocks :) but we went through...

spiccioli

Lot of power came on recently. Good stuff, I know about 4thash I talked over from gigas pool.

Any chance FD would add MM for NMC, DVC, IXC?  Over a month all those add up...

You're talking merged mining?

Damn...Long dry spell.

Correct...

At this difficulty, I'm not sure this pool is sustainable at this hash rate.

80 hours per block (average) is way too much variance.  I feel like I am losing money mining here and it is my own pool.

But the last thing I want to do is shut it down.  There are not enough pools and too much mining power is in too few.

@FD,

I wish I had an answer to the "problem".  I would enjoy mining here again but cannot stomach the variance either.  I wish there were 2-3 other pools in the .5-1.5 Ph/s range.  With the upcoming shipments from HF and Cointerra (along with more from KNC) any pool less than 1 Ph/s will be too much variance  :(

Yep.  I am happy that I contributed an open source stratum server implementation, which I know some people have picked up.  I'm glad I helped drive the change to higher difficulty mining.  I also demonstrated building high availability cloud based services. 

The bottom line is that I'm not going to let this pool just drain money in hosting costs.  I'm not going to tell people to mine on it when the variance is just to damn high.  I'm not going to switch back to PPS to take a bunch of risk myself to mitigate the variance.  So that probably means ceasing operations at some point soon.

@FD,

Are you willing to look at implementing MM (NMC, IXC, DVC)?  Having those can add enough extra income to offset the fees.

With Ghash, Eligius and Guild all offering NMC it makes it hard to choose a pool not offering at least NMC MM.

Do you think if I added merged mining that I would get enough hashing power for the pool to be viable?  According to dustcoin, that currently only brings a 1.6% increase in revenue which I think isn't enough of a carrot when measured against the terrible variance.

At this point I hate to say - probably not enough of a carrot.  That said, without NMC it makes it very tough to mine here (ignoring variance) as I am giving up ~1.6% in NMC and have fees too (no fees at Eligius and GHash).

I think many people forget you split the block fees with the block finder.  That is a great incentive for folks with several TH (i.e., those that might have a higher probability to find a block).

As I said above, I wish I had a solution that didn't simply put tons of risk on you (i.e., PPS).

What does it take to run this pool, you make eit sound like a bad investment but the one HHTT payment address at last checked showed over 80+ BTC in it. As long as the pool finds 4 blocks month, what you as the operator gets out of those four should b more than enough to run the server it's on I'd imagine.

As for merged mining, I say give it a shot beause at this point it couldnt hurt.

Have you not looked at the total history?

Total loss of > 818BTC

No, but I just did a check, Final Balance 98.0948075 BTC

at current BTC-e prices the pool has a current value of $68,600 assuming $700 per BTC.

I'm still curious though just how "bad" it could be to host the pool on w/e server it's on.

I gota cloud VPS with 70+gb of space a decen number of CPU cores and available memory and it cost me $100 a month. I don't pretend to know what it costs to host a pool but even on a $200 a month server, that's easily made as a pool opp with ducks settings and assuming a minimum of four bloks a month found

Well if variance is too high you could just make it a p2pool proxy, just like multipool does.
I think in the end most small pools will operate on top of p2pool.

I sent a PM, but I thought I'd post it here for everyone else's comment also along with a few other thoughts.

The two things that would make me mine continuously on HHTT are a larger value of N for PPLNS and merged mining for namecoin. In that order. I love the AWS setup, the minimalistic website, and the ability to define my difficulty. The vardiff adjustment on some other pools is too willing to change the setting every few minutes and create rejects. I would prefer to mine here, but I want to know that my effort will be counted for something in the case of pool hoppers increasing the pool's hash rate temporarily or my own miners going offline at a bad time. N should be at least large enough to cover several found blocks at bad luck. Namecoin mining doesn't do much, but it makes up for the higher fees on some other pools, and if it is done at even a high fee PPS it shows there is at least some progress being made.

I think the larger value of N would appeal to people from BTC Guild and the merged mining would appeal to people from Eligius who also like the lack of registration there. The AWS setup offers benefits that Eligius doesn't have for reporting and stats.

Merging other coins is a lot of work for not much benefit, but it would give an edge over Eligius and BTC Guild. Courting the interests of some hardware manufacturers or group buy coordinators might also be beneficial. For example, if you could figure out how to make it easy to split a group's hash power out to multiple payment addresses, maybe as a premium service, that seems to be something that a lot of group buy coordinators are spending a lot of time with.

It costs about $1000/mo to run.  It could probably be done cheaper.

The 80 BTC isn't really profit, it is my money in a pile to pay people as needed so that miners don't have to wait 120 confirmations to get paid.

You are right, it can be run pretty cheaply.  However, why would a miner stay with a pool when it is more likely that the difficulty will change under you before you even get a block?

That is an interesting idea.  I might look into that.

I'd like to see he pool survive bu no sure if it will now...

last_month last_week last_day last_hour last_5_min
27094.235 19630.003 7967.795 6337.613 5650.846

I'll be shutting down the pool today.  I would be surprised if there were any more blocks.

Thanks everyone.

For whatever it is worth, I've switched my personal miners to slush's pool with BTC Guild as a backup.

Sad to see it go  :'(

Yeah, me too.  I didn't expect it to be even this successful.  I don't know what I am going to look at all day now.

I should note that carefully shutting down something you have spent so long building is like strangling a kitten with your bare hands.

I'm having the last node refuse connections for one hour to help people figure out something is wrong.  After that, I'm going to bring up a p2pool node with a payout address of Sean's Outpost.

http://stratum.hhtt.1209k.com:9332/static/

Thanks for your effort in hosting and running the pool.  It was a good run and I believe it to be one of the most stable pools out there.  Good luck with your future plans, and HAPPY NEW YEAR!

Cheers!

 >:(

I have a few projects in mind.

1) A notification site, you put in bitcoin addresses or electrum master public keys and then you get a notification on any transactions that occur on any of the addresses.

2) A funds splitting app, where you define a split for funds.  Example: 25% goes to address a, 75% to address b.  Then you are issued an address and any funds that go to that address is split as defined automatically.

Both of those would be enabled with a bitcoin transaction processing engine using bitcoinj and electrum servers.  The transaction engine would be good for people building all sorts of bitcoin related things.

It was a good run!  Best wishes FD!

-Wave

Fireduck, what happened with my 0.49070038 PPLNS Share? Since last block found (26 Dec) I contribute with a lot of GH/s. I think you should keep mining alone and distribute the award when you find the block.

Thank you!

Yeah we all contributed lots of GH/s since the last found block.   But this is not a PPS  pool.  The problem is that the difficulty is so high and the hash rate of the pool could not keep up with the difficulty. Too much variance was killing the return.    Your PPLNS work is lost, move on.   ;-(

I just can't lost 0.49070038, it's too much. Please fireduck, do something. It's easy: keep mining solo and after 1~4 months when a block is found, just redistribute the revenue. Fireduck, I trust you, please do something. This service wasn't free, we paid fees. Thank you!  :-*

Fireduck, you said you have a fund to make payment liquid. So I think you can take this fund and distribute proportionally. Go fireduck! Go! Do something...  :'(

It wasn't free for him to provide the service to you either. In my opinion he has no moral obligation to do this for any of us. He certainly has no contractual obligation to do anything. He mined in his pool and lost the same future reward potential as everyone else with the shutdown.

I totally understand that, and I agree, but I think something can be done. Fry the brain and find a solution. I loved HHTT, but this is worse than horrible and terrible.

Don't forget about Eligius! :)

Yeah, this is why it was in no one's best interest to have this pool at this hash rate.  I am absolutely not going to solo mine with my hashing power.

If you are out ~0.5, I am out 4.5 from my own hashing.  I'm not going to get that either.

Even though I never had a chance to mine here, I'm really sorry to see the pool go. It was innovative, stable, and fun. I have no idea why it wasn't more popular than some of the other larger and less stable pools. I also loved some of the weirdness you included in the coinbase.

Thanks for running a great pool, Fireduck. Good luck with future endeavours.

Looks like I've lost a few days worth of profits... Never got paid. >:(

Me too... Very sad  :'(

But more sad of the fact HHTT, funny and cheap has gone.

Fireduck, better lucky for you in 2014.

No block
Fireduck, thank you for running this pool. To see it go is a loss for everyone.

So here's my HHTT in memoriam post: http://organofcorti.blogspot.com/2014/01/17-goodbye-hhtt-coinbase-will-never-be.html

fireduck, may your piles always be small ones, and your bunions always fade.

Fireduck,

I went solo one month ago since I had a few more meat-space duties to follow.

It is a sad day today and I can feel all your pain.

I've enjoyed your pool since the autumn of 2011 when I first started mining on it.

You made a great pool, the best in my opinion, I was not even using backup pools when I was mining on HHTT.

That said, you're a brilliant mind and I'm sure you'll soon find new ways to improve the BTC environment and have fun.

My best wishes for a great 2014!

spiccioli

Cut my teeth so to speak at this pool , far out man  , happy new year and all the best fireduck.

Ha, I didn't think anyone noticed.

I mostly stopped adding things because I changed some database security stuff which made it a pain to get to a system that could write to the db to add entries.

Hey, man. Great pool you had. However, WTF is everyone whining about you closing it, the new p2pool node you run is way better idea! I'm speaking of this: http://stratum.hhtt.1209k.com:9332/static/
I've already made 0.03 bitcoins in that pool and it has been online just a couple of days now.

Maybe I'm missing something but that page doesn't even look complete and how is one supposed to mine off this "new pool" let alone see the hasrate as a whole for said pool ?

It's fully functional, please refer to this: https://en.bitcoin.it/wiki/P2Pool

All the JSON stuff is working so that I was able to modify my ASIC monitoring script, the pool just found the 3rd block today!

Thx but I look at that and my head hurts lol...

Unfortunately http://stratum.hhtt.1209k.com:9332/static/ is currently DOWN!

Hey fireduck, what's going on?

He's closing the pool.

I don't mean HHTTMP, I mean the new pool he opened, the P2Pool.

If you would be so kind, could you please explain your reasoning for switching to Slush instead of any other pool? I tried to run my miners there, but there are constant issues with payouts and reward calculations. It is like the opposite of the stability, reliability, and transparency that HHTT had. I want to support a lower hash rate pool, and I don't mind the variance so much, but not at a significant cost in profitability.

Thank you for your input on this!

Alas, good luck fireduck. The backend of HHTT with all of the Amazon services was a work of art. :) I do very little BTC mining since I mine on my own TRC pool, but I'm still sad to see HHTT go.

Another pool I'd suggest people take a look at is bitparking (offers merge mining, and uses some of HHTT's back end software).

I am actually trying p2pool now.  I have a node setup with a 1% fee:
http://b.1209k.com:9332/static/

Note: I might take down or change this at any time.  It is not redundant.  Your username has to be exactly a bitcoin address or you won't get anything.

I've considered building a wrapper around p2pool to make a viable smaller pool but there are some problems.

1) With p2pool, you have to find mini-shares to get paid.  They are about 1m difficulty, so ok for large miners but not good for smaller guys.
2) The p2pool does adjust share difficulty, but on a global basis.  So with just my miners attached, everyone who connected will see about 1k share difficulty, which is again problematic for small miners.

I could pretty easily run redundant nodes (I am not yet and not sure I will) and could write some code to aggregate stats from them to give people reports so it has that going for it.

I might be able to solve problem #2 by hacking at the code a bit, but I'm not sure I want to mess with that.

Just attempted to fire up some mining to this pool and failed which led back here :(

Sorry to see this closed down. Thanks for all the hard work Fireduck and I hope you have success going forward.

p2pool address given does not resolve for me. Never mind. I got it.

Well the point of p2pool is that everyone should run their own p2pool and not connect to someone else running it, right?

p2Pool is not viable for smaller miners, so a p2Pool proxy is a good alternative.

Ah okay. I've not used it myself. How much hash power should someone have for it to be viable to run yourself?

I suppose you mean the difficulty for each worker, since it reads like node-basis (i.e with your miners...).
Actually everyone can adjust this by append the number they want to the username (address or not),
for example, 13qnEgPTxJW6mm88dLpnHXZyryN5EXBciq+16
But I think it just make the graphs looks nicer for small miners  ;)

Most p2Poolers say a share per day should be the minimum. I'm not sure what that means currently, but from the chart below you can see that the bulk of the p2Pool miners are above 100 Ghps.

http://3.bp.blogspot.com/-nfhLP_Wjjfs/UtOA6LUgO0I/AAAAAAAALY4/kYypdkygwns/s1600/8.userHashrate12-01-2014.png (http://organofcorti.blogspot.com.au/2014/01/january-12th-2013-weekly-pool-and.html?showComment=1389673402830)

Ah, didn't know that.  But that auto adjust to something to keep the graphs pretty would be very nice.

This can be done easily, but such a "big pool" feature might not be suitable for p2ool,
I guess it is why forrestv does not implement or hear the request.

You could try --miner-share-rate or --address-share-rate in auto-worker-diff branch of my git fork:
https://github.com/iongchun/p2pool.git (https://github.com/iongchun/p2pool.git)

Not mined here but seeing a pool close is sad. (i'm an altcoin pool op myself)

Maybe this would help you to open a mini pool piggybacking off the p2pool net?

https://github.com/dogestreet/proxypool

Hi fireduck, back when you posted I hadn't even looked at p2pool before but I've been into it a lot lately. I made a patch that addresses your point #2 above.

https://github.com/forrestv/p2pool/pull/174

It's actually live on the whole VTC p2pool network and works well. I didn't do a similar change for the pseudo share difficulty (the one for graphing/etc) because I was concerned about the increase in bandwidth if a large public node suddenly went from globally 1 share per second to having 1 share per second per miner. Of course, normal pools tend to vardiff people to submit shares every few seconds anyway, so maybe I should do that. It's easily enough to change.

Just noticed the website is still up!

http://hhtt.1209k.com/user-details.php?user=1Zevusze7BjTpp4srJhx4zkRBxpbgwU4A

Found Blocks

source   time   ok   win   error   difficulty   btc   found hash   block
sockthing/dub   2013-03-09 04:50:10   Y   Y      132   0.00074612   00000000 000000ff 0419cfbc   block
sockthing/iad   2013-03-01 09:09:37   Y   Y      257   0.00173999   00000000 000002b5 cf33afa0   block
pushpool   2013-02-10 00:49:18   Y   Y      65536   0.49519937   00000000 00000029 8cccf8dc   block
pushpool   2013-02-01 06:20:12   Y   Y      262   0.00218153   00000000 0000013b 69cbbd2a   block
pushpool   2012-09-30 06:59:02   Y   Y      4092   0.07071510   00000000 000001a2 ecb9c590   block


presently I shall ponder this under the tree of woe.


needs to be some nostalgia forum on here... and not archive.   ;D