Bitcoin Wiki - User contributions [en]

MtGox/API/Pubnub

2013-11-15T04:31:34Z

MagicalTux: fix wording

== Introduction ==

MtGox is now using the services of [http://www.pubnub.com Pubnub] to stream real time data, due to the difficulty to cope with the kind of volumes of data we need to broadcast realtime while keeping a reliable service.

Pubnub provides SDK in various languages: http://www.pubnub.com/developers

If you already use socketio, you may want to check https://github.com/pubnub/javascript/tree/master/socket.io

=== Access to public channels ===

It is possible to subscribe directly to any public channel listed on https://mtgox.com/api/2/stream/list_public?pretty through that interface.

Subscribe key for MtGox: <code>sub-c-50d56e1e-2fd9-11e3-a041-02ee2ddab7fe</code> (it's the same for everyone who want to use MtGox)

Some sample feeds on the pubnub console:

* http://www.pubnub.com/console?sub=sub-c-50d56e1e-2fd9-11e3-a041-02ee2ddab7fe&pub=demo&channel=d5f06780-30a8-4a48-a2f8-7ed181b4a13f&origin=pubsub.pubnub.com <- to access BTCUSD ticker
* http://www.pubnub.com/console?sub=sub-c-50d56e1e-2fd9-11e3-a041-02ee2ddab7fe&pub=demo&channel=dbf1dee9-4f2e-4a08-8cb7-748919a71b21&origin=pubsub.pubnub.com <- BTC trades

A very simple sample implementation: https://www.mtgox.com/lag.html (shows trade engine lag in realtime)

=== Access to private channels ===

Private channels can be accessed by first calling the https://www.mtgox.com/api/2/stream/private_get api. This API will return details to access the private API (subscribe key, auth key, encryption key, etc).

Private messages are encrypted using Pubnub's standard encryption method (AES128 CBC) and a shared secret obtained through the API. This guarantees that Pubnub has no knowledge of the private key and as such can't possibly read the private messages unless you access the console (as it's passed as parameter). As long as you don't call the stream/private_get api, no data for your user will be sent to Pubnub.

Once the number of seconds specified in "renew" has passed, you should call the API again to renew the auth key and password. If the auth key has changed, you will need to subscribe again to continue getting updates.
Once the number of seconds specified in "expires" has passed, no data will be sent anymore unless the API was called again.

If you call that API once every <code>renew</code>, the access data should not change, and you should continue getting updates as long as you're connected. Note that you can pass an extra parameter to this API (<code>renew=1</code>) to force the private key and auth key to change. Change in private key will be handled for all new messages (the old auth key will continue working until its expiration).

MtGox/API/Pubnub

2013-11-15T04:23:13Z

MagicalTux: initial text

== Introduction ==

MtGox is now using the services of [http://www.pubnub.com Pubnub] to stream real time data, due to the difficulty to cope with the kind of volumes of data we need to broadcast realtime while keeping a reliable service.

Pubnub provides SDK in various languages: http://www.pubnub.com/developers

If you already use socketio, you may want to check https://github.com/pubnub/javascript/tree/master/socket.io

=== Access to public channels ===

It is possible to register directly to any public channel listed on https://mtgox.com/api/2/stream/list_public?pretty through that interface.

Subscribe key for MtGox: <code>sub-c-50d56e1e-2fd9-11e3-a041-02ee2ddab7fe</code> (it's the same for everyone who want to use MtGox)

Some sample feeds on the pubnub console:

* http://www.pubnub.com/console?sub=sub-c-50d56e1e-2fd9-11e3-a041-02ee2ddab7fe&pub=demo&channel=d5f06780-30a8-4a48-a2f8-7ed181b4a13f&origin=pubsub.pubnub.com <- to access BTCUSD ticker
* http://www.pubnub.com/console?sub=sub-c-50d56e1e-2fd9-11e3-a041-02ee2ddab7fe&pub=demo&channel=dbf1dee9-4f2e-4a08-8cb7-748919a71b21&origin=pubsub.pubnub.com <- BTC trades

A very simple sample implementation: https://www.mtgox.com/lag.html (shows trade engine lag in realtime)

=== Access to private channels ===

Private channels can be accessed by first calling the https://www.mtgox.com/api/2/stream/private_get api. This API will return details to access the private API (subscribe key, auth key, encryption key, etc).

Private messages are encrypted using Pubnub's standard encryption method (AES128 CBC) and a shared secret obtained through the API. This guarantees that Pubnub has no knowledge of the private key and as such can't possibly read the private messages unless you access the console (as it's passed as parameter). As long as you don't call the stream/private_get api, no data for your user will be sent to Pubnub.

Once the number of seconds specified in "renew" has passed, you should call the API again to renew the auth key and password. If the auth key has changed, you will need to subscribe again to continue getting updates.
Once the number of seconds specified in "expires" has passed, no data will be sent anymore unless the API was called again.

If you call that API once every <code>renew</code>, the access data should not change, and you should continue getting updates as long as you're connected. Note that you can pass an extra parameter to this API (<code>renew=1</code>) to force the private key and auth key to change. Change in private key will be handled for all new messages (the old auth key will continue working until its expiration).

MtGox/API

2013-11-15T04:19:01Z

MagicalTux:

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

Two APIs are currently available:

* [[MtGox/API/HTTP|HTTP API]]
* [[MtGox/API/Pubnub|Streaming Pubnub API]]
* [[MtGox/API/Streaming|Streaming websocket API]]

__TOC__

==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 (100,000,000) || 0.00000001
|-
| USD, AUD, CAD, CHF, CNY, DKK, EUR, GBP, HKD, NZD, PLN, RUB, SGD, THB, NOK, CZK (price) || 1E5 (100,000) || 0.00001
|-
| JPY, SEK (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, NOK, CZK

==Date and time==

Most dates you will find in mtgox API are UNIX time

See http://en.wikipedia.org/wiki/Unix_time

Most programming languages should have tools for managing those timestamps

==See Also==

* [http://bitcointalk.org/index.php?topic=164404.0 MtGox API version 2: Unofficial Documentation]

Main Page

2013-05-08T22:55:35Z

MagicalTux: adding link to RO wiki (still new)

{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] wiki,</div>
<div style="top:+0.2em; font-size:95%;">For all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles. Anti-spam protection from [[BitcoinPayment]]</div>
'''[[:Category:Stubs|This wiki]] is maintained by the Bitcoin community.'''
|}

| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[http://bitcoin.org Frontpage]</span>
| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[[Forums]]</span>
| style="width:13%; font-size:120%; padding-right: 40px;" |
* <span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[Bitcoin.it Wiki|About]]''' - Information on this site.
[[de:Hauptseite]]
[[es:Página Principal]]
[[fr:Accueil]]
[[it:Pagina principale]]
[[pl:Strona główna]]
[[ru:Заглавная страница]]
[[zh-cn:首页]]
[[ro:Pagina principală]]

__NOTOC____NOEDITSECTION__

Node.js Example

2013-03-08T00:48:08Z

MagicalTux: adding content length to keep compatibility

<source lang="javascript">
var querystring = require('querystring'),
https = require('https'),
crypto = require('crypto');

function MtGoxClient(key, secret) {
this.key = key;
this.secret = secret;
}

MtGoxClient.prototype.query = function(path, args, callback) {
var client = this;

// if no args or invalid args provided, just reset the arg object
if (typeof args != "object") args = {};

// generate a nonce
args['nonce'] = (new Date()).getTime() * 1000;
// compute the post data
var post = querystring.stringify(args);
// compute the sha512 signature of the post data
var hmac = crypto.createHmac('sha512', new Buffer(client.secret, 'base64'));
hmac.update(post);

// this is our query
var options = {
host: 'mtgox.com',
port: 443,
path: '/api/' + path,
method: 'POST',
agent: false,
headers: {
'Rest-Key': client.key,
'Rest-Sign': hmac.digest('base64'),
'User-Agent': 'Mozilla/4.0 (compatible; MtGox node.js client)',
'Content-type': 'application/x-www-form-urlencoded',
'Content-Length': post.length
}
};

// run the query, buffer the data and call the callback
var req = https.request(options, function(res) {
res.setEncoding('utf8');
var buffer = '';
res.on('data', function(data) { buffer += data; });
res.on('end', function() { if (typeof callback == "function") { callback(JSON.parse(buffer)); } });
});

// basic error management
req.on('error', function(e) {
console.log('warning: problem with request: ' + e.message);
});

// post the data
req.write(post);
req.end();
};

var client = new MtGoxClient('mykey', 'mysecret');
client.query('1/BTCUSD/public/ticker', {}, function(json) {
// do something
console.log(json);
});
</source>

Template:BitcoinPayment

2013-01-19T01:31:26Z

MagicalTux:

== Purpose ==

The purpose of this page is to stop spam on the wiki by making spam too costly to be viable.

Funds sent to the wiki will be used to keep the wiki online (cost of domain name and hosting), and remaining funds will be donated to the Bitcoin Foundation.

== Status ==

{{#ifeq: {{{status}}} | todo | To move forward, you will need to send 0.05 bitcoins to [bitcoin:{{{addr}}} {{{addr}}}]. }}

{{#ifeq: {{{status}}} | done | Thank you for your support! }}

{{#ifeq: {{{status}}} | nologin | You'll need to login to know your status. }}

Template:BitcoinPayment

2013-01-19T01:31:05Z

MagicalTux:

== Purpose ==

The purpose of this page is to stop spam on the wiki by making spam too costly to be viable.

Funds sent to the wiki will be used to keep the wiki online (cost of domain name and hosting), and remaining funds will be donated to the Bitcoin Foundation.

== Status ==

{{#ifeq: {{{status}}} | todo | To move forward, you will need to send bitcoins to [bitcoin:{{{addr}}} {{{addr}}}]. }}

{{#ifeq: {{{status}}} | done | Thank you for your support! }}

{{#ifeq: {{{status}}} | nologin | You'll need to login to know your status. }}

Template:BitcoinPayment

2013-01-19T01:25:01Z

MagicalTux: Created page with "== Purpose == The purpose of this page is to stop spam on the wiki by making spam too costly to be viable. Funds sent to the wiki will be used to keep the wiki online (cost ..."

User talk:Nanotube

2013-01-17T08:08:54Z

MagicalTux: /* user access to modify pages */ new section

Hi Nanotube,
can you please delete [[Mining pool reward FAQ]]? I created it to provide information about some commonly confused issues, but it's being abused and thus can't serve this purpose. [[User:Holy-Fire|Holy-Fire]] 18:43, 26 May 2011 (GMT)
: I removed the troublesome content and left it to-the-point. This should serve to remove any abuse. --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 18:51, 26 May 2011 (GMT)
::Sorry, it really doesn't, see my comment on your talk page. [[User:Holy-Fire|Holy-Fire]] 19:08, 26 May 2011 (GMT)
:::posted my comments on firestorm's user talk page and the faq-page talk page. https://en.bitcoin.it/wiki/Talk:Mining_pool_reward_FAQ

==Help Page==

Hello, Nanotube. I've created a fairly simple [[Help:Contents|Help page]] that I'm going to be expanding over time. Would it be a good idea to link to this in the sidebar? --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 14:46, 30 May 2011 (GMT)
: add it as "Wiki Help", you think?--[[User:Nanotube|Nanotube]] 16:44, 30 May 2011 (GMT)
:: Just "Help" should be fine. I'll collaborate links to various FAQs and help pages regarding Bitcoin itself. I hope to make it the resource to go to if you need information on anything --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 17:06, 30 May 2011 (GMT)
::: How's the page looking? --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 05:19, 1 June 2011 (GMT)
:::: Looking good to me. :) Sorry for delay in response, been busy. --[[User:Nanotube|Nanotube]] 03:11, 30 June 2011 (GMT)
::::: Could you add it to the sidebar, then? I think it would be more useful than the FAQ --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 16:40, 21 July 2011 (GMT)
:::::: Took me long enough... but done! :) --[[User:Nanotube|Nanotube]] 22:27, 27 September 2011 (GMT)

==Another language==
If it will be possible Wiki in another language? Like Wikipedia it will be good to translate to other language, for example Polish. [[User:Frodo|Frodo]] 11:52, 4 May 2012 (GMT)

== user access to modify pages ==

Hi, as discussed, the process is available on [[Special:BitcoinPayment]] [[User:MagicalTux|MagicalTux]] ([[User talk:MagicalTux|talk]]) 08:08, 17 January 2013 (GMT)

MtGox/API/HTTP

2013-01-17T06:32:21Z

MagicalTux: /* PHP */ added support for api v2 calls in PHP example

Two versions of the HTTP API are currently available, see the following pages for details on the methods available for each:

* [[MtGox/API/HTTP/v0|Version 0]]
* [[MtGox/API/HTTP/v1|Version 1]]

== Summary ==

All HTTP API requests are sent to URLs beginning with <nowiki>https://mtgox.com/api/*</nowiki>. It allows placing orders, performing withdrawls, deposits, and other things. All responses are in [http://json.org/ JSON] format.

There is a [https://rubygems.org/gems/mtgox Ruby gem], [https://rubygems.org/gems/guten-mtgox guten-mtgox] and a [[Finance::MtGox|Perl module]] available for interacting with the HTTP API.

== Cache ==

All API methods are cached for 10 seconds. Do not request results more often than that, you might be blocked by the anti-DDoS filters.

== 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

== 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:

'''basically the base64 string should contain:'''
* the binary representation of the api key id
* binary hmac-sha512 signature
* json data

api key looks like that: 12345678-abcd-1234-abcd-50286e649d5c

it's actually hexadecimal, it should be converted to binary

hash should then be appended (binary too) and then encode everything in base64

'''Warning : the API is no more accepting authentication by login/pass ( since 2012 march 1 ) , you _need_ to use an API key.'''

=== perl ===

'''IMPORTANT! This is a simplified perl module simply returning user info not a full API, it is shown simply for illustrative purposes for those wishing to developing there own modules from scratch.. or bots.. or other'''

'''IMPORTANT! This requires you compiled perl libwww with https support'''

<source lang="perl">

#!/usr/bin/perl

use strict;
use warnings;

use Time::HiRes qw(gettimeofday);
use MIME::Base64;
use Digest::SHA qw(hmac_sha512);

use JSON;
use LWP::UserAgent;

use Data::Dumper;

my $lwp = LWP::UserAgent->new;
$lwp->agent("perl $]");

my $json = JSON->new->allow_nonref;

my $secret = '_MTGOX API SECRET GET YOURS AT https://classic.mtgox.com/support/tradeAPI';
my $key = '_MTGOX API KEY GET YOURS AT https://classic.mtgox.com/support/tradeAPI';

## user code

my $request = genReq('/1/generic/private/info');
my $res = $lwp->request($request);

# Check the outcome of the response
if ($res->is_success) {
print Dumper($json->decode( $res->content ))."\n";
}
else { print $res->status_line, "\n"; }

exit 0;

## sub routines and helpers

sub genReq {
my ($uri) = shift;

my $req = HTTP::Request->new(POST => 'https://mtgox.com/api/'.$uri);
$req->content_type('application/x-www-form-urlencoded');
$req->content("nonce=".microtime());
$req->header('Rest-Key' => $key);
$req->header('Rest-Sign' => signReq($req->content(),$secret));

return $req;
};

sub signReq {
my ($content,$secret) = @_;
return encode_base64(hmac_sha512($content,decode_base64($secret)));
}

sub microtime { return sprintf "%d%06d", gettimeofday; }

</source>
=== PHP ===
<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, '', '&');

$prefix = '';
if (substr($path, 0, 2) == '2/') {
$prefix = substr($path, 2)."\0";
}

// generate the extra headers
$headers = array(
'Rest-Key: '.$key,
'Rest-Sign: '.base64_encode(hash_hmac('sha512', $prefix.$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);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);

// 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 ===
<source lang="python">
from urllib import urlencode
import urllib2
import time
from hashlib import sha512
from hmac import HMAC
import base64
import json
def get_nonce():
return int(time.time()*100000)

def sign_data(secret, data):
return base64.b64encode(str(HMAC(secret, data, sha512).digest()))

class requester:
def __init__(self, auth_key, auth_secret):
self.auth_key = auth_key
self.auth_secret = base64.b64decode(auth_secret)

def build_query(self, req={}):
req["nonce"] = get_nonce()
post_data = urlencode(req)
headers = {}
headers["User-Agent"] = "GoxApi"
headers["Rest-Key"] = self.auth_key
headers["Rest-Sign"] = sign_data(self.auth_secret, post_data)
return (post_data, headers)

def perform(self, path, args):
data, headers = self.build_query(args)
req = urllib2.Request("https://mtgox.com/api/0/"+path, data, headers)
res = urllib2.urlopen(req, data)
return json.load(res)
</source>

=== Node.js ===
Generic [[Node.js Example]] trading library (supports MtGox and Bitfloor): https://github.com/bitfloor/trader.nodejs

=== Java ===

basic [[Java Example]] on https://gist.github.com/2396722 hoping for many java forks and pull requests on github

XChange API : https://github.com/timmolter/XChange

mtgox-java: A Java API (based on Spring & Maven) for the MtGox bitcoin exchange WebSocket & HTTP services.
http://grantsparks.github.com/mtgox-java/

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

==See Also==

* [[MtGox|Mt. Gox]]

CryptoPayment

2013-01-17T04:00:13Z

MagicalTux: Created page with "MediaWiki extension to limit spam critically. Suggested by various people and implemented here."

MediaWiki extension to limit spam critically.

Suggested by various people and implemented here.

MediaWiki:Group-trusted-member

2013-01-17T03:33:27Z

MagicalTux: Created page with "Trusted user"

Trusted user

MediaWiki:Group-trusted

2013-01-17T03:33:17Z

MagicalTux: Created page with "Trusted users"

Trusted users

MediaWiki:Sidebar

2011-10-22T11:11:30Z

MagicalTux:

MediaWiki:Sidebar

2011-10-16T01:10:24Z

MagicalTux:

BitcoinX (disambiguation)

2011-09-07T07:51:48Z

MagicalTux: Created page with "BitcoinX may refer to: * The BitcoinX Android Application * The BitcoinX.com service"

BitcoinX may refer to:

* [[BitcoinX (application)|The BitcoinX Android Application]]
* [[BitcoinX (service)|The BitcoinX.com service]]

BitcoinX (application)

2011-09-07T07:50:58Z

MagicalTux: moved BitcoinX to BitcoinX (application): There's more than one BitcoinX

An Android App to keep track of Bitcoin on [[MtGox]].

Information provided includes with bid, ask and 24 hour history.

This app was announced on June 14, 2011<ref>[http://forum.bitcoin.org/index.php?topic=16953.0 Android App to keep track of Bitcoin on MTGOX]</ref>.

==See Also==

* [[MtGox#Data Services]]

==External Links==

* [http://www.appbrain.com/app/bitcoinx/com.tempodynamics.BitCoin.BitCoinX BitcoinX] app on AppBrain

==References==
<references />

[[Category:Mobile]]

MtGox/API

2011-07-24T02:07:41Z

MagicalTux: updating api info

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

Two APIs are available at this point: 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.

== 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 [[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>

=== Methods ===

==== 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.

==== 0/history_[CUR].csv ====
Allows downloading the activity history for a given currency (BTC or USD for now).

== Websocket API ==
ported on 7/10/2011 from http://forum.bitcoin.org/index.php?topic=5855.0

===Connecting===

You can connect via: ws://websocket.mtgox.com/mtgox

The WebSocket protocol version used is that described in [http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-00 draft-ietf-hybi-thewebsocketprotocol-00] (aka draft-00).

===Channels===

The websocket will subscribe you to some channels automatically:

{| class="wikitable"
|-
! Channel ID !! Description
|-
| dbf1dee9-4f2e-4a08-8cb7-748919a71b21 || trades (each time a trade happens, you get something here)
|-
| d5f06780-30a8-4a48-a2f8-7ed181b4a13f || the mtgox ticker (lots of updates, with often the same data)
|-
| 24e67e0d-1cad-4cc0-9e7a-f8523ef460fe || depth information in realtime (price + amount + type... type=1=Ask, type=2=Bid)
|}

Additionally each user has a "own" channel which streams informations about orders (new order, deleted order, etc) and trades only the user's trades).

Each message is a JSON-encoded object, with at least "op" element. The "op" element contains the operation to be done (for outgoing messages), or the type of message (for incoming messages).

===Possible outgoing commands===

'''unsubscribe''' Stop receiving messages from a channel (parameter "channel")

===Incoming Data===

====Ticker====
<source lang="javascript">
{
"channel":"d5f06780-30a8-4a48-a2f8-ed181b4a13f",
"op":"private",
"origin":"broadcast",
"private":"ticker",
"ticker":{
"buy":0.9515,
"high":1,
"low":0.91,
"sell":0.9697,
"vol":34349
}
}
</source>

'''ticker''' contains the following:

{| class="wikitable"
|-
! Name !! Value
|-
| buy || lowest bid as float
|-
| sell || highest ask as float
|-
| high || maximum rate since last close as float
|-
| low || minimum rate since last close as float
|-
| vol || traded volume since last close
|}

====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",
"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",
"price":"14.43",
"price_int":"1443000",
"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
|-
| ||
|-
| ||

|}

====Order update (private)====

<source lang="javascript">
{
"channel":"(partial key)",
"op":"private",
"order_upd":{
"amount":1000,
"darkStatus":0,
"date":1302836027,
"oid":"(oid)",
"price":0.9899,"status":1
},
"origin":"broadcast",
"private":"order_upd"
}</source>

'''order_upd''' cointains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || change in volume of the order
|-
| darkStatus ||
|-
| oid || ID of the affected order
|-
| price ||
|-
| status ||
|}

Fallback Nodes

2011-07-18T14:56:10Z

MagicalTux: /* IPv4 Nodes */

Fallback Nodes

2011-07-18T14:52:53Z

MagicalTux: /* IPv4 Nodes */ re-adding de

Fallback Nodes

2011-07-18T08:00:00Z

MagicalTux: updating node ip

Fallback Nodes

2011-07-18T07:53:11Z

MagicalTux: /* IPv4 Nodes */ test

Fallback Nodes

2011-07-18T07:50:57Z

MagicalTux: /* IPv4 Nodes */ re-trying

Fallback Nodes

2011-07-18T07:49:56Z

MagicalTux: testing re-adding a node

MtGox/API

2011-07-18T05:58:13Z

MagicalTux: add reference PHP implementation for MtGox API

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

Two APIs are available at this point: 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.

== Legacy API ==
This API is available in <nowiki>https://mtgox.com/api/0/*</nowiki>, and provides various informations. It also supports making an order, a withdraw, a deposit, etc. There is also a [[Finance::MtGox|Perl module]] for interacting with the Legacy 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>

=== Methods ===

==== 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.

== Websocket API ==
ported on 7/10/2011 from http://forum.bitcoin.org/index.php?topic=5855.0

===Connecting===

You can connect via: ws://websocket.mtgox.com/mtgox

The WebSocket protocol version used is that described in [http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-00 draft-ietf-hybi-thewebsocketprotocol-00] (aka draft-00).

===Channels===

The websocket will subscribe you to some channels automatically:

{| class="wikitable"
|-
! Channel ID !! Description
|-
| dbf1dee9-4f2e-4a08-8cb7-748919a71b21 || trades (each time a trade happens, you get something here)
|-
| d5f06780-30a8-4a48-a2f8-7ed181b4a13f || the mtgox ticker (lots of updates, with often the same data)
|-
| 24e67e0d-1cad-4cc0-9e7a-f8523ef460fe || depth information in realtime (price + amount + type... type=1=Ask, type=2=Bid)
|}

Additionally each user has a "own" channel which streams informations about orders (new order, deleted order, etc) and trades only the user's trades).

Each message is a JSON-encoded object, with at least "op" element. The "op" element contains the operation to be done (for outgoing messages), or the type of message (for incoming messages).

===Possible outgoing commands===

'''unsubscribe''' Stop receiving messages from a channel (parameter "channel")

===Incoming Data===

====Ticker====
<source lang="javascript">
{
"channel":"d5f06780-30a8-4a48-a2f8-ed181b4a13f",
"op":"private",
"origin":"broadcast",
"private":"ticker",
"ticker":{
"buy":0.9515,
"high":1,
"low":0.91,
"sell":0.9697,
"vol":34349
}
}
</source>

'''ticker''' contains the following:

{| class="wikitable"
|-
! Name !! Value
|-
| buy || lowest bid as float
|-
| sell || highest ask as float
|-
| high || maximum rate since last close as float
|-
| low || minimum rate since last close as float
|-
| vol || traded volume since last close
|}

====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",
"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",
"price":"14.43",
"price_int":"1443000",
"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
|-
| ||
|-
| ||

|}

====Order update (private)====

<source lang="javascript">
{
"channel":"(partial key)",
"op":"private",
"order_upd":{
"amount":1000,
"darkStatus":0,
"date":1302836027,
"oid":"(oid)",
"price":0.9899,"status":1
},
"origin":"broadcast",
"private":"order_upd"
}</source>

'''order_upd''' cointains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || change in volume of the order
|-
| darkStatus ||
|-
| oid || ID of the affected order
|-
| price ||
|-
| status ||
|}

Mt. Gox

2011-07-14T23:21:45Z

MagicalTux: removing dark pools

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>. Bitcoins are bought on using funds from the trader's MTGUSD balance with Mt. Gox and when bitcoins are the funds from the proceeds are added to the trader's MTGUSD account with Mt. Gox.

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.

==Trading==
===Buying===

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.

===Selling===

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.

===Fees===

Mt. Gox subtracts a 0.65% trading fee from each party of successful trades made through the market.

When buying bitcoins, the fee will cause the number of Bitcoins bought to be 0.65% fewer. In other words, after buying 1.0 BTC the BTC balance for the account will increase by just 0.9935 BTC (1.0 BTC less the 0.0065 BTC fee)<ref>[http://forum.bitcoin.org/index.php?topic=12793.0 Dear Mt. Gox. Please make your accounting easier to understand.]</ref>. The per-BTC trade price reflected in the account history shows an amount recomputed to reflect the fee. The Quantity X Trade Price from the buy order will total the same dollar amount as is subtracted from the account after the trade executes.

When selling bitcoins, the fee will cause the proceeds of the sale to be 0.065 lower. After selling $100 worth of bitcoins the USD balance for the account will increase by just $99.35 USD ($100 USD less the $0.65 USD fee).

==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.

Note: Even though the site displays no ads, some browser ad-blocking utilities will interfere with the exchange's web site, specifically with the Add Bitcoins function.

===LRUSD===

There are no fees incurred when adding [[Liberty Reserve]] LRUSD funds to an account. Funds are available in minutes.

===Dwolla===

This option is among the fastest and least expensive methods for adding funds to a Mt. Gox account. The transaction fee on [[Dwolla]] costs just $0.25. The process is automated and the funds are 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>.

===International USD Bank Wire===

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.

===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.====

Adding funds to Dwolla from a bank account will use ACH though. The bank wire funding method has been temporarily disontinued due to difficulties in processing. Another banking relationship is being pursued.

====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. and 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. 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: aml@mtgox.com

===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.

===BTC===

Bitcoins may be withdrawn at no charge.

There have been sporadic reports where withdrawing the entire bitcoin balance results in an error message. This could the be the result of a possible error where the amount available for withdrawal gets miscalculated due to a rounding error. In at least one instance, a subsequent attempt to withdraw all but the last 1 BTC completed successfully.

===LRUSD===

There are two fees incurred when withdrawing LRUSD. Mt. Gox themselves subtracts 1% of the transfer amount as a fee before transferring away. Liberty Reserve then subtracts as a transfer fee 1% from the amount they've received.

For example, to withdraw $100 LRUSD, Mt. Gox will send $99 ($100 less a 1% fee)<ref>One member of [[Bitcoin-otc]] reports that this appears to be a 0.99% fee, not a 1.0%.</ref> Liberty Reserve will subtract $0.99 ($99 less a 1% fee) leaving a net amount at Liberty Received of $98.01.

===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. The direct ACH withdrawal method has been temporarily disontinued due to difficulties in processing. Another banking relationship is being pursued.

====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 is subtracted and the remaining amount is converted to AUD and sent through Technocash.

==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].

==API==

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

==Criticism==
After the addFunds form is displayed, it is not apparent to the user how to determine that address again. An account holder could become confused as to whether or not the correct address was used but after closing that page, there's no way to know at a later time what address "Send Bitcoins" had yielded.

==Data Services==

===Web===
* [[Bitcoin Charts]]
* Clark Moody's [[Real Time Bitcoin Market Data]] including Ticker, Order Book and Time Sales (Websockets browser support required)
* CodeStream's [http://codestream.de/bitcoin/chart.htm Adjustable Depth Chart] (Websockets browser support required)
* [[MtGox Live]] (Websockets browser support required)
* [http://btcbids.com/trader.php BTCBids trader view]
* [[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

==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>.

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.

==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]]

MtGox/API

2011-07-10T09:48:32Z

MagicalTux: /* Depth */ testing with source tag

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

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

== Legacy API ==
This API is available in <nowiki>https://mtgox.com/code/*</nowiki>, and provides various informations. It also supports making an order, a withdraw, a deposit, etc.

=== Authentication ===
Authentication is performed by posting a username and a password in variables "name" and "pass". Some methods do not require authentication.

=== Methods ===

==== 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.

== Websocket API ==
See: http://forum.bitcoin.org/index.php?topic=5855.0 (will be ported here soon)

===Connecting===

You can connect via: ws://websocket.mtgox.com/mtgox

===Channels===

The websocket will subscribe you to some channels automatically:
{| class="wikitable"
|-
! Channel ID !! Description
|-
| dbf1dee9-4f2e-4a08-8cb7-748919a71b21 || trades (each time a trade happens, you get something here)
|-
| d5f06780-30a8-4a48-a2f8-7ed181b4a13f || the mtgox ticker (lots of updates, with often the same data)
|-
| 24e67e0d-1cad-4cc0-9e7a-f8523ef460fe || depth information in realtime (price + amount + type... type=1=Ask, type=2=Bid)
|}

Additionally each user has a "own" channel which streams informations about orders (new order, deleted order, etc) and trades only the user's trades).

Each message is a JSON-encoded object, with at least "op" element. The "op" element contains the operation to be done (for outgoing messages), or the type of message (for incoming messages).

===Possible outgoing commands===

'''unsubscribe''' Stop receiving messages from a channel (parameter "channel")

===Incoming Data===

====Ticker====
{"channel":"d5f06780-30a8-4a48-a2f8-7ed181b4a13f","op":"private","origin":"broadcast","private":"ticker","ticker":"buy":0.9515,"high":1,"low":0.91,"sell":0.9697,"vol":34349}}

:The '''ticker''' field contains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| buy || lowest bid as float
|-
| sell || highest ask as float
|-
| high || maximum rate since last close as float
|-
| low || minimum rate since last close as float
|-
| vol || traded volume since last close
|}

====Trade====
{"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","tid":"1310279340877902","trade_type":"bid","type":"trade"}}

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || the traded amount in item (BTC), float, deprecated
|-
| amount_int || the traded amount * 10000
|-
| 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",
"price":"14.43",
"price_int":"1443000",
"type":1,
"type_str":"ask",
"volume":"-2.71",
"volume_int":"-271000000"
},
"op":"private",
"origin":"broadcast",
"private":"depth"
}</source>

:{| 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 * 10000
|-
| 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 * 10000
|-
| ||
|-
| ||

|}

====Order update (private)====

{"channel":"(partial key)","op":"private","order_upd":{"amount":1000,"darkStatus":0,"date":1302836027,"oid":"(oid)","price":0.9899,"status":1},"origin":"broadcast","private":"order_upd"}

:order_upd cointains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || change in volume of the order
|-
| darkStatus ||
|-
| oid || ID of the affected order
|-
| price ||
|-
| status ||
|}

MtGox/API

2011-07-10T09:48:02Z

MagicalTux: /* Depth */ testing data formatting

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

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

== Legacy API ==
This API is available in <nowiki>https://mtgox.com/code/*</nowiki>, and provides various informations. It also supports making an order, a withdraw, a deposit, etc.

=== Authentication ===
Authentication is performed by posting a username and a password in variables "name" and "pass". Some methods do not require authentication.

=== Methods ===

==== 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.

== Websocket API ==
See: http://forum.bitcoin.org/index.php?topic=5855.0 (will be ported here soon)

===Connecting===

You can connect via: ws://websocket.mtgox.com/mtgox

===Channels===

The websocket will subscribe you to some channels automatically:
{| class="wikitable"
|-
! Channel ID !! Description
|-
| dbf1dee9-4f2e-4a08-8cb7-748919a71b21 || trades (each time a trade happens, you get something here)
|-
| d5f06780-30a8-4a48-a2f8-7ed181b4a13f || the mtgox ticker (lots of updates, with often the same data)
|-
| 24e67e0d-1cad-4cc0-9e7a-f8523ef460fe || depth information in realtime (price + amount + type... type=1=Ask, type=2=Bid)
|}

Additionally each user has a "own" channel which streams informations about orders (new order, deleted order, etc) and trades only the user's trades).

Each message is a JSON-encoded object, with at least "op" element. The "op" element contains the operation to be done (for outgoing messages), or the type of message (for incoming messages).

===Possible outgoing commands===

'''unsubscribe''' Stop receiving messages from a channel (parameter "channel")

===Incoming Data===

====Ticker====
{"channel":"d5f06780-30a8-4a48-a2f8-7ed181b4a13f","op":"private","origin":"broadcast","private":"ticker","ticker":"buy":0.9515,"high":1,"low":0.91,"sell":0.9697,"vol":34349}}

:The '''ticker''' field contains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| buy || lowest bid as float
|-
| sell || highest ask as float
|-
| high || maximum rate since last close as float
|-
| low || minimum rate since last close as float
|-
| vol || traded volume since last close
|}

====Trade====
{"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","tid":"1310279340877902","trade_type":"bid","type":"trade"}}

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || the traded amount in item (BTC), float, deprecated
|-
| amount_int || the traded amount * 10000
|-
| 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.

{
"channel":"24e67e0d-1cad-4cc0-9e7a-f8523ef460fe",
"depth":{
"currency":"USD",
"item":"BTC",
"price":"14.43",
"price_int":"1443000",
"type":1,
"type_str":"ask",
"volume":"-2.71",
"volume_int":"-271000000"
},
"op":"private",
"origin":"broadcast",
"private":"depth"
}

:{| 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 * 10000
|-
| 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 * 10000
|-
| ||
|-
| ||

|}

====Order update (private)====

{"channel":"(partial key)","op":"private","order_upd":{"amount":1000,"darkStatus":0,"date":1302836027,"oid":"(oid)","price":0.9899,"status":1},"origin":"broadcast","private":"order_upd"}

:order_upd cointains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || change in volume of the order
|-
| darkStatus ||
|-
| oid || ID of the affected order
|-
| price ||
|-
| status ||
|}

MtGox/API

2011-07-10T09:46:44Z

MagicalTux: /* Websocket API */ putting websocket quoted data in pre

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

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

== Legacy API ==
This API is available in <nowiki>https://mtgox.com/code/*</nowiki>, and provides various informations. It also supports making an order, a withdraw, a deposit, etc.

=== Authentication ===
Authentication is performed by posting a username and a password in variables "name" and "pass". Some methods do not require authentication.

=== Methods ===

==== 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.

== Websocket API ==
See: http://forum.bitcoin.org/index.php?topic=5855.0 (will be ported here soon)

===Connecting===

You can connect via: ws://websocket.mtgox.com/mtgox

===Channels===

The websocket will subscribe you to some channels automatically:
{| class="wikitable"
|-
! Channel ID !! Description
|-
| dbf1dee9-4f2e-4a08-8cb7-748919a71b21 || trades (each time a trade happens, you get something here)
|-
| d5f06780-30a8-4a48-a2f8-7ed181b4a13f || the mtgox ticker (lots of updates, with often the same data)
|-
| 24e67e0d-1cad-4cc0-9e7a-f8523ef460fe || depth information in realtime (price + amount + type... type=1=Ask, type=2=Bid)
|}

Additionally each user has a "own" channel which streams informations about orders (new order, deleted order, etc) and trades only the user's trades).

Each message is a JSON-encoded object, with at least "op" element. The "op" element contains the operation to be done (for outgoing messages), or the type of message (for incoming messages).

===Possible outgoing commands===

'''unsubscribe''' Stop receiving messages from a channel (parameter "channel")

===Incoming Data===

====Ticker====
{"channel":"d5f06780-30a8-4a48-a2f8-7ed181b4a13f","op":"private","origin":"broadcast","private":"ticker","ticker":"buy":0.9515,"high":1,"low":0.91,"sell":0.9697,"vol":34349}}

:The '''ticker''' field contains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| buy || lowest bid as float
|-
| sell || highest ask as float
|-
| high || maximum rate since last close as float
|-
| low || minimum rate since last close as float
|-
| vol || traded volume since last close
|}

====Trade====
{"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","tid":"1310279340877902","trade_type":"bid","type":"trade"}}

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || the traded amount in item (BTC), float, deprecated
|-
| amount_int || the traded amount * 10000
|-
| 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.

{"channel":"24e67e0d-1cad-4cc0-9e7a-f8523ef460fe","depth":{"currency":"USD","item":"BTC","price":"14.43","price_int":"1443000","type":1,"type_str":"ask","volume":"-2.71","volume_int":"-271000000"},"op":"private","origin":"broadcast","private":"depth"}

:{| 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 * 10000
|-
| 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 * 10000
|-
| ||
|-
| ||

|}

====Order update (private)====

{"channel":"(partial key)","op":"private","order_upd":{"amount":1000,"darkStatus":0,"date":1302836027,"oid":"(oid)","price":0.9899,"status":1},"origin":"broadcast","private":"order_upd"}

:order_upd cointains the following:

:{| class="wikitable"
|-
! Name !! Value
|-
| amount || change in volume of the order
|-
| darkStatus ||
|-
| oid || ID of the affected order
|-
| price ||
|-
| status ||
|}

MtGox/API

2011-07-10T06:50:09Z

MagicalTux: about websocket API

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

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

== Legacy API ==
This API is available in <nowiki>https://mtgox.com/code/*</nowiki>, and provides various informations. It also supports making an order, a withdraw, a deposit, etc.

=== Authentication ===
Authentication is performed by posting a username and a password in variables "name" and "pass". Some methods do not require authentication.

=== Methods ===

==== 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.

== Websocket API ==
See: http://forum.bitcoin.org/index.php?topic=5855.0 (will be ported here soon)

MtGox/API

2011-07-10T06:49:31Z

MagicalTux: Created page with "The MtGox API provides various methods to access different informations from the market, place orders, and more. Two APIs are available at this point: the HTTP api (availabl..."

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

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

== Legacy API ==
This API is available in <nowiki>https://mtgox.com/code/*</nowiki>, and provides various informations. It also supports making an order, a withdraw, a deposit, etc.

=== Authentication ===
Authentication is performed by posting a username and a password in variables "name" and "pass". Some methods do not require authentication.

=== Methods ===

==== 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.

ID Backup

2011-05-01T09:39:49Z

MagicalTux: Created page with "== Proposal == This is a proposal for a method that would allow generation of bitcoin addresses tied to one's identity, and not to stored data. This would in theory allow someon..."

== Proposal ==

This is a proposal for a method that would allow generation of bitcoin addresses tied to one's identity, and not to stored data. This would in theory allow someone to send funds to himself in a way that ensures it will be possible to use those funds at any time in the future.

This should be used by people willing to "save" funds without having to rely on any third party service, and should be implemented in the bitcoin client, and not on a remote site.

== Method ==

The idea is to generate the ECDSA private key not from a random source, but from a SHA256/SHA512 hash of the previous informations, cut to the appropriate format.

=== Data ===

Each string data is prefixed of 2 bytes (little endian) containing their length, and must be represented as UTF-8

* Last Name
* First Names
* Birth name (if not different, skip)
* Birth date in string format (YYYY-MM-DD)
* Birth country (country code, 2 letters)
* Birth city
* Blood type (one of: A, B, AB, O)
* Passphrase (up to the user)
* 8 bytes integer "serial" (little endian), used to generate different keys for a single individual

It is possible to generate multiple addresses for a single individual by incrementing "serial". The software should initially increment "serial" until at least 100 concurrent addresses which have never been broadcasted on the blockchain are found.

=== Analysis ===

This is yet just a proposal, analysis is welcome

Main Page

2011-04-08T13:44:54Z

MagicalTux: adding languages link

{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to [[Bitcoin]] wiki,</div>
<div style="top:+0.2em; font-size:95%;">All your bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles.</div>
'''Improve [[:Category:Stubs|this wiki]] and [[Bitcoin:Contributors Award|earn bitcoins]].'''
|}

| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[http://bitcoin.org Frontpage]</span>
| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[http://bitcoin.org/smf Forum]</span>
| style="width:13%; font-size:120%; padding-right: 40px;" |
* <span class="plainlinks">[irc://irc.freenode.net/bitcoin-dev #bitcoin-dev]</span>
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[http://www.mediawiki.org/wiki/Help:Formatting Help]''' - Documentation on wiki editing.
* '''[[Bitcoin.it Wiki|About]]''' - Information on this site.

[[fr:Accueil]]
[[zh-cn:首页]]
[[es:Página Principal]]
[[it:Pagina principale]]
[[ru:Заглавная страница]]
[[de:Hauptseite]]

__NOTOC____NOEDITSECTION__

Fallback Nodes

2011-04-01T09:32:53Z

MagicalTux: Updating IP for magicaltux bitcoin node

This is a list of nodes which are considered reliable. Nodes from this list which are down for more than 24 hours will be automatically removed and status of each node is displayed and updated every hour by [[User:WikiBot|WikiBot]].

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

The [[Original Bitcoin client]] do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(host theymos.ath.cx |sed s/"^.*has address "//)

=== IP Transactions ===

You can also send [[IP Transactions]] to these nodes. If you include your bitcoin address in the "message" field, you may have your coins back.

=== Tor network ===

To use tor .onion addresses, you need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion

Once you have configured and restarted tor, 192.0.2.2 will connect to ijzt2eeizty3p5xe.onion when accessed through the Tor proxy (and likewise for the other IPs/onions). You can then run Bitcoin with -addnode=192.0.2.2, or even send bitcoins to that IP address. You can use any arbitrary IP addresses with MapAddress, though some of the common non-routable ranges (10.*, 192.168.*) will not work due to a Bitcoin bug. 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

== Nodes list ==

=== IPv4 Nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-01 09:00:09 || ?
|-
| jun.dashjr.org || Lightfoot Hosting || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-01 09:00:09 || ?
|-
| mining.bitcoin.cz || slush || 178.79.147.99 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-01 09:00:09 || No
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-01 09:00:14 || ?
|-
| bitcoin.chrishowie.com || cdhowie || 68.169.45.99 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-01 09:00:14 || No
|-
| btc1.justmoon.net || justmoon || 109.75.176.226 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-01 09:00:14 || Yes
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-01 09:00:14 || Yes
|-
| 217.157.1.202 || kseistrup || 217.157.1.202 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-01 09:00:15 || ?
|-
| zack.home.chrishowie.com || cdhowie || 98.222.140.181 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-01 09:00:15 || No
|-
| 178.63.15.200 || hendi || 178.63.15.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.1]}} || 2011-04-01 09:00:15 || ?
|-
| bitcoin.sipa.be || sipa || 178.18.90.41 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-04-01 09:00:15 || No
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-04-01 09:00:15 || Yes
|-
| fallback1.bitcoin.me.uk || Vladimir || 91.85.220.84 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-01 09:00:19 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-01 09:00:19 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-01 09:00:19 || No
|-
| bitlex.co.cc || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-01 09:00:19 || Yes
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-04-01 09:00:19 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-04-01 09:00:20 || ?
|-
| 84.114.155.197 || sniffy || 84.114.155.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2011-04-01 02:00:04 || Yes
|-
| 173.224.125.222 || MagicalTux [US] || 173.224.125.222 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2011-04-01 06:00:14 || No
|-
| nat.router.dashjr.org || Luke-Jr || 71.1.73.218 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || 2011-04-01 08:00:14 || ?
|-
| bitcoin.samara-lab.ru || m0Ray || 217.16.28.65 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || 2011-04-01 07:00:09 || ?

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-02-11 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-02-11 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-02-11 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-02-11 || Yes
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-02-11 || Yes
|-
| rnam4cxam62nkcyf.onion || BitLex || ? || 2011-02-11 || Yes
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-02-11 || ?
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-02-11 || ?
|-
| h4kklwodpcmo6cbq.onion || ? || ? || 2011-02-11 || ?
|-
| vv6kcfscuntybrzm.onion || ? || ? || 2011-02-11 || ?
|-
| nlnsivjku4x4lu5n.onion || ? || ? || 2011-02-11 || ?
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To accept IP transactions you will have to add the ''-allowreceivebyip'' flag to your command line parameters.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot will connect to your node every hour to check its status and version.

Fallback Nodes

2011-03-08T02:04:27Z

MagicalTux: /* IPv4 Nodes */ re-adding Luke-Jr (attempt to)

This is a list of nodes which are considered reliable. Nodes from this list which are down for more than 24 hours will be automatically removed and status of each node is displayed and updated every hour by [[User:WikiBot|WikiBot]].

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

The [[Original Bitcoin client]] do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(host theymos.ath.cx |sed s/"^.*has address "//)

=== IP Transactions ===

You can also send [[IP Transactions]] to these nodes. If you include your bitcoin address in the "message" field, you may have your coins back.

=== Tor network ===

To use tor .onion addresses, you need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion

Once you have configured and restarted tor, 192.0.2.2 will connect to ijzt2eeizty3p5xe.onion when accessed through the Tor proxy (and likewise for the other IPs/onions). You can then run Bitcoin with -addnode=192.0.2.2, or even send bitcoins to that IP address. You can use any arbitrary IP addresses with MapAddress, though some of the common non-routable ranges (10.*, 192.168.*) will not work due to a Bitcoin bug. 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

== Nodes list ==

=== IPv4 Nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-03-08 02:00:03 || ?
|-
| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-03-08 02:00:03 || ?
|-
| 217.157.1.202 || kseistrup || 217.157.1.202 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-03-08 02:00:03 || ?
|-
| 178.63.15.200 || hendi || 178.63.15.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.1]}} || 2011-03-08 02:00:03 || ?
|-
| lfmcal.dontexist.org || lfm || 75.158.131.108 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.20[.1]}} || 2011-03-08 02:00:04 || Yes
|-
| bitcoin-otc.com || nanotube || 69.163.132.101 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20}} || 2011-03-08 02:00:04 || No
|-
| bitcoin.sipa.be || sipa || 178.18.90.41 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-03-08 02:00:04 || No
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-03-08 02:00:04 || Yes
|-
| fallback.bitcoin.me.uk || Vladimir || 91.85.220.84 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 02:00:04 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 02:00:05 || No
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 02:00:05 || Yes
|-
| 174.120.185.74 || MagicalTux [US] || 174.120.185.74 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 02:00:05 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 02:00:05 || No
|-
| lyasoff.com || ? || 200.35.150.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 02:00:05 || ?
|-
| bitlex.co.cc || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 02:00:05 || Yes
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-03-08 02:00:06 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-03-08 02:00:06 || ?
|-
| nat.router.dashjr.org || Luke-Jr || 71.1.73.218 || {{Table Value No}} || {{Fallback Nodes/Node Old|version=0.3.20[.1]}} || 2011-03-08 02:00:06 || ?


