The past is hilarious. More music videos need to include shooting pants off people playing bag pipes.
|
|
|
I rebuilt the latest git-head and it still says "2.0.9" instead of "2.1.0" cgminer version 2.0.9 - Started: [2011-12-27 18:26:22] -------------------------------------------------------------------------------- (5s):667.5 (avg):734.3 Mh/s | Q:10 A:1 R:0 HW:0 E:10% U:11.64/m TQ: 4 ST: 4 SS: 0 DW: 0 NB: 1 LW: 0 GF: 0 RF: 0 Connected to http://goat1.zapto.org:8337 with LP as user redemerald Block: 0000014bb22ba5dbb6f2d4a0ab571ae0... Started: [18:26:06] -------------------------------------------------------------------------------- [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit GPU 0: 68.0C 4340RPM | 388.2/462.4Mh/s | A:1 R:0 HW:0 U:11.64/m I:8 GPU 1: 64.5C | 370.5/371.2Mh/s | A:1 R:0 HW:0 U:11.64/m I:7 GPU 2: 56.0C 3395RPM | 315.4/299.6Mh/s | A:0 R:0 HW:0 U:0.00/m I:8 --------------------------------------------------------------------------------
Other than that, looks good so far.
|
|
|
Just sent my 5 to 148KkS2vgVi4VzUi4JcKzM2PMaMVPi3nnq
Thanks again. I'll post something that actually uses this soon. Is anyone else who pledged (or not) actually using the RPC yet?
|
|
|
This looks like something that should be on the wiki
|
|
|
This thread is better than porn
|
|
|
I just have one 5970 that is unbranded (so Dell). I almost bought a second but then they became impossible to find.
I first had it set to 835/300, but it crashed after a few days. It's been really stable at 830/300 since June on stock air cooling in an ACd server room so it never gets above 75C with 85% fans. It's in a spare antec 1200. I would love to build a custom case for the nerdgasm, but I have other projects to work on.
|
|
|
Sorry for the typo that ended up confusing a ton of people...I meant 3BTC and typed $3.00. Anyway, glad to see that the 3BTC price has passed and look forward to adding a few shares to my portfolio.
Anyway, adding a FPGA could be a good investment but wouldn't be a significant part of our hashing power. I don't know that the cost savings in electricity would be worth the initial outlay especially given the potentially rapid advances in FPGA miners. On the other hand, investing in a water cooling solution could both greatly increase hashing power at little/no electrical costs.
Does water cooling reduce electrical costs? I thought it just helped with noise and heat.
|
|
|
Wouldn't work without modifying the protocol and sourcecode.
What would have to change in the protocol? I just want to see the IPs that bitcoin is talking to.
|
|
|
Total time logged in: 3 days, 14 hours and 59 minutes.
|
|
|
If someone wants to pull the master tree and check the formatting now please? My main rig just blew a mobo so I can't even check the GPU output cgminer version 2.0.9 - Started: [2011-12-27 04:50:37] -------------------------------------------------------------------------------- (5s):644.4 (avg):708.8 Mh/s | Q:10 A:1 R:0 HW:0 E:10% U:11.87/m TQ: 4 ST: 4 SS: 0 DW: 0 NB: 1 LW: 0 GF: 0 RF: 0 Connected to http://goat1.zapto.org:8337 with LP as user redemerald Block: 00000b3c547d8b81053607186b8dd5cf... Started: [04:50:12] -------------------------------------------------------------------------------- [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit GPU 0: 61.0C 4316RPM | 378.3/468.1Mh/s | A:0 R:0 HW:0 U:0.00/m I:8 GPU 1: 57.5C | 380.1/380.1Mh/s | A:1 R:0 HW:0 U:11.87/m I:7 GPU 2: 47.0C 3369RPM | 348.5/305.4Mh/s | A:1 R:0 HW:0 U:11.87/m I:8 --------------------------------------------------------------------------------
Looks good
|
|
|
Ah, that's where I thought you would have seen the list of hidden services. They shouldn't be listed elsewhere, since they're useless without the instructions.
I removed them from the other page, added a link and expanded the explanation of how to properly connect to the hidden services. I still think that if I set my server running the tor hidden service to also proxy it's connections through tor, then it will reject incoming connections and not work properly.
|
|
|
Are you using mapaddress?
I just added this to my torrc and made my bitcoin.conf match mapaddress 192.0.2.2 p2hwc26zdsrqxiix.onion mapaddress 192.0.2.3 sh4ep6zb6vnoa2h5.onion mapaddress 192.0.2.4 iy6ni3wkqazp4ytu.onion mapaddress 192.0.2.5 bxfna6fhddpzduck.onion
I'll let you know if it works. Why does bitcoin not support using a remote DNS? I would think it should considering it has proxy support. Oh wow. I finally found this page https://en.bitcoin.it/wiki/Fallback_Nodes#Tor_networkWould sure be nice if https://en.bitcoin.it/wiki/Tor mentioned it... EDIT: That did it theymos! Thanks! $ bitcoind getinfo { "version" : 50000, "balance" : 3.74654100, "blocks" : 159331, "connections" : 1, "proxy" : "127.0.0.1:9050", "generate" : false, "genproclimit" : -1, "difficulty" : 1159929.49722438, "hashespersec" : 0, "testnet" : false, "keypoololdest" : 1319583806, "keypoolsize" : 101, "paytxfee" : 0.00000000, "errors" : "" }
I'll add something to the wiki to make this more clear for people
|
|
|
So I voted no, but then I went to a Christmas party today and did talk about it. My family seemed pretty interested. Some of them had actually heard about it already but didn't know much about it. I didn't get too technical and explained hashing as "difficult math" but they got the basic idea. I made my main point that it cannot be printed by some idiotic central authority (i.e. The Fed) and cannot be seized by any bank or government and allows near instant transfer anywhere, including places that the government/credit company/bank/etc does not want you to send money like WikiLeaks.
I think it went over well. No one seemed bored at least.
|
|
|
I'd pretty much guarantee that FPGAs will be cheaper in 6 months. Maybe get more GPUs now and save the FPGAs for later when their $/hash is down.
And what do you mean "Free electricity in my office" I thought your were paying ~$0.13/kWh
|
|
|
I like namecoin, but it has different use cases than bitcoin and so a thin client isn't really useful. The rest of the alt-chains are scams or not that useful. I thought I might like litecoin, but it seems to be a waste of electricity. Let's get electrum working. By then the alt-chains we are talking about today will probably be dead and so implementing them will just be wasted time. Keeping our eye on a modular app design is important though. Having to install pygtk on my mac was a bit of work and won't ever be available on my iPhone, so electrum's ease-of-use is less than I would prefer. Is there interest in a web-based electrum client? It could store your private keys (that aren't deterministic) in local storage like GLBSE does. I'm a web developer, I haven't done much work with desktop GUIs, and I want to help this project so a website is where I can help. If we had a simple webapp we could use phonegap and really easily have electrum clients on every major smartphone.
|
|
|
I am trying to setup a tor hidden service for bitcoin and am having a difficult time getting it to actually work. It would be helpful if I could see the clients connected to me instead of just the number of clients connected to me. Is this possible?
I don't mind having to modify some code and rebuilding the client, but my C is rusty and some tips on where to start would be great if this is what I need to do.
Sadly, I'm pretty certain that bitcoin does not play nice as a tor hidden service since I'm pretty sure bitcoin wants IPs and tor doesn't give it any. As laws stand now, there isn't really any reason to hide that you are running a node but now just I want to know why tor hidden services don't work properly.
If anyone runs bitcoin through a tor proxy and has the hidden services working, please let me know.
|
|
|
I think light clients (server based) will be far more successful. I don't think the fact that the client can hold private keys will be of great relevance since I think most bitcoin payments in the future won't even hit the bitcoin network.
Um. Holding the private keys is one of the most important things in my mind. This means that you don't have trust whatever server you are using to not steal your coins and it also means that if said server goes offline, you can still access your coins.
|
|
|
EDIT: Actually, I'm not sure that's enough to fix it. Right now my server does not have "proxy", "connect", or "nolisten" in it's config.
When Bitcoin uses Tor, nolisten is automatically applied, and you can't override it. I'm pretty sure connections from localhost are allowed. When Bitcoin uses Tor as a proxy, nolisten is automatically applied. More specifically, when a proxy on 9050 is detected, nolisten is automatically applied. I think this is dumb since tor might be on a different port, but thats for another topic. Your patch changes this. However, I have NOT set "proxy" on the server running the hidden service. All I did was setup a hidden service that points to 8333. Bitcoin on this server is currently completely unaware of tor being used. However I still cannot get a connection to any of the listed tor hidden services. That's why I think there is something more going on. I ran a second bitcoind on my tor server (where the primary bitcoind is public) with nolisten and connect=127.0.0.1 (which is similar to how a connection coming to the hidden service would look), and it was able to connect. I also ran a second bitcoind on my client (where the primary bitcoind proxies via tor) that has "nolisten" and "connect=127.0.0.1." It was unable to connect which makes me believe that when "nolisten" is set, even connections from localhost fail. I think that there might be a problem with bitcoin trying to resolve the onion names via dns or something instead of passing them to the proxy like it should, but I'm not sure and my C is really rusty so auditing the code will take me a while. Once I get this working properly, I may add "proxy" back to the config. For now, I don't mind broadcasting that I am running a node on my IP and I also like having better connectivity to the network. Mila, do you have any connections? I'm wondering if I just need to be more patient since tor can take a while to resolve. I still think something else in the bitcoin client needs to be modified though.
|
|
|
fNoListen = GetBoolArg("-nolisten") //|| fTOR; Whoops, you need a semicolon before that comment. I'll build it with these changes soon. I need to download some dependencies first. I'm still not convinced this will work though as I noted in my previous posts' edit.
|
|
|
It changed within the last month or two, I think. You'd need to make these changes to fix it: net.cpp if (/*fUseProxy ||*/ mapArgs.count("-connect") || fNoListen) { // Proxies can't take incoming connections addrLocalHost.ip = CAddress("0.0.0.0").ip; printf("addrLocalHost = %s\n", addrLocalHost.ToString().c_str()); init.cpp fNoListen = GetBoolArg("-nolisten") //|| fTOR; <3 EDIT: Actually, I'm not sure that's enough to fix it. Right now my server does not have "proxy", "connect", or "nolisten" in it's config. When connecting to the IP directly from another node, the connection works. When I try to use the hidden service from my remote node (which should appear to the server as a connection from localhost), my node fails to connect. Your code changes don't seem to do anything for that failure.
|
|
|
|