<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description>The official blog of BitMe, The place to buy and sell Bitcoins</description><title>BitMe blog</title><generator>Tumblr (3.0; @bitmex)</generator><link>http://bitmex.tumblr.com/</link><item><title>BitBox</title><description>&lt;a href="http://blog.inbitbox.com/post/49441634698/bitbox"&gt;BitBox&lt;/a&gt;: &lt;p&gt;&lt;a href="http://blog.inbitbox.com/post/49441634698/bitbox" class="tumblr_blog" target="_blank"&gt;inbitbox&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Bitcoin emerged from necessity.&lt;/p&gt;
&lt;p&gt;The 2008 financial crisis forced people to question and reevaluate their relationship with money and the cacophony of financial instruments built on top of it. What they found were systems that were opaque and anachronistic. The money we use today wasn’t made for…&lt;/p&gt;&lt;/blockquote&gt;</description><link>http://bitmex.tumblr.com/post/49462838551</link><guid>http://bitmex.tumblr.com/post/49462838551</guid><pubDate>Thu, 02 May 2013 17:45:00 -0400</pubDate></item><item><title>Suspending Operations</title><description>&lt;p&gt;BitMe is suspending operations indefinitely. The website will remain up until April 15.&lt;/p&gt;

&lt;p&gt;Great thanks to all of our customers!&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/45831990730</link><guid>http://bitmex.tumblr.com/post/45831990730</guid><pubDate>Wed, 20 Mar 2013 08:53:00 -0400</pubDate></item><item><title>Server Crash Recovery</title><description>&lt;p&gt;On Monday Morning, February 18 at 03:09 UTC, both our website and the REST API stopped responding to requests. We initially believed this to be a network connectivity issue at our data center, but it later became apparent that our server had crashed.&lt;/p&gt;

&lt;p&gt;A trip out to the data center had confirmed that the server was completely unresponsive. We did a hard-reboot on the system and brought it back up. The RAID immediately began to resync itself, and after reviewing some logs, we declared the major &amp;#8220;fire&amp;#8221; to be out.&lt;/p&gt;

&lt;p&gt;We took the downtime as an opportunity to do some software upgrades that we had been planning for, as some downtime was necessary to complete them.&lt;/p&gt;

&lt;p&gt;After being extra cautious and allowing the RAID resynchronization process to complete, we were able to bring the system back up at approximately 02:00 UTC on February 19.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/43489181506</link><guid>http://bitmex.tumblr.com/post/43489181506</guid><pubDate>Tue, 19 Feb 2013 10:48:07 -0500</pubDate><category>disclosure</category><category>downtime</category></item><item><title>Two-factor Authentication</title><description>&lt;p&gt;&lt;img src="http://media.tumblr.com/696b114aaa1a9730bc2e7d782e7d5ee0/tumblr_inline_mhaflf51X61qz4rgp.png" alt="Two-factor authentication"/&gt;&lt;/p&gt;

