Site Announcements – BitMEX Blog https://blog.bitmex.com The official blog of BitMEX, the Bitcoin Mercantile Exchange. Wed, 13 Dec 2017 08:53:47 +0000 en-US hourly 1 https://wordpress.org/?v=4.9.1 https://blog.bitmex.com/wp-content/uploads/2015/03/favicon-128x128.png Site Announcements – BitMEX Blog https://blog.bitmex.com 32 32 78374597 BitMEX Product List Update https://blog.bitmex.com/site_announcement/bitmex-product-list-update/ Wed, 13 Dec 2017 08:53:47 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=7139 Quarterly Bitcoin / USD Futures Contracts

The following quarterly contracts will be listed on or before 15 December 2017 12:00 UTC:

  • BitMEX Bitcoin / USD 30 March 2018 futures contract, XBTH18

We will add the BitMEX Bitcoin / USD 29 June 2018 futures contract, XBTM18, in the near future.

Quarterly Bitcoin / JPY Futures Contracts

No new Bitcoin / JPY quarterly contract will be listed after the BitMEX Bitcoin / JPY 29 December 2017 futures contract, XBJZ17, expires. We will add a Bitcoin / JPY perpetual swap in the near future.

Quarterly Altcoin Futures Contracts

The following quarterly contracts will be listed on or before 15 December 2017 12:00 UTC:

  • BitMEX Ether / Bitcoin 30 March 2018 futures contract, ETHH18
  • BitMEX Dash / Bitcoin 30 March 2018 futures contract, DASHH18
  • BitMEX Litecoin / Bitcoin 30 March 2018 futures contract, LTCH18
  • BitMEX Monero / Bitcoin 30 March 2018 futures contract, XMRH18
  • BitMEX Ripple / Bitcoin 30 March 2018 futures contract, XRPH18
  • BitMEX Zcash / Bitcoin 30 March 2018 futures contract, ZECH18

Please note the fee structure for all altcoin futures contracts will change to maker / taker, -0.05% / +0.25%.

]]>
h 7139
Order Placement Limits https://blog.bitmex.com/site_announcement/order-placement-limits/ Sat, 09 Dec 2017 14:22:44 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=7005 Starting December 11th, 2017 at 12:00 UTC, the following limits will be applied:

(1) Maximum 200 open orders per contract per account;
(2) Maximum 10 stop orders per contract per account;
(3) Maximum 10 contingent orders per contract per account.

When placing a new order that causes these caps to be exceeded, it will be rejected with the message “Too many [open|stop|contingent] orders”.

These caps are designed to improve the overall trading experience on BitMEX and will be reviewed and updated periodically.

]]>
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEymWgs+xpR9eu3mF214jUHu5Q5YoFAlor8bkACgkQ14jUHu5Q 5Yqj2xAAhEiICEtHQ50c4lthSdcT7o/8XjkGtDYjaamrL0ICMIIo+1e7qD7WLRRc CDURi+ZyT3NHNaeB7jBkJIF2TQ72vG1DCcYoUt7ZbrE9970KfJNgVTQ//U8sApMF AyhCh/1K9HVSFnzurLeHmnZeblVpdtdp9ihsYZdOjZWmQzJOgr/jfKhh9DmFqrNW hqgnQN+HQcbcWBMoOwCYZsmWUB2ns6RoOZ7olrQdwA1rcvChmnKMD9HjM3Dk/viw laqOeUdRT1DUn655zTNBFgrjiRoiM4IgkcOHFPVbehtSODXoMkEcJeEiexv+Qr7S 678SqlVDnFTJfk2dtXuW/rsoxQbY0ijjZP6YkKRVF30Ws0nIBHHTJCAFUOu4B60W /fGgnTBVLkp0ij2cXufAIZrgbX78p/u1rNv4KL5cCXKbrkv7gdWJ8Jg9aYjbBct7 Q5P1oX6dtpODz6d+04ST5UGDGX47XwxyvRk0jjhQey+u25sC++/zAQ6bhXUJzP7G BmMk1zg+EIkqT8rZafR0ao32ma+Ev+oPZI/8gXuTa3DINESdannDkZ2P2t6/o+hq hPIDiQKa+dagKr15wVevUD/8laI6P7USPEBv8jiQ5Kw1sFyETJfZtRW3V7qx4I/U VLwOq/KLOIQ6GwauVSsV0j39iX/ydA7DwkiFjyjJchj6ZkMlIO4= =qnOb -----END PGP SIGNATURE----- 7005
Update to System Overload Policy https://blog.bitmex.com/site_announcement/update-to-system-overload-policy/ Sun, 03 Dec 2017 23:17:50 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=6958 BitMEX is experiencing record-breaking load at this time due to recent Bitcoin price movements. Our engine team is working full-time to improve performance, delivering a 20% performance improvement on Friday and with more to come. Above all, BitMEX is committed to correctness in its trading engine and to real-time correctness auditing. BitMEX positions and orders are always internally consistent from open to close.

