This document discusses how to configure cgminer for HHTT.
If you are not using cgminer, just try pointing your software at:
With cgminer, the simplest thing to do is to create a config file named something clever like hhtt.cfg and then run 'cgminer -c hhtt.cfg'. The examples below are what to put in your config file.
Your username tells HHTT everything it needs to know about you. It should be your bitcoin address, an underscore and a difficulty that you wish to use.
For example I have a single 60 GH/s BFL Single. 60 * 4 = 240.
Allowable range is 1 to 65536.
This is recommended for most everyone.
{ "pools" : [ { "url": "stratum+tcp://set0.hhtt.1209k.com:3333", "user": "1FdkASiCe5Tkueouk2mZHfnDPGwtYFYFRW_256", "pass": "moo" }, { "url": "stratum+tcp://set1.hhtt.1209k.com:3333", "user": "1FdkASiCe5Tkueouk2mZHfnDPGwtYFYFRW_256", "pass": "moo" } ], "load-balance" : true }
Replace the address in user with your bitcoin address and put in your desired difficulty.
This is assuming you have tor running as a socks proxy on port 9050
{ "pools" : [ { "url": "socks5:localhost:9050|stratum+tcp://zy2e3jz56abvdndx.onion:3333", "user": "1FdkASiCe5Tkueouk2mZHfnDPGwtYFYFRW_256", "pass": "moo" }, { "url": "socks5:localhost:9050|stratum+tcp://4s4vswb6lcmpm4wy.onion:3333", "user": "1FdkASiCe5Tkueouk2mZHfnDPGwtYFYFRW_256", "pass": "moo" }, { "url": "socks5:localhost:9050|stratum+tcp://aqkdl2ssyrxymggx.onion:3333", "user": "1FdkASiCe5Tkueouk2mZHfnDPGwtYFYFRW_256", "pass": "moo" }, { "url": "socks5:localhost:9050|stratum+tcp://nkf5yhpk6aqrx3zu.onion:3333", "user": "1FdkASiCe5Tkueouk2mZHfnDPGwtYFYFRW_256", "pass": "moo" } ], "load-balance" : true }
All endpoints will answer stratum on port 3333.
Non-tor endpoints will answer on 80 and 443 as well.
Never depend on a single node, any single node can do down and stay down for a long time.
DNS round-robin nodes are pulled when they fail health check but the health checks are not perfect and take time to take effect. This is why the example config has a load balance among the two sets. cgminer is smart enough to figure out which is healthy and use that faster than dns round robin.
It is unlikely that one of the set0 or set1 endpoints will be down, but it is possible. Never depend on a single endpoint there.
If you must use a single endpoint, use stratum.hhtt.1209k.com.
Latency across the world (~100ms) makes no noticable difference. Don't worry about using a near node.