Bitcoin Wiki - User contributions [en]

Bitstamp

2013-06-25T14:50:39Z

Emery: Tulpenmanie is now Dojima

A currency exchange, which operates a BTC/USD market with support for various currencies for deposit and withdrawal.

==Trading==
*Buying/selling

A buy/sell order is executed partially or in full when the price bid can be matched against a sell/buy order that is at or below the bid amount.

==Adding funds==

===BTC===
There are no fees incurred when when transferring bitcoins for deposit. Funds are available once confirmed (3 confirms), a process that can take roughly 30minutes. A Bitstamp [[Redeemable code]] (coupon) denominated in BTC or BTC and USD can be deposited. The bitcoins using these coupons are instantly credited.

===EUR===
Exchange accepts EUR deposits via SEPA transfers, then converts them to USD and credits them to online account. '''No deposit fees!'''<br/>

===GBP===
Exchange accepts wire transfers in GBP, then converts them to USD and credits them to online account.<br/>
Charging 0.1% deposit fee(minimum fee = $15)

===USD===
Exchange accepts international wire transfers in USD, charging 0.1% deposit fee(minimum fee = $15)<br/>
Exchange accepts a Bitstamp redeemable code (coupon) in USD denomination or combination of USD and BTC<br/>
Exchange supports transfers between Dwolla, MtGox, Cash Bank Deposits, BTC-E and VirWox via '''Bitinstant'''.

===CHF===
Exchange accepts wire transfers in CHF, then converts them to USD and credits them to online account.<br/>
Charging 0.1% deposit fee(minimum fee = $15)

==Withdrawing funds==

===BTC===
Bitcoins may be withdrawn at no charge. Withdrawals can be sent to a bitcoin address or they can be made using a [[Redeemable code]] (coupon).

===EUR===
SEPA withdrawals are charged with fixed 0.90€ fee once your funds are converted to EUR. Minimum amount for SEPA withdrawal is $10,00.

===GBP===
GBP wire deposits and withdrawals in GBP are supported.<br/>

===USD===
International wire withdrawals in USD will be charged with 0.09% fee, minimum fee is $15,00. Minimum amount for international withdrawal is $50,00.<br/>

===CHF===
International wire withdrawals in CHF will be charged with 0.09% fee, minimum fee is $15,00. Minimum amount for international withdrawal is $50,00.<br/>

