I'm mining with GPU now, works great.
Testing it for 2-3 weeks for stability, then release.
wouldnt u like a "beta " tester alongside you? +1 willing to donate my time to do some "testing". |
|
|
|
|
@ckolivas: Is there an issue tracker for cgminer? I am having trouble with ztex (hence dont want to threadjack here about competing vendor). Whats the best place to report it? I am a little reluctant to post in the huge cgminer thread without reading 512 pages....
bfgminer works fine, cgminer detects the ztex, but breaks during configuration. Id much rather use cgminer for my purpose.
|
|
|
|
anyone working on a LQC pool? 25
lqc bounty
i tried to port p2pool ( Warning: non functional - https://github.com/turtle83/p2pool-lqc ) Too many apis missing from liquidcoin deamon.... its a very old fork of bitcoind . If someone can safely re-do the lqc code should be really easy to get p2pool to work... |
|
|
|
... So, all 3 of them contributed to both projects  Somewhat incorrect. .... Apologies, didnt know the full history. |
|
|
|
That's good IMO, I had a bad feeling about 5Ghash+ password crackers being released into the wild with no oversight.
Oversight? You're sounding like a statist. I say release 5 Gh/s password crackers into the wild and let the chips fall where they may! +1 Id expect this to be the what people replacing FPGA with ASIC do... Time to use scrypt with a very high N for security purposes... Or SHA-512. But yeah, bitcoin FPGAs usually take getwork/stratum data as input and give as output a 32-bit nonce. They do not transmit the hashes outside the chip because 300Million x 256bit per second is 76.8Gbits of bandwidth. So no, they can't really be used to crack passwords. I would imagine that ASICs use the same sort of paradigm. Yeah ASIC work in similar manner IMHO, but what i mean is FPGA can be re-programmed to find hashes. No need for bandwidth. Send target hash. let fpga run bruteforce , and return valid cleartext if found. 200MH sha256(sha256(x)) ~ 400 MH sha256(x). 6 character lower case + upper case + number = 56800235584 combinations or ~56800 MH so 142 seconds on single lx150 prolly take lesser time since data sizes is small... dunno... |
|
|
|
|
even in 0.05 diff... my turtle rig has yet to find a block... orphan or otherwise...
|
|
|
|
it's Obama's fault
No Bush did it! |
|
|
|
Downloading blocks... so far ~23000 . difficulty : 0.05000000 So 23000th block was mined at so low difficulty? How? {
"version" : 50003,
"balance" : 0.00000000,
"blocks" : 23000,
"connections" : 7,
"proxy" : "",
"generate" : false,
"genproclimit" : -1,
"difficulty" : 0.05000000,
"hashespersec" : 0,
"networkhashps" : 1399392,
"testnet" : false,
"keypoololdest" : 1368816856,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
|
|
|
|
gentlemen: excellent news. i just heard from our wonderful, glorious cat.
we're the first to get delivered.
That is fantastic! It's great to have good news in ASIC-land, when it's so often...not. Or is it fantASIC? |
|
|
|
gentlemen: excellent news. i just heard from our wonderful, glorious cat.
we're the first to get delivered.
wait can't news awesome |
|
|
|
That's good IMO, I had a bad feeling about 5Ghash+ password crackers being released into the wild with no oversight.
Oversight? You're sounding like a statist. I say release 5 Gh/s password crackers into the wild and let the chips fall where they may! +1 Id expect this to be the what people replacing FPGA with ASIC do... Time to use scrypt with a very high N for security purposes... |
|
|
|
The basic principle of Proof of Work scheme is - hard to do the work and easy to check that it is done right. There is no easy way to check that newly discovered digits of PI are not just taken from the air, so it will not work.
Exactly. I thought about picoin months ago.... and while bitcointalk was loading in my browser i realized it would be just as hard to validate the PoW as to do the work itself.. so pointless exercise. |
|
|
|
But thats not a fork of the original p2pool, hence its a mamoth task to track changes and make sure there is no hidden backdoor or exploit. |
|
|
|
As I promised, I'm announcing the release date and time one day before.
Onecoin will be released tomorrow, 17.05.13 at 12:00 GMT
Please clarify. You mean:- 1) UTC (Forum time) or 2) UK local time GMT is confusing word, open to interpretation. |
|
|
|
What is the difference between plain JS and Web Workers anyway?
Plain JS will run on the UI thread. So it will make scroling and other legit activities on the page much slower. (inversely those things will interfere the miner). Only one thing can happen in a thread at a time, so mining and UI things will fight each other for the slot. It could make the browser tab completely unresponsive even. Webworkers run in seperate thread, so UI thread is not affected. On most computers it would likely run on a completely different cpu. http://html5demos.com/worker go there click start worker, you will see your system is using 100% cpu on one core... but the browser window still responds like usual . i.e. u can scroll, etc. Runing this in plain JS is worse than water boarding the user IMHO. |
|
|
|
|
Show Posts