Unfortunately, when load spikes, we cannot service every incoming request while maintaining acceptable response times. In early November, we implemented a cap on the maximum number of requests that can enter the engine queue, after which new requests are rejected until the queue has shrunk. Many of you have experienced this as the “System Overload” message (also known as “Load Shedding”).

For the benefit of our traders, the following request types are no longer subject to rejection during overload:

  • Adding/removing margin from a position or adjusting leverage.
  • Canceling an order.
  • Market or Limit Close of a position, when using the Close buttons on the Position table.
    • For API users, this corresponds to use of the “Close” execInst.

New orders and order amends are still subject to rejection on overload. We will keep you updated as we improve the situation.

 

]]>
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEymWgs+xpR9eu3mF214jUHu5Q5YoFAlokqDUACgkQ14jUHu5Q 5Yr92RAAqAKKs2WxV+ZFwOBHUr4sK8I9AerpVLxfkF+jZm09qGQCQBy1s1DYP6gj LV+9+ribJNEMsMuQK64cpCp9iep/LnJKApQxlRUglEYB+UtsLrS9lV5P3244CfKK lYpYv0Ann6konksIi9IOy8gt3B/QgOL3HwOywIO3We/4NlSIGuGyk7Ptj/seke+5 SiHsq+UlBDK7AO5KA0iNRuvFGNwOhIy6cTgJQbZbtZ9g9OUrTu9ZXP/2OrY9UpCQ YC/vMcjA5phBMEMq/fclu2fTQaz56TaoF64gO+Ngvb0bPltTH0dyg9/Zi+NHHrqV Aus+FO8sCudBMtEGDT68+Q4dbJDUYTS16jLhGE35F40G3o1nQ5cjbWmZuwuAUmQc zLL+tTAwwV4kaw3UakQyVbcklPyeLM2xsioMjI7YvMI7zWM4IHWXPcN69juIht6h NKRmi6cEysiGuS6ek8WmGUYHOzomO4LU12pEK7IBrHZbYGhiKzIwLEUuoSnL/cja 1gC0fBhXezi3Gb/v77OpfXMnLGP7b4RIR9Vwwt0c8p7t3UMkOzV7jX1fVdk7EhsG 0ngRjmKzrKMXehZdel1NIQDRIRoI9Byz+huDJydBUH3b9ifJr3UoEjaYJFgQ1muM yolYOa12n2cAOThhoD7Vm9ZhJ3M69/rZT84/h+t9Hu8ufMsH8y4= =Vf/+ -----END PGP SIGNATURE----- 6958
Completed Maintenance: November 30, 3:30 UTC https://blog.bitmex.com/site_announcement/pending-maintenance-thursday-november-30-330-utc/ Thu, 30 Nov 2017 02:48:37 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=6930 Maintenance is complete.

We have successfully tested a new hardware configuration for our trading engine. We will be taking down the engine at 3:30 UTC (in one hour) for about 15 minutes to do the switchover. After completion, we will tweet and initiate a 3-minute cancel-only period.

Orders left open over maintenance will remain open, as will positions. If this concerns you, please cancel your orders and/or close your positions before the maintenance interval.

