No, none. Already read all the pages.
Did you read the actual magazine, or just the scanned pages? |
|
|
|
|
With many reports of people getting the november issue of Bitcoin Magazine, and indeed even some scans surfacing, I was wondering if there was any relevant new information to be found in that magazine.
I was under the impression, that the november issue of Bitcoin Magazine would contain more detailed information regarding BFL's ASICs, and stated that issue #4 will answer many questions that people were asking. I've seen scans of this magazine, and it all looks like 6 month old information to me.
Could anyone with access to the full magazine confirm if there indeed is any previously undisclosed detailed technical information on BFL's products?
|
|
|
|
Spartan-6 chips are actually quite a bit worse at Bitcoin mining than comparably-sized Virtex ones, it's just that the price difference more than makes up for it.
Word. I'm running -3I chips and max out at 300Mhps per chip. |
|
|
|
|
Thanks for the update Friedcat! Just my curiosity, do you have everything else that you need ready? E.g. PCB's, PSUs, components for PCBs, reserved manufacturing slot at assembly house..
|
|
|
|
We don't need silly pictures, we need a demonstration of the chip doing the actual hashing! even if it is an early prototype with a few percent less performance!
Guess what, they don't have one. |
|
|
|
Please provide evidence or it didn't happen. A link to the relevant posts would suffice, thanks! Cool story, bro.
Inaba/Josh, I'm really beginning to regret I paid you back those 138BTC what your pool's bug paid me. I thought you were a nice guy. I'm beginning to think I was mistaken. Why do you need deny the problems you've had with your pool? Even I sent you a mail regarding my 7.2GH/s miner showing up as 5.5 GH/s on your pool, just to get ignored. I really think/hope you've got better things to do. So why don't you just do us all a favor and stop hijacking your employer's competitor's thread? Thanks. |
|
|
|
|
Just got this from GBLSE:
"Your GLBSE account has been processed for bitcoin. The next step will be to send you information about your assets, and to provide this information to issuers (if you agreed) allowing you to continue your relationship with your issuers." Let's keep fingers crossed!
|
|
|
|
|
I'd like someone on the board to comment whether they're up-to-date with how this is being handled from Bitfountain's side. I haven't heard anything for several days, and boy would it make me feel better if I knew what's going on.
Did Bitfountain hold any BTC on GLBSE? Does GLBSE going under affect the speed of the manufacturing process in any way? How are the dividens going to get paid without GLBSE? What will happen to us shareholders if GLBSE fails to provide information on who's holding stock? Is there a plan B?
|
|
|
|
три модели - 1 ГХ/с, 4 ГХ/с и 48 ГХ/с Цена самого дешёвого девайса ожидается в районе 32 БТЦ по предзаказу. Наверное ты опечатался и имел в виду 32 USD? Иначе я не понимаю. Да нет, вроде бы не опечатался. При условии отсутствия БФЛ, цена около $320 за 1+ ГХ/с в настоящее время выглядит нормально. Для меня очень важно не обещать того, что может оказаться неосуществлённым. Так что лучше пообещать 1 ГХ и сделать 4 Гх, чем пообещать 4, а сделать 2. А вот за $32 это невозможно, разве что только если заказывать сотни тысяч, чтобы себестоимость каждого чипа была менее $2-$5 [/quote] Bonds are traded via icbit.se at ~$300 per Gh/s as "DB.RCLMR". The price is justified by the "absence of competition" (in real life). Your numbers are a bit off. It's closer to ~$35 per GH/s for the biggest device. The smallest one is more expensive, but still very far from ~$300 per Gh/s. These are contradictory by a magnitude. Tycho, you say 35 USD per GH/s on this thread and 32 BTC per GH/s on the russian thread. |
|
|
|
GLBSE uses SSL from the browser to Cloudflare and from Cloudflare to the GLBSE server, cloudflare can minify JavaScript (hence the "we may change site content" in their TOS). I have a paid service with them.
OMG you're using cloudflare? So you're trusting all our wealth in hands of a SSL proxy?! I'm out!  |
|
|
|
|
I'm running CGMiner 2.6.4 on RPi with 13 Ztex 1.15x. I've taped RPi's USB ports 5V+ line, so power from USB hubs doesn't leak into Pi. Only problem I'm having is one random board dying out after a while. Disconnecting this dead board will cause another random board to fail after a while.
|
|
|
|
Whoever help me figure out how to get this running, I'll send them a free steam activation key for supreme commander and forged Alliance.
I installed the client and can created my ppcoin.conf file in my roaming/ppcoin folder. I'm pretty sure the ppcoin.conf file is setup wrong and that's why it can't connect or start mining. My 7950's are remaining idle.
Your ppcoin.conf file should look like this: rpcuser = anyusernameyoulike rpcpassword = anypasswordulike server = 1 rpcallowip = 127.0.0.1 Then start your cgminer and add a pool: URL: http://127.0.0.1:9902username: same as set above for rpcuser password: same as set above for rpcpassword |
|
|
|
It's kinda cute, but the GTA4 Liberty City map as bg befuzzles me. |
|
|
|
|
I think you should list one more risk in your list of risk scenarios, which is another manufacturer beating you in time to market or manufacture. The implications of this would potentially be higher difficulty at start of mining + earlier halving of the block reward. Hedge would ofc be the same: to diversify your portfolio.
|
|
|
|
I'm having issues running a cluster of 16 Ztex 1.15x boards with CGMiner or BFGMiner on Raspberry Pi. For some reason, 1random board dies within 1 hour and LED 2 goes on.
It's still alive, it's just twiddling thumbs. If LED2 is on the board is in power save mode. This happens if the board receives no new work for 5min. I'm not familiar with BFGMiner please report this bug in the BFGMiner thread (or use BTCMiner). Thank you for your analysis. I've already contacted developers of both programs, but was trying to get some more clues as to what is causing this. You see the miner software thinks the board is not responding and thus first declares it as "sick" after 60 or 90 sec of inactivity (don't remember precisely) and tries to restart it. That seems to fail every time. Then it's finally declared "dead" after 10 minutes of inactivity. Interestingly enough, this bug doesn't seem to affect rigs which also have GPUs in them. |
|
|
|
|
I'm having issues running a cluster of 16 Ztex 1.15x boards with CGMiner or BFGMiner on Raspberry Pi. For some reason, 1random board dies within 1 hour and LED 2 goes on. Then it keeps mining nicely as long as I leave the dead board connected. If I disconnect the dead board, soon another board dies. Everything works on BTCMiner, so I doubt it's a USB cable. LED 2 points to the EZ USB, any ideas?
|
|
|
|
|
I have found a bug that is reproducible. It seems cgminer always declares 1 ztex board dead after a while (1h or so). Interestingly enough this does not happen on my other rigs that are x86 based, and have also GPU's connected to them. Very weird indeed. Reproducible also in BFGMiner.
Also, if 1 board is declared dead and is kept connected to the computer, no more boards will be decalred dead. If I disconnect the dead board, soon another one will get sick and dead.
System setup:
CGMiner 2.6.4 running on Raspberry Pi
14-18 ztex 1.15x
|
|
|
|
Elden,
Is it possible to run the tricone mining host software on a Raspberry Pi?
I've tried it some time ago without success. You can experiment with it also by using ARM version of BTC miner http://blog.villekangas.com/?p=23. I believe some libs used by TML need to be ported. Maybe you can get Ville to do it with a small donation  |
|
|
|
|
Show Posts