&lt;p&gt;Two-factor authentication is now available for your BitMe account using TOTP compatible devices such as Google Authenticator.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/41607367698</link><guid>http://bitmex.tumblr.com/post/41607367698</guid><pubDate>Sun, 27 Jan 2013 09:18:31 -0500</pubDate></item><item><title>USD rounding</title><description>&lt;p&gt;Since the &lt;a href="http://bitmex.tumblr.com/post/36064685790/new-order-rules" target="_blank"&gt;new order rules&lt;/a&gt; have gone into effect, we have taken additional measures to make the site more user-friendly. All USD user balances have been rounded up to 3 decimal places. Other USD values when calculated will also be rounded up to 3 decimal places:&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;order Cost (when buying Bitcoins)&lt;/li&gt;
&lt;li&gt;order Gain (when selling Bitcoins)&lt;/li&gt;
&lt;li&gt;order execution fee (when selling Bitcoins)&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;BTC values should continue to function the same for the most part, except that when calculating the order execution fee in BTC (when buying Bitcoins), the value will always be rounded up to 8 decimal places.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/38916122368</link><guid>http://bitmex.tumblr.com/post/38916122368</guid><pubDate>Wed, 26 Dec 2012 21:20:32 -0500</pubDate></item><item><title>New SSL certificate</title><description>&lt;p&gt;We have moved Cloudflare in front of our site, and thus our SSL certificate has changed. If you get a nasty error warning when going to bitme.com, then please clear your browser cache and try again.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/37238363321</link><guid>http://bitmex.tumblr.com/post/37238363321</guid><pubDate>Tue, 04 Dec 2012 22:47:53 -0500</pubDate></item><item><title>New order execution fees</title><description>&lt;p&gt;Starting December 10 at 03:00 UTC, BitMe will be changing it&amp;#8217;s fees for order executions. Liquidity provider rebates will be discontinued, but they will be replaced with a discounted rate. The new fees are as follows:&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;0.75% taker fee&lt;/li&gt;
&lt;li&gt;0.60% provider fee&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;This should create a more sustainable revenue stream, so we can continue providing improvements and great service!&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/37098676123</link><guid>http://bitmex.tumblr.com/post/37098676123</guid><pubDate>Mon, 03 Dec 2012 01:36:39 -0500</pubDate><category>update</category></item><item><title>New user-friendly UI</title><description>&lt;p&gt;&lt;a href="http://i.imgur.com/JGrlO.png" target="_blank"&gt;&lt;img src="http://i.imgur.com/JGrlO.png" alt="BitMe before and after dashboard update"/&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Over Thanksgiving weekend we quietly released a significant overhaul to the dashboard UI. This UI is the first thing users see when they log-in and allows users to place buy and sell orders for Bitcoins, see their current account balances, see best prices from the order book, and the status of their own orders.&lt;/p&gt;

&lt;p&gt;These changes are meant to address the confusion new users would run into when trying to buy Bitcoins. New users were often confused to the point of sending support emails on the most important aspect of the site, creating Bitcoin orders. This wasn&amp;#8217;t their fault, but rather the non-user-friendly UI that was filled with jargon (bid, ask, currency pair, rate, quantity) and required users to manually calculate how many Bitcoins they could buy with a given amount of US Dollars.&lt;/p&gt;

&lt;p&gt;Now when logging in, the first thing the user should notice at the top of the their dashboard will be two widgets - one for buying Bitcoins, the other for selling Bitcoins. The price (per Bitcoin, in USD) is defaulted to current best bid/ask and the user can either enter in the quantity of Bitcoins they would like to buy/sell, or simply the amount of USD they want to spend/gain.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/36805820163</link><guid>http://bitmex.tumblr.com/post/36805820163</guid><pubDate>Thu, 29 Nov 2012 07:38:53 -0500</pubDate><category>update</category></item><item><title>New order rules</title><description>&lt;p&gt;tl;dr&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;changes go live December 23&lt;/li&gt;
&lt;li&gt;rate precision (tick size) changing from 8 to 3 for orders&lt;/li&gt;
&lt;li&gt;new minimum quantity for orders 0.1&lt;/li&gt;
&lt;li&gt;new error code 1402 for API on POST /rest/order/create&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;Starting December 23, the rate precision (tick size) on BitMe will be changed from 8 to 3. This will limit the rate (or price per Bitcoin) to 3 decimal places. The new minimum quantity for an order will be 0.1.&lt;/p&gt;

&lt;p&gt;When the changes go live any orders still open with a rate precision greater than 3 or a quantity less than 0.1 will be closed. New orders will automatically be opened for any order that has a remaining unexecuted quantity of 0.1 and was closed because of the rate precision violation. Bids will be rounded down, while asks will be rounded up, ensuring the user gets a better rate than they had anticipated.&lt;/p&gt;

&lt;p&gt;Also, a new pre-order check will be added that prevents a user from placing an order that matches/overlaps with any existing open order they have. A new API error code, 1402, has been added for this scenario for the POST /order/create call.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/36064685790</link><guid>http://bitmex.tumblr.com/post/36064685790</guid><pubDate>Mon, 19 Nov 2012 09:23:00 -0500</pubDate><category>update</category></item><item><title>BitMe back up after being down for a few days</title><description>&lt;p&gt;BitMe is now fully back up after being down for a few days. I was out of town at a conference and was unable to attend to my daily duties.&lt;/p&gt;

