<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace V5 Site Server v5.13.159 (http://www.squarespace.com) on Fri, 24 May 2013 11:14:58 GMT--><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><title>Blog</title><link>http://blog.bitinstant.com/blog/</link><description></description><lastBuildDate>Thu, 16 May 2013 05:36:57 +0000</lastBuildDate><copyright></copyright><language>en-US</language><generator>Squarespace V5 Site Server v5.13.159 (http://www.squarespace.com)</generator><item><title>BitInstant Dealing with Increased Traffic and Transaction Delays</title><category>Bitcoin</category><category>backlogs</category><category>bitinstant</category><category>customer service</category><category>customer support</category><dc:creator>BitInstant</dc:creator><pubDate>Wed, 10 Apr 2013 19:08:44 +0000</pubDate><link>http://blog.bitinstant.com/blog/2013/4/10/bitinstant-dealing-with-increased-traffic-and-transaction-de.html</link><guid isPermaLink="false">1479007:17514312:33278308</guid><description><![CDATA[<p>The last few months have seen some growing pains here at BitInstant that you may have, unfortunately, had to deal with. Let&rsquo;s get this blog rolling by flat out apologizing for that. We&rsquo;re sorry for delays in transactions and communication. We understand how much it sucks to be sweating your money without great communication. So, keep reading and you&rsquo;ll learn what&rsquo;s been going on and how we&rsquo;re changing to make these problems a thing of the past.</p>
<p>&nbsp;</p>
<p><strong>Why the Problems?</strong></p>
<p>&nbsp;</p>
<p>With all the popular media attention bitcoin has been getting lately, people have been getting wise to the idea that this is the future. As a result, BitInstant been slammed with new and return users alike. And it&rsquo;s not just us; our partner exchanges have been feeling the burn too. So why exactly does that cause problems?</p>
<p>&nbsp;</p>
<p><strong>How BitInstant Works</strong></p>
<p>&nbsp;</p>
<p>To understand this it&rsquo;s important that you realize exactly how BitInstant works. It takes time to move funds around, even digitally. We created BitInstant to help you get money faster by creating accounts at the different exchanges and putting our own funds into them.</p>
<p>&nbsp;</p>
<p>When you make a new BitInstant transaction we aren&rsquo;t able to magically move YOUR funds faster &ndash; we take some of OUR funds out of OUR account and move them into your account on whatever exchange you&rsquo;ve chosen. When things are running smoothly our funds show up in your account and you go on your happy way. Then we patiently wait for your funds to catch up to our account and repopulate our reserves &ndash; a process that can take days.&nbsp;</p>
<p>&nbsp;</p>
<p><strong>What are you doing with my money when I don&rsquo;t see it? </strong></p>
<p>We&rsquo;ve heard a lot of complaints suggesting that when you don&rsquo;t get your money immediately it&rsquo;s because we&rsquo;re hanging on to it so that we can make more money. So let&rsquo;s set the record straight, this is definitely not what&rsquo;s happening. We don&rsquo;t hold bitcoins and don&rsquo;t make more money when your orders are delayed; it actually hurts us because orders are processing more slowly. When you send us your funds we immediately initiate your requested transaction and queue the funds to enter your requested exchange. We aren&rsquo;t trying to game the system and we&rsquo;re not making more money when your transaction is delayed.</p>
<p>&nbsp;</p>
<p><strong>What&rsquo;s the Problem?</strong></p>
<p>&nbsp;</p>
<p>High volume with lots of requests for fund transactions increases the demand on our accounts. Because it can take days for us to receive the funds that previous customers sent, our reserves on the different exchanges can get low. When many people make near simultaneous demands on our system it&rsquo;s been hard to keep up with the demand.</p>
<p>&nbsp;</p>
<p><strong>How are we fixing this? </strong></p>
<p>&nbsp;</p>
<p>We are working to be aware of issues sooner so that we can temporarily disable transaction methods when backlogs exist. This will ensure that customers who have placed transactions will have their orders fulfilled before new orders are entered into the system. We have backup liquidity providers that we are working on getting online to help prevent these situations. So when you see an exchange temporarily disabled from our list of transaction methods &ndash; this is what&rsquo;s going on. We&rsquo;ll also alert you via @bitinstanthelp on Twitter when we make these temporary changes to the transaction methods.</p>
<p>&nbsp;</p>
<p>We take these problems very seriously and work every day to improve our customer experience. In the last six weeks we&rsquo;ve hired four new full-time support staffers to help process tickets and we&rsquo;ve been training them on our systems. There&rsquo;s a lot to know to help process your orders but we&rsquo;re starting to turn the team loose to help out which should make a notable difference on our support ticket turn-around time.</p>
<p>&nbsp;</p>
<p>We&rsquo;ve added a support form to our website to help collect the information that we need to solve your problem quickly (<a href="https://www.bitinstant.com/contact">https://www.bitinstant.com/contact</a>). This will reduce the number of interactions that are required to solve problems. You can also access this form from our Facebook page by clicking the &ldquo;WuFoo&rdquo; icon at the top of the page.</p>
<p>&nbsp;</p>
<p>We&rsquo;ve also launched a Twitter account to help alert you to potential delays in our system. Please follow @bitinstanthelp &ndash; we will be updating this account regularly when our support team is working.</p>
<p>&nbsp;</p>
<p>**We will still be working through the tickets that are still outstanding in our system but you are welcome to submit a new request through the form to make sure we have all the necessary information to solve your problem.</p>
<p>&nbsp;</p>
<p><strong>Conclusion</strong></p>
<p>We&rsquo;re sorry that we haven&rsquo;t been able to keep ahead of the Bitcoin demand, but we&rsquo;re actively trying to solve these problems. The items listed above are only the beginning of the support improvements we have planned for the coming weeks. We hope that you will bear with us through some of our growing pains and understand that we value our customers and want nothing more than for your transactions to be quick and painless. We will always do our best to try and turn problems into happy customers. If you think we&rsquo;ve made a mistake let us know and we&rsquo;ll work with you to refund fees and resolve the situation. &nbsp;&nbsp;&nbsp;<strong></strong></p>]]></description><wfw:commentRss>http://blog.bitinstant.com/blog/rss-comments-entry-33278308.xml</wfw:commentRss></item><item><title>Your Email Just Got More Interesting!</title><dc:creator>BitInstant</dc:creator><pubDate>Wed, 03 Apr 2013 05:19:40 +0000</pubDate><link>http://blog.bitinstant.com/blog/2013/4/3/your-email-just-got-more-interesting.html</link><guid isPermaLink="false">1479007:17514312:33185455</guid><description><![CDATA[<p>It’s here! We’re happy to announce that bitcoin-to-email is up and running again. This popular feature allows you to send bitcoins directly, and conveniently, to an email address. We apologize for the delay in reinstating this feature but we wanted to make sure it was good to go. </p>