|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-02-11 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-02-11 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-02-11 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-02-11 || Yes
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-02-11 || Yes
|-
| rnam4cxam62nkcyf.onion || BitLex || ? || 2011-02-11 || Yes
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-02-11 || ?
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-02-11 || ?
|-
| h4kklwodpcmo6cbq.onion || ? || ? || 2011-02-11 || ?
|-
| vv6kcfscuntybrzm.onion || ? || ? || 2011-02-11 || ?
|-
| nlnsivjku4x4lu5n.onion || ? || ? || 2011-02-11 || ?
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To accept IP transactions you will have to add the ''-allowreceivebyip'' flag to your command line parameters.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot will connect to your node every hour to check its status and version.

Fallback Nodes

2011-03-08T01:29:04Z

MagicalTux: /* IPv4 Nodes */ Adding Luke-Jr node

This is a list of nodes which are considered reliable. Nodes from this list which are down for more than 24 hours will be automatically removed and status of each node is displayed and updated every hour by [[User:WikiBot|WikiBot]].

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

The [[Original Bitcoin client]] do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(host theymos.ath.cx |sed s/"^.*has address "//)

=== IP Transactions ===

You can also send [[IP Transactions]] to these nodes. If you include your bitcoin address in the "message" field, you may have your coins back.

=== Tor network ===

To use tor .onion addresses, you need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion

Once you have configured and restarted tor, 192.0.2.2 will connect to ijzt2eeizty3p5xe.onion when accessed through the Tor proxy (and likewise for the other IPs/onions). You can then run Bitcoin with -addnode=192.0.2.2, or even send bitcoins to that IP address. You can use any arbitrary IP addresses with MapAddress, though some of the common non-routable ranges (10.*, 192.168.*) will not work due to a Bitcoin bug. 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

== Nodes list ==

=== IPv4 Nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-03-08 01:00:02 || ?
|-
| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-03-08 01:00:03 || ?
|-
| 217.157.1.202 || kseistrup || 217.157.1.202 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-03-08 01:00:03 || ?
|-
| 178.63.15.200 || hendi || 178.63.15.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.1]}} || 2011-03-08 01:00:04 || ?
|-
| lfmcal.dontexist.org || lfm || 75.158.131.108 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.20[.1]}} || 2011-03-08 01:00:06 || Yes
|-
| bitcoin-otc.com || nanotube || 69.163.132.101 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20}} || 2011-03-08 01:00:06 || No
|-
| bitcoin.sipa.be || sipa || 178.18.90.41 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-03-08 01:00:06 || No
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-03-08 01:00:06 || Yes
|-
| fallback.bitcoin.me.uk || Vladimir || 91.85.220.84 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 01:00:06 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 01:00:07 || No
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 01:00:07 || Yes
|-
| 174.120.185.74 || MagicalTux [US] || 174.120.185.74 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 01:00:07 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 01:00:07 || No
|-
| lyasoff.com || ? || 200.35.150.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 01:00:08 || ?
|-
| bitlex.co.cc || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-03-08 01:00:08 || Yes
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-03-08 01:00:09 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-03-08 01:00:09 || ?
|-
| nat.router.dashjr.org || Luke-Jr

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-02-11 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-02-11 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-02-11 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-02-11 || Yes
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-02-11 || Yes
|-
| rnam4cxam62nkcyf.onion || BitLex || ? || 2011-02-11 || Yes
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-02-11 || ?
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-02-11 || ?
|-
| h4kklwodpcmo6cbq.onion || ? || ? || 2011-02-11 || ?
|-
| vv6kcfscuntybrzm.onion || ? || ? || 2011-02-11 || ?
|-
| nlnsivjku4x4lu5n.onion || ? || ? || 2011-02-11 || ?
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To accept IP transactions you will have to add the ''-allowreceivebyip'' flag to your command line parameters.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot will connect to your node every hour to check its status and version.