&lt;p&gt;-Sean Lavine
BitMe, LLC Founder&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/34428422045</link><guid>http://bitmex.tumblr.com/post/34428422045</guid><pubDate>Sat, 27 Oct 2012 14:16:49 -0400</pubDate></item><item><title>BitMe security improvements and other changes</title><description>&lt;p&gt;BitMe has released a software upgrade this evening with the following changes:&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;Password is now required to be entered for both VouchX and Bitcoin withdrawals&lt;/li&gt;
&lt;li&gt;Confirmation screen for Bitcoin withdrawals shows user the amount and address&lt;/li&gt;
&lt;li&gt;VouchX withdrawals that fail no longer get &amp;#8220;stuck&amp;#8221; in pending status; they now are automatically cancelled&lt;/li&gt;
&lt;li&gt;VouchX withdrawals are now charged a 2% fee&lt;/li&gt;
&lt;li&gt;International wire transfer withdrawals have been temporarily suspended&lt;/li&gt;
&lt;/ul&gt;</description><link>http://bitmex.tumblr.com/post/32167025620</link><guid>http://bitmex.tumblr.com/post/32167025620</guid><pubDate>Sun, 23 Sep 2012 20:54:58 -0400</pubDate><category>update</category></item><item><title>New Payment Methods</title><description>&lt;p&gt;&lt;a href="https://bitme.com" target="_blank"&gt;BitMe&lt;/a&gt; is proud to announce that in keeping with it&amp;#8217;s theme of simplicity and ease of use - it is now accepting several new payment methods including:&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;Direct Deposit to your bank account&lt;/li&gt;
&lt;li&gt;cash deposit to BitMe&lt;/li&gt;
&lt;li&gt;wire transfer - US&lt;/li&gt;
&lt;li&gt;wire transfer - international&lt;/li&gt;
&lt;/ul&gt;</description><link>http://bitmex.tumblr.com/post/30492801977</link><guid>http://bitmex.tumblr.com/post/30492801977</guid><pubDate>Wed, 29 Aug 2012 21:46:38 -0400</pubDate></item><item><title>Software update, downtime</title><description>&lt;p&gt;Starting August 29 at 00:30 GMT, BitMe will be down for approximately an hour for a large software update.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/30418488000</link><guid>http://bitmex.tumblr.com/post/30418488000</guid><pubDate>Tue, 28 Aug 2012 19:58:00 -0400</pubDate><category>update</category><category>downtime</category></item><item><title>Software update to fix withdrawals to self</title><description>&lt;p&gt;Saturday evening (August 18) it was discovered after reviewing transactional logs that a user had withdrawn Bitcoins from their BitMe account to themselves (using their BitMe deposit address). The BitMe software was not able to handle this automatically. The user&amp;#8217;s account was debited (for the withdrawal) but the credit (for the deposit) was not able to be processed automatically as normally.&lt;/p&gt;

&lt;p&gt;The user&amp;#8217;s account has been manually adjusted to correct the issue, and the BitMe software has since been updated to correctly handle this in the future.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/29831203730</link><guid>http://bitmex.tumblr.com/post/29831203730</guid><pubDate>Mon, 20 Aug 2012 11:40:00 -0400</pubDate><category>disclosure</category></item><item><title>Hardened SSL/TLS configuration</title><description>&lt;p&gt;Saturday evening a user reported an issue with BitMe&amp;#8217;s SSL/TLS server configuration. A notable issue was it&amp;#8217;s susceptibility to a protocol-based vulnerability with SSL/TLS known as &lt;a href="http://luxsci.com/blog/is-ssltls-really-broken-by-the-beast-attack-what-is-the-real-story-what-should-i-do.html" target="_blank"&gt;BEAST&lt;/a&gt;. While this is a potentially serious issue, it can be difficult to pull off, as an attacker must first create a man-in-the-middle attack via another method.&lt;/p&gt;