<p>When you submit a “bitcoin-to-email” transaction the recipient email address will immediately receive a confirmation email containing a link to claim the bitcoins at their leisure. It couldn’t be simpler! </p>

<p>Why would you want to send bitcoins to an email address? Great question! Use this service when you don’t have your wallet address handy or when you want to send bitcoin to someone without a wallet. Maybe you want to introduce someone to the wonderful world of bitcoin. The possibilities are endless and we’re here to enable them. </p>

<p>As with any online transfer of funds, this option is as safe as its end point. When creating a transfer, you are asked to set up a <span class="caps">PIN </span>that will be required when withdrawing the funds. This prevents someone from trying to steal them. If you’ve taken the proper precautions, this is a great, simple way to send bitcoin.</p>

<p><a href="http://www.bitinstant.com">Click here to get started!</a></p>
]]></description><wfw:commentRss>http://blog.bitinstant.com/blog/rss-comments-entry-33185455.xml</wfw:commentRss></item><item><title>It's back! Receive your order directly to your Bitcoin address.</title><dc:creator>BitInstant</dc:creator><pubDate>Sat, 16 Mar 2013 00:50:09 +0000</pubDate><link>http://blog.bitinstant.com/blog/2013/3/15/its-back-receive-your-order-directly-to-your-bitcoin-address.html</link><guid isPermaLink="false">1479007:17514312:33050399</guid><description><![CDATA[<p>Dear Bitcoin Community,</p>

<p>Thank you for bearing with us over the past couple weeks, they&rsquo;ve been rough. </p>

<p>On one side, we were dealing with the technical and PR ramifications of the hack that occurred, and on the other side we were upgrading core components in the system which enables us to send Bitcoin orders directly to Bitcoin addresses and email addresses (Coinapult).</p>