Manaty

2011-03-06T04:17:16Z

MagicalTux: fix extra space

[[File:Logo.png|200px|thumb|right]]

'''Manaty''' is a French based freelance software development company created in 2006, specialized in Business System Solutions (BSS) software, mainly for the telecom industry.

'''Manaty''' represents an international team of highly-skilled and devoted developers, architects, project leaders and testers deployed in 8 countries all over the world (France, Lithuania, USA, Morocco, Malaysia, Philippines, China, Argentina). The freelance working model allows for an ability to operate 24/7 internationally and to create cost-efficient, high-quality BSS software.

<br />

'''New Product:'''
* '''MEVEO''' - Event-based Billing System ('''Open source''', web-based)
:* Modules: Catalog Management, Users and Accounts Management, Back Office, Self Care, Mediation, Rating, Billing, Invoicing, ...

<br />

'''Products:'''
* MVNO BSS Platform
* M2M BSS Platform
* E-commerce Platform
* Custom Development (JAVA, .NET, PHP, C/C++, mobile, FLEX)

[http://www.manaty.net More information]

User talk:Casascius

2011-02-22T02:47:54Z

MagicalTux: /* Tonal & Radial bitcoins */ (fixing typo)

Please provide me a BitCoin address so I can reimburse for your [https://en.bitcoin.it/w/index.php?title=Script&curid=106&diff=1746&oldid=1743 change that I appreciate]. [[User:Luke-jr|Luke-jr]] 20:21, 11 January 2011 (GMT)

== Tonal & Radial bitcoins ==

Hello, I noticed your contributions to the tonal bitcoin page. While it is perfectly fine for you to disagree with tonal bitcoin and to explain how tonal bitcoin may be more confusing than helping for most people, the way you did it was closer to trolling than contributing. The goal of this wiki is to let everyone contribute and provide neutral informations. Anyway has you have proven to be unable to contribute neutral informations about tonal bitcoins, I'd recommend you just ignore this subject. [[User:MagicalTux|MagicalTux]] 02:47, 22 February 2011 (GMT)

User talk:Casascius

2011-02-22T02:47:43Z

MagicalTux: /* Tonal & Radial bitcoins */ new section

Please provide me a BitCoin address so I can reimburse for your [https://en.bitcoin.it/w/index.php?title=Script&curid=106&diff=1746&oldid=1743 change that I appreciate]. [[User:Luke-jr|Luke-jr]] 20:21, 11 January 2011 (GMT)

== Tonal & Radial bitcoins ==

Hello, I noticed your contributions to the tonal bitcoin page. While it is perfectly fine for you to disagree with tonal bitcoin and to explain how tonal bitcoin may be more confusing than helping for most people, the way you did it was closer to trolling than contributing. The goal of this wiki is to let everyone contribute and provide neutral informations. Anyway has you have proven to be unable to contribute neutral informations about tonal bitcoins, I'd recommand you just ignore this subject. [[User:MagicalTux|MagicalTux]] 02:47, 22 February 2011 (GMT)

Chariottrading.com

2011-02-17T08:29:21Z

MagicalTux: fix link

The Chariot Trading Company specializes in trading precious metals, base metals, and rare coins.

T majority of tradings are through online auctions on Webstore.com and ebay.

Bitcoin is now accepted as payment method for some of the items traded.

==External links==
* [http://www.chariottrading.com/index.html Official website]

Nanaimo Gold

2011-02-17T08:26:29Z

MagicalTux: fix link

An operation by Shane Smith, is an independent business operator, located in Nanaimo BC Canada.

It is an exchange between an individual and the operator.

==Currency type:==
* Bitcoin
* Pecunix
* Liberty Reserve
* c-gold
* HD-Money
==Accept payment by:==
* Western Union Money Transfer
* Moneygram Express
* Canada Post Money Order
* Western Union Money Order
* Cash by mail or visit his office

==External links==
* [http://www.nanaimogold.com/ Official website]

Bitlex.co.cc

2011-02-17T08:23:41Z

MagicalTux: fixed link

Trade between bitcoin and Linden dollar (L$), the virtual currency used internally in the virtual world Second Life® (SL).

Linden dollar (L$) for bitcoins on an automated, HUD based system. However, sale of bitcoins for L$ is not automatic yet.

==External links==
* [http://Bitlex.co.cc/ Official website]
* [http://secondlife.com/ Second Life]

Bitcoin 2 Credit Card

2011-02-17T08:23:18Z

MagicalTux: fix link

Exchange bitcoin for a virtual VISA® credit cards.

A virtual credit card is a credit card without the physical plastic card. Buyer will get the card number, expiry, and other relevant details. The virtual can be used to make purchases such as online and telephone purchases where a physical plastic card isn't required.

Site is operated by Madhatter (from the Bitcoin forums), who also operate the [[Bitcoin4cash.com]].

==External links==
* [http://www.Bitcoin2cc.com/ Official website]

Gavin Andresen

2011-02-17T03:41:15Z

MagicalTux: changed page to be a redirect

#REDIRECT [[User:Gavinandresen]]

QBitcoin

2011-02-17T03:37:09Z

MagicalTux: adding link to see how much was received

QBitcoin is a Qt-based C++ bitcoin client written to provide a better API and internals.

Current version: ''None'' (status: coding)

Support address: [http://blockexplorer.com/q/getreceivedbyaddress/1MGQF37NYdpGnPdJXKksb4uHCQSSJrL86R 1MGQF37NYdpGnPdJXKksb4uHCQSSJrL86R]

== Structure ==

* [[QBitcoin Wallet|Wallet]]: a separate process (maybe a separate binary) that will handle wallet operations through a dedicated line (create address, delete address, etc)
* CORE: The bitcoin core itself, handling P2P connections/etc
* CLI: A cli version of bitcoin with optional interactive terminal
* GUI: The GUI
* API Client: a really simple program that will send commands over JSON-RPC or binary api, will also be made available in various languages such as C/C++/PHP and whatever people feel like contributing
* Miners: the client should be compatible with most common bitcoin miners, however I'll try to at least provide an example CPU miner using the binary API

== Features ==

=== Version 0.1.0 ===

'''Please note''': this version is planned for mid-january 2011

* API/GUI/CORE: Use Qt API, for networking and GUI. The CLI version will also depend on Qt (just not on QtGui, so no depency on X/etc)
* CORE: No included miner (instead we may have an external miner)
* API: JSON-RPC api compatible with existing API, both in CLI and GUI versions (can be disabled)
* API: binary api for faster calls (useful for gpu miners, for example)
* API: Improved API functions (in both binary & JSON-RPC) for coins manipulation
* CORE: OpenSSL optional, only if you want to enable API SSL (uses Qt's dynamic linking to openssl for binary version, compiling yourself will * depend on how you configured Qt)
* CORE: DB format will be sqlite3 (using QtSql, except for the wallet)
* CORE: Wallet DB will be handled by a separate process using a limited internal API (protects the wallet against unauthorized accesses). Also this process will not depend on any external library (everything will be compiled in). The following components will be compiled in:
** sqlite3 library (public domain) for wallet database handling
** libtomcrypt/libtommath (public domain/WTFPL) for bitcoin address handling/generation/signing/etc and PRNG (fortuna)
* API/GUI: Automatic update process for binary builds (disabled if compiled from source). Updates will be signed using a RSA key known to the client (or maybe an EC key? to be defined)
* CORE/API/GUI: Support for multiple chains/wallets in same process (ie. access testnet without starting another bitcoin client)
* API/GUI: Fee setting interface (configure your own fees as you wish)
* GUI: Better transactions listing
* GUI: Ability to re-order history columns
* GUI: Documentation
* WALLET: Private key password encryption (AES256), makes the wallet require a password to sign a transaction

=== Future ===

* API/GUI: Ability to choose which addresses to send coins from
* CORE: Support for loadable plugins (bitDNS, etc)
* CORE: [http://en.wikipedia.org/wiki/Internet_Gateway_Device_Protocol uPnP support]
* CORE: Port randomization
* CORE: Append [http://www.shoup.net/papers/iso-2_1.pdf ECIES] encrypted messages to transactions
* GUI: Bitcoin URL support

[[Category:Clients]]

User talk:Nefario

2011-02-17T03:33:53Z

MagicalTux:

== Chinese translation ==

Hi, it seems you have tried to add chinese content, however it is not the right way to do that. Would you confirm you want to work on a chinese wiki? If so we can create zh-tw (I guess that's the corresponding POSIX language for zh-hans) version. Would that be OK with you? [[User:MagicalTux|MagicalTux]] 19:14, 2 January 2011 (GMT)
: Hi, you translated the english [[FAQ]] to chinese by mistake. I've reverted your changes and copied your content to [[:zh-cn:FAQ]]. [[User:MagicalTux|MagicalTux]] 03:29, 17 February 2011 (GMT)
:: Also fixed pages [[Buying bitcoins]] (moved to [[:zh-cn:购买bitcoins]]) and [[Getting started]] (not moved since I don't know the chinese title, content at [https://en.bitcoin.it/w/index.php?title=Getting_started&oldid=3819]. [[User:MagicalTux|MagicalTux]] 03:33, 17 February 2011 (GMT)

Help:Installing Bitcoin Core

2011-02-17T03:31:54Z

MagicalTux: Reverted edits by Nefario (talk) to last revision by Genjix

An account can effortlessly be created using an [[eWallet]] service. eWallet services provide an online wallet to hold your bitcoins.

This guide covers installing Bitcoin without needing a third party wallet service.

== For Windows computers ==

=== Installation ===
[http://sourceforge.net/projects/bitcoin/ Download] and install Bitcoin.

[[File:Install fin.png|frame|none|Complete installation wizard]]

=== Initialization ===

The first time you run Bitcoin, it needs to download all the blocks to setup. You already have your bitcoin address at this point, but you won't see any transactions before the initialisation is complete (it can take from half to a few hours).

[[File:First time run fin.png|frame|none|Bitcoin is initialising by establishing a connection to other clients and downloading the blocks.]]

[[File:Bitcoin all blocks fin.png|frame|none|Completed download of block-chain.]]

Your address (you can have as many as you want) is at the top. Below is your balance which will be zero. The list below shows your transactions.

== For Mac computers ==

Download the [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.19/bitcoin-0.3.19-macosx.zip/download OS X version] of Bitcoin and expand the archive.

[[File:BcOSX.png|thumb|none|Contents of the Bitcoin archive after expansion]]

Drag the Bitcoin icon to the desired install location, and double-click or Cmd-O (⌘O) to run the application. The Bitcoin window will open and connections will start up in minutes. The blocks will begin downloading. Your address and balance are at the top of the window. Click "Copy to Clipboard" to copy your address. Transactions are displayed in the main window.

[[File:BcOSXrunning.png|thumb|none|Main window]]

As Bitcoin currently does not support hiding with Cmd-H (⌘H), it is recommended that users tick the "Minimize on close" option in the Preferences menu to prevent accidental program exits.

[[File:BcOSXPreferences.png|thumb|none|Preferences window on OS X]]

== Getting my first coins ==

The [[Bitcoin Faucet]] [https://freebitcoins.appspot.com/ website] currently hands out 0.05 BTC to new bitcoin users. Fill in the form with your bitcoin address. When you wish to add more, view [[Buying bitcoins]].

[[File:Get some btc.png|frame|none|Getting free coins from the Faucet]]

A new entry should appear in Bitcoin. The network hasn't yet confirmed it, but you know it's being processed. After about one hour it should get 6 confirmations. You are able to spend the coins when there is only one confirmation.

The confirmation counter (like the block counter) will increase by one roughly every 10 minutes. Six confirmations are considered as 100% sure a transfer has been processed.

[[File:First btc recv.png|frame|none]]

[[File:Six confirms bitcoin client.png|frame|none]]

== Points to remember ==

* You don't need to be online to receive BTC.
* You can create as many new addresses as you like. Using a different address each time helps keep you [[Anonymity|anonymous]].
* You can be [[Anonymity|anonymous]] with adequate precautions.
* You cannot send BTC to an invalid address. Typos are not a worry as the payment will refuse to send.
* The wallet file holds the keys that allow spending and thus the computer should be [[Securing_your_wallet|protected]] from the risk of loss and theft.

Proceed to the [[Introduction|introduction]]

== Technical ==
=== Block chain ===
The [[block chain]] is a neverending story of every transaction throughout the network from day 1 (genesis). The first time you run Bitcoin, it is downloaded and verified on your computer. Every new transaction is added to the end of this chain and verified by the network to be valid.

=== Addresses ===
Whenever you send a coin, you are actually sending a cryptographically signed message, associating your coin with the recipient's address. This effectively transfers ownership to to the recipient. Once they own the coin, they are free to transfer it to another person.

A wallet is a collection of addresses. You can create as many new addresses as you wish; having more addresses makes you more anonymous, because then people cannot see how much BTC you received. Your wallet contains the secret keys used for spending that money, and must be [[Securing your wallet|backed-up regularly]]. If you lose the wallet then you no longer possess the money.

=== Generating ===
New coins are minted through generating hashes. These generators are rewarded with a small fee for the computationally intensive task of incorporating your transactions into the block-chain. This fee halves each time 210000 blocks are added to the block chain, or approximately every 4 years. The fee will keep halving until it effectively reaches zero, at which point 21 million coins will be in circulation.

[[Category:Introduction]]

Buying bitcoins

2011-02-17T03:30:31Z

MagicalTux: Undo revision 3815 by Nefario (talk), moved to zh-cn site

One issue currently facing a newcomer to bitcoin is, how do I get some? While there is the [[bitcoin faucet]] that can get you started with a small fraction of a coin, when getting larger amounts the user faces an abundance of choice. This page will cut through the clutter, and help direct you to the right exchanger for your needs.

==Large amounts==

For large amounts of bitcoin (USD 1000 or more), you probably would get the best rate if you deposit funds via bank wire, ACH, Euro bank transfer, or via [[Liberty Reserve]] into a major exchange. The following exchanges are currently available that take currency deposits:

* [[MtGox]]
* [[Bitcoin Central]]
* [[Btcex]]
* Other [[:Category:Exchanges|Exchanges]]

==Small amounts==

For smaller amounts, bank transfer fees or Liberty Reserve conversion fees are usually too expensive. Thus other methods are usually a better choice. The following exchanges will enable you to acquire smaller amounts of bitcoin at reasonable rates:

* [[CoinPal]] accepts [[PayPal]] for purchases of small lots of bitcoin.
* [[Bitcoin 4 Cash]] will sell you bitcoins in exchange for cash in the mail.
* [[Bitcoin Morpheus]] will sell you bitcoins for PayPal, check, money order or cash in the mail.
* [[bitcoin-otc]] IRC trading marketplace will usually have people willing to deal for small and larger amounts using various payment methods, including [[PayPal]], [[Dwolla]], [[Linden Dollars]], etc.

==eWallet==

Some [[:Category:Services|services]] hold your bitcoins in an [[eWallet]] and provide funding methods.

* [[YouTipIt]] Add funds with PayPal.

==See Also==

* [[:Category:Digital_currencies|Digital Currencies]]

[[Category:Exchanges]]
[[Category:Introduction]]
[[zh-cn:购买bitcoins]]

User talk:Nefario

2011-02-17T03:29:34Z

MagicalTux:

Help:FAQ

2011-02-17T03:28:27Z

MagicalTux: moved chinese translation to zh-cn, added a language link

Here you will find answers to the most commonly asked questions.

== General ==
=== What are bitcoins? ===
Bitcoins or coins are the main unit of currency of the Bitcoin system. A commonly used shorthand for bitcoins is “BTC” to refer to a price in Bitcoins (eg: “100 BTC”)
A Bitcoin isn't actually a 'thing' you can point at. It is just a number associated with a [[Address|Bitcoin Address]]. See also an [[Introduction|easy intro]] to bitcoin.

=== How are new Bitcoins created? ===

[[File:total_bitcoins_over_time_graph.png|thumb|Number of bitcoins over time, assuming a perfect 10-minute interval.]]
New coins are generated by a network node each time it finds the solution to a certain mathematical problem (i.e. creates a new [[block]]), which is difficult to perform and can demonstrate a [[proof of work]]. The reward for solving a block is [[controlled inflation|automatically adjusted]] so that in the first 4 years of the Bitcoin network, 10,500,000 coins will be created. The amount is halved each 4 years, so it will be 5,250,000 in years 4-8, 2,625,000 in years 8-12 and so on. Thus the total number of coins will approach 21,000,000 over time.

In addition, built into the network is a system that attempts to allocate new coins in blocks about every 10 minutes, on average, somewhere on the network. As the number of people who are using the Bitcoin software to attempt to generate these new coins changes, the difficulty of creating new coins changes. This happens in a manner that is agreed upon by the network as a whole, based upon the time taken to generate the previous 2016 blocks. The difficulty is therefore related to the average computing resources devoted to generate these new coins over the time it took to create these previous blocks. The likelihood of somebody "discovering" one of these blocks is based on the computer they are using compared to all of the computers also generating blocks on the network.

=== What's the current total amount of Bitcoins in existence? ===

[http://blockexplorer.com/q/totalbc Current count]

The number of blocks times the coin value of a block is the number of coins in existence. The coin value of a block is 50 BTC for each of the first 210,000 blocks, 25 BTC for the next 210,000 blocks, then 12.5 BTC, 6.25 BTC and so on.

=== How divisible are Bitcoins? ===

Technically, a Bitcoin can be divided down to 8 decimals using existing data structures, so 0.00000001 BTC is the smallest amount currently possible. Discussions about and ideas for ways to provide for even smaller quantities of Bitcoins may be created in the future if the need for them ever arises. For convenience, the program currently accepts only 2 decimal places as quantities smaller than 0.01 BTC are considered of trivial value and are usually used only to attack the network.

=== How does the halving work when the number gets really small? ===

The reward will go from 0.00000001 to 0. Then no more coins will likely be created.

The calculation is done as a right bitwise shift of a 64-bit signed integer. The integer is equal to the number of Bitcoins * 100,000,000. This is how all Bitcoin balances/values are stored internally.

Keep in mind that using current rules this will take nearly 100 years before it becomes an issue and Bitcoins may change considerably before that happens.

=== How long will it take to generate all the coins? ===

The last block that will generate coins will be block #6,929,999. This should be generated around year 2140. Then the total number of coins in circulation will remain static at 20,999,999.9769.

Even if the allowed precision is expanded from the current 8 decimals, the total BTC in circulation will always be slightly below 21 million (assuming everything else stays the same). For example, with 16 decimals of precision, the end total BTC would be 20999999.999999999496.

=== If no more coins are going to be generated, will more blocks be created? ===

Absolutely! Even before the creation of coins ends, the use of [[transaction fee|transaction fees]] will likely make creating new blocks more valuable from the fees than the new coins being created. When coin generation ends, what will sustain the ability to use bitcoins will be these fees entirely. There will be blocks generated after block #6,929,999, assuming that people are still using Bitcoins at that time.

== Networking ==

=== Do I need to configure my firewall to run bitcoin? ===

Bitcoin will connect to other nodes, usually on tcp port 8333. You will need to allow outgoing TCP connections to port 8333 if you want to allow your bitcoin client to connect to many nodes. Bitcoin will also try to connect to IRC (tcp port 6667) to meet other nodes to connect to.

If you want to restrict your firewall rules to a few ips and/or don't want to allow IRC connection, you can find stable nodes in the [[Fallback Nodes|fallback nodes list]].

[[zh-cn:FAQ]]
[[fr:FAQ]]
{{fromold|bitcoins}}

[[Category:Technical]]
[[Category:Vocabulary]]