|
Wow. I'm totally going to try this when I get some time.
|
|
|
|
With any water cooling kits, make sure you added stuff to the fluid to keep algae down. Also, I hope you didn't mix metals. Aluminium + copper = bad in a loop. Aside from that, that looks awesome! How cool are the miners running? No doubt that radiator can handle the heat 
|
|
|
|
Now what? Microsoft will buy bitcoin like it bought Skype? :-)
Microsoft will have to talk to the CEO of Bitcoin first. Who's that ? All of us but none of us.
|
|
|
|
assuming 3 tubes can be plugged into one controller......does each tube need a individual IP, or just one for the controller?
I can confirm that 3 tubes work off one controller. You just need to set them all to the correct ID's and chain them correctly and they'll come up.
|
|
|
|
I just don't get it, I have one of the S3's they raffled off.. I know its true because I set it up for him 
|
|
|
|
|
My friend, Rustiga submitted 38,573,325 shares in the last round, PPLNS was only at 5,533,631. Mine on the other hand match at 58,226,377. Any idea why his are so low?
|
|
|
|
lol yes.. I know I know.. it really shouldn't happen again, but I digress... Everyone keep in mind that maintaining pool speed, stability, and uptime is of the most importance as it's also handling our internal and partner mining operations... we're currently over 1PH ourselves... There's a new PPS (pay per share) system coming into place in the near future that'll pay out every 10 minutes. If anyone's interested in helping beta test this please private message me.
PM Sent 
|
|
|
|
|
Just report the posts. They have their own thread.
|
|
|
|
|
If you want gigabit speeds to all your devices, you need Cat5E or better along with a gigabit switch. For most stuff at home, any gigabit switch will work. I have't had one die on me yet.
|
|
|
|
|
Anything will be fine as long as it allows for the device to connect to the internet.
|
|
|
|
|
To run the exe or not....
source?
|
|
|
|
Fixed it! ~/nomp/coins/guinea.json { "name": Guinea", "symbol": "GUINEA", "algorithm": "sha256", "txMessages": true }
|
|
|
|
|
OK, I'll keep digging then. If I find a solution, I'll post it.
|
|
|
|
Any idea what I'm not doing right? My local pool running nomp gets and error of the block decode failing. my coin.json { "name": "Guinea", "symbol": "GUINEA", "algorithm": "sha256" }
error: ThreadRPCServer method=submitblock
******* exception encountered ******* guinead[0x5342bc] guinead[0x41fc07] guinead[0x4234c8] guinead[0x4ef883] guinead[0x4f06e6] guinead[0x4c0ef3] guinead[0x4c4520] /usr/lib/libboost_thread.so.1.49.0(+0xe95b)[0x7f28afd4f95b] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7f6e)[0x7f28aef53f6e] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f28ae4609cd]
|
|
|
|
That is crazy. Why would they stop accepting bitcoin? They probably just wanted to get the free publicity. I just checked. It's still there.
|
|
|
|
|
Option is still there. I just checked. Were you trying to purchase from the Marketplace? I tried picking up a CPU and bitcoin was an option.
|
|
|
|
|
Got this up on my local pool within 30 minutes. Coin compiled form source in OP and works fine with NOMP. A++, will continue to mine!
|
|
|
|
from the skype crew hope this helps and thanks
[1:21:55 PM] argakiig: remove libboost 1.54
and go back to libboost 1.4x
[1:24:37 PM] argakiig: 13.04 and 14.04 use a libboost 1.5x
dyoungii: apt-get install libboost1.48-all-dev
trying now and will report back. Still nothing... Same error. ******* exception encountered ******* tekcoind[0x533a4c] tekcoind[0x41fdc7] tekcoind[0x423688] tekcoind[0x4ef6b3] tekcoind[0x4f0516] tekcoind[0x4c0d23] tekcoind[0x4c4350] /usr/lib/libboost_thread.so.1.49.0(+0xe95b)[0x7fee09c1f95b] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7f6e)[0x7fee08e23f6e] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fee083309cd]
I'm just going to download the window client and point my pool at it and see if that works.
|
|
|
|
I et this error from my stratum when connected over roc: rpc error with daemon instance 0 when submitting block with submitblock {"code":-22,"message":"Block decode failed"}
What does this mean?
This is what i get from the debug in the tekcoind:
ThreadRPCServer method=submitblock
******* exception encountered ******* tekcoind[0x53354c] tekcoind[0x41f157] tekcoind[0x422f18] tekcoind[0x4f01b2] tekcoind[0x4f0f36] tekcoind[0x4bf582] tekcoind[0x4c2c10] /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0(+0xba4a)[0x7f7fc547ea4a] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f7fc4688182] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f7fc3b9530d]
I am having the same issue with my local setup. Any ideas? $ tekcoind getinfo { "version" : "v1.1.0.0-gf96a5a-TEK", "protocolversion" : 60006, "walletversion" : 60000, "balance" : 0.00000000, "newmint" : 0.00000000, "stake" : 0.00000000, "blocks" : 435172, "moneysupply" : 1490519.87117800, "connections" : 7, "proxy" : "", "difficulty" : 284098.24045857, "testnet" : false, "keypoololdest" : 1404738618, "keypoolsize" : 101, "paytxfee" : 0.00010000, "errors" : "" }
|
|
|
|
I've been trying to setup a Curecoin pool using NOMP but haven't had any luck yet, is there something out of the ordinary with block submissions? I keep seeing messages like this when submitting a block:
We thought a block was found but it was rejected by the daemon, share data: {"job":"10a2","ip":"127.0.0.1","worker":"bsom.1","height":2903,"reward":13000000,"difficulty":106.83760684,"shareDiff":"78839945.97002709","blockDiff":3675593.04712938,"blockDiffActual":3675593.04712938,"blockHash":"000000000000003679e92759a80c36f6f40d2a370bf9f03ce0567b707358369b"}
Using the latest wallet with the following coin config:
{ "name": "Curecoin", "symbol": "CURE", "algorithm": "sha256" }
I have the same issues as well. I am very interested in the answer. Same issue here, too Anyone? I have everything in place for a CURE pool and miners wanting to mine but its useless if block submissions don't work. I believe runlinux found a solution to this that he mentioned in IRC, something about setting the daemon settings to accept some sort of message. I'll ask him on IRC and post back. Any luck? Still looking to get a CURE pool running. { "name": "Curecoin", "symbol": "CURE", "algorithm": "sha256", "txMessages" : true }
|
|
|
|
|