&lt;p&gt;BitMe has since hardened it&amp;#8217;s SSL/TLS configuration for SSL v3.0/TLS v1.0 to mitigate this issue and has added support for TLS versions 1.1 and 1.2 for clients supporting it.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/28756745019</link><guid>http://bitmex.tumblr.com/post/28756745019</guid><pubDate>Sun, 05 Aug 2012 04:52:45 -0400</pubDate><category>disclosure</category></item><item><title>Updated Account Recovery / Security Features</title><description>&lt;p&gt;BitMe has been updated with several new account recovery/security features.&lt;/p&gt;

&lt;h2&gt;Security Questions&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;New users&lt;/strong&gt; are required to answer security questions when joining. These will be used as part of the lost password process.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Current users&lt;/strong&gt; will soon be required to answer security questions upon logging in before continuing, these may be answered now by logging in to your account and navigating to the &amp;#8220;Account&amp;#8221; tab.&lt;/p&gt;

&lt;h2&gt;API Keys&lt;/h2&gt;

&lt;ul&gt;&lt;li&gt;Creating a new API key now requires your account password to be entered&lt;/li&gt;
&lt;li&gt;API secrets are now hidden by default when viewing API keys for your account&lt;/li&gt;
&lt;/ul&gt;</description><link>http://bitmex.tumblr.com/post/28676654256</link><guid>http://bitmex.tumblr.com/post/28676654256</guid><pubDate>Fri, 03 Aug 2012 23:54:41 -0400</pubDate><category>security</category></item><item><title>Software Update</title><description>&lt;p&gt;BitMe will be undergoing a software update August 4&amp;#160;03:00 UTC and will be unavailable during this time. Expected downtime is 30 minutes or less.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/28651541692</link><guid>http://bitmex.tumblr.com/post/28651541692</guid><pubDate>Fri, 03 Aug 2012 17:27:00 -0400</pubDate><category>downtime</category><category>update</category></item><item><title>Disclosure: bug affecting order placement</title><description>&lt;p&gt;Late Friday night (UTC) a user reported an error they were receiving while attempting to place an order through BitMe. This error contained the message &amp;#8220;Cannot have more than 100 open orders&amp;#8221;. This is known as code 1401 in the &lt;a href="http://bitme.github.com/rest/" target="_blank"&gt;API&lt;/a&gt;. The BitMe Founder immediately investigated the issue and indeed confirmed that this was a bug. The pre-order placement check that emits this error was counting a user&amp;#8217;s closed orders as part of this limit.&lt;/p&gt;

&lt;p&gt;This bug was within the order placement system and therefore affected both API and normal web users. The bug was confirmed, test coverage expanded, and a fix was deployed to testnet and production in approximately 30 minutes.&lt;/p&gt;

&lt;p&gt;These facts have been agreed upon by the reporter of the issue prior to publication. Thanks to deego for responsibly reporting this.&lt;/p&gt;

&lt;p&gt;You can read more about BitMe&amp;#8217;s disclosure policy as part of it&amp;#8217;s broader &lt;a href="https://bitme.com/security" target="_blank"&gt;security policy&lt;/a&gt;.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/27183622852</link><guid>http://bitmex.tumblr.com/post/27183622852</guid><pubDate>Sat, 14 Jul 2012 04:01:00 -0400</pubDate><category>disclosure</category></item><item><title>Open Beta</title><description>&lt;p&gt;&lt;a href="https://bitme.com" target="_blank"&gt;BitMe&lt;/a&gt; is now in open beta and available for trading!&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/26755696142</link><guid>http://bitmex.tumblr.com/post/26755696142</guid><pubDate>Sun, 08 Jul 2012 06:02:00 -0400</pubDate></item><item><title>BitMe testnet reset</title><description>&lt;p&gt;The BitMe testnet site has been reset.&lt;/p&gt;</description><link>http://bitmex.tumblr.com/post/24026693704</link><guid>http://bitmex.tumblr.com/post/24026693704</guid><pubDate>Tue, 29 May 2012 19:36:45 -0400</pubDate><category>bitme</category><category>testnet</category></item></channel></rss>
