Using Go language? Get a star from me.

Result: array of asset names and balance amount

{"error":[],"result":{"XXBT":"0.4000000000"}}

Result: object of asset name and balance amount pairs

I need to vent for a minute, because I'm so fucking sick and tired of this when I have to modify someone elses code, or even look upon it.

If you code in 1TBS style, I fucking hate you.  I hate you with every fiber of my being.  I want to know what is wrong in your brain that makes you think that 1TBS is the "proper" or more "acceptable" way to style your code.  Why are you so fucking dense and incapable of simple human comprehension of visual coding styles that you want to subject others to your shitbag, fucked up, illegible coding style?  I fucking hate you.  I FUCKING HATE YOU AND I AM NOT THE ONLY ONE.  If I could reach through the internet and punch you in the face, I would.  I would spend my days punching every single asshole who writes code in 1TBS style in the face... that would be my purpose in life and I would attack that purpose like a manic-depressive fat girl on a giant ham after her internet boyfriend left her for another lithe woodelf in a different guild.  

I would sit, at my chair and spend 23 hours a day, taking only a single hour to sleep and eat and shit throughout a 24 hour day, punching you in the face.  On Christmas and other holidays, I would treat myself and fly around around the world, with a satellite phone hooked up to my laptop on a chartered jet, punching each of you in the face over the internet, just so I could spend more than 24 hours in a single day punching you.  I would have this jet fly with the setting sun, so I am always punching you just when you're sitting down to dinner, I would do this for nearly 48 hours straight, hopped up on Mt. Dew and Red Bull. This is how much I hate you.

On New Years, I would fly to Australia and spend the entire day punching the most egregious offenders of this fucked up indent style, then I would fly to back to the US and DO IT ALL OVER AGAIN ON THE SAME DAY.

Tell me, you 1TBS motherfuckers, tell me why you think your indent style is something even marginally approaching reasonable?  It's fucked up.  It is idiotic.  IT IS COMPLETELY UNREADABLE. Why do you do it?  Do you hate other people?  Are you so antisocial that you can't get it through your head that it makes your code look like complete shit?  Do you not understand that it makes debugging or following your code all but impossible?  Do you think you are in 1970 where every single byte counts?  What is it?  What makes you think it's ok to indent like this?


That is fucking goddamned unreadable.

Pick a readable indent style. Allman makes the most sense:


Look.  Gaze upon it. It's easy to follow.  It's easy on the eyes.  You can quickly see what bits of code belong to what controlling statment.  You can see what opening brace matches with what closing brace.  You can see what else matches with what if.  You can see how many else statements there are.  Seriously.  Look at it.  Now look back at your shitbag 1TBS code and tell me the same thing is true.  You can't, because if you do you are a fucking liar.  You're already an idiot for using 1TBS, don't make yourself a liar, too.

Now, go cry me a fucking river about how Allman takes up more room or some other line of complete bullshit.  It's not about visually compacting your code, it's about MAKING IT FUCKING READABLE.  Your shitbag style may be more compact, but guess what?  WHO THE FUCK CARES?  Nobody.  Not a single fucking person on the planet will ever care how compact your code is.  They care about whether it works.  Then there's the poor fucking bastards that have to maintain it after you've gone off to spread your disease to other projects, and let me tell you, they do NOT FUCKING GIVE A SHIT how compact your code is.  They care about it being readable and sensible.  Your shitty style is neither.  STOP.  JUST STOP.  Take your 1TBS style and stick it so far up your ass that it pops out the top of your head, hopefully taking the part of your brain with it that makes you think 1TBS is an acceptable indentation style.

Fuck you.

Or better yet, if you hate BFL that much, let the public record stand.  Stop giving them publicity.  Talk about other hardware vendors and how they screwed up.  It seems like people feel validated to have an Inaba post show up just so they can say "SEE?!  SEE?!  THERE IS THE DEVIL HIMSELF!". 

And for disclosure, no I don't have any monarchs on order, but if BFL catches up to the point where it is reasonable to order > ship within a week and their hardware is priced right I would purchase from them again because everything from my purchase to change of address to interactions with employees has been pleasant.  Not the same story for everyone, but otherwise they've lived up to their end of the bargain, albeit delivering late.

^^^ There was an issue with API, but it's fixed now so you should see 3 digit decimal place precision via API as well.

{"error":[],"result":{"XXBTZUSD":{"asks":[["180.99000","1.000",1382812788],["181.09000","1.000",1382812790],["181.49000","2.000",1382812791],["181.99000","5.000",1382812793],["182.10779","2.318",1382816070],["183.14787","2.311",1382814912],["184.00000","4.000",1382803434],["184.18721","2.301",1382799994],["185.00000","0.068",1382783772],["185.22970","2.304",1382799185],["186.25941","2.393",1382805478],["187.29523","2.360",1382815870],["195.00000","69.600",1382815830]],"bids":[["180.10000","1.000",1382812787],["176.74142","2.391",1382805850],["175.72506","2.200",1382794683],["175.00000","0.200",1382816691],["174.69205","2.257",1382799184],["174.11000","10.000",1382769865],["173.66816","2.233",1382799994],["172.64736","2.309",1382814911],["171.63269","2.356",1382816154],["162.00000","36.700",1382815828],["160.00000","0.275",1382654380],["150.00000","0.500",1382652252],["128.00000","0.220",1381961554],["116.54000","0.560",1381201402],["115.60000","0.850",1381201417],["113.00000","0.350",1381201510],["111.80000","0.365",1381201438]]}}}

