Maged, if you want we could do some sort of insurance or bet on pirate defaulting. That way you can stay in BTC.
BTC is an experiment and well... this is how it goes:)
That doesn't help me if BTC is worth 50% of what it was before he defaulted. Actually, Pirate defaulting should cause BTC to gain value. My reasoning is that Pirate is likely long on Bitcoin. I expect him to keep most of the stolen BTC, while a fraction of the defrauded people will likely re-buy part of the BTC they lost.
|
|
|
Yes, most of the resetters are USB devices, but connect them to a $25 Raspberry Pi computer (USB host), and your $100+ device still seems overpriced...
|
|
|
enterpoint has sold over a 100 boards (without a decent bitstream)
How did that happen?!? Because their prices are the lowest by far: $640 for a quad LX150 board. Compare this to Ztex's $920 (qty 50+), or btcfpga's $1070...
|
|
|
Some of the Rev3 came with fans on the bottom, too. The difference between the two is that the Rev3 has the heatpipe system.
Yeah, maybe its an error in the document Yes it is an error in the document. All my rev3 (ie. with heatpipe) singles came with a sheet incorrectly stating "rev 1".
|
|
|
Also related: https://bitcointalk.org/index.php?topic=37451.0merphi: I designed a similar product, for my own needs, that controls more computers (45), is cheaper ($80), and is simpler. Like yours, the device activates the power/reset swich and is controllable by an API using my own scripts. I think you need to revise your specs or price if you want to find a market in this community. Like Blazr said, the people here are very resourceful and favor very much simple & cheap products over overengineered/expensive ones.
|
|
|
With a desktop power supply powering my 6 singles and a Dreamplug, I get about 50 Watts per single at the wall.
It must be the default power adapter that eats up a whole 30 Watts to itself.
Thanks for report, but could you measure it with multimeter - voltage and current consumed by board ? That is really interesting. And possibly core voltage ? Thanks again!!! Jothan's numbers are incorrect (perhaps he is trying to subtract a baseline idle power consumption that is incorrectly measured, or his watt meter is defective, or his singles are throttling)... I measured power consumption with a clamp meter around the 12V input, and I get 66W per Single (rev 3 without the big 80mm fan an the bottom, the ones with the fan consume 68W), with an average 81W at the wall measured with a kill-a-watt, meaning the power adapters are 66/81 = 81% efficient. And BFL seems to be using core voltage of 1.1V per the test points in the top right corner of their PCB: https://i.imgur.com/vrzol.jpgI measured 1.13V with a multimeter on this 1.1V test point.
|
|
|
Weirdly enough when I touch the case of my single wrong (particularly on the underside) it starts making a wretched rattling noise. I'm not sure where that bottom fan is interfering but I have been trying to figure it out. I ended up just placing it out of the way and have been avoiding moving it This happens because the poor mechanical design of the Single leaves too little space between the case and the fan, so the blades sometimes touch the case. I fixed 2 of my Singles exhibiting this pb by adding 4 washers between the 4 bottom standoffs and the PCB, pushing the bottom side of the case further down by another extra 1mm.
|
|
|
The right term is majority attack.
|
|
|
If that was 2 days ago, why do you post today that you haven't heard anything from our company in 8 days?
cuz0882, can you answer this question?
|
|
|
Its only hyperthreaded? Thats kinda pointless altogether.
I use this term liberally. I have no idea what type of threading Xeon Phi will implement (the GPU way: switching unconditionally to the next thread on each instruction; or the CPU way: switching to the next thread when the current one would wait on memory). But either way, it does not matter to us. Mining is an embarrassingly parallel workload, so an implementation can be adjusted to fully exploit the ALU resources of Xeon Phi, and whatever type of threading Xeon Phi implement will not add supplemental performance.
|
|
|
I see why you are confused. 2112 meant superscalar, not hyperthreaded, as pointed out by others.
I think the confusion runs deeper that just me. Here's the quote from the "Knights Corner Performance Monitoring Units"; Intel's document number: 327357-001 2. 4-Way Threaded: Each Knights Corner core is able to process 4 threads concurrently.
Xeon Phi is hyperthreaded (the vendor-neutral term for this is SMT = symmetric multithreading), but as I am sure you know SMT does not increase the performance at all of ALU-bound workloads. Therefore we can ignore SMT when making theoretical estimations of the performance of bitcoin mining.
|
|
|
I wonder how this number is going to change once we include the information that the basic core resembles Pentium which was dual pipeline and that now the cores are 4 way hyperthreaded.
Sorry, I got a little confused. I see why you are confused. 2112 meant superscalar, not hyperthreaded, as pointed out by others.
|
|
|
I thought hyperthreading only have like a 25% performance boost tops?
2112 is not talking about hyperthreading. He is talking about the U and V pipelines of the original Pentium CPU, where a single core, a single thread, can execute up to 2 instructions per clock. It is unclear whether Xeon Phi can dual-issue LRBni (512-bit) instructions (and has enough execution units to execute 2 per cycle), or can only do it for x86-64 (32/64-bit) instructions. I assumed the former, hence my 280 Mhash/s estimate. If not, performance would be 560 Mhash/s as 2112 pointed out.
|
|
|
rjk: nope. This 45586 part (there are many of them) and the other do not have the plastic bridge between pins 7-8, and (as you pointed out) do not appear to have the right keying which should be:
LL RRSS SRRR
L = Latch R = Round S = Square
|
|
|
I actually know a person who works for Intel who is developing this. You would all shit your pants if you knew who he was in this community and you probably wouldn't believe me.
I don't think you are telling the truth. He says this is going to get about 2.4 Ghash range (they are still testing it) and it was supposed to cost about 1000 dollars but maybe they want to compete with asic and offer cheaper prices? But again, this card isn't really for Bitcoin, so who knows.
Xeon Phi should get about 280 Mhash/s (1200 billion 32-bit operations per sec / 4300 operations): https://bitcointalk.org/index.php?topic=88407.msg974306#msg974306
|
|
|
Thank you theymos for implementing the watchlist! Had you not done it yourself, I would have looked into writing it myself
|
|
|
OK I can see that happening in the face of a sudden dramatic drop in network hash power, which at this point I find unlikely. Taking your example further, we could say that for a diff of 1.7m, a drop to 3Th/s would need only 3 more Th/s to 51%, however it would be extremely boring because the network would be functioning at half speed and everything would take twice as long to occur.
What I am saying is true even if the hash rate suddenly increases by 2x. If it does, then you would need 24 Thash/s to perform a majority attack, while the difficulty would still be 1.7M. There. I gave you 3 scenarios where you would need either 6 Thash/s, or 12 Thash/s, or 24 Thash/s, to perform an attack, and in all 3 cases the difficulty would still be 1.7M for up to 2016 blocks. The bottom line is that the difficulty factor is an average of the last full chunk of 2016 blocks, whereas a majority attack only needs to be executed for a handful of blocks (depending on how many confirmations are required by the recipient you are planning to double spend), and the global hash rate can vary either up or down quickly between these 2 intervals.
|
|
|
no, its not what you were saying. what i said is completely true. difficulty has nothing to do with the 51% takeover. raising or lowering the difficulty would have 0 effect on the 51% takeover. bottom line is that you need 51% of the network's total hashing power.
The difficulty directly affects how much power you need to have in order to achieve 51%, correct? Technically, no. Because the difficulty adjusts itself with a certain latency. Right now the difficulty is 1.7M and the hash rate is 12 Thash/s. So you need 12 Thash/s right now to perform a majority attack. But if tomorrow the hash rate drops to 6 Thash/s for whatever reason, then you would only need 6 Thash/s, while the difficulty would still be 1.7M. The difficulty would only drop to 850k after up to 2016 blocks.
|
|
|
|