544
|
Bitcoin / Hardware / Re: "Avalon" ASIC, announcement & pre-order. second wave @ 9:00am EDT, 10/03
|
on: October 07, 2012, 12:07:54 AM
|
I'm pretty sure BFL would rather package dogshiat in a box with a lifetime warranty. They'll claim to be first to market even if it takes 5 rmas to get a half working ASIC.
I went with Avalon because dr zhang actually does what he says and he's very good at taking care of his customers. He knows his shit too. BFL, not so much.
|
|
|
547
|
Bitcoin / Hardware / Re: Can someone explain how the ASIC vendors can supply double spec hardware ?
|
on: October 03, 2012, 07:30:46 PM
|
And see this is the thing the vast majority fails to see, these asic's as far as everyone knows are designed after old low end model chips. When a designer coughs up the 10k plus for a virtex-7 and builds that to ASIC, all there products will be null.... 150k LE VS 2Mil LE lol
There's always a better product coming or possible. These aren't static. I mean when Apollo launched the computer it used to go the the moon and back is overpowered by modern watches now. In a couple of years these will be paperweights. In 10-15 years we'll have some sort of personal data device/phone/watch/whatever than can do circles around anything we have now. The only real question is will you get a return on your investment? It's a game of chicken.
|
|
|
550
|
Alternate cryptocurrencies / Altcoin Discussion / Re: New Ixcoin fork -> I0coin
|
on: September 28, 2012, 04:22:10 PM
|
D-Day is approaching. the old iocoin client is floundering and the qt build crashes constantly. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just commited the patch to enable BIP16 & BIP30 on Mon, 01 Oct 2012 00:00:00 GMT, that is a plenty of time to make sure that all the miners and clients upgrade to the new client & daemon before the changes on the protocol get implemented. Also, here is a compiled windows executable of the latest i0coin client: http://kr105.com/i0release.rarMD5: b6e857ce844e3a9634e2cdb3d8789b6c SHA256: be7392209ed3bb00b8deabaf8394b83e79201ce2bce52be6d31d8044f6fa2996 Source: https://github.com/kR105/i0coin/Have fun! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQIcBAEBAgAGBQJPm4clAAoJEPNF3YKtV8UAXEwQAKD0JX/OoCVxDsjxVYulhfDk NlhMHnxiS3zdD12PLXYDo8ii/v97ZGuRKHWz5QgTYEPoQDCluMzF4Lc8jM8GIv16 TWzJmH0mEzTkb0s+PsjoZebYzNia6T1luqe/ergIKvKZnR25dLMB+nUVTuNYzA4+ Vs+dnyOfTvHF+EhQexxrQgv5b+DDwtgaLr3ZOHHbLb2p5I29B1s5A+YUk3Ij8eFq W4BQZHds7phSIp5KKmOXNmtMmJqBGzGtYoxvX4Ql2td72JCsNrdb/82FugmuqMOA 132MT7ZYDH6q6uvOvnfFNifMkxOCk+KTmkrwBnEcb2P2tmY+RCaH5GfVJgOVHeFi oAF1DkAvjstLpHkyUjRcp1iml4R8Lq/OZmPOrCc5Oul78XFuUWPaoF5C2GaZSgWs O1zA5RUNXrDw2EuyOHyIV82SOrXSvqQj0Ju0F+f145I8RdfVvPYT9Ls9YYbKTiCs /Tww52jvRCVUQrlg3rXmxKXXtwXmcvNWM1rWN3O7gniDcJzowwvTRTn+8n64SRD3 u0PHPi0lXUcEnGs1IughknexB4z9ErhF+Qbg3bpDRNPD4GBVEaG1aJPbBVdoJ5oq v4CxqbCize5WQms1p+sNbeMXGnGhapIGhzukLBG1kpS5V51wIXg2OOrrOrkRz3Y6 iwi+Lr9oq7easbwt2pCW =84BM -----END PGP SIGNATURE-----
|
|
|
552
|
Bitcoin / Pools / Re: [400GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
|
on: September 28, 2012, 02:39:48 PM
|
V5 still seems to have problems with memory leaks, seems more to be an issue with how it talks to .7 bitcoin qt as when it happens, both start to consume HUGE amounts of memory. run_p2pool will start blasting lost connection messages or scrolling this message constantly exceptions.ValueError: too many file descriptors in select() 2012-09-28 09:44:04.312000 > Unhandled Error 2012-09-28 09:44:04.312000 > Traceback (most recent call last): 2012-09-28 09:44:04.312000 > File "run_p2pool.py", line 5, in <module> 2012-09-28 09:44:04.312000 > 2012-09-28 09:44:04.312000 > File "p2pool\main.pyc", line 781, in run 2012-09-28 09:44:04.312000 > 2012-09-28 09:44:04.312000 > File "twisted\internet\base.pyc", line 1162, in run 2012-09-28 09:44:04.312000 > 2012-09-28 09:44:04.312000 > File "twisted\internet\base.pyc", line 1174, in mainLoop 2012-09-28 09:44:04.312000 > 2012-09-28 09:44:04.312000 > --- <exception caught here> --- 2012-09-28 09:44:04.312000 > File "twisted\internet\selectreactor.pyc", line 104, in doSelect 2012-09-28 09:44:04.312000 > 2012-09-28 09:44:04.312000 > File "twisted\internet\selectreactor.pyc", line 40, in win32select 2012-09-28 09:44:04.312000 > 2012-09-28 09:44:04.312000 > exceptions.ValueError: too many file descriptors in select() eventually it'll use up all available ram and blow up.
|
|
|
555
|
Bitcoin / Mining / Re: can there be an early difficulty adjustment?
|
on: September 25, 2012, 10:46:55 PM
|
You all do realize that if mining hardware kept getting more widespread and more powerful at an insane rate like 4x per block cycle, bitcoins would be depleted in 25 years instead of 100, right? Cutting off like 7 days may not seem bad but any reduction to the useable life is bad. That's why the protocol should have been designed to overcompensate for overmining in the next cycle. Like if 1.2x the bitcoins are mined because of an increase in GH/s, adapt the next cycle to anticipate at 0.8 total bitcoin mining rate over the next difficulty period.
It'll end up like namecoid did a while back with months between difficulty changes.
|
|
|
|