==Fees==
Bitstamp charges a trading fee from each party of successful trades made through the market. The amount of the fee will vary based on a 30 day trading history. The rate for new accounts and those with the lowest volume is 0.5%. Refer to the [https://www.bitstamp.net/fee_schedule fee schedule] to determine discount levels. The fee that was charged appears in the account history next to each trade.

==Internal transfers==
Bitstamp allows internal transfer of funds to other users using Bitstamp codes. One party withdraws funds by creating a code and then sending (in a secure manner) the code to a trusted user who then redeems that code by using deposit Bitstamp code option. The code denominations can be in BTCs, USDs, or combination of those two.

==Instant transfers via other services==
'''BitInstant'''
*Dwolla
*Liberty Reserve
*MtGox
*Cash Bank Deposits
*BTC-E
*VirWox

==Localization==
Bitstamp is localizing website with online collaborative online translating tool. Feel free to join and help with translation to your native language.

Link: http://crowdin.net/project/bitstamp

==Account Security==

Access to an account may be protected with the optional Google Authenticator utility.

==Language Support==

The site has support for various languages:

* English
* Dutch
* Italian
* Polish
* Slovenian
* Finnish
* Czech
* Russian

==API==
API is available https://www.bitstamp.net/api/

==Data Services==

===Linux===
* [https://github.com/3M3RY/Dojima Dojima] market client

==History==

The exchange was announced on August 22, 2011<ref>[http://bitcointalk.org/index.php?topic=38711.0 www.BITSTAMP.net Bitcoin exchange site for USD/BTC]</ref>. Bitstamp.net is owned by Bitstamp d.o.o. and based in Slovenia.

On May 12, 2012 the exchange began offering volume discounts for trading fees<ref>[http://bitcointalk.org/index.php?topic=81519.0 Bitstamp introduces volume discount program]</ref>.

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]

==External Links==

* [http://www.bitstamp.net Bitstamp] web site
* [http://twitter.com/#!/BitStamp @Bitstamp] Twitter

==References==
<References />

[[Category:Exchanges]]
[[Category:EWallets]]

BTC-e

2013-06-25T14:50:16Z

Emery: Tulpenmanie is now Dojima

A [[currency exchange]] with market for trading between bitcoins and other currencies, including the U.S. dollar, Russian ruble and other cryptocurrencies [[Litecoin]] and [[Namecoin]]. The site has Russian and English user interface translations.

==Features==

===Currency pairs===
[http://www.btc-e.com BTC-E] supports the exchange between the major currency pairs, such as:

* BTC/USD
* BTC/EUR (Euro)
* BTC/RUR (Russian Ruble)
* USD/RUR
* EUR/USD
* LTC/BTC, LTC/USD, LTC/RUR
* NMC/BTC

===Deposit options===

====BTC====
There is no fee for depositing bitcoins or depositing (redeeming) a BTC-e [[redeemable code]] (BTC).

====USD====
* Cash deposit (USD currency) at Post of Russia
* Cash deposit (USD currency) at various banks: (Savings Bank of Russia (Sberbank), Privatbank, RU/UA Terminals, Russian banks, Евросеть (Euroset), Лидер (Lider), Contact, Anelik, UNIStream)
* [[Liberty Reserve]]
* Webmoney WMZ (with volume discount available<ref>If the amount to deposit more than 30 WMZ, fee is reduced to 0.08%. Contact site support via private message for details</ref>)
* Interkassa.com (VISA, MasterCard, PayPal, LiqPay, etc.)
* Yandex.ru
* LiqPay
* Perfect Money
* Qiwi
* [[OKPay]]
* RBK Money
* Additional digital currencies (НСМЭП (NSMEP), Единый Кошелек (Unified Purse), TeleMoney, moneymail, Unikarta, webcreds.com, z-payment, MTS, Альфа-Клик (Alfa-Click), Megafon, Monexy, Pin-Code)
* BTC-e [[redeemable code]], including those obtained from [[BitInstant]] (funding options include QIWI, Cyberplat) and AurumXChange
* International Wire Transfer (Wires in currency other than USD will be converted to USD at no charge<ref>[https://btc-e.com/news/97 Webmoney, Okpay, International bank transfer / EU Bank Transfer (SEPA)]</ref>

====EUR====

* SEPA bank transfer (fee applies)

====RUR====
* QIWI
* LiqPay
* Webmoney WMR
* BTC-e redeemable code
* Bank transfer

===Withdraw options===
====BTC====
There is 0.01 BTC fee to withdraw bitcoins. Also available for withdrawal to BTC-e redeemable code (BTC).

====USD====

* Liberty Reserve
* Webmoney WMZ
* [[PayPal]]
* Perfect Money
* LiqPay
* QIWI
* OKPay
* [[Payza]]/AlertPay
* Epese.com
* Ecoin.cc
* RedPass.com
* Privatbank - USD, UAH
* Savings Bank (Sberbank)
* Telebank
* Alfa Bank
* Wire Transfer
* BTC-E redeemable code (cash out aurumxchange --> MtGox)

====EUR====
Withdrawal methods in Euro.

* SEPA bank transfer (fee applies)

====RUB====
Withdrawal methods in Rubles.

* QIWI
* LiqPay
* Webmoney WMR
* Яндекс.Деньги (Yandex)
* RBK Money
* Cash deposit into account at Сбербанка России! (Savings Bank Sberbank), Телебанк (Telebank), and АльфаБанк (Alfa Bank)
* Cash in Moscow, Russia (delivery to your address is possible)
* Transferred to credit card - VISA and MasterCard
* BTC-e redeemable code (RUR)
* Bank transfer

==Data Services==
===Linux===
* [https://github.com/3M3RY/Dojima Dojima] market client

==History==

The site was first announced on July 17, 2011<ref>[http://bitcointalk.org/index.php?topic=29698.0 Btc-e.com exchange for the exchange of BTC <-> USD]</ref> with test mode trading. Live trading began on August 7, 2011<ref>[http://bitcointalk.org/index.php?topic=29698.msg437237#msg437237 Btc-e.com]</ref>.

On July 31, 2012 the service reported a security incident in which halted trading and caused financial loss to the exchange. The exchange says it covered losses from reserves and trading resumed in a matter of hours<ref>[https://btc-e.com/news/81 News / Trade is stopped]</ref>.

On August 2, 2012 the service added an API for trading, but still lacks an API for bitcoin withdrawals (something offered by every major exchange). On August 20, 2012 the service added BTC/RUR and USD/RUR trading markets. On September 3, 2012 the service added numerous RUR deposit and withdawal methods as well as more USD deposit and withdrawal methods<ref>[https://btc-e.com/news/87 News / Update commissions deposit & withdrawal + add new methods withdrawal]</ref>.

==Criticism==
Bitcoin community member [[User:Luke-jr|Luke-Jr]] claims that BTC-E has frozen his account and funds on their own accord.{{cite}}

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]

==External Links==

* [http://www.btc-e.com BTC-E] exchange website

==References==
<references />

[[Category:Exchanges]]
[[Category:EWallets]]

CampBX

2013-06-25T14:49:09Z

Emery: Tulpenmanie is now Dojima

A bitcoin [[currency exchange]]/trading platform site headquartered in USA - Atlanta, GA.

CampBX is a platform where you can buy and sell Bitcoins for US Dollars in real-time using advanced order-matching algorithms. Any buy or sell order that you place is matched against a database of other orders. If a perfect match is found, a Bitcoin-to-USD trade is executed instantly. If there are no matching orders at the price you specified, then your order can remain open for up to 31 days. To maintain fairness in trading, CampBX have taken a purely-platform approach and they are never a counter-party to any trade.

This platform was designed from the ground up with stability and security as top priorities, and became the first Bitcoin website to obtain Payment Card Industry (PCI) certification and the McAfee Secure seal of confidence on June 28th, 2011 <ref>[https://bitcointalk.org/index.php?topic=23938.0 CampBX Hacker / Security Audit: Results]</ref>.

CampBX is also the first Bitcoin platform to bring advanced features like Margin Trading and Short-selling, and have several more innovative features in pipeline.

There are no fees required to open a CampBX account.

==Headquarter and Offices==
This platform is operated by BulBul Investments LLC, which is a corporate entity registered with the State of Georgia, and is headquartered in Atlanta at 2002 Summit Blvd #300, Atlanta, GA 30319. At launch time CampBX maintained a 4-people development office for a 3-month period; however as the development-phase ended they have switched to a Flex-office plan to save costs.

==Major Features==
CampBX aims to be the feature leader, and this vision is reflected in a comprehensive list of features:

<ul>
<li> Security certification from McAfee</li>
<li> Advanced trading options with AON/FOK/Market</li>
<li> STOPLOSS and Short-Selling available soon </li>
<li> Trading API available</li>
<li> Wallet API available </li>
<li> CBX Instant Bitcoin Transfers Feature </li>
<li> Stoploss / Custom Order Expiry Date/Time </li>
<li> SMS (Text Message) Notifications </li>
<li> Two-Factor Authentication </li>
<li> Based in USA - Atlanta </li>
</ul>

==Adding Funds==
Funds deposited with the exchange for escrow towards placing a buy order include the following.

===BTC===

* Adding bitcoins to the account balance incurs no fees.

===USD===

* [[Dwolla]] (instant). There is a $1,000 per-day transfer limit regardless of deposit or withdrawal.
* P2P bank transfer (available through Chase, Bank of America, Wells Fargo and ING, credited after 3 business days)
* Personal Check
* USPS Postal Money Order (No fee to receive, costs only $1.55 to send $1,000)
* Canada Post Money Order (USD)

==Withdrawing Funds==

===BTC===

* CampBX does not have any fees for Bitcoin withdrawals. The default withdrawal limit is 500 Bitcoins per-day; this limit can be increased by submitting a ticket to the help-desk. Account-to-account (A2A) transfers to another Camp BX account can be made. In the accountholder's profile is the CBX Instant Transfer which the sender needs to know.

===USD===

* [[Dwolla]] (instant). There is a $1,000 per-day transfer limit regardless of deposit or withdrawal.
* ACH Withdrwal (Direct deposit)
* Bank transfer (Domestic wire)
* International Bank transfer (International wire)
* USPS Postal Money Order

==Trading==

CampBX is the only Bitcoin exchanges to offer both market orders as well as limit orders. Market orders get filled regardless of the price.
Additional Advanced Trading options include Fill-or-Kill and All-or-Nothing fills. Fill-or-Kill means that if the order cannot immediately be matched, it will be cancelled automatically. All-or-Nothing means that the order will match only when the entire quantity in the order can be traded. One option is to set a custom expiry date for each order, which allows setting up advanced trading strategies.
The trading algorithms implement trading functionality described in the following SEC Investor Bulletin as closely as possible:
http://www.sec.gov/investor/alerts/trading101basics.pdf

CampBX also provides Quick Trades for casual Bitcoin users, where you enter the quantity and the desired price for buying or selling Bitcoins, and execute the trade. All prices entered are "Limit" prices, where the platform will find a matching trade at given price or better.

Additionally, though currently disabled, the exchange's trading site refers to margin trading (buying on margin and shorting) -- something that no other exchange has offered yet.

===Fees===

Trades on the exchange incur a commission (fee) of 0.55%. (Volume discounts available)

==Data Services==
===Linux===
* [https://github.com/3M3RY/Dojima Dojima] market client

==History==

A story of firsts:

CampBX was the first Bitcoin trading platform to launch on Testnet <ref>[https://bitcointalk.org/index.php?topic=20777.0 CampBX Platform in Beta: Margin Trading, Short Selling, and Advanced Orders]</ref>. This allowed Bitcoin users to try out CampBX without risking their Bitcoins on an unknown website. Following a major CBX Testnet opened for public trial on June 21st, and in the following 15 days handled trading of ~90,000 testnet coins.
CampBX trade engine supported multiple advanced trading features like Margin Trading, Short Selling, Advanced Order Execution like FOK (Fill-or-Kill), (AON) All-or-Nothing orders, Stoploss, and custom expiry dates for orders.

On June 28th, we went through a rigorous third-party security audit by McAfee Hacker Safe (McAfee Secure) and two more white-hat auditors. As our commitment to transparency, we shared the results of the audit in a public forum <ref>[https://bitcointalk.org/index.php?topic=23938.0 CampBX Hacker / Security Audit: Results]</ref>. CampBX obtained compliance with 7 security standards including PCI (Payment Card Industry) compliance, another major first in the Bitcoin world.

We ended the testnet phase and opened for trading following the Independence Day on July 5th, 2011 <ref>[http://forum.bitcoin.org/index.php?topic=26202.0 CampBX Launch - Free Trades for All Bxlievers!]</ref>. As we grow, we are determined to continue this tradition of security, transparency, and customer service.

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]

==External Links==

* [https://CampBX.com/register.php?r=JBfCSWoQaow CampBX Home Page]
* [https://twitter.com/CampBX [[Twitter]] Feed for CampBX]
* [https://facebook.com/CampBX [[Facebook]] page for CampBX]
* [https://campbx.com/api.php API Reference]
* [https://campbx.com/faq.php Office Location and FAQ]
* [https://campbx.com/contact.php Helpdesk for CampBX]
* [https://CampBX.com/register.php?r=JBfCSWoQaow CampBX Terms of Use (User Agreement)]

==References==
<References />

[[Category:Exchanges]]
[[Category:EWallets]]

Mt. Gox

2013-06-25T14:47:42Z

Emery: Tulpenmanie is no longer developed

'''MtGox''', called "Mount Gox" or "MTGOX", has been the most widely used bitcoin [[currency exchange]] market<ref>2011-06-07 on #bitcoin-otc: "MagicalTux: you could use the count of users on mtgox (went over 30k recently)"</ref> since it was started, and remains the largest in terms of popularity and volume.

A registrant on MtGox has at least two sub-accounts: one for bitcoins (BTC), and one for US dollars (USD or MTGUSD) or other national currency. Bitcoins are bought using funds from the trader's national currency account, and the proceeds from the sale of bitcoins are deposited into the same account. Trading must always involve bitcoins as trading between different national currencies is not offered.

Trades on Mt. Gox's execute from balances on deposit with the exchange which in turn makes trading on the market instantaneous, compared to some other Bitcoin markets where a subsequent settlement occurs manually between the trading partners. The disadvantage of this is that a third party must be trusted with keeping the money safe.

MtGox was originally started by Jed McCaleb in July 2010, and was sold to [[Tibanne Co.]] in Japan in March 2011. It is currently operated by Tibanne Co., managed by Mark Karpeles (MagicalTux).

==Trading==
===Buying and selling===

Buying and selling Bitcoins is simple. A buy order is executed partially or in full when the price bid can be matched against a sell order that is at or below the bid amount. A sell order is executed partially or in full when the price asked can be matched against a buy order that is at or above the ask amount. Orders that cannot be matched immediately remain in the orderbook.

Unfunded orders do not appear in the order book, but are automatically readded if a deposit is credited. For example, Mt. Gox allows the entry of a "buy" order even if the account has insufficient funds. If possible, Mt. Gox will execute a portion of the order if it can be partially funded. If a deposit is later credited and the deposit resolves the insufficient funds status of an outstanding order, the order will be immediately activated, and if possible, executed.

===Fees===

Mt. Gox charges a trading fee of up to 0.6% from each party of successful trades made through the market. The fee appears in the account history next to each trade. The trading fee is discounted for larger customers based on volume, which is calculated as a sliding window over the last 720 hours (30 days).

The fees are, by default, subtracted from the proceeds of each trade (e.g., a buy of 1.0 BTC will add to the account balance 0.994 BTC when the exchange fee is 0.6%). An account setting will allow fees to be added to the purchase amount instead (e.g., buying 1.0 BTC at $5 will cost about $5.03 when the exchange fee is 0.6%).

==Adding Funds==

===BTC===
There are no fees incurred when transferring bitcoins to a Mt. Gox account.

Funds are available once [[confirmation|confirmed]] (6 blocks)<ref>[http://www.bitcoin.org/smf/index.php?topic=3851.msg55220#msg55220 How long does it take to Deposit bitcoins to MtGox?]</ref>, a process that can take roughly an hour.

The deposit address is presented along with a QR code that can be scanned with a mobile. This address does not change with each deposit request.

The Add Bitcoins function experiences issues with some browser ad-blocking utilities even though no advertisements are displayed on the website.

====Redeemable Code====

Bitcoins from another Mt. Gox user sent by Mt. Gox [[redeemable code]] (A.K.A. "coupon") may be deposited and will be available for trading immediately.

===Dwolla===

Dwolla is among the fastest and least expensive methods for adding funds from the United States of America to a Mt. Gox account. The transaction fee on [[Dwolla]] is merely $0.25. The process is automated and the funds become available for trading within an hour<ref>[http://forum.bitcoin.org/index.php?topic=15107.msg205622#msg205622 Dwolla to Mt. Gox vs. Dwolla to TradeHill]</ref>.

===OKPay===

[[OKPay]] may be used for depositing funds to USD, EUR, GBP, CHF, and RUB<ref>[https://support.mtgox.com/entries/21034626-okpay OKPAY]</ref>.

===Cash Deposit===

====U.S. (USD)====
* BitInstant - Cash (U.S. dollars) may be deposited at any of thousands of banks, 7-11, Walmart, CVS, Moneygram and more that [[BitInstant]] uses to transfer funds to your Mt. Gox account.

====Brazil (BRL)====
* BitInstant - Cash (Brazilian real) may be deposited using Boleto or through Banco Recomendito.

====Brazil (BRL)====
* BitInstant - Cash (Russian rubles) may be deposited using QIWI or Cyberplat

====UK (GBP)====
* Barclays - Cash (British pound sterling) may be deposited at any Barclays location. There is a 1.5% fee on deposits made with this method<ref>[https://mtgox.com/press_release_20120806.html Introducing a new 1.5% fee on Barclays cash deposit]</ref>.

===Bank Wire===

====International USD====
Funds in USD may be wired to the exchange's bank in Japan. Each wire is subject to a per-wire fee plus any intermediate fees.

====International Wire====

An account can be configured with a wallet for each of the currencies that the exchange supports<ref>[https://mtgox.zendesk.com/entries/20413328-mt-gox-opens-15-new-currency-markets Mt.Gox Opens 15 New Currency Markets]</ref>. When a wire is received in one of these currencies, that account will be credited.

* USD - U.S. Dollar
* EUR - Euro (SEPA or Int'l wire)
* CAD - Canadian Dollar
* GBP - British Pound (Domestic or Int'l wire)
* CHF - Swiss Francs
* RUB - Russian Rubles
* AUD - Australian Dollars
* SEK - Swedish Krona
* DKK - Danish Krona
* HKD - Hong Kong Dollars
* PLN - Polish Zloty (Domestic or Int'l wire)
* CNY - Chinese Yuan
* SGD - Singapore Dollars
* TBH - Thai Baht
* NZD - New Zealand Dollars
* JPY - Japanese Yen (Domestic or Int'l wire)

====AurumXChange USD, EUR and CAD====

Funds may be wired to [[AurumXChange Company]] as USD, EUR or CAD (the latter two of which would then be exchanged into USD) for purchase of a Mt. Gox USD [[redeemable code]] (voucher). Other digital currencies such as [[Liberty Reserve]] can be converted for transfer to Mt. Gox as well. The redeemable code provided is then used to load USD funds into an account with Mt. Gox.

===Direct Deposit===
====EU====

Funds in EUR may be added using SEPA Direct Debit for free, with funds convert to USD at the current ECB rate at the time the funds are received<ref>[http://www.bitcoin.org/smf/index.php?topic=5461.0 MTGox: Euro deposits]</ref>.

====U.S.====

Mt. Gox doesn't directly support an ACH-based (direct deposit) deposit method. Dwolla supports ACH-based fund transfers and those funds can then be deposited with Mt. Gox.

====UK====

Funds may be sent as a GBP direct deposit free of charge.

====Australia====

Funds may be sent using direct deposit (BPay) for a AU$2.00 per-deposit fee. The funds will be converted to USD at the current rate.

==Withdrawing Funds==

MtGox imposes a $1,000 USD limit for withdrawals per 24 hours and a $10,000 USD limit for withdrawals per month with most non-verified accounts. Bitcoins withdrawn are counted toward this limit as well and the USD value is calculated at the market rate at the time of the attempted withdrawal. Customers that have been Verified have higher limits and customers that have Trusted status have limits even higher<ref>[http://bitcoin.stackexchange.com/questions/2442/mtgox-trusted-vs-verified MtGox - trusted vs verified]</ref>. Any [[MtGox#Transfers_to_Other_Customers|account-to-account transfers]] made also count toward this limit as well.

Requests for higher withdrawal limits may be submitted by email
* For higher limits for withdrawal of USD funds, email: aml@mtgox.com
* For higher limits for withdrawal of BTC funds, email: btcupd@mtgox.com

See the [[MtGox#AML|AML]] section regarding verification levels for AML purposes.

===Dwolla===

[[Dwolla]] is among the fastest and least expensive methods for withdrawing USD funds from a Mt. Gox account. The transaction fee to do so is just $0.25.
[[Dwolla]] withdrawals are processed every hour during business hours (Japan time) and every 12 hours on weekends.

As of 25 May 2012, MtGox requires account holders to be "verified (level 1) - 'see below'" to withdraw via Dwolla. <ref>https://support.mtgox.com/entries/21503347-new-aml-policy-for-all-dwolla-users</ref>

The status of the withdrawal request will show one of the following status codes:

* Preparing: System is running checks to see if the transfer can be executed.
* Confirmed: Transfer can be executed and is pending in queue.
* Todo: Transfer is near the top of the queue and will be executed soon.
* Processed: Transfer has been processed.

===BTC===

Bitcoins may be withdrawn at no charge.

A [[green address]] option is available though this type of transaction could experience a delay if the exchange's wallet funding level for green address transactions is insufficient. The withdrawal form also offers an "open transaction" option which forces the transaction to go through the blockchain. If the recipient of a BTC withdrawal happens to also be from Mt. Gox's [[EWallet]], then that transfer would occur instantly and the transaction would not be broadcast to the Bitcoin network. This "open transaction" option forces a withdrawal to be broadcast to the Bitcoin network.

====Redeemable Code====

Mt. Gox no longer allows bitcoins or other currency to be withdrawn using a [[redeemable code]].

===Direct Deposit===
====U.S.====

There is currently no option for withdrawing funds through a direct deposit bank transaction. Funds withdrawn to Dwolla may then, in turn, be withdrawn with bank funds deposited as an ACH transaction.

====EU====

You may withdraw any amount as a direct deposit to your bank. There is a 2% fee on these withdrawals. Contact the exchange by e-mail for this service.

====Australia====

A per-withdrawal fee (2,000 JPY) is subtracted and the remaining amount is sent via international wire in the chosen currency. If not AUD then an exchange fee of 2.5% will be charged.

===International Wire===

To any IBAN, SWIFT/BIC and ABA routable bank<ref>[http://www.facebook.com/MtGox/posts/343372689080478 Mt.Gox now offers international wire transfer to all US Banks]</ref>. Fee applies.

=

==Customer Service==

The preferred method for obtaining service is to place a request through the exchange's [https://mtgox.zendesk.com help desk]. Another method is to send e-mail with the request.

==Wallet/Banking==

An account at this exchange can be considered to be an [[eWallet]]. This service also offers [[:Category:ECommerce|eCommerce]] merchant [https://mtgox.com/merch/about payment services].

==Security Center==

The Security Center allows an account to be secured through the use of one or more One Time Password (OTP) solutions such as what YubiKey and Google Authenticator offer. Features can be protected where the OTP must be provided for each action and are configured independently.

For example, a typical configuration is to set OTP as being required for both withdrawals and security center changes but not for login. With that configuration, the worst damage that can happen from a compromised account or session would be that bitcoins would be bought or sold (though they could also be bought and sold over and over until funds are depleted).

* Login - The OTP must be provided for each login.
* Withdraw - The OTP must be provided for each withdrawal request.
* Security - The OTP must be provided during each configuration change to be performed.

==AML==

Varying degrees of verification will allow for greater per-day and per-month total amounts to be withdrawn<ref>[http://support.mtgox.com/entries/20919111-aml-account-statuses AML Account Statuses]</ref>.

===Unverified (Level 0)===

Designed for basic users, consumers and Bitcoin enthusiasts where 10,000 USD (monthly) is enough for most needs.

===Verified (Level 1)===

The "verified" status is designed for active traders and/or small companies.

===Trusted (Level 2)===

The “trusted” status is designed for day traders, professionals, and companies.

==API==

Mt Gox offers an [[MtGox/API|API]] which can be used to automate operations.

==Data Services==

===Web===
* Bitstock live watcher for trades, depth, history [http://bitstock.info bitstock.info] (Websockets browser required)
* [[Bitcoin Charts]]
* Clark Moody's [[Real Time Bitcoin Market Data]] including Ticker, Order Book and Time Sales (Websockets browser support required)
* [[MtGox Live]] (Websockets browser support required)
* [[Bitcoin Arbitrage Opportunities]] (Websockets browser support required)
* [[Bitcoin Prices]] market rates in multiple currencies

===Windows===
* [[Sierra Chart MtGox Bridge]] trading and charting tool.
* [[ToyTrader]] command line trading tool

===Mac OS X===
* [[BitTicker]] for Mac OS X
* [http://sneak.datavibe.net/20110613/mtgoxwatcher MtGox Watcher] for Mac OS X

===Mobile===
* [[BitcoinX]] mobile app with bid, ask and 24 hour history. For Android
* [[MtGox Live]] Bitcoin Trader with buy, sell, send, chart and depth for Android and iOS
* [https://play.google.com/store/apps/details?id=com.veken0m.cavirtex Bitcoinium] for Android on Google Play

=== firefox addon ===
* [https://github.com/joric/mtgox-ticker] firefox ticker addon

===Linux===
* [http://www.goxsh.info goxsh] command line ticker / depth chart

==E-Commerce==

Online sellers can accept bitcoins for payment using the Mt. Gox's E-commerce Solution, which is an interface to the exchange's [[MtGox/API/HTTP/v1#Merchant_System|Merchant System API]].

==History==
The exchange went online on July 18, 2010.<ref>[http://www.bitcoin.org/smf/index.php?topic=444.0 MtGox announcement on forum]</ref>

On October 10, 2010 the exchange switched from [[PayPal]] to Liberty Reserve as the main funding option as a result of this attack. Former PayPal customers still had the possibility to withdraw their USD using alternative methods.

On March 6th, 2011 ownership of the exchange changed hands<ref>[https://bitcointalk.org/index.php?topic=4187.0 Mtgox is changing owners]</ref>. Tibanne publishes their [http://legal.tibanne.com/docs/20110801_company_certificate.pdf company certificate] from the Japanese government.

On June 19, 2011 the service experienced a significant security breach<ref>[https://support.mtgox.com/entries/20224998-huge-bitcoin-sell-off-due-to-a-compromised-account-rollback Huge Bitcoin sell off due to a compromised account - rollback]</ref>. The incident caused a selloff down to BTC/USD of $0.01 due to fraudulent trading. The site was disabled and all trading following the point that fraudulent trading began was rolled back. Complicating this breach was the release of a list of the exchange's accounts including username, email address and a password hash, which forced the exchange to implement an account recovery method for customers to regain control of their accounts.

In July, 2011 it was observed that the exchange no longer allows new registrations to occur without having a valid e-mail address.

On July 19, 2011 a press release announced that MtGox had acquired [[MtGox Live]].<ref>[https://mtgox.com/press_release_20110719.html World's Leading Bitcoin Exchange, Mt.Gox, acquires MtGoxLive.com]</ref>

Announced on March 6, 2012 was the Merchant Solution and API<ref>[https://mtgox.com/press_release_20120306.html Mt.Gox launches the definitive bitcoin checkout solution]</ref>

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]
* [[MtGox/API|API]]
* [[Bitcoin Ladder]]

==External Links==

* [https://mtgox.com MT. Gox exchange] website
* [https://mtgox.com/merch/about Mt. Gox Merchant Services]
* [https://mtgox.zendesk.com Customer Service Help Desk]

==References==
<references/>

[[Category:Exchanges]]
[[Category:eWallets]]
[[Category:Shopping Cart Interfaces]]
[[ru:MtGox]]

MtGox/API/Streaming

2012-10-05T19:04:23Z

Emery: The websocket is gone. DOES ANYONE ELSE SEE A GLARING SECURITY ISSUE IN PEOPLE OTHER THAN MTGOX STAFF EDITING THIS PAGE?!

Real time streaming data may be obtained over the streaming API, implemented in [http://socket.io/ Socket.io]<ref>Socket.io forum announcement by MagicalTux: https://bitcointalk.org/index.php?topic=14412.msg613271#msg613271</ref>. The original WebSocket API<ref>Original WebSocket thread: https://bitcointalk.org/index.php?topic=5855.msg86219</ref> is deprecated as of 11-Nov-2011.

==Connecting==
The following JavaScript code establishes a connection in the browser:
<source lang="javascript">
<script src="https://socketio.mtgox.com/socket.io/socket.io.js"></script>
<script>
var conn = io.connect('https://socketio.mtgox.com/mtgox');
conn.on('message', function(data) {
// Handle incoming data object.
});
</script>
</source>

==the Currency parameter ==
use :
websocket.mtgox.com:80/mtgox?Currency=EUR

and the websocket will give you updates in EUR currency

The session ID expires after 30 seconds

==Handling Events==
Socket.io exposes a simple interface for handling events. Handling <tt>message</tt> events is shown above, but there are other events that may be handled:
<source lang="javascript">
conn.on('connect', onConnect);
conn.on('disconnect', onDisconnect);
conn.on('error', onError);
conn.on('message', onMessage);
</source>

==Incoming Data==
Data arrives as a full object instead of as JSON text, eliminating the need to parse the data in the JavaScript handler. Messages that come across the socket to trigger the <tt>message</tt> event will contain the following minimum components:
<source lang="javascript">
{
"op":<OPERATION_TYPE>
}
</source>

The <tt>OPERATION_TYPE</tt> field may take these values:

:{| class="wikitable"
|-
! OPERATION_TYPE !! Description
|-
| subscribe || Notification that the user is subscribed to a channel
|-
| unsubscribe || Messages will no longer arrive over the channel
|-
| remark || A server message, usually a warning
|-
| private || The operation for depth, trade, and ticker messages
|-
| result || The response for op:call operations
|}

===op:subscribe and op:unsubscribe===
The subscribe and unsubscribe message data are very simple, containing the channel and the operation.
<source lang="javascript">
{
"channel":<CHANNEL_ID>,
"op":"subscribe" OR "unsubscribe"
}
</source>

Some of the channels are:

:{| class="wikitable"
|-
! Channel ID !! Description
|-
| dbf1dee9-4f2e-4a08-8cb7-748919a71b21 || Trades
|-
| d5f06780-30a8-4a48-a2f8-7ed181b4a13f || Ticker
|-
| 24e67e0d-1cad-4cc0-9e7a-f8523ef460fe || Depth
|}

===op:remark===
The remark operation contains message and success fields.
<source lang="javascript">
{
"op":"remark",
"message":<MESSAGE FROM THE SERVER>,
"success":<boolean>
}
</source>

===op:private===
The payloads of the <tt>op:private</tt> messages contain the real time market information. Each message follows this form:

<source lang="javascript">
{
"channel":<CHANNEL_ID>,
"op":"private",
"private":<MESSAGE_TYPE>,
<MESSAGE_TYPE>:<DATA_PAYLOAD>
}
</source>

The <tt>MESSAGE_TYPE</tt> field may take the values:

:{| class="wikitable"
|-
! MESSAGE_TYPE !! Description
|-
| ticker || Ticker messages
|-
| trade || Trades, as they occur
|-
| depth || Orders placed or removed
|-
| result || The result of a websocket-encapsulated [[MtGox/API/HTTP/v1|version 1 HTTP API]] request
|}

====Ticker====
Ticker messages contain the current inside Bid and Ask as well as daily highs, lows, and volume. The fields contained in the ticker match those defined in the version 1.0 API above. All fields contain <tt>currency</tt>, <tt>display</tt>, <tt>value</tt>, and <tt>value_int</tt> entries.
<source lang="javascript">
{
"channel":"d5f06780-30a8-4a48-a2f8-7ed181b4a13f",
"op":"private",
"origin":"broadcast",
"private":"ticker",
"ticker":{
"avg":{
"currency":"USD",
"display":"$2.26847",
"value":"2.26847",
"value_int":"226847"
},
"buy":{...},
"high":{...},
"last":{..},
"last_local":{...},
"last_orig":{...},
"low":{...},
"sell":{...},
"vol":{
"currency":"BTC",
"display":"118,696.02104208",
"value":"118696.02104208",
"value_int":"11869602104208"
},
"vwap":{...}
}
}
</source>

====Trade====
<source lang="javascript">{
"channel":"dbf1dee9-4f2e-4a08-8cb7-748919a71b21",
"op":"private",
"origin":"broadcast",
"private":"trade",
"trade":{
"amount":2.71,
"amount_int":"271000000",
"date":1310279340,
"item":"BTC",
"price":14.43,
"price_currency":"USD",
"price_int":"1443000",
"primary":"Y",
"properties":"limit, mixed_currency",
"tid":"1310279340877902",
"trade_type":"bid",
"type":"trade"
}
}
</source>

'''trade''' contains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || the traded amount in item (BTC), float, deprecated
|-
| amount_int || the traded amount * 1E8
|-
| date || unix timestamp of trade
|-
| item || What was this trade about
|-
| price || price per unit, float, deprecated
|-
| price_int || price in smallest unit as integer (5 decimals of USD, 3 in case of JPY)
|-
| price_currency || currency in which trade was completed
|-
| tid || Trade id (big integer, which is in fact trade timestamp in microseconds)
|-
| trade_type || Did this trade result from the execution of a bid or a ask?
|-
|}

====Depth====

Changes to the market depth data are broadcast so an up-to-date market depth can be kept by clients.

<source lang="javascript">{
"channel":"24e67e0d-1cad-4cc0-9e7a-f8523ef460fe",
"depth":{
"currency":"USD",
"item":"BTC",
"now":"1323644358437819",
"price":"14.43",
"price_int":"1443000",
"total_volume_int":"849766000",
"type":1,
"type_str":"ask",
"volume":"-2.71",
"volume_int":"-271000000"
},
"op":"private",
"origin":"broadcast",
"private":"depth"
}</source>

'''depth''' contains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| currency || the currency affected
|-
| item || the item (BTC)
|-
| price || price as a float, deprecated
|-
| total_volume_int || total volume at this price, after applying the depth update, can be used as a starting point before applying subsequent updates.
|-
| price_int || the price at which volume change happened (5 decimal for USD, 3 for JPY)
|-
| type || 1=ask, 2=bid. deprecated, use type_str
|-
| type_str || type of order at this depth, either "ask" or "bid"
|-
| volume || the volume change as float, deprecated
|-
| volume_int || volume change * 1E8

|}

=== op:result ===

Output from [[MtGox/API/HTTP/v1|HTTP API version 1]] requests that were sent over the websocket.

<source lang="javascript">{
"id":<REQUEST ID>,
"op":"result",
"result": {
...
}
}</source>

"result" contains the result of the call the same as if it were called over the HTTP API. <REQUEST ID> is the ID chosen by you when the request was sent.

=== Private per-account messages ===

The streaming API provides a private channel for every user which receives updates for account-related activities like new orders being created. To subscribe, do:

<source lang="javascript">{
"op":"mtgox.subscribe",
"key":<PRIVATE_IDKEY>
}</source>

<PRIVATE_IDKEY> is obtained by sending a request to [[MtGox/API/HTTP/v1#idKey|generic/private/idkey]] in the version 1 API. Either over HTTP or through the websocket using [[#Authenticated_commands|op:call]].

==== user_order ====

user_order is sent when a the status of a user's order is changed.

<source lang="javascript">{
"channel": <USER CHANNEL GUID>
"op": "private".
"origin": "broadcast",
"private": "user_order".
"user_order": {
"amount": {
"currency": "BTC",
"display": "1.00000000\U00a0BTC",
"value": "1.00000000",
"value_int": "100000000"
},
"currency": "USD",
"date": "1330522328",
"item": "BTC",
"oid": <ORDER GUID>,
"price": {
"currency": "USD",
"display": "$10.00000",
"value": "10.00000",
"value_int": "1000000",
};
"status": <ORDER STATUS>,
"type": <ORDER TYPE>,
};
}</source>

{| class="wikitable"
|-
! Name !! Value
|-
| USER CHANNEL GUID || GUID of private user channel
|-
| ORDER GUID || GUID of order
|-
| ORDER STATUS || New status of the order. Valid states are: pending, post-pending, open, executing, invalid, or stop.
|-
| ORDER TYPE || bid or ask
|}

When an order is cancelled, the "user_order" field only contains the "oid", and none of the other fields.

==== wallet ====

Updates to the user's wallet balance.

<source lang="javascript">{
"channel": <USER CHANNEL GUID>,
"op": "private",
"origin": "broadcast",
"private": "wallet",
"wallet": {
"op": <UPDATE SOURCE>,
"amount": {
...
},
"info": <UPDATE INFO>,
"ref": <REFERENCE CODE>,
"balance": {
...
}
}
}</source>

"..." values above are normal 'amount' type dictionaries containing "currency", "value", "value_int", and "display".

{| class="wikitable"
|-
! Name !! Value
|-
| USER CHANNEL GUID || GUID of private user channel
|-
| ORDER GUID || GUID of order
|-
| UPDATE SOURCE || Cause of the balance update. Can be: in, out, earned, spent, withdraw, or deposit
|-
| UPDATE INFO || Human readable string describing the update. Same string you see in the account history on mtgox.com
|-
| REFERENCE CODE || Reference code for bank transfers. "null" if this isn't a bank transfer.
|}

Description of the different source types:
{| class="wikitable"
|-
! Source !! Description
|-
| deposit || Account deposits
|-
| withdraw || Account withdrawals
|-
| earned || Amount of USD gained from a trade
|-
| spent || Amount of USD used for a trade
|-
| in || Amount of BTC gained from a trade
|-
| out || Amount of BTC used for a trade
|-
| fee || MtGox fees
|}

==== trade ====

Trades that happen on behalf of a user whose private channel you're subscribed to issue trade messages with the same format as the [[MtGox/API/Streaming#Trade|public trades channel]] does. If you're subscribed to both, be careful not to take both into account during calculations, it might cause some hard to track down issues

== Outgoing commands==
=== Direct commands ===

Commands that can be sent without authentication

==== unsubscribe ====
Stop receiving messages from a channel

<source lang="javascript">{
"op":"unsubscribe",
"channel":<CHANNEL ID>
}</source>

Responds with an identical message to confirm
==== mtgox.subscribe ====
Subscribe to a channel to start receiving messages from it.

<source lang="javascript">{
"op": "mtgox.subscribe",
"type": "ticker"
}</source>
"type" can be ticker, trades, or depth.

=== Authenticated commands ===

These commands require an API key and secret pair to sign requests. Any of the [[MtGox/API/HTTP/v1|HTTP API version 1]] methods can be called. Responses are [[MtGox/API/Streaming#op:result|op:result]]

<source lang="javascript">{
"op":"call",
"id":<REQUEST ID>,
"call":<BASE-64 ENCODED SIGNED REQUEST>,
"context":"mtgox.com"
}</source>

<REQUEST ID> can be any string, it's used to identify the response as belonging to this request when an answer comes back. md5'ing your nonce is a good way to get an id.

"call" must be a base-64 encoded string consisting of, in order: an API key, a signed copy of the request, and the request text itself.

The queries themselves look like:
<source lang="javascript">{
"id":<REQUEST ID>,
"call":<HTTP API ENDPOINT>,
"nonce":<REQUEST NONCE>,
"params":<REQUEST PARAMETERS>,
"item":"BTC"
}</source>

<HTTP API ENDPOINT> is the last two path components of any version 1 API endpoint, for example [[#Private_info|private/info]], or [[#Cancelled_Trades|public/cancelledtrades]].

<REQUEST PARAMETERS> is optional for any request that doesn't have parameters.

The signing process is similar to the HTTP API, but because we can't send headers in an open websocket, the API key and signed request are simply prepended to the actual query data and base64 encoded. Reference implementations are available at https://github.com/MtGox/websocket

Here's a sample of how to create a valid request in PHP 5.3:
<source lang="php">$nonce = explode(' ', microtime(false));
$nonce = $nonce[1].substr($nonce[0], 2, 6);
$id = md5($nonce); // id can be anything to recognize this call
$query = array('call' => $call, 'params' => $params, 'item' => $item, 'currency' => $currency, 'id' => $id, 'nonce' => $nonce);
$query = json_encode($query);
// generate signature
$sign = hash_hmac('sha512', $query, base64_decode($apiSecret), true);
// prefix signature to query
$query = pack('H*', str_replace('-','',$apiKey)).$sign.$query;
// send query
$call = array('op' => 'call', 'call' => base64_encode($query), 'id' => $id, 'context' => 'mtgox.com');
// $call can now be pushed out to the websocket</source>

== examples ==

=== ticker ===
javascript, using hookio :

http://www.youtube.com/watch?v=KD5ljtNK72U

http://github.com/hookio

http://github.com/cronopio/hook.io-mtgox

Another node.js project, using plain websockets (largely based on cronopio's work) :

https://github.com/dlanod/node-mtgox-websocket-client

A python example :
https://github.com/3M3RY/python-mtgox

A Java example:
https://github.com/timmolter/XChange

=== arbitrage ===
https://github.com/goteppo/ArBit

=== websocket tools ===
https://github.com/cronopio/hook.io-ws

https://github.com/dlanod/node-mtgox-websocket-client

https://github.com/progrium/wssh
<source lang="bash">wssh websocket.mtgox.com:80/mtgox | grep depth 1>>depth.txt</source>

==See Also==

* [[MtGox/API/HTTP/v1]]

== References ==
<references></references>

CampBX

2012-09-25T21:57:49Z

Emery: added reference to tulpenmanie application

A bitcoin [[currency exchange]]/trading platform site headquartered in USA - Atlanta, GA.

CampBX is a platform where you can buy and sell Bitcoins for US Dollars in real-time using advanced order-matching algorithms. Any buy or sell order that you place is matched against a database of other orders. If a perfect match is found, a Bitcoin-to-USD trade is executed instantly. If there are no matching orders at the price you specified, then your order can remain open for up to 31 days. To maintain fairness in trading, CampBX have taken a purely-platform approach and they are never a counter-party to any trade.

This platform was designed from the ground up with stability and security as top priorities, and became the first Bitcoin website to obtain Payment Card Industry (PCI) certification and the McAfee Secure seal of confidence on June 28th, 2011 <ref>[https://bitcointalk.org/index.php?topic=23938.0 CampBX Hacker / Security Audit: Results]</ref>.

CampBX is also the first Bitcoin platform to bring advanced features like Margin Trading and Short-selling, and have several more innovative features in pipeline.

There are no fees required to open a CampBX account.

==Headquarter and Offices==
This platform is operated by BulBul Investments LLC, which is a corporate entity registered with the State of Georgia, and is headquartered in Atlanta at 2002 Summit Blvd #300, Atlanta, GA 30319. At launch time CampBX maintained a 4-people development office for a 3-month period; however as the development-phase ended they have switched to a Flex-office plan to save costs.

==Major Features==
CampBX aims to be the feature leader, and this vision is reflected in a comprehensive list of features:

<ul>
<li> Security certification from McAfee</li>
<li> Advanced trading options with AON/FOK/Market</li>
<li> STOPLOSS and Short-Selling available soon </li>
<li> Trading API available</li>
<li> Wallet API available </li>
<li> CBX Instant Bitcoin Transfers Feature </li>
<li> Stoploss / Custom Order Expiry Date/Time </li>
<li> SMS (Text Message) Notifications </li>
<li> Two-Factor Authentication </li>
<li> Based in USA - Atlanta </li>
</ul>

==Adding Funds==
Funds deposited with the exchange for escrow towards placing a buy order include the following.

===BTC===

* Adding bitcoins to the account balance incurs no fees.

===USD===

* [[Dwolla]] (instant). There is a $1,000 per-day transfer limit regardless of deposit or withdrawal.
* Personal Check
* USPS Postal Money Order (No fee to receive, costs only $1.55 to send $1,000)
* Canada Post Money Order (USD)

==Withdrawing Funds==

===BTC===

* CampBX does not have any fees for Bitcoin withdrawals. The default withdrawal limit is 500 Bitcoins per-day; this limit can be increased by submitting a ticket to the help-desk. Account-to-account (A2A) transfers to another Camp BX account can be made. In the accountholder's profile is the CBX Instant Transfer which the sender needs to know.

===USD===

* [[Dwolla]] (instant). There is a $1,000 per-day transfer limit regardless of deposit or withdrawal.
* ACH Withdrwal (Direct deposit)
* Bank transfer (Domestic wire)
* International Bank transfer (International wire)
* USPS Postal Money Order

==Trading==

CampBX is the only Bitcoin exchanges to offer both market orders as well as limit orders. Market orders get filled regardless of the price.
Additional Advanced Trading options include Fill-or-Kill and All-or-Nothing fills. Fill-or-Kill means that if the order cannot immediately be matched, it will be cancelled automatically. All-or-Nothing means that the order will match only when the entire quantity in the order can be traded. One option is to set a custom expiry date for each order, which allows setting up advanced trading strategies.
The trading algorithms implement trading functionality described in the following SEC Investor Bulletin as closely as possible:
http://www.sec.gov/investor/alerts/trading101basics.pdf

CampBX also provides Quick Trades for casual Bitcoin users, where you enter the quantity and the desired price for buying or selling Bitcoins, and execute the trade. All prices entered are "Limit" prices, where the platform will find a matching trade at given price or better.

Additionally, though currently disabled, the exchange's trading site refers to margin trading (buying on margin and shorting) -- something that no other exchange has offered yet.

===Fees===

Trades on the exchange incur a commission (fee) of 0.55%. (Volume discounts available)

==Data Services==
===Linux===
* [https://github.com/3M3RY/tulpenmanie tulpenmanie] graphical trading platform

==History==

A story of firsts:

CampBX was the first Bitcoin trading platform to launch on Testnet <ref>[https://bitcointalk.org/index.php?topic=20777.0 CampBX Platform in Beta: Margin Trading, Short Selling, and Advanced Orders]</ref>. This allowed Bitcoin users to try out CampBX without risking their Bitcoins on an unknown website. Following a major CBX Testnet opened for public trial on June 21st, and in the following 15 days handled trading of ~90,000 testnet coins.
CampBX trade engine supported multiple advanced trading features like Margin Trading, Short Selling, Advanced Order Execution like FOK (Fill-or-Kill), (AON) All-or-Nothing orders, Stoploss, and custom expiry dates for orders.

On June 28th, we went through a rigorous third-party security audit by McAfee Hacker Safe (McAfee Secure) and two more white-hat auditors. As our commitment to transparency, we shared the results of the audit in a public forum <ref>[https://bitcointalk.org/index.php?topic=23938.0 CampBX Hacker / Security Audit: Results]</ref>. CampBX obtained compliance with 7 security standards including PCI (Payment Card Industry) compliance, another major first in the Bitcoin world.

We ended the testnet phase and opened for trading following the Independence Day on July 5th, 2011 <ref>[http://forum.bitcoin.org/index.php?topic=26202.0 CampBX Launch - Free Trades for All Bxlievers!]</ref>. As we grow, we are determined to continue this tradition of security, transparency, and customer service.

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]

==External Links==

* [https://CampBX.com/register.php?r=JBfCSWoQaow CampBX Home Page]
* [https://twitter.com/CampBX [[Twitter]] Feed for CampBX]
* [https://facebook.com/CampBX [[Facebook]] page for CampBX]
* [https://campbx.com/api.php API Reference]
* [https://campbx.com/faq.php Office Location and FAQ]
* [https://campbx.com/contact.php Helpdesk for CampBX]
* [https://CampBX.com/register.php?r=JBfCSWoQaow CampBX Terms of Use (User Agreement)]

==References==
<References />

[[Category:Exchanges]]
[[Category:EWallets]]

BTC-e

2012-09-25T21:56:07Z

Emery: line spacing

A [[currency exchange]] with market for trading between bitcoins and other currencies, including the U.S. dollar, Russian ruble and other cryptocurrencies [[Litecoin]] and [[Namecoin]]. The site has Russian and English user interface translations.

==Features==

===Currency pairs===
[http://www.btc-e.com BTC-E] supports the exchange between the major currency pairs, such as:
* BTC/USD
* BTC/RUR (Russian Ruble)
* USD/RUR
* LTC/BTC, LTC/USD
* NMC/BTC

===Deposit options===

====BTC====
There is no fee for depositing bitcoins or depositing (redeeming) a BTC-e [[redeemable code]] (BTC).

====USD====
* Cash deposit (USD currency) at Post of Russia
* Cash deposit (USD currency) at various banks: (Savings Bank of Russia (Sberbank), Privatbank, RU/UA Terminals, Russian banks, Евросеть (Euroset), Лидер (Lider), Contact, Anelik, UNIStream)
* [[Liberty Reserve]]
* Webmoney WMZ (with volume discount available<ref>If the amount to deposit more than 30 WMZ, fee is reduced to 0.08%. Contact support site support via private message for details</ref>)
* Interkassa.com (VISA, MasterCard, PayPal, LiqPay, etc.)
* Yandex.ru
* LiqPay
* Perfect Money
* Qiwi
* [[OKPay]]
* RBK Money
* Additional digital currencies (НСМЭП (NSMEP), Единый Кошелек (Unified Purse), TeleMoney, moneymail, Unikarta, webcreds.com, z-payment, MTS, Альфа-Клик (Alfa-Click), Megafon, Monexy, Pin-Code)
* BTC-e [[redeemable code]], including those obtained from [[BitInstant]] (funding options include QIWI, Cyberplat) and AurumXChange
* International Wire Transfer

====RUR====
* QIWI
* LiqPay
* Webmoney WMR
* BTC-e redeemable code
* Bank transfer

===Withdraw options===
====BTC====
There is no fee to withdraw bitcoins. Also available for withdrawal to BTC-e redeemable code (BTC).

====USD====

* Liberty Reserve
* Webmoney WMZ
* [[PayPal]]
* Perfect Money
* LiqPay
* QIWI
* OKPay
* [[Payza]]/AlertPay
* Epese.com
* Ecoin.cc
* RedPass.com
* Privatbank - USD, UAH
* Savings Bank (Sberbank)
* Telebank
* Alfa Bank
* Wire Transfer
* BTC-E redeemable code (cash out aurumxchange --> MtGox)

====RUB====
Withdrawal methods in Rubles.

* QIWI
* LiqPay
* Webmoney WMR
* Яндекс.Деньги (Yandex)
* RBK Money
* Cash deposit into account at Сбербанка России! (Savings Bank Sberbank), Телебанк (Telebank), and АльфаБанк (Alfa Bank)
* Cash in Moscow, Russia (delivery to your address is possible)
* Transferred to credit card - VISA and MasterCard
* BTC-e redeemable code (RUR)
* Bank transfer

==Data Services==
===Linux===
* [https://github.com/3M3RY/tulpenmanie tulpenmanie] graphical trading platform

==History==

The site was first announced on July 17, 2011<ref>[http://bitcointalk.org/index.php?topic=29698.0 Btc-e.com exchange for the exchange of BTC <-> USD]</ref> with test mode trading. Live trading began on August 7, 2011<ref>[http://bitcointalk.org/index.php?topic=29698.msg437237#msg437237 Btc-e.com]</ref>.

On July 31, 2012 the service reported a security incident in which halted trading and caused financial loss to the exchange. The exchange says it covered losses from reserves and trading resumed in a matter of hours<ref>[https://btc-e.com/news/81 News / Trade is stopped]</ref>.

On August 2, 2012 the service added an API for trading, but still lacks an API for bitcoin withdrawals (something offered by every major exchange). On August 20, 2012 the service added BTC/RUR and USD/RUR trading markets. On September 3, 2012 the service added numerous RUR deposit and withdawal methods as well as more USD deposit and withdrawal methods<ref>[https://btc-e.com/news/87 News / Update commissions deposit & withdrawal + add new methods withdrawal]</ref>.

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]

==External Links==

* [http://www.btc-e.com BTC-E] exchange website

==References==
<references />

[[Category:Exchanges]]
[[Category:EWallets]]

BTC-e

2012-09-25T21:54:52Z

Emery: added reference to tulpenmanie application

A [[currency exchange]] with market for trading between bitcoins and other currencies, including the U.S. dollar, Russian ruble and other cryptocurrencies [[Litecoin]] and [[Namecoin]]. The site has Russian and English user interface translations.

==Features==

===Currency pairs===
[http://www.btc-e.com BTC-E] supports the exchange between the major currency pairs, such as:
* BTC/USD
* BTC/RUR (Russian Ruble)
* USD/RUR
* LTC/BTC, LTC/USD
* NMC/BTC

===Deposit options===

====BTC====
There is no fee for depositing bitcoins or depositing (redeeming) a BTC-e [[redeemable code]] (BTC).

====USD====
* Cash deposit (USD currency) at Post of Russia
* Cash deposit (USD currency) at various banks: (Savings Bank of Russia (Sberbank), Privatbank, RU/UA Terminals, Russian banks, Евросеть (Euroset), Лидер (Lider), Contact, Anelik, UNIStream)
* [[Liberty Reserve]]
* Webmoney WMZ (with volume discount available<ref>If the amount to deposit more than 30 WMZ, fee is reduced to 0.08%. Contact support site support via private message for details</ref>)
* Interkassa.com (VISA, MasterCard, PayPal, LiqPay, etc.)
* Yandex.ru
* LiqPay
* Perfect Money
* Qiwi
* [[OKPay]]
* RBK Money
* Additional digital currencies (НСМЭП (NSMEP), Единый Кошелек (Unified Purse), TeleMoney, moneymail, Unikarta, webcreds.com, z-payment, MTS, Альфа-Клик (Alfa-Click), Megafon, Monexy, Pin-Code)
* BTC-e [[redeemable code]], including those obtained from [[BitInstant]] (funding options include QIWI, Cyberplat) and AurumXChange
* International Wire Transfer

====RUR====
* QIWI
* LiqPay
* Webmoney WMR
* BTC-e redeemable code
* Bank transfer

===Withdraw options===
====BTC====
There is no fee to withdraw bitcoins. Also available for withdrawal to BTC-e redeemable code (BTC).

====USD====

* Liberty Reserve
* Webmoney WMZ
* [[PayPal]]
* Perfect Money
* LiqPay
* QIWI
* OKPay
* [[Payza]]/AlertPay
* Epese.com
* Ecoin.cc
* RedPass.com
* Privatbank - USD, UAH
* Savings Bank (Sberbank)
* Telebank
* Alfa Bank
* Wire Transfer
* BTC-E redeemable code (cash out aurumxchange --> MtGox)

====RUB====
Withdrawal methods in Rubles.

* QIWI
* LiqPay
* Webmoney WMR
* Яндекс.Деньги (Yandex)
* RBK Money
* Cash deposit into account at Сбербанка России! (Savings Bank Sberbank), Телебанк (Telebank), and АльфаБанк (Alfa Bank)
* Cash in Moscow, Russia (delivery to your address is possible)
* Transferred to credit card - VISA and MasterCard
* BTC-e redeemable code (RUR)
* Bank transfer

==Data Services==

===Linux===
* [https://github.com/3M3RY/tulpenmanie tulpenmanie] graphical trading platform

==History==

The site was first announced on July 17, 2011<ref>[http://bitcointalk.org/index.php?topic=29698.0 Btc-e.com exchange for the exchange of BTC <-> USD]</ref> with test mode trading. Live trading began on August 7, 2011<ref>[http://bitcointalk.org/index.php?topic=29698.msg437237#msg437237 Btc-e.com]</ref>.

On July 31, 2012 the service reported a security incident in which halted trading and caused financial loss to the exchange. The exchange says it covered losses from reserves and trading resumed in a matter of hours<ref>[https://btc-e.com/news/81 News / Trade is stopped]</ref>.

On August 2, 2012 the service added an API for trading, but still lacks an API for bitcoin withdrawals (something offered by every major exchange). On August 20, 2012 the service added BTC/RUR and USD/RUR trading markets. On September 3, 2012 the service added numerous RUR deposit and withdawal methods as well as more USD deposit and withdrawal methods<ref>[https://btc-e.com/news/87 News / Update commissions deposit & withdrawal + add new methods withdrawal]</ref>.

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]

==External Links==

* [http://www.btc-e.com BTC-E] exchange website

==References==
<references />

[[Category:Exchanges]]
[[Category:EWallets]]

Bitstamp

2012-09-25T21:54:06Z

Emery: added reference to tulpenmanie application

An currency exchange which operates a BTC/USD market with support for various currencies for deposit and withdrawal.

==Trading==
*Buying/selling

A buy/sell order is executed partially or in full when the price bid can be matched against a sell/buy order that is at or below the bid amount.

==Adding funds==

===BTC===
There are no fees incurred when when transferring bitcoins for deposit. Funds are available once confirmed (3 confirms), a process that can take roughly 30minutes. A Bitstamp [[Redeemable code]] (coupon) denominated in BTC or BTC and USD can be deposited. The bitcoins using these coupons are instantly credited.

===EUR===
Exchange accepts EUR deposits via SEPA transfers, then converts them to USD and credits them to online account. '''No deposit fees!'''<br/>

===GBP===
Exchange accepts wire transfers in GBP, then converts them to USD and credits them to online account.<br/>
Charging 0.1% deposit fee(minimum fee = $15)

===USD===
Exchange accepts international wire transfers in USD, charging 0.1% deposit fee(minimum fee = $15)<br/>
Exchange accepts MtGox - USD redeemable codes, charging 2% fee.<br/>
Exchange accepts a Bitstamp redeemable code (coupon) in USD denomination or combination of USD and BTC<br/>
Exchange supports transfers between Dwolla, Liberty Reserve, MtGox, Cash Bank Deposits, Crypto X Change, Bitcoinica, BTC-E and VirWox via '''Bitinstant'''.

===CHF===
Exchange accepts wire transfers in CHF, then converts them to USD and credits them to online account.<br/>
Charging 0.1% deposit fee(minimum fee = $15)

==Withdrawing funds==

===BTC===
Bitcoins may be withdrawn at no charge. Withdrawals can be sent to a bitcoin address or they can be made using a [[Redeemable code]] (coupon).

===EUR===
SEPA withdrawals are charged with fixed 0.90€ fee once your funds are converted to EUR. Minimum amount for SEPA withdrawal is $10,00.

===GBP===
GBP wire deposits and withdrawals in GBP are supported.<br/>

===USD===
International wire withdrawals in USD will be charged with 0.09% fee, minimum fee is $15,00. Minimum amount for international withdrawal is $50,00.<br/>

Withdrawal can occur using a Bitstamp redeemable code (coupon) (USD denomination) or as a Mt. Gox redeemable code (2% fee).

===CHF===
International wire withdrawals in CHF will be charged with 0.09% fee, minimum fee is $15,00. Minimum amount for international withdrawal is $50,00.<br/>

==Fees==
Bitstamp charges a trading fee from each party of successful trades made through the market. The amount of the fee will vary based on a 30 day trading history. The rate for new accounts and those with the lowest volume is 0.5%. Refer to the [https://www.bitstamp.net/fee_schedule fee schedule] to determine discount levels. The fee that was charged appears in the account history next to each trade.

==Internal transfers==
Bitstamp allows internal transfer of funds to other users using Bitstamp codes. One party withdraws funds by creating a code and then sending (in a secure manner) the code to a trusted user who then redeems that code by using deposit Bitstamp code option. The code denominations can be in BTCs, USDs, or combination of those two.

==Instant transfers via other services==
'''BitInstant'''
*Dwolla
*Liberty Reserve
*MtGox
*Cash Bank Deposits
*Crypto X Change
*Bitcoinica
*BTC-E
*VirWox

==Localization==
Bitstamp is localizing website with online collaborative online translating tool. Feel free to join and help with translation to your native language.

Link: http://crowdin.net/project/bitstamp

==Account Security==

Access to an account may be protected with the optional Google Authenticator utility.

==Language Support==

The site has support for various languages:

* English
* Dutch
* Italian
* Polish
* Slovenian

==API==
API is available https://www.bitstamp.net/api/

==Data Services==

===Linux===
* [https://github.com/3M3RY/tulpenmanie tulpenmanie] graphical trading platform

==History==

The exchange was announced on August 22, 2011<ref>[http://bitcointalk.org/index.php?topic=38711.0 www.BITSTAMP.net Bitcoin exchange site for USD/BTC]</ref>. Bitstamp.net is owned by Bitstamp d.o.o. and based in Slovenia.

On May 12, 2012 the exchange began offering volume discounts for trading fees<ref>[http://bitcointalk.org/index.php?topic=81519.0 Bitstamp introduces volume discount program]</ref>.

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]

==External Links==

* [http://www.bitstamp.net Bitstamp] web site
* [http://twitter.com/#!/BitStamp @Bitstamp] Twitter

==References==
<References />

[[Category:Exchanges]]
[[Category:EWallets]]

Mt. Gox

2012-09-25T21:48:40Z

Emery: /* Linux */ added reference to tulpenmanie application

'''MtGox''', called "Mount Gox" or "MTGOX", has been the most widely used bitcoin [[currency exchange]] market<ref>2011-06-07 on #bitcoin-otc: "MagicalTux: you could use the count of users on mtgox (went over 30k recently)"</ref> since it was started, and remains the largest in terms of popularity and volume.

A registrant on MtGox has at least two sub-accounts: one for bitcoins (BTC), and one for US dollars (USD or MTGUSD) or other national currency. Bitcoins are bought using funds from the trader's national currency account, and the proceeds from the sale of bitcoins are deposited into the same account. Trading must always involve bitcoins as trading between different national currencies is not offered.

Trades on Mt. Gox's execute from balances on deposit with the exchange which in turn makes trading on the market instantaneous, compared to some other Bitcoin markets where a subsequent settlement occurs manually between the trading partners. The disadvantage of this is that a third party must be trusted with keeping the money safe.

MtGox was originally started by Jed McCaleb in July 2010, and was sold to [[Tibanne Co.]] in Japan in March 2011. It is currently operated by Tibanne Co., managed by Mark Karpeles (MagicalTux).

==Trading==
===Buying and selling===

Buying and selling Bitcoins is simple. A buy order is executed partially or in full when the price bid can be matched against a sell order that is at or below the bid amount. A sell order is executed partially or in full when the price asked can be matched against a buy order that is at or above the ask amount. Orders that cannot be matched immediately remain in the orderbook.

Unfunded orders do not appear in the order book, but are automatically readded if a deposit is credited. For example, Mt. Gox allows the entry of a "buy" order even if the account has insufficient funds. If possible, Mt. Gox will execute a portion of the order if it can be partially funded. If a deposit is later credited and the deposit resolves the insufficient funds status of an outstanding order, the order will be immediately activated, and if possible, executed.

===Fees===

Mt. Gox charges a trading fee of up to 0.6% from each party of successful trades made through the market. The fee appears in the account history next to each trade. The trading fee is discounted for larger customers based on volume, which is calculated as a sliding window over the last 720 hours (30 days).

The fees are, by default, subtracted from the proceeds of each trade (e.g., a buy of 1.0 BTC will add to the account balance 0.994 BTC when the exchange fee is 0.6%). An account setting will allow fees to be added to the purchase amount instead (e.g., buying 1.0 BTC at $5 will cost about $5.03 when the exchange fee is 0.6%).

==Adding Funds==

===BTC===
There are no fees incurred when transferring bitcoins to a Mt. Gox account.

Funds are available once [[confirmation|confirmed]] (6 blocks)<ref>[http://www.bitcoin.org/smf/index.php?topic=3851.msg55220#msg55220 How long does it take to Deposit bitcoins to MtGox?]</ref>, a process that can take roughly an hour.

The deposit address is presented along with a QR code that can be scanned with a mobile. This address does not change with each deposit request.

The Add Bitcoins function experiences issues with some browser ad-blocking utilities even though no advertisements are displayed on the website.

====Redeemable Code====

Bitcoins from another Mt. Gox user sent by Mt. Gox [[redeemable code]] may be deposited and will be available for trading immediately.

===Dwolla===

Dwolla is among the fastest and least expensive methods for adding funds to a Mt. Gox account. The transaction fee on [[Dwolla]] is merely $0.25. The process is automated and the funds become available for trading within an hour<ref>[http://forum.bitcoin.org/index.php?topic=15107.msg205622#msg205622 Dwolla to Mt. Gox vs. Dwolla to TradeHill]</ref>.

===OKPay===

OKPay may be used for depositing funds to USD, EUR, GBP, CHF, and RUB<ref>[https://support.mtgox.com/entries/21034626-okpay OKPAY]</ref>.

===Cash Deposit===

====U.S. (USD)====
* BitInstant - Cash (U.S. dollars) may be deposited at any of thousands of banks, 7-11, Walmart, CVS, Moneygram and more that [[BitInstant]] uses to transfer funds to your Mt. Gox account.

====Brazil (BRL)====
* BitInstant - Cash (Brazilian real) may be deposited using Boleto or through Banco Recomendito.

====Brazil (BRL)====
* BitInstant - Cash (Russian rubles) may be deposited using QIWI or Cyberplat

====UK (GBP)====
* Barclays - Cash (British pound sterling) may be deposited at any Barclays location. There is a 1.5% fee on deposits made with this method<ref>[https://mtgox.com/press_release_20120806.html Introducing a new 1.5% fee on Barclays cash deposit]</ref>.

===Bank Wire===

====International USD====
Funds in USD may be wired to the exchange's bank in Japan. Each wire is subject to a per-wire fee plus any intermediate fees.

====International Wire====

An account can be configured with a wallet for each of the currencies that the exchange supports<ref>[https://mtgox.zendesk.com/entries/20413328-mt-gox-opens-15-new-currency-markets Mt.Gox Opens 15 New Currency Markets]</ref>. When a wire is received in one of these currencies, that account will be credited.

* USD - U.S. Dollar
* EUR - Euro (SEPA or Int'l wire)
* CAD - Canadian Dollar
* GBP - British Pound (Domestic or Int'l wire)
* CHF - Swiss Francs
* RUB - Russian Rubles
* AUD - Australian Dollars
* SEK - Swedish Krona
* DKK - Danish Krona
* HKD - Hong Kong Dollars
* PLN - Polish Zloty (Domestic or Int'l wire)
* CNY - Chinese Yuan
* SGD - Singapore Dollars
* TBH - Thai Baht
* NZD - New Zealand Dollars
* JPY - Japanese Yen (Domestic or Int'l wire)

====AurumXChange USD, EUR and CAD====

Funds may be wired to [[AurumXChange Company]] as USD, EUR or CAD (the latter two of which would then be exchanged into USD) for for purchase of a Mt. Gox USD [[redeemable code]] (voucher). Other digital currencies such as [[Liberty Reserve]] can be converted for transfer to Mt. Gox as well. The redeemable code provided is then used to load USD funds into an account with Mt. Gox.

===Direct Deposit===
====EU====

Funds in EUR may be added using SEPA Direct Debit for free, with funds convert to USD at the current ECB rate at the time the funds are received<ref>[http://www.bitcoin.org/smf/index.php?topic=5461.0 MTGox: Euro deposits]</ref>.

====U.S.====

Mt. Gox doesn't directly support an ACH-based (direct deposit) deposit method. Dwolla supports ACH-based fund transfers and those funds can then be deposited with Mt. Gox.

====UK====

Funds may be sent as a GBP direct deposit free of charge.

====Australia====

Funds may be sent using direct deposit (BPay) for a AU$2.00 per-deposit fee. The funds will be converted to USD at the current rate.

==Withdrawing Funds==

MtGox imposes a $1,000 USD limit for withdrawals per 24 hours and a $10,000 USD limit for withdrawals per month with most non-verified accounts. Bitcoins withdrawn are counted toward this limit as well and the USD value is calculated at the market rate at the time of the attempted withdrawal. Customers that have been Verified have higher limits and customers that have Trusted status have limits even higher<ref>[http://bitcoin.stackexchange.com/questions/2442/mtgox-trusted-vs-verified MtGox - trusted vs verified]</ref>. Any [[MtGox#Transfers_to_Other_Customers|account-to-account transfers]] made also count toward this limit as well.

Requests for higher withdrawal limits may be submitted by email
* For higher limits for withdrawal of USD funds, email: aml@mtgox.com
* For higher limits for withdrawal of BTC funds, email: btcupd@mtgox.com

See the [[MtGox#AML|AML]] section regarding verification levels for AML purposes.

===Dwolla===

[[Dwolla]] is among the fastest and least expensive methods for withdrawing USD funds from a Mt. Gox account. The transaction fee to do so is just $0.25.
[[Dwolla]] withdrawals are processed every hour during business hours (Japan time) and every 12 hours on weekends.

As of 25 May 2012, MtGox requires account holders to be "verified (level 1) - 'see below'" to withdraw via Dwolla. <ref>https://support.mtgox.com/entries/21503347-new-aml-policy-for-all-dwolla-users</ref>

The status of the withdrawal request will show one of the following status codes:

* Preparing: System is running checks to see if the transfer can be executed.
* Confirmed: Transfer can be executed and is pending in queue.
* Todo: Transfer is near the top of the queue and will be executed soon.
* Processed: Transfer has been processed.

===BTC===

Bitcoins may be withdrawn at no charge.

A [[green address]] option is available though this type of transaction could experience a delay if the exchange's wallet funding level for green address transactions is insufficient. The withdrawal form also offers an "open transaction" option which forces the transaction to go through the blockchain. If the recipient of a BTC withdrawal happens to also be from Mt. Gox's [[EWallet]], then that transfer would occur instantly and the transaction would not be broadcast to the Bitcoin network. This "open transaction" option forces a withdrawal to be broadcast to the Bitcoin network.

====Redeemable Code====

Bitcoins to another Mt. Gox account may be sent by Mt. Gox [[redeemable code]].

===Redeemable Code (Currency)===

Funds may be withdrawn by sending a Mt. Gox redeemable code (voucher) to another party.

The denominated of the code will be for the currency of the account's wallet that is active when the withdrawal request is inititiated (e.g., MTGUSD, MTGEUR, MTGAUD, MTGCAD, etc.)

Following are some of the services which accept a Mt. Gox redeemable code.

====AurumXChange USD, EUR and CAD====

Funds sent to [[AurumXChange Company]] can then be wired to a USD, EUR or CAD bank account or they can be converted to another digital currency, such as Liberty Reserve.

====BitInstant====

USD funds sent to to [[BitInstant]] can then be transferred further through their service.

===Direct Deposit===
====U.S.====

There is currently no option for withdrawing funds through a direct deposit bank transaction. Funds withdrawn to Dwolla may then, in turn, be withdrawn with bank funds deposited as an ACH transaction.

====EU====

You may withdraw any amount as a direct deposit to your bank. There is a 2% fee on these withdrawals. Contact the exchange by e-mail for this service.

====Australia====

A per-withdrawal fee (2,000 JPY) is subtracted and the remaining amount is sent via international wire in the chosen currency. If not AUD then an exchange fee of 2.5% will be charged.

===International Wire===

To any IBAN, SWIFT/BIC and ABA routable bank<ref>[http://www.facebook.com/MtGox/posts/343372689080478 Mt.Gox now offers international wire transfer to all US Banks]</ref>. Fee applies.

==Transfers to Other Customers==

Mt. Gox funds, either USD or BTC, may be sent to another Mt. Gox customer using a redeemable Mt. Gox code (voucher).

==Customer Service==

The preferred method for obtaining service is to place a request through the exchange's [https://mtgox.zendesk.com help desk]. Another method is to send e-mail with the request.

==Wallet/Banking==

An account at this exchange can be considered to be an [[eWallet]]. This service also offers [[:Category:ECommerce|eCommerce]] merchant [https://mtgox.com/merch/about payment services].

==Security Center==

The Security Center allows an account to be secured through the use of one or more One Time Password (OTP) solutions such as what YubiKey and Google Authenticator offer. Features can be protected where the OTP must be provided for each action and are configured independently.

For example, a typical configuration is to set OTP as being required for both withdrawals and security center changes but not for login. With that configuration, the worst damage that can happen from a compromised account or session would be that bitcoins would be bought or sold (though they could also be bought and sold over and over until funds are depleted).

* Login - The OTP must be provided for each login.
* Withdraw - The OTP must be provided for each withdrawal request.
* Security - The OTP must be provided during each configuration change to be performed.

==AML==

Varying degrees of verification will allow for greater per-day and per-month total amounts to be withdrawn<ref>[http://support.mtgox.com/entries/20919111-aml-account-statuses AML Account Statuses]</ref>.

===Unverified (Level 0)===

Designed for basic users, consumers and Bitcoin enthusiasts where 10,000 USD (monthly) is enough for most needs.

===Verified (Level 1)===

The "verified" status is designed for active traders and/or small companies.

===Trusted (Level 2)===

The “trusted” status is designed for day traders, professionals, and companies.

==API==

Mt Gox offers an [[MtGox/API|API]] which can be used to automate operations.

==Data Services==

===Web===
* Bitstock live watcher for trades, depth, history [http://bitstock.info bitstock.info] (Websockets browser required)
* [[Bitcoin Charts]]
* Clark Moody's [[Real Time Bitcoin Market Data]] including Ticker, Order Book and Time Sales (Websockets browser support required)
* [[MtGox Live]] (Websockets browser support required)
* [[Bitcoin Arbitrage Opportunities]] (Websockets browser support required)
* [[Bitcoin Prices]] market rates in multiple currencies

===Windows===
* [[Sierra Chart MtGox Bridge]] trading and charting tool.
* [[ToyTrader]] command line trading tool

===Mac OS X===
* [[BitTicker]] for Mac OS X
* [http://sneak.datavibe.net/20110613/mtgoxwatcher MtGox Watcher] for Mac OS X

===Mobile===
* [[BitcoinX]] mobile app with bid, ask and 24 hour history. For Android
* [[MtGox Live]] Bitcoin Trader with buy, sell, send, chart and depth for Android and iOS

=== firefox addon ===
* [https://github.com/joric/mtgox-ticker] firefox ticker addon

===Linux===
* [http://www.goxsh.info goxsh] command line ticker / depth chart
* [https://github.com/3M3RY/tulpenmanie tulpenmanie] graphical trading platform

==E-Commerce==

Online sellers can accept bitcoins for payment using the Mt. Gox's E-commerce Solution, which is an interface to the exchange's [[MtGox/API/HTTP/v1#Merchant_System|Merchant System API]].

==History==
The exchange went online on July 18, 2010.<ref>[http://www.bitcoin.org/smf/index.php?topic=444.0 MtGox announcement on forum]</ref>

On October 10, 2010 the exchange switched from [[PayPal]] to Liberty Reserve as the main funding option as a result of this attack. Former PayPal customers still had the possibility to withdraw their USD using alternative methods.

On March 6th, 2011 ownership of the exchange changed hands<ref>[http://www.bitcoin.org/smf/index.php?topic=4187.0 Mtgox is changing owners]</ref>. Tibanne publishes their [http://legal.tibanne.com/docs/20110801_company_certificate.pdf company certificate] from the Japanese government.

On June 19, 2011 the service experienced a significant security breach<ref>[https://support.mtgox.com/entries/20224998-huge-bitcoin-sell-off-due-to-a-compromised-account-rollback Huge Bitcoin sell off due to a compromised account - rollback]</ref>. The incident caused a selloff down to BTC/USD of $0.01 due to fraudulent trading. The site was disabled and all trading following the point that fraudulent trading began was rolled back. Complicating this breach was the release of a list of the exchange's accounts including username, email address and a password hash, which forced the exchange to implement an account recovery method for customers to regain control of their accounts.

In July, 2011 it was observed that the exchange no longer allows new registrations to occur without having a valid e-mail address.

On July 19, 2011 a press release announced that MtGox had acquired [[MtGox Live]].<ref>[https://mtgox.com/press_release_20110719.html World's Leading Bitcoin Exchange, Mt.Gox, acquires MtGoxLive.com]</ref>

Announced on March 6, 2012 was the Merchant Solution and API<ref>[https://mtgox.com/press_release_20120306.html Mt.Gox launches the definitive bitcoin checkout solution]</ref>

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]
* [[MtGox/API|API]]

==External Links==

* [https://mtgox.com MT. Gox exchange] website
* [https://mtgox.com/merch/about Mt. Gox Merchant Services]
* [https://mtgox.zendesk.com Customer Service Help Desk]

==References==
<references/>

[[Category:Exchanges]]
[[Category:eWallets]]
[[Category:Shopping Cart Interfaces]]
[[ru:MtGox]]

MtGox/API

2012-02-12T08:26:18Z

Emery: Added python example

The [[MtGox]] API provides methods to access information from the market, place orders, and more.

Two APIs are currently available: the HTTP API (available by posting to mtgox.com/code/*) and the websocket API.

==Number Formats==

In the "old API", currency- and amount-values (price, volume,...) were given as '''float'''. These values are likely being deprecated and replaced by fields of the same name with "_int" as suffix. These are '''fixed-decimal''', so you have to move the decimal point yourself (divide). The exponent differs based on the kind of the value.

In order to convert the '''int''' to a '''decimal''' you can...

{| class="wikitable"
|-
! kind of field !! ...divide by !! ...multiply by
|-
| BTC (volume, amount) || 1E8 (10,000,000) || 0.00000001
|-
| USD (price) || 1E5 (100,000) || 0.00001
|-
| JPY (price) || 1E3 (1,000) || 0.001
|}

Implementation advice: it's probably best to use '''int''' or '''Decimal''' (if your language/db offers such a type) in your clients. Using '''float''' will likely lead to nasty rounding problems.

== Currency Symbols ==
List of the currency symbols available with the API:

USD, AUD, CAD, CHF, CNY, DKK, EUR, GBP, HKD, JPY, NZD, PLN, RUB, SEK, SGD, THB

== HTTP API ==
This API is available in <nowiki>https://mtgox.com/api/*</nowiki>, and provides various informations. It also supports making an order, a withdraw, a deposit, etc. There is also a [https://rubygems.org/gems/mtgox Ruby gem] and [[Finance::MtGox|Perl module]] for interacting with the HTTP API.

=== Authentication ===

Authentication is performed by signing each request using HMAC-SHA512. The request must contain an extra value "nonce" which must be an always incrementing numeric value. A reference implementation is provided here:
<source lang="php">
<?php

function mtgox_query($path, array $req = array()) {
// API settings
$key = '';
$secret = '';

// generate a nonce as microtime, with as-string handling to avoid problems with 32bits systems
$mt = explode(' ', microtime());
$req['nonce'] = $mt[1].substr($mt[0], 2, 6);

// generate the POST data string
$post_data = http_build_query($req, '', '&');

// generate the extra headers
$headers = array(
'Rest-Key: '.$key,
'Rest-Sign: '.base64_encode(hash_hmac('sha512', $post_data, base64_decode($secret), true)),
);

// our curl handle (initialize if required)
static $ch = null;
if (is_null($ch)) {
$ch = curl_init();
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_USERAGENT, 'Mozilla/4.0 (compatible; MtGox PHP client; '.php_uname('s').'; PHP/'.phpversion().')');
}
curl_setopt($ch, CURLOPT_URL, 'https://mtgox.com/api/'.$path);
curl_setopt($ch, CURLOPT_POSTFIELDS, $post_data);
curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);

// run the query
$res = curl_exec($ch);
if ($res === false) throw new Exception('Could not get reply: '.curl_error($ch));
$dec = json_decode($res, true);
if (!$dec) throw new Exception('Invalid data received, please make sure connection is working and requested API exists');
return $dec;
}

// example 1: get infos about the account, plus the list of rights we have access to
var_dump(mtgox_query('0/info.php'));

// old api (get funds)
var_dump(mtgox_query('0/getFunds.php'));

// trade example
// var_dump(mtgox_query('0/buyBTC.php', array('amount' => 1, 'price' => 15)));
</source>

Python version here: https://bitcointalk.org/index.php?topic=49789.msg592388#msg592388

=== Cache ===

All of the API methods below have cached results, ticker, depth . . . have a 10 seconds cache .
No need to poll more often, you wont have more results, you could just be blocked by the prolexic anti ddos features.

=== Methods API version 0===

==== 0/data/getTrades.php ====
This allows retrieving all trades which happened in the last 24 hours. The returned data is cached and may not reflect latest activity.

Parameters:
* since: Passing a tid in "since" allows retrieving all trades since that trade. The passed id is may not exist. Ie. to get all trades from the very beginning one would just call https://mtgox.com/code/data/getTrades.php?since=0 . since returns only 100 trades, and you can call the method again by passing the latest trade you have imported in since.

* data is returned in standard json format like :
<source lang="php">
[
{"date":1279408157,
"price":"0.04951",
"amount":"20",
"price_int":"4951",
"amount_int":"2000000000",
"tid":"1",
"price_currency":"USD",
"item":"BTC",
"trade_type":""
"primary":"Y"
},
{"date":1279424586,"price":"0.05941","amount":"50.01","price_int":"5941","amount_int":"5001000000","tid":"2","price_currency":"USD","item":"BTC","trade_type":""}]
</source>

==== 0/getDepth.php ====
Get the current Market depth

https://mtgox.com/api/0/data/getDepth.php?Currency=PLN

https://mtgox.com/api/0/data/getDepth.php?Currency=AUD

https://mtgox.com/api/0/data/getDepth.php?Currency=USD

==== 0/getFunds.php ====
Get your current balance

https://mtgox.com/api/0/getFunds.php

getfunds is now deprecated since multi currency, please use info.php

==== 0/buyBTC.php ====
Place an order to Buy BTC

https://mtgox.com/api/0/buyBTC.php

POST data: amount=#&price=#&Currency=PLN

returns a list of your open orders

you can omit the price to do a market order

==== 0/sellBTC.php ====
Place an order to Sell BTC

https://mtgox.com/api/0/sellBTC.php

POST data: &amount=#&price=#&Currency=PLN

returns a list of your open orders

you can omit the price to do a market order

==== 0/getOrders.php ====
Fetch a list of your open Orders

https://mtgox.com/api/0/getOrders.php

oid: Order ID

type: 1 for sell order or 2 for buy order

status: 1 for active, 2 for not enough funds

==== 0/cancelOrder.php ====
Cancel an order

https://mtgox.com/api/0/cancelOrder.php

POST data: oid=#&type=#

oid: Order ID

type: 1 for sell order or 2 for buy order

==== 0/redeemCode.php ====
Used to redeem a mtgox coupon code

https://mtgox.com/api/0/redeemCode.php

* call with a post parameter "code" containing the code to redeem

* it will return an array with amount (float amount value of code), currency (3 letters, BTC or USD), reference (the transaction id), and status

==== 0/withdraw.php ====
withdraw / Send BTC

https://mtgox.com/api/0/withdraw.php

POST data: group1=BTC&btca=bitcoin_address_to_send_to&amount=#

* pass btca parameter to withdraw to a btc adress

* pass group1 for a coupon : BTC2CODE or USD2CODE

* pass group1=DWUSD&dwaccount=XXX-XXX-XXXX (no btca=xxxxxxx) for a dwolla withdraw

* pass green=1 to use the new greenaddress feature ( see [[GreenAddress]] )
* return code and status if successful

To make a withdraw in another Currency , use group1=USD2CODE and add a Currency parameter ( example Currency=EUR to get a mtgox EUR coupon )

==== 0/btcAddress.php ====
get a bitcoin deposit adress for your account

https://mtgox.com/api/0/btcAddress.php

* pass POST data "description" to add a description that will appear in your history when this BTC address receive a deposit

*pass POST data "ipn" to add an url that mtgox will ping whenever this new address receive funds
description ( see above ) is also required for ipn to work

* returns a bitcoin deposit address

==== 0/history_[CUR].csv ====

Allows downloading your activity history for a given currency (BTC or USD for now).

https://mtgox.com/api/0/history_BTC.csv

https://mtgox.com/api/0/history_USD.csv

encoding is utf-8

==== 0/info.php ====

https://mtgox.com/api/0/info.php

returns info about your account, funds, fees, API privileges, withdraw limits . . .

==== 0/ticker ====

http://mtgox.com/api/0/data/ticker.php

returns the current ticker :

<source lang="php">
{"ticker":
{
"high":5.70653,
"low":5.4145,
"avg":5.561388723,
"vwap":5.610932845,
"vol":55698,
"last":5.56915,
"buy":5.51326,
"sell":5.5672
}
}
</source>

the time frame for high, low, vol, avg, vwap . . . is sliding 24 hours

what is vwap ?

please see http://en.wikipedia.org/wiki/VWAP

=== API version 0 examples ===

==== all api shell type CLI ====

python : http://www.goxsh.info/

perl : http://pastebin.com/vEpgw5nW

==== other ====

https : http://stackoverflow.com/questions/7046370/https-request-with-boost-asio-and-openssl

https://github.com/sje397/mtgox-plasmoid

module perl : http://search.cpan.org/~mndrix/Finance-MtGox-0.02/

==== gather data ====

https://github.com/Lexiks/MyBitBoard

==== gettrade ====

bash : https://bitcointalk.org/index.php?topic=39402.0

perl : http://pastebin.com/raw.php?i=pmhMXZJu

==== ticker ====

http://pastebin.com/pd0ZR4WY

=== Methods API version 1===

==== Multi Currency Ticker ====

https://mtgox.com/api/1/BTCUSD/public/ticker
https://mtgox.com/api/1/BTCEUR/public/ticker

returns the current ticker for the selected currency :

<source lang="php">
{
"result":"success",
"return":
{
"high": {"value":"5.70653","value_int":"570653","display":"$5.70653","currency":"USD"},
"low": {"value":"5.4145","value_int":"541450","display":"$5.41450","currency":"USD"},
"avg": {"value":"5.561119626","value_int":"556112","display":"$5.56112","currency":"USD"},
"vwap": {"value":"5.610480461","value_int":"561048","display":"$5.61048","currency":"USD"},
"vol":
{
"value":"55829.58960346",
"value_int":"5582958960346",
"display":"55,829.58960346\u00a0BTC",
"currency":"BTC"
},
"last_local":{"value":"5.5594","value_int":"555940","display":"$5.55940","currency":"USD"},
"last_orig":{"value":"5.5594","value_int":"555940","display":"$5.55940","currency":"USD"},
"last":{"value":"5.5594","value_int":"555940","display":"$5.55940","currency":"USD"},
"buy":{"value":"5.53587","value_int":"553587","display":"$5.53587","currency":"USD"},
"sell":{"value":"5.56031","value_int":"556031","display":"$5.56031","currency":"USD"}
}
</source>

note : last_local include only the last trade in the selected currency, last_orig include data of the original last trade ( currency,price in currency . . . ),last can be a conversion of the last trde in another currency

==== Multi Currency depth ====

https://mtgox.com/api/1/BTCPLN/public/depth?raw

https://mtgox.com/api/1/BTCAUD/public/depth?raw

==== Multi currency trades ====

https://mtgox.com/api/1/BTCPLN/public/trades?raw

https://mtgox.com/api/1/BTCAUD/public/trades?raw

to get only the trades since a given trade id, you can add the parameter since=<trade_id>

https://mtgox.com/api/1/BTCUSD/public/trades?since=0

https://mtgox.com/api/1/BTCEUR/public/trades?since=1316312781670700

For multi currency,also returns the primary value,"Y" or "N", the primary currency is always the buyers currency

A trade can appear in more than one currency, to ignore duplicates, use only the trades having primary =Y

example of returned data :
<source lang="php">
{"date":1316312781,
"price":"3.5599",
"amount":"3.6900096",
"price_int":"355990",
"amount_int":"369000960",
"tid":"1316312781670700",
"price_currency":"EUR",
"item":"BTC",
"trade_type":"bid",
"primary":"Y",
"properties":"limit,mixed_currency"
}
</source>

==== Cancelled Trades ====

https://mtgox.com/api/1/BTCUSD/public/cancelledtrades

returns a list of all the cancelled trades this last month, list of trade ids in json format .

==== Full Depth ====

https://mtgox.com/api/1/BTCUSD/public/fulldepth

returns full depth

==== Private info ====

https://mtgox.com/api/1/generic/private/info

returns information about your account, funds, fees, API privileges, withdraw limits . . .

==== Your open orders ====

https://mtgox.com/api/1/generic/private/orders

returns information about your current open orders

==== Submit an order ====

https://mtgox.com/api/1/BTCUSD/private/order/add

parameters:
* type (bid|ask)
* amount_int <amount as int>
* price_int <price as int> (can be omitted to place market order)

submits an order and returns info about success or error

==== Currency information ====

https://mtgox.com/api/1/generic/public/currency

pass parameter ?currency=<currency_symbol>

returns information about a currency ( number of decimals . . . )

==== HOTP key ====

https://mtgox.com/api/1/generic/public/hotp_gen

used to generate a new HOTP key ( useful for developpers )

== Streaming API ==
Real time streaming data may be obtained over the streaming API, implemented in [http://socket.io/ Socket.io]<ref>Socket.io forum announcement by MagicalTux: https://bitcointalk.org/index.php?topic=14412.msg613271#msg613271</ref>. The original WebSocket API<ref>Original WebSocket thread: https://bitcointalk.org/index.php?topic=5855.msg86219</ref> is deprecated as of 11-Nov-2011.

===Connecting===
The following JavaScript code establishes a connection in the browser:
<source lang="javascript">
<script src="https://socketio.mtgox.com/socket.io/socket.io.js"></script>
<script>
var conn = io.connect('https://socketio.mtgox.com/mtgox');
conn.on('message', function(data) {
// Handle incoming data object.
});
</script>
</source>

The session ID expires after 30 seconds

===Handling Events===
Socket.io exposes a simple interface for handling events. Handling <tt>message</tt> events is shown above, but there are other events that may be handled:
<source lang="javascript">
conn.on('connect', onConnect);
conn.on('disconnect', onDisconnect);
conn.on('error', onError);
conn.on('message', onMessage);
</source>

===Incoming Data===
Data arrives as a full object instead of as JSON text, eliminating the need to parse the data in the JavaScript handler. Messages that come across the socket to trigger the <tt>message</tt> event will contain the following minimum components:
<source lang="javascript">
{
"op":<OPERATION_TYPE>
}
</source>

The <tt>OPERATION_TYPE</tt> field may take these values:

:{| class="wikitable"
|-
! OPERATION_TYPE !! Description
|-
| subscribe || Notification that the user is subscribed to a channel
|-
| unsubscribe || Messages will no longer arrive over the channel
|-
| remark || A server message, usually a warning
|-
| private || The operation for depth, trade, and ticker messages
|}

===op:subscribe and op:unsubscribe===
The subscribe and unsubscribe message data are very simple, containing the channel and the operation.
<source lang="javascript">
{
"channel":<CHANNEL_ID>,
"op":"subscribe" OR "unsubscribe"
}
</source>

Some of the channels are:

:{| class="wikitable"
|-
! Channel ID !! Description
|-
| dbf1dee9-4f2e-4a08-8cb7-748919a71b21 || Trades
|-
| d5f06780-30a8-4a48-a2f8-7ed181b4a13f || Ticker
|-
| 24e67e0d-1cad-4cc0-9e7a-f8523ef460fe || Depth
|}

===op:remark===
The remark operation contains message and success fields.
<source lang="javascript">
{
"op":"remark",
"message":<MESSAGE FROM THE SERVER>,
"success":<boolean>
}
</source>

===op:private===
The payloads of the <tt>op:private</tt> messages contain the real time market information. Each message follows this form:

<source lang="javascript">
{
"channel":<CHANNEL_ID>,
"op":"private",
"private":<MESSAGE_TYPE>,
<MESSAGE_TYPE>:<DATA_PAYLOAD>
}
</source>

The <tt>MESSAGE_TYPE</tt> field may take the values:

:{| class="wikitable"
|-
! MESSAGE_TYPE !! Description
|-
| ticker || Ticker messages
|-
| trade || Trades, as they occur
|-
| depth || Orders placed or removed
|}

====Ticker====
Ticker messages contain the current inside Bid and Ask as well as daily highs, lows, and volume. The fields contained in the ticker match those defined in the version 1.0 API above. All fields contain <tt>currency</tt>, <tt>display</tt>, <tt>value</tt>, and <tt>value_int</tt> entries.
<source lang="javascript">
{
"channel":"d5f06780-30a8-4a48-a2f8-7ed181b4a13f",
"op":"private",
"origin":"broadcast",
"private":"ticker",
"ticker":{
"avg":{
"currency":"USD",
"display":"$2.26847",
"value":"2.26847",
"value_int":"226847"
},
"buy":{...},
"high":{...},
"last":{..},
"last_local":{...},
"last_orig":{...},
"low":{...},
"sell":{...},
"vol":{
"currency":"BTC",
"display":"118,696.02104208",
"value":"118696.02104208",
"value_int":"11869602104208"
},
"vwap":{...}
}
}
</source>

====Trade====
<source lang="javascript">{
"channel":"dbf1dee9-4f2e-4a08-8cb7-748919a71b21",
"op":"private",
"origin":"broadcast",
"private":"trade",
"trade":{
"amount":2.71,
"amount_int":"271000000",
"date":1310279340,
"item":"BTC",
"price":14.43,
"price_currency":"USD",
"price_int":"1443000",
"primary":"Y",
"properties":"limit, mixed_currency",
"tid":"1310279340877902",
"trade_type":"bid",
"type":"trade"
}
}
</source>

'''trade''' contains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || the traded amount in item (BTC), float, deprecated
|-
| amount_int || the traded amount * 1E8
|-
| date || unix timestamp of trade
|-
| item || What was this trade about
|-
| price || price per unit, float, deprecated
|-
| price_int || price in smallest unit as integer (5 decimals of USD, 3 in case of JPY)
|-
| price_currency || currency in which trade was completed
|-
| tid || Trade id (big integer, which is in fact trade timestamp in microseconds)
|-
| trade_type || Did this trade result from the execution of a bid or a ask?
|-
|}

====Depth====

Changes to the market depth data are broadcast so an up-to-date market depth can be kept by clients.

<source lang="javascript">{
"channel":"24e67e0d-1cad-4cc0-9e7a-f8523ef460fe",
"depth":{
"currency":"USD",
"item":"BTC",
"now":"1323644358437819",
"price":"14.43",
"price_int":"1443000",
"total_volume_int":"849766000",
"type":1,
"type_str":"ask",
"volume":"-2.71",
"volume_int":"-271000000"
},
"op":"private",
"origin":"broadcast",
"private":"depth"
}</source>

'''depth''' contains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| currency || the currency affected
|-
| item || the item (BTC)
|-
| price || price as a float, deprecated
|-
| price_int || the price at which volume change happened (5 decimal for USD, 3 for JPY)
|-
| type || 1=ask, 2=bid. deprecated, use type_str
|-
| type_str || type of order at this depth, either "ask" or "bid"
|-
| volume || the volume change as float, deprecated
|-
| volume_int || volume change * 1E8

|}

=== Outgoing commands===
==== Direct commands ====

Commands that can be sent without authentication

===== unsubscribe =====
Stop receiving messages from a channel

<source lang="javascript">{
"op":"unsubscribe",
"channel":<CHANNEL ID>
}</source>

Responds with an identical message to confirm
===== mtgox.subscribe =====
Subscribe to a channel to start receiving messages from it.

<source lang="javascript">{
"op": "mtgox.subscribe",
"type": "ticker"
}</source>
"type" can be ticker, trades, or depth.

==== Authenticated commands ====

These commands require an API key and secret pair to sign requests. Any of the "version 1" requests from the HTTP API can be called.

<source lang="javascript">{
"op":"call",
"id":<REQUEST ID>,
"call":<BASE-64 ENCODED SIGNED REQUEST>,
"context":"mtgox.com"
}</source>

<REQUEST ID> can be any string, it's used to identify the response as belonging to this request when an answer comes back. md5'ing your nonce is a good way to get an id.

"call" must be a base-64 encoded string consisting of, in order: an API key, a signed copy of the response, and the response text itself.

The queries themselves look like:
<source lang="javascript">{
"id":<REQUEST ID>,
"call":<HTTP API ENDPOINT>,
"nonce":<REQUEST NONCE>,
"params":<REQUEST PARAMETERS>,
"item":"BTC"
}</source>

<HTTP API ENDPOINT> is the last two path components of any version 1 API endpoint, for example [[#Private_info|private/info]], or [[#Cancelled_Trades|public/cancelledtrades]].

<REQUEST PARAMETERS> is optional for any request that doesn't have parameters.

The signing process is similar to the HTTP API, but because we can't send headers in an open websocket, the API key and signed request are simply prepended to the actual query data and base64 encoded. Reference implementations are available at https://github.com/MtGox/websocket

Here's a sample of how to create a valid request in PHP 5.3:
<source lang="php">$nonce = explode(' ', microtime(false));
$nonce = $nonce[1].substr($nonce[0], 2, 6);
$id = md5($nonce); // id can be anything to recognize this call
$query = array('call' => $call, 'params' => $params, 'item' => $item, 'currency' => $currency, 'id' => $id, 'nonce' => $nonce);
$query = json_encode($query);
// generate signature
$sign = hash_hmac('sha512', $query, base64_decode($apiSecret), true);
// prefix signature to query
$query = pack('H*', str_replace('-','',$apiKey)).$sign.$query;
// send query
$call = array('op' => 'call', 'call' => base64_encode($query), 'id' => $id, 'context' => 'mtgox.com');
// $call can now be pushed out to the websocket</source>

=== examples ===

==== ticker ====
javascript, using hookio :

http://www.youtube.com/watch?v=KD5ljtNK72U

http://github.com/hookio

http://github.com/cronopio/hook.io-mtgox

Another node.js project, using plain websockets (largely based on cronopio's work) :

https://github.com/dlanod/node-mtgox-websocket-client

A python example :
https://github.com/3M3RY/python-mtgox

==== arbitrage ====
https://github.com/goteppo/ArBit

==== websocket ====
https://github.com/cronopio/hook.io-ws

https://github.com/dlanod/node-mtgox-websocket-client

== References ==
<references></references>

Protocol documentation

2012-02-03T18:12:45Z

Emery: added getwork note.

Sources:
* [[Original Bitcoin client]] source

Type names used in this documentation are from the C99 standard.

For protocol used in mining, see [[Getwork]].

==Common standards==

=== Hashes ===

Usually, when a hash is computed within bitcoin, it is computed twice. Most of the time [http://en.wikipedia.org/wiki/SHA-2 SHA-256] hashes are used, however [http://en.wikipedia.org/wiki/RIPEMD RIPEMD-160] is also used when a shorter hash is desirable (for example when creating a bitcoin address).

Example of double-SHA-256 encoding of string "hello":

hello
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 (first round of sha-256)
9595c9df90075148eb06860365df33584b75bff782a510c6cd4883a419833d50 (second round of sha-256)

For bitcoin addresses (RIPEMD-160) this would give:

hello
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 (first round is sha-256)
b6a9c8c230722b7c748331a8b450f05566dc7d0f (with ripemd-160)

=== Merkle Trees ===

Merkle trees are binary trees of hashes. Merkle trees in bitcoin use '''Double''' SHA-256, and are built up as so:

hash(a) = sha256(sha256(a))

hash(a) hash(b) hash(c)
hash(hash(a)+hash(b)) hash(hash(c)+hash(c))
hash(hash(hash(a)+hash(b))+hash(hash(c)+hash(c)))

They are paired up, with the last element being _duplicated_.

Note: Hashes in Merkle Tree displayed in the [[Block Explorer]] are of little-endian notation. For some implementations and [http://www.fileformat.info/tool/hash.htm calculations], the bits need to be reversed before they are hashed, and again after the hashing operation.

=== Signatures ===

Bitcoin uses [http://en.wikipedia.org/wiki/Elliptic_curve_cryptography Elliptic Curve] [http://en.wikipedia.org/wiki/Digital_Signature_Algorithm Digital Signature Algorithm] ([http://en.wikipedia.org/wiki/Elliptic_Curve_DSA ECDSA]) to sign transactions.

For ECDSA the secp256k1 curve from http://www.secg.org/collateral/sec2_final.pdf is used.

Public keys (in scripts) are given as 04 <x> <y> where ''x'' and ''y'' are 32 byte big-endian integers representing the coordinates of a point on the curve or in compressed form given as <sign> <x> where <sign> is 0x02 if ''y'' is even and 0x03 if ''y'' is odd. Signatures use [http://en.wikipedia.org/wiki/Distinguished_Encoding_Rules DER encoding] to pack the ''r'' and ''s'' components into a single byte stream (this is also what OpenSSL produces by default).

=== Transaction Verification ===
Transactions are cryptographically signed records that reassign ownership of Bitcoins to new addresses. Transactions have ''inputs'' - records which reference the funds from other previous transactions - and ''outputs'' - records which determine the new owner of the transferred Bitcoins, and which will be referenced as inputs in future transactions as those funds are respent.

Each ''input'' must have a cryptographic digital signature that unlocks the funds from the prior transaction. Only the person possessing the appropriate [[private key]] is able to create a satisfactory signature; this in effect ensures that funds can only be spent by their owners.

Each ''output'' determines which Bitcoin address (or other criteria, see [[Scripting]]) is the recipient of the funds.

In a transaction, the sum of all inputs must be equal to or greater than the sum of all outputs. If the inputs exceed the outputs, the difference is considered a [[transaction fee]], and is redeemable by whoever first includes the transaction into the block chain.

A special kind of transaction, called a [[coinbase transaction]], has no inputs. It is created by [[miners]], and there is one coinbase transaction per block. Because each block comes with a reward of newly created Bitcoins (e.g. 50 BTC for the first 210,000 blocks), the first transaction of a block is, with few exceptions, the transaction that grants those coins to their recipient (the miner). In addition to the newly created Bitcoins, the coinbase transaction is also used for assigning the recipient of any transaction fees that were paid within the other transactions being included in the same block. The coinbase transaction can assign the entire reward to a single Bitcoin address, or split it in portions among multiple addresses, just like any other transaction. Coinbase transactions always contain outputs totaling the sum of the block reward plus all transaction fees collected from the other transactions in the same block.

Most Bitcoin outputs encumber the newly transferred coins with a single ECDSA private key. The actual record saved with inputs and outputs isn't necessarily a key, but a ''script''. Bitcoin uses an interpreted scripting system to determine whether an output's criteria have been satisfied, with which more complex operations are possible, such as outputs that require two ECDSA signatures, or two-of-three-signature schemes. An output that references a single Bitcoin address is a ''typical'' output; an output actually contains this information in the form of a script that requires a single ECDSA signature (see [[OP_CHECKSIG]]). The output script specifies what must be provided to unlock the funds later, and when the time comes in the future to spend the transaction in another input, that input must provide all of the thing(s) that satisfy the requirements defined by the original output script.

=== Addresses ===

A bitcoin address is in fact the hash of a ECDSA public key, computed this way:

Version = 1 byte of 0 (zero); on the test network, this is 1 byte of 111
Key hash = Version concatenated with RIPEMD-160(SHA-256(public key))
Checksum = 1st 4 bytes of SHA-256(SHA-256(Key hash))
Bitcoin Address = Base58Encode(Key hash concatenated with Checksum)

The Base58 encoding used is home made, and has some differences. Especially, leading zeroes are kept as single zeroes when conversion happens.

== Common structures ==

Almost all integers are encoded in little endian. Only IP or port number are encoded big endian.

=== Message structure ===

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || magic || uint32_t || Magic value indicating message origin network, and used to seek to next message when stream state is unknown
|-
| 12 || command || char[12] || ASCII string identifying the packet content, NULL padded (non-NULL padding results in packet rejected)
|-
| 4 || length || uint32_t || Length of payload in number of bytes
|-
| 4 || checksum || uint32_t || First 4 bytes of sha256(sha256(payload)) (not included in version or verack)
|-
| ? || payload || uchar[] || The actual data
|}

Before 20 February 2012, the version and verack messages do not have a checksum; the payload starts 4 bytes earlier. On and after 20 February 2012, all messages have checksums.

Known magic values:

{|class="wikitable"
! Network !! Magic value !! Sent over wire as
|-
| main || 0xD9B4BEF9 || F9 BE B4 D9
|-
| testnet || 0xDAB5BFFA || FA BF B5 DA
|}

=== Variable length integer ===

Integer can be encoded depending on the represented value to save space. Variable length integers always precede an array/vector of a type of data that may vary in length.

{|class="wikitable"
! Value !! Storage length !! Format
|-
| < 0xfd || 1 || uint8_t
|-
| <= 0xffff || 3 || 0xfd followed by the length as uint16_t
|-
| <= 0xffffffff || 5 || 0xfe followed by the length as uint32_t
|-
| - || 9 || 0xff followed by the length as uint64_t
|}

=== Variable length string ===

Variable length string can be stored using a variable length integer followed by the string itself.

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || length || [[Protocol_specification#Variable_length_integer|var_int]] || Length of the string
|-
| ? || string || char[] || The string itself (can be empty)
|}

=== Network address ===

When a network address is needed somewhere, this structure is used. This protocol and structure supports IPv6, '''but note that the original client currently only supports IPv4 networking'''. Network addresses are not prefixed with a timestamp in the version message.

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || time || uint32 || the Time (version >= 31402)
|-
| 8 || services || uint64_t || same service(s) listed in [[#version|version]]
|-
| 16 || IPv6/4 || char[16] || IPv6 address. Network byte order. The original client only supports IPv4 and only reads the last 4 bytes to get the IPv4 address. However, the IPv4 address is written into the message as a 16 byte [http://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses IPv4-mapped IPv6 address]
(12 bytes ''00 00 00 00 00 00 00 00 00 00 FF FF'', followed by the 4 bytes of the IPv4 address).
|-
| 2 || port || uint16_t || port number, network byte order
|}

Hexdump example of Network address structure

<pre>
0000 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0010 00 00 FF FF 0A 00 00 01 20 8D ........ .

Network address:
01 00 00 00 00 00 00 00 - 1 (NODE_NETWORK: see services listed under version command)
00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 01 - IPv6: ::ffff:10.0.0.1 or IPv4: 10.0.0.1
20 8D - Port 8333
</pre>

=== Inventory Vectors ===

Inventory vectors are used for notifying other nodes about objects they have or data which is being requested.

Inventory vectors consist of the following data format:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || type || uint32_t || Identifies the object type linked to this inventory
|-
| 32 || hash || char[32] || Hash of the object
|}

The object type is currently defined as one of the following possibilities:

{|class="wikitable"
! Value !! Name !! Description
|-
| 0 || ERROR || Any data of with this number may be ignored
|-
| 1 || MSG_TX || Hash is related to a transaction
|-
| 2 || MSG_BLOCK || Hash is related to a data block
|}

Other Data Type values are considered reserved for future implementations.

=== Block Headers ===

Block headers are sent in a headers packet in response to a getheaders message.

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || Block version information, based upon the software version creating this block
|-
| 32 || prev_block || char[32] || The hash value of the previous block this particular block references
|-
| 32 || merkle_root || char[32] || The reference to a Merkle tree collection which is a hash of all transactions related to this block
|-
| 4 || timestamp || uint32_t || A timestamp recording when this block was created (Limited to 2106!)
|-
| 4 || bits || uint32_t || The calculated difficulty target being used for this block
|-
| 4 || nonce || uint32_t || The nonce used to generate this block… to allow variations of the header and compute different hashes
|-
| 1 || txn_count || uint8_t || Number of transaction entries, this value is always 0
|}

== Message types ==

=== version ===

When a node creates an outgoing connection, it will immediately advertise its version. The remote node will respond with its version. No futher communication is possible until both peers have exchanged their version.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || int32_t || Identifies protocol version being used by the node
|-
| 8 || services || uint64_t || bitfield of features to be enabled for this connection
|-
| 8 || timestamp || int64_t || standard UNIX timestamp in seconds
|-
| 26 || addr_recv || net_addr || The network address of the node receiving this message
|-
|colspan="4"| version >= 106
|-
| 26 || addr_from || net_addr || The network address of the node emitting this message
|-
| 8 || nonce || uint64_t || Node random nonce, randomly generated every time a version packet is sent. This nonce is used to detect connections to self.
|-
| ? || user_agent || [[#Variable length string|var_str]] || [[BIP_0014|User Agent]] (0x00 if string is 0 bytes long)
|-
|colspan="4"| version >= 209
|-
| 4 || start_height || int32_t || The last block received by the emitting node
|}

If the emitter of the packet has version >= 209, a "verack" packet shall be sent if the version packet was accepted.

The following services are currently assigned:

{|class="wikitable"
! Value !! Name !! Description
|-
| 1 || NODE_NETWORK || This node can be asked for full blocks instead of just headers.
|}

Hexdump example of version message (note the message header for this version message does not have a checksum):
<pre>
0000 F9 BE B4 D9 76 65 72 73 69 6F 6E 00 00 00 00 00 ....version.....
0010 55 00 00 00 9C 7C 00 00 01 00 00 00 00 00 00 00 U....|..........
0020 E6 15 10 4D 00 00 00 00 01 00 00 00 00 00 00 00 ...M............
0030 00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 01 ................
0040 20 8D 01 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 00 FF FF 0A 00 00 02 20 8D DD 9D 20 2C .......... ... ,
0060 3A B4 57 13 00 55 81 01 00 :.W..U...

Message header:
F9 BE B4 D9 - Main network magic bytes
76 65 72 73 69 6F 6E 00 00 00 00 00 - "version" command
55 00 00 00 - Payload is 85 bytes long
- No checksum in version message until 20 February 2012. See https://bitcointalk.org/index.php?topic=55852.0
Version message:
9C 7C 00 00 - 31900 (version 0.3.19)
01 00 00 00 00 00 00 00 - 1 (NODE_NETWORK services)
E6 15 10 4D 00 00 00 00 - Mon Dec 20 21:50:14 EST 2010
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 01 20 8D - Recipient address info - see Network Address
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 02 20 8D - Sender address info - see Network Address
DD 9D 20 2C 3A B4 57 13 - Node random unique ID
00 - "" sub-version string (string is 0 bytes long)
55 81 01 00 - Last block sending node has is block #98645
</pre>

=== verack ===

The ''verack'' message is sent in reply to ''version'' for clients >= 209. This message consists of only a [[#Message structure|message header]] with the command string "verack".

Hexdump of the verack message:

<pre>
0000 F9 BE B4 D9 76 65 72 61 63 6B 00 00 00 00 00 00 ....verack......
0010 00 00 00 00 ....

Message header:
F9 BE B4 D9 - Main network magic bytes
76 65 72 61 63 6B 00 00 00 00 00 00 - "verack" command
00 00 00 00 - Payload is 0 bytes long
</pre>

=== addr ===

Provide information on known nodes of the network. Non-advertised nodes should be forgotten after typically 3 hours

Payload (maximum payload length: 1000 bytes):

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 1+ || count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of address entries
|-
| 30x? || addr_list || (uint32_t + net_addr)[] || Address of other nodes on the network. version < 209 will only read the first one. The uint32_t is a timestamp (see note below).
|}

'''Note''': Starting version 31402, addresses are prefixed with a timestamp. If no timestamp is present, the addresses should not be relayed to other peers, unless it is indeed confirmed they are up.

Hexdump example of ''addr'' message:
<pre>
0000 F9 BE B4 D9 61 64 64 72 00 00 00 00 00 00 00 00 ....addr........
0010 1F 00 00 00 ED 52 39 9B 01 E2 15 10 4D 01 00 00 .....R9.....M...
0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF ................
0030 FF 0A 00 00 01 20 8D ..... .

Message Header:
F9 BE B4 D9 - Main network magic bytes
61 64 64 72 00 00 00 00 00 00 00 00 - "addr"
1F 00 00 00 - payload is 31 bytes long
ED 52 39 9B - checksum of payload

Payload:
01 - 1 address in this message

Address:
E2 15 10 4D - Mon Dec 20 21:50:10 EST 2010 (only when version is >= 31402)
01 00 00 00 00 00 00 00 - 1 (NODE_NETWORK service - see version message)
00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 01 - IPv4: 10.0.0.1, IPv6: ::ffff:10.0.0.1 (IPv4-mapped IPv6 address)
20 8D - port 8333
</pre>

=== inv ===

Allows a node to advertise its knowledge of one or more objects. It can be received unsolicited, or in reply to ''getblocks''.

Payload (maximum payload length: 50000 bytes):

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of inventory entries
|-
| 36x? || inventory || [[Protocol specification#Inventory Vectors|inv_vect]][] || Inventory vectors
|}

=== getdata ===

getdata is used in response to inv, to retrieve the content of a specific object, and is usually sent after receiving an ''inv'' packet, after filtering known elements.

Payload (maximum payload length: 50000 bytes):

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of inventory entries
|-
| 36x? || inventory || [[Protocol specification#Inventory Vectors|inv_vect]][] || Inventory vectors
|}

=== getblocks ===

Return an ''inv'' packet containing the list of blocks starting right after the last known (and correct) hash in the block locator object, up to hash_stop or 500 blocks, whichever comes first. To receive the next blocks hashes, one needs to issue getblocks again with a new block locator object.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || the protocol version
|-
| 1+ || hash count || [[Protocol_specification#Variable_length_integer|var_int]] || number of block locator hash entries
|-
| 32+ || block locator hashes || char[32] || block locator object; newest back to genesis block (dense to start, but then sparse)
|-
| 32 || hash_stop || char[32] || hash of the last desired block; set to zero to get as many blocks as possible (500)
|}

To create the block locator hashes, keep pushing hashes until you go back to the genesis block. After pushing 10 hashes back, the step backwards doubles every loop:

<pre>
// From libbitcoin which is under AGPL
std::vector<size_t> block_locator_indices(int top_depth)
{
// Start at max_depth
std::vector<size_t> indices;
// Push last 10 indices first
size_t step = 1, start = 0;
for (int i = top_depth; i > 0; i -= step, ++start)
{
if (start >= 10)
step *= 2;
indices.push_back(i);
}
indices.push_back(0);
return indices;
}
</pre>

Note that it is allowed to send in fewer known hashes down to a minimum of just one hash. However, the purpose of the block locator object is to detect a wrong branch in the caller's main chain. If the peer detects that you are off the main chain, it will send in block hashes which are earlier than your last known block. So if you just send in your last known hash and it is off the main chain, the peer starts over at block #1.

=== getheaders ===

Return a ''headers'' packet containing the headers of blocks starting right after the last known (and correct) hash in the block locator object, up to hash_stop or 2000 blocks, whichever comes first. To receive the next block headers, one needs to issue getheaders again with a new block locator object. The ''getheaders'' command is used by thin clients to quickly download the blockchain where the contents of the transactions would be irrelevant (because they are not ours).

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || the protocol version
|-
| 1+ || hash count || [[Protocol_specification#Variable_length_integer|var_int]] || number of block locator hash entries
|-
| 32+ || block locator hashes || char[32] || block locator object; newest back to genesis block (dense to start, but then sparse)
|-
| 32 || hash_stop || char[32] || hash of the last desired block header; set to zero to get as many blocks as possible (2000)
|}

For the block locator object in this packet, the same rules apply as for the [[Protocol_specification#Variable_length_integer|getblocks]] packet.

=== tx ===

''tx'' describes a bitcoin transaction, in reply to ''getdata''

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || Transaction data format version
|-
| 1+ || tx_in count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of Transaction inputs
|-
| 41+ || tx_in || tx_in[] || A list of 1 or more transaction inputs or sources for coins
|-
| 1+ || tx_out count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of Transaction outputs
|-
| 8+ || tx_out || tx_out[] || A list of 1 or more transaction outputs or destinations for coins
|-
| 4 || lock_time || uint32_t || The block number or timestamp at which this transaction is locked:
{|class="wikitable"
! Value !! Description
|-
| 0 || Always locked
|-
| < 500000000 || Block number at which this transaction is locked
|-
| >= 500000000 || UNIX timestamp at which this transaction is locked
|}
A non-locked transaction must not be included in blocks, and it can be modified by broadcasting a new version before the time has expired (replacement is currently disabled in Bitcoin, however, so this is useless).

|}

TxIn consists of the following fields:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 36 || previous_output || outpoint || The previous output transaction reference, as an OutPoint structure
|-
| 1+ || script length || [[Protocol_specification#Variable_length_integer|var_int]] || The length of the signature script
|-
| ? || signature script || uchar[] || Computational Script for confirming transaction authorization
|-
| 4 || [http://bitcoin.stackexchange.com/q/2025/323 sequence] || uint32_t || Transaction version as defined by the sender. Intended for "replacement" of transactions when information is updated before inclusion into a block.
|}

The OutPoint structure consists of the following fields:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 32 || hash || char[32] || The hash of the referenced transaction.
|-
| 4 || index || uint32_t || The index of the specific output in the transaction. The first output is 0, etc.
|}

The Script structure consists of a series of pieces of information and operations related to the value of the transaction.

(Structure to be expanded in the future… see script.h and script.cpp and [[Script]] for more information)

The TxOut structure consists of the following fields:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 8 || value || uint64_t || Transaction Value
|-
| 1+ || pk_script length || [[Protocol_specification#Variable_length_integer|var_int]] || Length of the pk_script
|-
| ? || pk_script || uchar[] || Usually contains the public key as a Bitcoin script setting up conditions to claim this output.
|}

Example ''tx'' message:
<pre>
000000 F9 BE B4 D9 74 78 00 00 00 00 00 00 00 00 00 00 ....tx..........
000010 02 01 00 00 E2 93 CD BE 01 00 00 00 01 6D BD DB .............m..
000020 08 5B 1D 8A F7 51 84 F0 BC 01 FA D5 8D 12 66 E9 .[...Q........f.
000030 B6 3B 50 88 19 90 E4 B4 0D 6A EE 36 29 00 00 00 .;P......j.6)...
000040 00 8B 48 30 45 02 21 00 F3 58 1E 19 72 AE 8A C7 ..H0E.!..X..r...
000050 C7 36 7A 7A 25 3B C1 13 52 23 AD B9 A4 68 BB 3A .6zz%;..R#...h.:
000060 59 23 3F 45 BC 57 83 80 02 20 59 AF 01 CA 17 D0 Y#?E.W... Y.....
000070 0E 41 83 7A 1D 58 E9 7A A3 1B AE 58 4E DE C2 8D .A.z.X.z...XN...
000080 35 BD 96 92 36 90 91 3B AE 9A 01 41 04 9C 02 BF 5...6..;...A....
000090 C9 7E F2 36 CE 6D 8F E5 D9 40 13 C7 21 E9 15 98 .~.6.m...@..!...
0000A0 2A CD 2B 12 B6 5D 9B 7D 59 E2 0A 84 20 05 F8 FC *.+..].}Y... ...
0000B0 4E 02 53 2E 87 3D 37 B9 6F 09 D6 D4 51 1A DA 8F N.S..=7.o...Q...
0000C0 14 04 2F 46 61 4A 4C 70 C0 F1 4B EF F5 FF FF FF ../FaJLp..K.....
0000D0 FF 02 40 4B 4C 00 00 00 00 00 19 76 A9 14 1A A0 ..@KL......v....
0000E0 CD 1C BE A6 E7 45 8A 7A BA D5 12 A9 D9 EA 1A FB .....E.z........
0000F0 22 5E 88 AC 80 FA E9 C7 00 00 00 00 19 76 A9 14 "^...........v..
000100 0E AB 5B EA 43 6A 04 84 CF AB 12 48 5E FD A0 B7 ..[.Cj.....H^...
000110 8B 4E CC 52 88 AC 00 00 00 00 .N.R......

Message header:
F9 BE B4 D9 - main network magic bytes
74 78 00 00 00 00 00 00 00 00 00 00 - "tx" command
02 01 00 00 - payload is 258 bytes long
E2 93 CD BE - checksum of payload

Transaction:
01 00 00 00 - version

Inputs:
01 - number of transaction inputs

Input 1:
6D BD DB 08 5B 1D 8A F7 51 84 F0 BC 01 FA D5 8D - previous output (outpoint)
12 66 E9 B6 3B 50 88 19 90 E4 B4 0D 6A EE 36 29
00 00 00 00

8B - script is 139 bytes long

48 30 45 02 21 00 F3 58 1E 19 72 AE 8A C7 C7 36 - signature script (scriptSig)
7A 7A 25 3B C1 13 52 23 AD B9 A4 68 BB 3A 59 23
3F 45 BC 57 83 80 02 20 59 AF 01 CA 17 D0 0E 41
83 7A 1D 58 E9 7A A3 1B AE 58 4E DE C2 8D 35 BD
96 92 36 90 91 3B AE 9A 01 41 04 9C 02 BF C9 7E
F2 36 CE 6D 8F E5 D9 40 13 C7 21 E9 15 98 2A CD
2B 12 B6 5D 9B 7D 59 E2 0A 84 20 05 F8 FC 4E 02
53 2E 87 3D 37 B9 6F 09 D6 D4 51 1A DA 8F 14 04
2F 46 61 4A 4C 70 C0 F1 4B EF F5

FF FF FF FF - sequence

Outputs:
02 - 2 Output Transactions

Output 1:
40 4B 4C 00 00 00 00 00 - 0.05 BTC (5000000)
19 - pk_script is 25 bytes long

76 A9 14 1A A0 CD 1C BE A6 E7 45 8A 7A BA D5 12 - pk_script
A9 D9 EA 1A FB 22 5E 88 AC

Output 2:
80 FA E9 C7 00 00 00 00 - 33.54 BTC (3354000000)
19 - pk_script is 25 bytes long

76 A9 14 0E AB 5B EA 43 6A 04 84 CF AB 12 48 5E - pk_script
FD A0 B7 8B 4E CC 52 88 AC

Locktime:
00 00 00 00 - lock time
</pre>

=== block ===

The '''block''' message is sent in response to a getdata message which requests transaction information from a block hash.

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || Block version information, based upon the software version creating this block
|-
| 32 || prev_block || char[32] || The hash value of the previous block this particular block references
|-
| 32 || merkle_root || char[32] || The reference to a Merkle tree collection which is a hash of all transactions related to this block
|-
| 4 || timestamp || uint32_t || A unix timestamp recording when this block was created (Currently limited to dates before the year 2106!)
|-
| 4 || bits || uint32_t || The calculated [[Difficulty|difficulty target]] being used for this block
|-
| 4 || nonce || uint32_t || The nonce used to generate this block… to allow variations of the header and compute different hashes
|-
| ? || txn_count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of transaction entries
|-
| ? || txns || tx[] || Block transactions, in format of "tx" command
|}

The SHA256 hash that identifies each block (and which must have a run of 0 bits) is calculated from the first 6 fields of this structure (version, prev_block, merkle_root, timestamp, bits, nonce, and standard SHA256 padding, making two 64-byte chunks in all) and ''not'' from the complete block. To calculate the hash, only two chunks need to be processed by the SHA256 algorithm. Since the ''nonce'' field is in the second chunk, the first chunk stays constant during mining and therefore only the second chunk needs to be processed. However, a Bitcoin hash is the hash of the hash, so two SHA256 rounds are needed for each mining iteration.
See [[Block hashing algorithm]] for details and an example.

=== headers ===

The ''headers'' packet returns block headers in response to a ''getheaders'' packet.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of block headers
|-
| 81x? || headers || [[Protocol_specification#Block_Headers|block_header]][] || [[Protocol_specification#Block_Headers|Block headers]]
|}

Note that the block headers in this packet include a transaction count (a var_int, so there can be more than 81 bytes per header) as opposed to the block headers which are sent to miners.

=== getaddr ===

The getaddr message sends a request to a node asking for information about known active peers to help with identifying potential nodes in the network. The response to receiving this message is to transmit an addr message with one or more peers from a database of known active peers. The typical presumption is that a node is likely to be active if it has been sending a message within the last three hours.

No additional data is transmitted with this message.

=== checkorder ===

This message is used for [[IP Transactions]], to ask the peer if it accepts such transactions and allow it to look at the content of the order.

It contains a CWalletTx object

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
|colspan="4"| Fields from CMerkleTx
|-
| ? || hashBlock
|-
| ? || vMerkleBranch
|-
| ? || nIndex
|-
|colspan="4"| Fields from CWalletTx
|-
| ? || vtxPrev
|-
| ? || mapValue
|-
| ? || vOrderForm
|-
| ? || fTimeReceivedIsTxTime
|-
| ? || nTimeReceived
|-
| ? || fFromMe
|-
| ? || fSpent
|}

=== submitorder ===

Confirms an order has been submitted.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 32 || hash || char[32] || Hash of the transaction
|-
| ? || wallet_entry || CWalletTx || Same payload as checkorder
|}

=== reply ===

Generic reply for [[IP Transactions]]

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || reply || uint32_t || reply code
|}

Possible values:

{|class="wikitable"
! Value !! Name !! Description
|-
| 0 || SUCCESS || The IP Transaction can proceed (''checkorder''), or has been accepted (''submitorder'')
|-
| 1 || WALLET_ERROR || AcceptWalletTransaction() failed
|-
| 2 || DENIED || IP Transactions are not accepted by this node
|}

=== ping ===

The ''ping'' message is sent primarily to confirm that the TCP/IP connection is still valid. An error in transmission is presumed to be a closed connection and the address is removed as a current peer. No reply is expected as a result of this message being sent nor any sort of action expected on the part of a client when it is used.

=== alert ===

An '''alert''' is sent between nodes to send a general notification message throughout the network. If the alert can be confirmed with the signature as having come from the the core development group of the Bitcoin software, the message is suggested to be displayed for end-users. Attempts to perform transactions, particularly automated transactions through the client, are suggested to be halted. The text in the Message string should be relayed to log files and any user interfaces.

Alert format:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || payload || var_str || Serialized alert payload
|-
| ? || signature || var_str || An ECDSA signature of the message
|}

The developers of Satoshi's client use this public key for signing alerts:
04fc9702847840aaf195de8442ebecedf5b095cdbb9bc716bda9110971b28a49e0ead8564ff0db22209e0374782c093bb899692d524e9d6a6956e7c5ecbcd68284
(hash) 1AGRxqDa5WjUKBwHB9XYEjmkv1ucoUUy1s

The payload is serialized into a var_str to ensure that versions using incompatible alert formats can still relay alerts among one another. The current alert payload format is:
{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || Version || int32_t || Alert format version
|-
| 8 || RelayUntil || int64_t || The timestamp beyond which nodes should stop relaying this alert
|-
| 8 || Expiration || int64_t || The timestamp beyond which this alert is no longer in effect and should be ignored
|-
| 4 || ID || int32_t || A unique ID number for this alert
|-
| 4 || Cancel || int32_t || All alerts with an ID number less than or equal to this number should be canceled: deleted and not accepted in the future
|-
| ? || setCancel || set<int> || All alert IDs contained in this set should be canceled as above
|-
| 4 || MinVer || int32_t || This alert only applies to versions greater than or equal to this version. Other versions should still relay it.
|-
| 4 || MaxVer || int32_t || This alert only applies to versions less than or equal to this version. Other versions should still relay it.
|-
| ? || setSubVer || set<string> || If this set contains any elements, then only nodes that have their subVer contained in this set are affected by the alert. Other versions should still relay it.
|-
| 4 || Priority || int32_t || Relative priority compared to other alerts
|-
| ? || Comment || string || A comment on the alert that is not displayed
|-
| ? || StatusBar || string || The alert message that is displayed to the user
|-
| ? || Reserved || string || Reserved
|}

== Scripting ==

See [[script]].

== Wireshark dissector ==
A dissector for wireshark is being developed at https://github.com/blueCommand/bitcoin-dissector

==See Also==

* [[Network]]
* [[Protocol rules]]
[[zh-cn:协议说明]]
[[Category:Technical]]
[[Category:Developer]]

Bitcoin Wiki - User contributions [en]

Bitstamp

BTC-e

CampBX

Mt. Gox

MtGox/API/Streaming

CampBX

BTC-e

BTC-e

Bitstamp

Mt. Gox

MtGox/API

Protocol documentation

Recommended Reading