Any trigger orders (such as stops) will *not* activate during this period. Once trading restarts, if the price at that time would trigger your order, it will trigger then.

]]>
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEymWgs+xpR9eu3mF214jUHu5Q5YoFAlofhTYACgkQ14jUHu5Q 5YpGjBAAyAjw7Nu+cIyR848SePBBGt2EgKcasHzLc5uWLsrSoEo3+w6wVIz5qdo0 NtxJ5Dcggc1In/Ihq45Od+PHPs2fVaSRBtgPq/EGvwhdf9nluSGoBznVrXvGgiuK GyxZH+4165f16acw9fCgZb61kFwAFa/B36rVEkc0H57tUJ62Un/bTvlRE1LAjzr2 mIN9iziG1UCP8rV3Hn142bu9g+uLxlaoEXmXw7k1QiI9a4qEr42iRBBtoRZ9ToxH TNaD4dukk6YmegL9a67ViUu+4vuzXM6IvZGew8h6w5KXRLp40OJJXyt9jIYLTFhj 47AXRlOGlo3h0MkJr9c9aL1BG5/F6CW9Pd8xiqZvYfayKJqlcoUode8oyPKI/idW J2BxOizffSb+DjoGJEPpRc4BzcV9EzbgqKFNaL29D+7/2NjOqXB+4mtiI9fetDyJ /mdg8JRAPZPN+ozLrzuIHZUNXKdTX3Sx6DPJqOw4nZk2zFtvM16uB5uQ7EHYhgc2 glals3WZykfopkUWBKRzAc8/TfchckdYXSxJNfbWLPNSCQgQfUVS7mgrGznN47ky f5U42lwJe8rDhSD+5jRQ2yb7B5q9dDi0GWE7CgXn5W3x5ESSychz56ic14D4Fjng Y3ZdYpJb1wLZS4TJ3zK5IfNi6GH2gCyOeEoCK9IVwWue0VtbGr8= =L45z -----END PGP SIGNATURE----- 6930
Bitcoin Cash Futures Now Live https://blog.bitmex.com/site_announcement/bitcoin-cash-futures-now-live/ Wed, 15 Nov 2017 07:42:31 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=6548 We are pleased to announce that the BitMEX 24 November 2017 Bitcoin Cash / Bitcoin futures contract is now live.​

  • Symbol: BCHX17
  • Expiry Date: 24 November 2017 12:00 UTC
  • Contract Value: 1 BCH
  • Underlying: Poloniex Bitcoin Cash / Bitcoin exchange rate
  • Leverage: 20x

​BitMEX Bitcoin Cash Holdings

On or before 31 December 2017:​

  • The amount of Bitcoin Cash a user is entitled to is determined by their Margin Balance at 1 August 2017 13:17 UTC, a few seconds after block 478,588.
  • Users will not receive Bitcoin Cash, rather BitMEX will sell all users’ Bitcoin Cash, and credit their wallet with the Bitcoin proceeds.

BitMEX Future Hard Fork Policy

BitMEX does not agree with contentious hard forks, and does not accept the manner in which Bitcoin Cash was forked, or the lack of preparation or notice before the fork; we consider this a dangerous action that imposes unacceptable costs on end-users and businesses. Please read our Policy on Bitcoin Hard Forks for acceptable hard-fork criteria.

