Many times but never close enough for the finer points  Thanks! I just got 10Mhash more per card by adding WORKSIZE=128. |
|
|
|
Wow, Stratum climbed from 80 or so if I recall correctly to 124.506 Ghash/s over night.
Yea I remember it at 80 too. And the normal cluster was 2000 and is now down to 1935. Awesome! Healthy for the network too. |
|
|
|
|
Hey everyone,
I have a few 5870s running Phoenix 1.7.5 and they each get about 400Mhash/s. I use the phatk kernel. I haven't investigated switching things in awhile, and maybe it is late in the game now that the ASIC revolution is around the corner. But is this an acceptable hashrate? I saw some posts where people were getting 420+Mhash/s. I'm just wondering it its even worth my time at the moment to upgrade & test newer miners & kernels. Besides temperature issues this system has been stable since last spring so I haven't tinkered with it.
They are on Slush's pool using his new Stratum mining protocol and rejects have dropped from .84% to .07% under Stratum.
Thanks!
|
|
|
|
Well it worked! Average hashrate in last 10 rounds: 2789 Mhash/s Finally up to full capacity! (Estimated at 2800Mhash/s - 400mhz per 5870) If I sell them on Ebay one day would it be ok to mention they were run outdoors?  |
|
|
|
I have 4 cards on there now Here are the stats: [397.47 Mhash/sec] [7714 Accepted] [8 Rejected] [RPC (+LP)] [398.73 Mhash/sec] [7717 Accepted] [9 Rejected] [RPC (+LP)] [383.78 Mhash/sec] [7205 Accepted] [3 Rejected] [RPC (+LP)] [400.54 Mhash/sec] [7507 Accepted] [3 Rejected] [RPC (+LP)] 23/30,140 = .07631055% vs. [366.03 Mhash/sec] [114607 Accepted] [980 Rejected] [RPC (+LP)] [401.11 Mhash/sec] [199204 Accepted] [1697 Rejected] [RPC (+LP)] [398.42 Mhash/sec] [199115 Accepted] [1620 Rejected] [RPC (+LP)] 4,297/512,926 = .837742676% So there's some real world data for everyone! Edit: Make that 7! |
|
|
|
In this case you now have BTC "in an address" which has a public key published to the block chain. Is that right?
That's right. As far as the best place to learn, I think I learned pretty much everything from reading these boards.  Neat, thanks Yea these boards are great! So would there be a disadvantage from then sending *all* coins in a wallet to a new address? That would clean things up so to speak. Could there be any disadvantages you could think of? One could possibly be that if someone sent coins to one address, and then saw it sent as an input along with other inputs in a transaction, they would be able to tie the owner to the other addresses (if they knew who s/he was), right? Thanks! |
|
|
|
|
RC3 working fine on Windows 8.
|
|
|
|
That RAR file has the CRC32s of the PDFs when they are not encrypted. We could generate all the CRC32 collisions of valid PDFs with the exact number of bytes, hahaha. Probably not computationally feasible though We might as well try breaking AES |
|
|
|
Go for it! Looks like I just found a block! Brings our total to 10... any way of finding out which blocks were mine? So far 0 stales on the new proxy We average about .8%. Is that normal? PS Could not resist and have 2 cards on the new Stratum protocol now! |
|
|
|
Let's celebrate! Block of round #13852 has been finished by Stratum pool! And the founder iiiis.... no digital, it's not you :-(. Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2". Congrats! I'm planning on trying it soon with about 2.8Ghash (I emailed yesterday with a bug which you are working on), but I am running phoenix miner. I think it is the latest of the 1.x branch. Should it work? (Also any reason to switch miners... I get about 400Mhash from each of my 5870s. It could be a pain cause I have a lot of custom scripts for temperature control although IIRC they should work with any miner as they just use aticonfig.) Did you tried to install dependencies by "sudo easy_install twisted stratum" ? I'll have time to dig into and release some fix only on Monday. But this is quite specific bug happening on your system and that command above should help you. Basically you can run any getwork miner towards stratum proxy, including phoenix. So there's no reason to move to other miner if you'll have some monitoring scripts. Also I'll work on stratum patch for Phoenix 2 soon. It works! I had to install easy_install first naturally and run "sudo easy_install -U distribute" but it looks good! I just moved one rig outside and there's a tarp over it to deflect any rain so that is a bit of fun today... 1 card on that rig is now on stratum! I'll compare the rejects over the next 24 hours or so and report back. Then I'll switch both cards to stratum. Next week I'll move over all 2.8 Ghash. |
|
|
|
You guys are a huge help; I didn't think of the heatpipes freezing up. It won't go even to 32F for quite awhile so I will investigate that further. I one on the balcony now with a nice tarp over it (just noticed a bug flying by.. think I left the screen door open for too long!), and I ran a "rain test" by using a watering pitcher to simulate rain beating down on the tarp They run cooler & at higher clock speeds now! The rigs aren't in cases actually, they are just motherboards with an HD and a few cards in them along with a PSU. One is out there now, so I just need to transfer the other one. |
|
|
|
How cold are we talking? Here in Maine, the winters can get pretty chilly!
Dust wouldn't be my main concern running outdoor rigs, as Graet mentioned you can clean them pretty easily! My main concern would be moisture/condensation. Can you ensure they will be kept dry at all time?
Good question, I am in NC... there is no roof at the moment but I have an outdoor storage area I will put them in, and keep the door open perhaps with a tarp to deflect rain which might blow in. Just started one up so the test is in progress! |
|
|
|
Cool This will be interesting! Too bad nobody could see me with a vacuum cleaner on my balcony... |
|
|
|
I did this last summer on my back verandah starting to warm up here again, they will be going out soon Awesome Just cleaned off the verandah here, going to run a test Fortunately there is an electrical outlet outside. No Ethernet though! They obviously were not thinking ahead when they constructed this place! (No Ethernet inside for that matter). |
|
|
|
Just kidding But has anyone run rigs... outside?! We have broken a few A/Cs now to the point where we don't keep all of the rigs in one apartment  At the moment they run OK when the room they are in is 90F. A control script clocks down if any of the cores hit 83/84C. That actually doesn't happen often because there are extra fans zip-tied onto the cards. Problem now is it is cooler outside so the general ambient temperature of this place is far lower. Of course the rig room is hot but with the door open it vents out and distributes. But if the door is closed (the noise is insane so I keep it that way during the day) then it gets too hot! Basically in the summer the A/C would run and cool everything. Since the thermostat is far from the rigs it doesn't heat up enough to kick on. I would have to keep this place really cool in order to compensate for this. So.... given that they run fine in a 90F room (I wonder about the power subunit of the card though...) and it is only about 80F out these days, provided I could keep them safe from rain and insects I was thinking about putting them on the porch? There would be no room to heat up and they would be much quieter from my perspective. Totally crazy idea? We have about 2.8Ghash and I want to try and run for as long as possible until ASIC release and difficulty drop! Thanks! |
|
|
|
Maybe I'll turn my spare GPUs to cracking ECDSA when I convert to ASICs.
GPUs are no good at point multiplication from what I was able to discover on the very limited amount of data on the subject a few months back. Parallelization is not a performance enhancement. I always thought address reuse was mainly to protect privacy somewhat - would you mind explaining this more? How does address re-use let the public key be known?
It is about privacy, for the most part. When you send a transaction with an address that is only known to the network as a hash, you must give your public key, or your public key will be derived from the signature. Then the network knows the public key for that address. But as RIPEMD160 is "160 bits of security" vs. the effective 128-bits of security of a 256-bit elliptic curve, it is 32 bits more secure in a sense, but not really against a brute-force attack as it just adds another step of first converting private keys into public keys (a relatively slow operation compared to hashing) then hashing (very fast) to see if it matches the hash. But since a RIPEMD160 hash is not necessarily just a hash of a public key (could be scripts or something else to throw it off, or one of several signature algorithms in the future), the address space being larger does make it somewhat more secure under some circumstances. Ok cool, I read about this some more and I want to make sure I am starting to understand it. Please correct me if I am wrong. So the idea is that receiving multiple times to one address would not be bad, because in that case only the hash is published. But the problem comes in if you spend coins from that address (in which case 100% of them are sent, some to the receiver, and some back to you as change in a new address), and THEN you again receive coins to the address which you received from. In this case you now have BTC "in an address" which has a public key published to the block chain. Is that right? Thanks! |
|
|
|
Let's celebrate! Block of round #13852 has been finished by Stratum pool! And the founder iiiis.... no digital, it's not you :-(. Blocks done by Stratum can be easily identified on blockchain.info; they're "Relayed by slush" and have "Version 2". Congrats! I'm planning on trying it soon with about 2.8Ghash (I emailed yesterday with a bug which you are working on), but I am running phoenix miner. I think it is the latest of the 1.x branch. Should it work? (Also any reason to switch miners... I get about 400Mhash from each of my 5870s. It could be a pain cause I have a lot of custom scripts for temperature control although IIRC they should work with any miner as they just use aticonfig.) |
|
|
|
Maybe I'll turn my spare GPUs to cracking ECDSA when I convert to ASICs.
GPUs are no good at point multiplication from what I was able to discover on the very limited amount of data on the subject a few months back. Parallelization is not a performance enhancement. I always thought address reuse was mainly to protect privacy somewhat - would you mind explaining this more? How does address re-use let the public key be known?
It is about privacy, for the most part. When you send a transaction with an address that is only known to the network as a hash, you must give your public key, or your public key will be derived from the signature. Then the network knows the public key for that address. But as RIPEMD160 is "160 bits of security" vs. the effective 128-bits of security of a 256-bit elliptic curve, it is 32 bits more secure in a sense, but not really against a brute-force attack as it just adds another step of first converting private keys into public keys (a relatively slow operation compared to hashing) then hashing (very fast) to see if it matches the hash. But since a RIPEMD160 hash is not necessarily just a hash of a public key (could be scripts or something else to throw it off, or one of several signature algorithms in the future), the address space being larger does make it somewhat more secure under some circumstances. Thanks Etlase2! Where is the best place to read about these internals? I am going to study https://en.bitcoin.it/wiki/Transactions but is anywhere else good? Besides the source code |
|
|
|
|
Interesting the files inside the archive have a modification date of 1/7/2012 8:18am. Why would they have been created so long ago?
|
|
|
|
In the unlikely event that secp256k1 is ever totally broken, there is still the hashing problem to deal with.
As in, even if someone can find the private key for every possible public key, most public keys aren't known, only the RIPEMD160(SHA256(public_key)) is in the blockchain, unless you re-use addresses, which everyone has been warned not to do.
I always thought address reuse was mainly to protect privacy somewhat - would you mind explaining this more? How does address re-use let the public key be known? |
|
|
|
|
Show Posts