<p>For those interested, much of this work involved switching Coinapult to Electrum and updating API calls. We also had to fix bugs originating with MtGox&rsquo;s API which became exponentially more problematic as volume exploded from recent buying interest. Our system was dropping orders due to &ldquo;odd data&rdquo; coming from the API calls throughout. </p>

<p>In any case, during this process, many customer orders were not processed promptly by us, and this is entirely our fault. Growing pains are inevitable, but it&rsquo;s still not acceptable for our customers to be affected by them.</p>

<p>We apologize sincerely for such delays over the past couple weeks, and for any orders or emails that went unanswered during that time. </p>

<p>To remedy this, for any orders which failed or did not process due to bugs on our end, we will honor the BTC exchange rate at the time of your purchase (bad for us, good for you, since the price has increased significantly). </p>

<p>We are also waiving/returning any fees associated with those orders.</p>

<p>And fortunately, as you may have noticed, our Bitcoin payout option is back! Yes, we&rsquo;re excited also. You can now once again place cash deposit orders and receive the Bitcoins directly without having to deal with any exchange. This has been running smoothly since last night.</p>

<p>All new orders as of now should work as expected, and the much-loved Bitcoin-to-Email feature will also be back very shortly. Not only have things recovered, but the system is now stronger and more robust than ever.</p>

<p>Thank you sincerely to all of our customers. Let&rsquo;s push on forward. </p>