However, months after the fork, it is clear this coin still has value and popular demand, so we have decided to credit Bitcoin at the prevailing Bitcoin Cash price. Do not expect future coins to be credited in this way. BitMEX reserves the right to credit forks or not – in the presence of doubt, always withdraw first.

]]>
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEymWgs+xpR9eu3mF214jUHu5Q5YoFAloTRNkACgkQ14jUHu5Q 5YoU/BAAiuL+TheeTkdX3w5mwSo7p+PPR2fY5mCJ9OT8flimbNV6Ga1a2rNKYwkL VqmjPUvBca/MTuSQWufI9rvMNX3Tk920B/nwpDxH2A1DmW/2Fk7vb1TR0yb232tV rp+gdupCT+6V/M8pICMTyrCrgzWKDHYXH7xwoLSQxgGdxWi4xwIfphhtAOaUfjIZ gH7AaLJ1dMj5z5DP32q8cR8/1SesbKwmqq7cm4n1SHeWK+FH+ZPhoUQlaSTaKUqN ATlTMwhzEImlFmgM6sJ4SzTAy0mk40HUSIFhWieHbmBWFLyLMgSHlAZowKMAOdoA PxI887bb02zDHj1/CImZujk6BemvyAGptJi3CVERM6QfpegpcRBrkQ+4a8Zpx+zv cZBoeksI0LgMkNcStn7HRNtBYPemVcDsozZzLhtKvMQ8cOcK8ZD10jkRAtkurh4P QDD2Pc2P+ZiR2taRt68Le6leT+fWvC0CSke/sKhx3+mmB/KG3KMzCMR626+FXfvw t3XyefJktNlR5aV8sU1D3fItLVeELyD6vHGoaTD26CMz6qSvxnORW8aRRnqNKeQw u2rv9yUllpPBaduR6Ptzy5NpikrKOZebrt3BFWb9RUX/LwLtybydQYsBgM8tahLO h/P2ESw3KihhhY89k6OE6IdE9zaPNHsHfhmZ6YphBbCPZDGMwtM= =vBbI -----END PGP SIGNATURE----- 6548
Summary of Completed Maintenance https://blog.bitmex.com/site_announcement/summary-of-completed-maintenance/ Fri, 10 Nov 2017 22:53:42 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=6368 Maintenance yesterday, November 9th, went off without a hitch. This update was to increase trading capacity and improve behavior under high load. A list of changes:

  • Our trading engine was upgraded to a more modern server with faster, newer CPUs. This has improved overall latency and queue depth.
  • Load-shedding has been implemented. If the trading engine’s queue depth grows beyond an internal threshold, new requests will be immediately refused with a 503 until the queue shrinks again. Order cancellations are not subject to this restriction.
  • We have quadrupled capacity on the subsystem responsible for user authorization and API keys. This is a future-proofing measure and is unlikely to be noticed by users.
]]>
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEymWgs+xpR9eu3mF214jUHu5Q5YoFAloGLmsACgkQ14jUHu5Q 5YpY8Q/+LImIAkkTg5wV/0KY7bI/Pl5WKEMqbjANFUWqBeqBXJBo6x+3RsLwdriT NQ0euR4+qxtFklxWrnGV9d6MGJWmWNnkir3oOHToLg4fdagfSXsbCqgeDRolJfVc Ps8YwtC4tHDCBy9hbkOYCGmBGm4f63VR59tH8m07ek1bjta+HPL7wviCC8a3kBvC +taZjmk/mp6NYVTxIjqN4+zpuVpXQMxVPe7F6vs3x7Cu22GdZY2sv9kDx5ttKnYK vVwB3SL/F7MsetQNVybIi/ewIJjTnxnxdQoBjrhuhpoEHKLOmglIayjIi400J81x 7+f1kRKPuUdoAm2OrAxkZrJhytq8Z6wrkFB2kCG9/Y+WB+O64K2zFuTigizPZe2T Tq/TD3NRGC4s1kO3g6M1XOOZB5jv+74pgLimY7kyEqN3mj3JPDLhN3zLhUtYXdlJ LVz2dEyQzHYVOEVQVksh40IkFHeRwK2NHWXyIvGVloL5tOa0S5gsFEDJ6Hao+Ark GCxdtzqFYboJgnivSvMSsvflU6bHkic340qDjiyK1cqBZcurUfsHe6mSk8tyBn5f 1x4QkcGmnENnYiYMJMGXxLvOZqjTJlcrowZIgaC2lZqX7vxb5oz3XoPX0TPVY+X/ Q+An+DrZJE4cEO69jVOM5/g1QPaRX/HcaWVbROzZeSSaFaonXXk= =1F50 -----END PGP SIGNATURE----- 6368
Scheduled Maintenance: November 9, 2017 https://blog.bitmex.com/site_announcement/scheduled-maintenance-november-9-2017/ Sat, 04 Nov 2017 23:14:36 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=6339 The BitMEX platform will halt trading on November 9 at 18:00 UTC for a database upgrade. Once the platform is back online, we will notify via Twitter, enter a cancel-only period for 5 minutes, and trading will resume.