Order volume precision has been increased to 3 decimal places in Kraken market data. Order volume data is still being rounded up as stated above, except now it's being rounded up in the third decimal place.

So, for example, an order with an actual volume of 1.0341 will appear in the order book as a volume of 1.035.

We hope this level of volume precision is more convenient for everyone and appreciate our users openly communicating with us about the features they would like to see on the exchange.

And... another ~1000 units shipped today.  1/3 of the entirety of KnC's shipment... in one day.

Um... yeah.  So this turned into a bit of a hate-fest.  Serious replies still appreciated, curious why the vendor pool, if mining is such a good investment, has basically dried up after early next year?

This thread starting good....and BAM !

Trolls come back again with BFL rage  

Come on...

So for an update on shipping times... As you might imagine, we get this question a lot. It seems like it would be a simple question to answer, but it's not. Let me describe the process so people can better understand why.


If you look at the current FPGA board in a Single or MiniRig, you'll see lots of capacitors, resistors, etc... about 350 little tiny parts attached to the board. Contrary to some of the conspiracy theories out there, all our boards are completely custom made, they aren't purchased from another manufacturer, etc... they are designed by us and made for us and us alone. As such, we are required to volume source every single part that goes on the board.


The ASICs are similar in so far as they also have nearly 350 components on each board. With the FPGAs, we sourced parts in the hundreds or low thousands at a time. For some of the ASIC parts, we are sourcing hundreds of thousands at a time which requires direct ordering & lead time dependancy from the respective manufacturers. However, for this first batch, we're mostly able to depend on available distribution stock from places like Mouser and DigiKey. Shortly after we get the first batch of everything in, we'll have our larger mega stockpiles arrive from other vendors and/or direct from the distributors, it's just the first batch that's going to be rough.


So, we've got he myriad distributors shipping thousands of little pieces to us, the PCB manufacturer sending us the bare PCBs, the HSF manufacturer sending the HSFs to us, the PSU manufacturer sending the PSU's to us, the case manufacturer sending the cases to us and most importantly, the fab sending the ASIC chips to us. All of these must arrive on time and as expected for everything to go off without a hitch. So far, so good.


When we made our announcement for shipping dates, we padded in some extra weeks in case of delays, and as we try to herd all these cats into one corral, our padding is slowly eaten up with mostly minor problems, but they all add up. With the bump in specs, we spent some time ensuring the power subsystem is over powered to accommodate the new and future power requirements - our chips are capable of higher speeds than what we initially intended to send out in the first batch, and they still have quite a bit of headroom; We decided to go ahead design the power subsystem to handle the maximum theoretical load of the chips. This means we can now crank the board up with some minor tweaking. Each chip is theoretically capable of operating at 1 GHz, we are running them at 500 MHz with the new specs... we will likely never see 1 GHz operations, simply because of heat density issues and a few other factors, but we have at least another 25% of headroom we can play with, if not more. Again, we built in a lot of padding into the specs, just in case something went wrong. We have basically padded everything we could in terms of estimates and that padding is what has allowed us to bump specs on short notice and keep our shipping times in line even in the face of delays.


Ok, so we have the cats herded, the specs staked out, now we have to actually build these things. As many of you know, we've purchased SMT machines to allow us to manufacture our own boards - and I have mentioned this before, but many have not heard it - we will not be using the SMT equipment to process our first batch of boards; we will be using the same house that did the pick and place for our previous generation products, which means we're still at the mercy of someone else for our first batch shipments. There has been some delays at that stage, but we have the padding, so it's not been a critical issue. There has also been some delays at the foundry, but again, we have padding, so it's not been a critical issue. We are also paying for an expedited run at the foundry (which does not come cheap) to keep our timeline up. All these things have to work out perfectly and our timeline is still looking good. However, if something does not work out perfectly, our timeline is going to slip, plain and simple. We've used up most of our padding at this point and we are still ironing out a few little wrinkles here and there. This has been a long explanation for a simple answer: I would like to tell you we are still on time or pretty close to it, because we are. However, I would also like to tell you that we are going to slip a couple weeks or so if anything goes wrong, and given the complexity of the issues facing us, I would say it's almost inevitable something will crop up between now and the beginning of November that we are not expecting; What that is, I don't know yet, but I would rather error on the side of caution, say the timeline is going to slip a little bit and then surprise everyone with an early delivery than promise an early delivery and not meet that promise. So that's what I'm doing and there's your answer. When I have more information, I'll let people know as soon as I can.

Endless, repetitious, unsubstantiated bullshit...

There are no orders being shipped that were ordered a year ago, please stop spreading false information.  Our failure rate on hardware is less than 1%, much better than industry average, so again, your argument is invalid.