<p>-Charlie Shrem</p>]]></description><wfw:commentRss>http://blog.bitinstant.com/blog/rss-comments-entry-33050399.xml</wfw:commentRss></item><item><title>Events of Friday - BitInstant Back Online</title><dc:creator>BitInstant</dc:creator><pubDate>Mon, 04 Mar 2013 16:03:57 +0000</pubDate><link>http://blog.bitinstant.com/blog/2013/3/4/events-of-friday-bitinstant-back-online.html</link><guid isPermaLink="false">1479007:17514312:32916667</guid><description><![CDATA[<p>
<p>Afternoon folks!&nbsp;</p>
<div></div>
<div>As many of you know, BitInstant was down starting Thursday evening and was turned back on today (Monday) with a limited relaunch.&nbsp;</div>
<div></div>
<div>None of your personal or transactional information has been leaked. We keep all that data offline to protect everyones privacy.&nbsp;</div>
<div></div>
<div>Over the weekend the BitInstant team has been hard at work securing our system from a sophisticated attack on Thursday evening. Overall, due to major choke points and redundancies in our system, the hacker was only able to walk away with $12,480 USD in BTC, and send them in 3 installments of 333 BTC to bitcoin addresses.&nbsp;</div>
<div>&nbsp;</div>
<div>15WeVhV1rSUVGqBWuzi4ogV3BGSwAw8fCX</div>
<div>12Sfsc4XVBfSkcz9CayqfZdhYuntbjtjXp</div>
<div>1Fimj1BzMBessvPw2RKeqvgPg7VLgJCQi</div>
<div></div>
<div></div>
<div></div>
<div id="_mcePaste"></div>
<div id="_mcePaste"></div>
<div><span style="text-decoration: underline;">Background:</span></div>
<div id="_mcePaste">We've long been targeted by someone using social engineering tactics to attempt to compromise our various accounts at exchanges, with our hosting provider Amazon AWS and even on my personal accounts, mostly without success. At no time have we ever had a single system or account compromised through technical means, or indeed at all before yesterday. For the sake of convenience I'll refer to this mystery person as simply "the attacker". This individual was only successful due to the failure of the staff at our domain registrar as I will explain below, we intend to move to a more secure registrar ASAP.</div>
<div></div>
<div></div>
<div></div>
<div id="_mcePaste"></div>
<div id="_mcePaste"></div>
<div><span style="text-decoration: underline;">What happened:</span></div>
<div id="_mcePaste">The attacker contacted our domain registrar at Site5 posing as me and using a very similar email address as mine, they did so by proxying through a network owned by a haulage company in the UK whom I suspect are innocent victims the same as ourselves. Armed with knowledge of my place of birth and mother's maiden name alone (both facts easy to locate on the public record) they convinced Site5 staff to add their email address to the account and make it the primary login (this prevented us from deleting it from the account). We immediately realized what was going on, and logged in to change the information back. After changing this info and locking the attacker out, overnight he was able to revert my changes and point our website somewhere else. Site5 is denying any damages, but we suspect this was partly their fault.&nbsp;</div>
<div></div>
<div id="_mcePaste"></div>
<div id="_mcePaste">After gaining access, they redirected DNS by pointing the nameservers to hetzner.de in germany, they used hetzner's nameservers to redirect traffic to a hosting provider in ukraine. By doing this, he locked out both my login and Gareths's login and they used this to hijack our emails and reset the login for one exchange (VirWox), enabling them to gain access and steal $12,480 USD worth of BTC. No other exchanges were affected due to either Mult Factor Authentication, OTP, Yubikey's and auto lockdowns.&nbsp;</div>
<div></div>
<div>The hacker was also able to pull a few hours of internal company emails. However due to mandatory PGP encrytion between members of our company and tools like Cryptocat, sensitive information was not breached.&nbsp;</div>
<div></div>
<div></div>
<div></div>
<div id="_mcePaste"></div>
<div id="_mcePaste"></div>
<div id="_mcePaste"></div>
<div id="_mcePaste"><span style="text-decoration: underline;">Information about the attacker:</span></div>
<div id="_mcePaste">Based on their general MO, the attacker is not highly technically skilled but is sneaky enough to cover their tracks. Some of the hosting providers they directed our domain at may have billing information, but such billing information is likely a stolen card. Geographically, I would personally suspect them to be Russian, based on the choice of providers and based on past fruitless attempts that clearly were of Russian origin. They seem focused on me in particular and have tried many times to gain access to my accounts (both personal and business)</div>
<div></div>
<div id="_mcePaste"></div>
<div id="_mcePaste"></div>
<div></div>
<div>Other parties involved (the attacker used these parties in some way):</div>
<div></div>
<div id="_mcePaste"></div>
<div id="_mcePaste"></div>
<div>meta.ua - email provider</div>
<div id="_mcePaste">hetzner.de - nameservers for the first attempt were hosted here</div>
<div id="_mcePaste">ukraine.com.ua - hosting provider involved in the first hijack</div>
<div id="_mcePaste">smtp.parkside.at - mail provider which was involved in the email hijack</div>
<div id="_mcePaste">Circle Express Ltd - their network was used as a proxy, the actual IP</div>
<div id="_mcePaste">is registered to BT PLC but is used by Circle Express on a business</div>
<div id="_mcePaste">line of some variety</div>
<div id="_mcePaste"></div>
<div id="_mcePaste"></div>
<div></div>
<div></div>
<div></div>
<div>So, we wanted to provide this update in order to continue our practice of transparency, but also as a lesson to the community - you must be ever-vigilant in making security your top priority. We outline many more of our security protocals here:&nbsp;bitinstant.com/security</div>
<div></div>
<div></div>
<div></div>
<div></div>
<div>Thanks for your patience, support, and trust during these times.&nbsp;</div>
<div></div>
<div></div>
<div></div>
<div>- The Team @ BitInstant.&nbsp;</div>
</p>]]></description><wfw:commentRss>http://blog.bitinstant.com/blog/rss-comments-entry-32916667.xml</wfw:commentRss></item><item><title>Bitcoin Payment Network Adds Hundreds of Thousands of Locations Worldwide</title><category>Bitcoin</category><category>Brazil</category><category>Buy Bitcoin</category><category>Cash deposits</category><category>Press Release</category><category>Press Release</category><category>Russia</category><dc:creator>BitInstant</dc:creator><pubDate>Tue, 05 Jun 2012 02:57:12 +0000</pubDate><link>http://blog.bitinstant.com/blog/2012/6/4/bitcoin-payment-network-adds-hundreds-of-thousands-of-locati.html</link><guid isPermaLink="false">1479007:17514312:16575610</guid><description><![CDATA[Locations throughout North America, Eastern Europe and Latin America now enable Bitcoin purchase via Cash Deposits.]]></description><wfw:commentRss>http://blog.bitinstant.com/blog/rss-comments-entry-16575610.xml</wfw:commentRss></item><item><title>IT'S ALIVE</title><dc:creator>BitInstant</dc:creator><pubDate>Tue, 05 Jun 2012 02:33:53 +0000</pubDate><link>http://blog.bitinstant.com/blog/2012/6/4/its-alive.html</link><guid isPermaLink="false">1479007:17514312:16575357</guid><description><![CDATA[<p>The BitInstant Blog has been born. Hide your women and children.&nbsp;</p>]]></description><wfw:commentRss>http://blog.bitinstant.com/blog/rss-comments-entry-16575357.xml</wfw:commentRss></item></channel></rss>