Upon resumption of trading, the tick size on XBT products will be increased from 0.1 to 0.5 USD, and on XBJ products from 1 to 100 JPY. If you are using automated tools, please ensure they are aware of the change and submitting/amending with the proper tick size.

]]>
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEymWgs+xpR9eu3mF214jUHu5Q5YoFAloDiN0ACgkQ14jUHu5Q 5YpxLRAAg1LTjEbQxQeomZM2kQtYX9Pp6jyb8qnhsYTYsZT+uXWoYggOM8wDtEfZ 1pgbWnxnZ4WfPxlCj2YYGta4Z9fONI/6LLKGuiZmm94QueYZyvUZrKRaMPqup3vk xJuHBKmOJMYG9H70y6rZiXrVHi4QGO2feKhD2geZrE39FO1tfgZEuOHfuz3lWAsq gIw5Y6UxHrmporssX6rrOwHk5YOvr/vOFgZARqX/5rwQpkvmkxxOEd99kVlwU1To C+ngWqPjrva726ARW2gVJACCM3TNkAQrmtIvSmGKfI/TQOFXp3/HhPNThYp9JuX6 pUsHV+qZGJ/wdPwGOU1lH9baJD/+lNJ3ChgzkFLZceOUMedwsC1rn4e2cGocPrqq IhGrRQfGwxQLom+6aoDEuFDoU883twIEiHGtzx3w5Ad+TDkmMC6+H9XKdgOpQ/hu frh417XW2U+oj6u3reb5z1zDF8weERq5mVYZVlmLWwXTvC+YCrE9WhlbMr1EChrr ych9KGg5yHfBn32hfCxxNJiWAxtNhMtc9ox0FN8okbpVF4UutZAOFDfLvi2iF8HQ OdCB8LUviUies566/mUU/wwPL5BBofF3Ek0ywqSWTXpjin81XXvw7xELfkZcPZwJ PfcbaGA8BSkFw9ceHSvPBtR/Vju3PAdkh/zeDy0DsrFa3VoaiUQ= =F9IV -----END PGP SIGNATURE----- 6339
Additional Withdrawal Round for Bitcoin Gold https://blog.bitmex.com/site_announcement/additional-withdrawal-round-bitcoin-gold/ Mon, 23 Oct 2017 19:19:17 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=6190 Like other Bitcoin hard-forks, BitMEX will not support Bitcoin Gold (BTG).

At block 491407, the BTG team intends to snapshot balances. Note that the BTG client is not completed and will not be released at this time. Therefore, there is little risk of leaks through transaction replay, assuming the BTG team properly implements replay protection by the actual client/network launch.

BitMEX will process an additional round of withdrawals at 22:00 UTC (in 2 hours 40min) for users who wish to hold Bitcoin in their own address for the snapshot. It is safe to re-deposit after block 491407.

]]>
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEymWgs+xpR9eu3mF214jUHu5Q5YoFAlnuQLoACgkQ14jUHu5Q 5YprSRAAi+6XfM29W0z/8iwPucOTE/A64cmEXMAX8frjDzkRTO7Pns2SgEp6/VBE jAiIkMOGAs/GL9XBW9TdK9T2ABUYx8lQ2/eVcIqIJjkXg6qMCvKj72goOcAULEF6 9wbZtYUJcVGkWV7Z6vcFuMpeBhGo2ScQAhMnYD1USagWjGPUzDg1PLC/Xi62inA+ mu1SmKbHoKmGtVW37udx2Foxwl9aTnJNJGqbWNCNd0TTCf4YeqziB6YVet5v8qBp x6kFeqL4ddI7r1GXskkVuDXbnWSwmrNdrGBe3H2nTsQiiP8j0WC3c1RZJjHSiaTp JF77MwStCy/McG5SFeBdg2y2YIra/9bEWI0z3wwqYKMli6snw8LSwW3l0tAvEMz1 FMZ/fTimANWoqt+hYmIEUs5KEkj8JZ4KEYId/SNOXZEb52RUot7ZaowmcTBfM5oH DApvbJlehRgfCu/NSs+kpxOo6dZteS471emP/Suy4ApIb4Ml60ykuva89YqYRcfG 1hS23SpsWinDJriMyVQGLdsMu9wSHkQwwOj987tTf1tlEBZGO0chSz0WRHTPyGTT 9+CckwEaOpbkadgh5aUnvzoH1xvcXY2pCP+4ecqYtwoP3DheIFn1VBJcmup2rRsj yveNhddijwz5Ap4NWq5esi9ZX6S4fJF9295zdoOpwL11TFKAUhM= =lLzf -----END PGP SIGNATURE----- 6190
BitMEX News & Changelog: October 14, 2017 https://blog.bitmex.com/site_announcement/bitmex-news-changelog-october-14-2017/ Sat, 14 Oct 2017 23:11:54 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=5993 We’ve published a new changelog for this month. Highlights include beta Russian translation, performance improvements, bugfixes & news.

]]>
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEymWgs+xpR9eu3mF214jUHu5Q5YoFAlnjcd8ACgkQ14jUHu5Q 5YpurBAAzcDla9Egnn9hmTYo1zh3RrzHOZanJ5lCdB6LeoVVHooNNVRp1ET5q5U9 qMFwkjKQnRZtJQZdn9QcpHy9az8Ghtdz8L7ESsBdBwyELxvieEqLHqnS4PZ+4W8J ICU4Mcu2Ddj5ghR8rbxFB7dO84r0Oi+62lq/vHg4AO2zhuJr+I5JzT/ybDjZ6es8 h7xFBhJhS3JIu46y8tN6ClZYLG1Y1jy/3jDWPHhSarOSECZAqchT8QrZTF28hRU9 4dL5FmWzj2TiFWyQD5fa7taVhwFfd5EphHWzYd1umH7eVE44rugJf9gwE4hbB2dH h8yO3EVzLHhbzDupENLVxTv/tWF0f0uzA1KkNEOV2ivtn6hSaqjI3tc5rJqhLu7K zryH6Z1z70w152wionyupPhoP6HIk1+69Z20p/HEm+3fvdn1lKSn/JlA8DTa1HXd xQFJNEEK4rfCQS7wYLy0Akgx/hXiy2h755Mljc00VScv3y0c5IYdU5GLB5LIcSOS gL0cQn6SGiNL1T/hGeIhwzH7wO7cxsCncMqARWhgHOnSwdvT/nhlU/wLnX+XDfio 8X7KUa2JScbWXjXztz96Lb89jL+ri77UxqG7asHKj7GEPssoqNWPKezVWw8Dm1Be 5vDuNz8FatpTY4j65UCrQNQLFJt0lgmzU4ueiqJO48oqwYmRrEo= =35eH -----END PGP SIGNATURE----- 5993
Rate Limiting on WebSocket Connections https://blog.bitmex.com/site_announcement/rate-limiting-websocket-connections/ Mon, 02 Oct 2017 14:57:12 +0000 https://blog.bitmex.com/?post_type=site_announcement&p=5431 After 12:00 UTC on Tuesday, October 3, BitMEX will begin rate-limiting incoming WebSocket connections (as in, opening the socket itself) at a burst rate of 20 connections per hour.

We do not expect this to affect normal users, as our recent (July 8) migration to a Token Bucket rate limiter effectively doubled available capacity for all users.

Additionally, the ability to authenticate to the WebSocket using email and password has been removed due to abuse, and the command cancelAllAfter, when invoked via websocket, is now properly ratelimited.

]]>
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEymWgs+xpR9eu3mF214jUHu5Q5YoFAlndGXAACgkQ14jUHu5Q 5YoTYBAAlpA6tSKytgyLA7DTl/xnfLfQfPQU9IfsfLoMtEBS3QApNDiXneptrpgq KlFG0azFetNGPMMDFLpEx/gnU0vxuISNgOmqMgMYbLbzUhDJQjewo6QzSIjPAZym lnw85rkOlhUpGvqf6ucj+gBLDoSRJvKuikAylHdpGhHRfhwWkkpa3f+7B1E6RLHl a8z4pcMURJTyPNnlEpaOkGsnS+7MQBLDxCzQpNvyM6VN6O7HL1YdxTprJJAcB5EH 5yTcZCETx1cQkNvcAaIM2asPY79uiA3PYWVzA7znsQ4VLR0aHK+Gbqecty9NAUEr FYN0UbVG6s9wOtPG9dcFo0hgMs1KW01kwINcEXu+r+VOj9rSspnyuSD6a026530Y AWLUm9koLEG5gEQclYjqA4zdNLTBINRuqUwUZ0+RtlpSJOEQsvRcE1DJUViM2JmU zU6UIcAaB5pCkZB8vAITZj2wgdFOZX0acgENvEMCvb3sTbLIzL0ykazSkd4Z8Rqt +GjMb+OTUqjYF9/kzOKT2b/+JpGeQg0dwLNzI73WYZmPimyqqbX3Pf0hLlkxk8a7 BiBBd7FlGK6Z6pG3P3NLTZFsAmXE3s5r2Drka9vJJqHiN/6mQDZ3LwMCoYikGKpP NgreRO97+Ntr8edjA9D3x6rXKLtZGQul7xEgtZIsmI1zRS9mggY= =16AO -----END PGP SIGNATURE----- 5431