Bitcoin Wiki - User contributions [en]

List of address prefixes

2024-01-07T21:13:17Z

Wargo: Updated links

Blockchain-based currencies use encoded strings, which are in a [[Base58Check encoding]] with the exception of [[Bech32]] encodings. The encoding includes a prefix (traditionally a single ''version byte''), which affects the leading symbol(s) in the encoded result. The following is a list of some prefixes which are in use in the reference Bitcoin codebase.<ref>https://github.com/bitcoin/bitcoin/blob/26.x/src/kernel/chainparams.cpp#L144-L146</ref><ref>https://github.com/bitcoin/bitcoin/blob/26.x/src/kernel/chainparams.cpp#L250-L252</ref><ref>https://github.com/bitcoin/bitcoin/blob/26.x/src/kernel/chainparams.cpp#L516-L518</ref>

{| class="wikitable"
|-
!Decimal prefix
!Hex
!Example use
!Leading symbol(s)
!Example
|-
|0
|00
|Pubkey hash ([[Transaction#Pay-to-PubkeyHash|P2PKH address]])
|1
|<tt>17VZNX1SN5NtKa8UQFxwQbFeFc3iqRYhem</tt>
|-
|5
|05
|Script hash ([[Pay to script hash|P2SH address]])
|3
| <tt>3EktnHQD7RiAE6uzMj2ZifT9YgRrkSgzQX</tt>
|-
|128
|80
|Private key ([[Wallet import format|WIF]], uncompressed pubkey)
|5
|<tt>5Hwgr3u458GLafKBgxtssHSPqJnYoGrSzgQsPwLFhLNYskDPyyA</tt>
|-
|133
|80
|Private key ([[Wallet import format|WIF]], uncompressed pubkey, Electrum-defined<ref name="electrum-300-wif">[https://github.com/spesmilo/electrum/blob/3.0.0/RELEASE-NOTES#L42]</ref> and now deprecated<ref name="electrum-310-wif">[https://github.com/spesmilo/electrum/blob/3.1.0/RELEASE-NOTES#L58]</ref>)
|5
|<tt>5TfQjD9DLFeUFmDiDrzsdtSGQss93o4pvsmQcgmjfcQVLsEgAoM</tt>
|-
|128
|80
|Private key ([[Wallet import format|WIF]], compressed pubkey)
|K ''or'' L
|<tt>L1aW4aubDFB7yfras2S1mN3bqg9nwySY8nkoLmJebSLD5BWv3ENZ</tt>
|-
|129-134
|80
|Private key ([[Wallet import format|WIF]], compressed pubkey, Electrum-defined<ref name="electrum-300-wif" /> and now deprecated<ref name="electrum-310-wif" />)
|L
|<tt>LkUevPi661korFvRdQQUkEX35rA484oAwzsT93383q6mUqVe5cw2</tt>
|-
|135
|80
|Private key ([[Wallet import format|WIF]], compressed pubkey, Electrum-defined<ref name="electrum-300-wif" /> and now deprecated<ref name="electrum-310-wif" />)
|L ''or'' M
|<tt>M3dv4iRtSKb5oHwxjZCGLai1aiZMnuLdGt7iFwjK2ncC3Vu7tRwP</tt>
|-
|4 136 178 30
|0488B21E
|[[BIP 0032|BIP32]] pubkey
|xpub
|<tt>xpub661MyMwAqRbcEYS8w7XLSVeEsBXy79zSzH1J8vCdxAZningWLdN3
zgtU6LBpB85b3D2yc8sfvZU521AAwdZafEz7mnzBBsz4wKY5e4cp9LB</tt>
|-
|4 136 173 228
|0488ADE4
|BIP32 private key
|xprv
|<tt>xprv9s21ZrQH143K24Mfq5zL5MhWK9hUhhGbd45hLXo2Pq2oqzMMo63o
StZzF93Y5wvzdUayhgkkFoicQZcP3y52uPPxFnfoLZB21Teqt1VvEHx</tt>
|-
|111
|6F
|Testnet pubkey hash
|m ''or'' n
|<tt>mipcBbFg9gMiCh81Kj8tqqdgoZub1ZJRfn</tt>
|-
|196
|C4
|Testnet script hash
|2
|<tt>2MzQwSSnBHWHqSAqtTVQ6v47XtaisrJa1Vc</tt>
|-
|239
|EF
|Testnet Private key ([[Wallet import format|WIF]], uncompressed pubkey)
|9
|<tt>92Pg46rUhgTT7romnV7iGW6W1gbGdeezqdbJCzShkCsYNzyyNcc</tt>
|-
|239
|EF
|Testnet Private key ([[Wallet import format|WIF]], compressed pubkey)
|c
|<tt>cNJFgo1driFnPcBdBX8BrJrpxchBWXwXCvNH5SoSkdcF6JXXwHMm</tt>
|-
|4 53 135 207
|043587CF
|Testnet BIP32 pubkey
|tpub
|<tt>tpubD6NzVbkrYhZ4WLczPJWReQycCJdd6YVWXubbVUFnJ5KgU5MDQrD9
98ZJLNGbhd2pq7ZtDiPYTfJ7iBenLVQpYgSQqPjUsQeJXH8VQ8xA67D</tt>
|-
|4 53 131 148
|04358394
|Testnet BIP32 private key
|tprv
|<tt>tprv8ZgxMBicQKsPcsbCVeqqF1KVdH7gwDJbxbzpCxDUsoXHdb6SnTPY
xdwSAKDC6KKJzv7khnNWRAJQsRA8BBQyiSfYnRt6zuu4vZQGKjeW4YF</tt>
|-
|
|
|Bech32 pubkey hash or script hash
|bc1
|<tt>bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4</tt>
|-
|
|
|Bech32 testnet pubkey hash or script hash
|tb1
|<tt>tb1qw508d6qejxtdg4y5r3zarvary0c5xw7kxpjzsx</tt>
|}

Note that private keys for compressed and uncompressed bitcoin public keys use the same version byte. The reason for the compressed form starting with a different character is because a 0x01 byte is appended to the private key before base58 encoding.

The following table shows the leading symbol(s) and address length(s) for 160 bit hashes for each of the possible decimal version values:

{| class="wikitable"
|-
!Decimal version
!Leading symbol
!Address length
|-
|0
|1
|up to 34
|-
|1
|Q-Z, a-k, m-o
|33
|-
|2
|o-z, 2
|33 or 34
|-
|3
|2
|34
|-
|4
|2 or 3
|34
|-
|5-6
|3
|34
|-
|7
|3 or 4
|34
|-
|8
|4
|34
|-
|9
|4 or 5
|34
|-
|10-11
|5
|34
|-
|12
|5 or 6
|34
|-
|13
|6
|34
|-
|14
|6 or 7
|34
|-
|15-16
|7
|34
|-
|17
|7 or 8
|34
|-
|18
|8
|34
|-
|19
|8 or 9
|34
|-
|20-21
|9
|34
|-
|22
|9 or A
|34
|-
|23
|A
|34
|-
|24
|A or B
|34
|-
|25-26
|B
|34
|-
|27
|B or C
|34
|-
|28
|C
|34
|-
|29
|C or D
|34
|-
|30-31
|D
|34
|-
|32
|D or E
|34
|-
|33
|E
|34
|-
|34
|E or F
|34
|-
|35-36
|F
|34
|-
|37
|F or G
|34
|-
|38
|G
|34
|-
|39
|G or H
|34
|-
|40-41
|H
|34
|-
|42
|H or J
|34
|-
|43
|J
|34
|-
|44
|J or K
|34
|-
|45-46
|K
|34
|-
|47
|K or L
|34
|-
|48
|L
|34
|-
|49
|L or M
|34
|-
|50-51
|M
|34
|-
|52
|M or N
|34
|-
|53
|N
|34
|-
|54
|N or P
|34
|-
|55-56
|P
|34
|-
|57
|P or Q
|34
|-
|58
|Q
|34
|-
|59
|Q or R
|34
|-
|60-61
|R
|34
|-
|62
|R or S
|34
|-
|63
|S
|34
|-
|64
|S or T
|34
|-
|65-66
|T
|34
|-
|67
|T or U
|34
|-
|68
|U
|34
|-
|69
|U or V
|34
|-
|70-71
|V
|34
|-
|72
|V or W
|34
|-
|73
|W
|34
|-
|74
|W or X
|34
|-
|75-76
|X
|34
|-
|77
|X or Y
|34
|-
|78
|Y
|34
|-
|79
|Y or Z
|34
|-
|80-81
|Z
|34
|-
|82
|Z or a
|34
|-
|83
|a
|34
|-
|84
|a or b
|34
|-
|85
|b
|34
|-
|86
|b or c
|34
|-
|87-88
|c
|34
|-
|89
|c or d
|34
|-
|90
|d
|34
|-
|91
|d or e
|34
|-
|92-93
|e
|34
|-
|94
|e or f
|34
|-
|95
|f
|34
|-
|96
|f or g
|34
|-
|97-98
|g
|34
|-
|99
|g or h
|34
|-
|100
|h
|34
|-
|101
|h or i
|34
|-
|102-103
|i
|34
|-
|104
|i or j
|34
|-
|105
|j
|34
|-
|106
|j or k
|34
|-
|107-108
|k
|34
|-
|109
|k or m
|34
|-
|110
|m
|34
|-
|111
|m or n
|34
|-
|112-113
|n
|34
|-
|114
|n or o
|34
|-
|115
|o
|34
|-
|116
|o or p
|34
|-
|117-118
|p
|34
|-
|119
|p or q
|34
|-
|120
|q
|34
|-
|121
|q or r
|34
|-
|122-123
|r
|34
|-
|124
|r or s
|34
|-
|125
|s
|34
|-
|126
|s or t
|34
|-
|127-128
|t
|34
|-
|129
|t or u
|34
|-
|130
|u
|34
|-
|131
|u or v
|34
|-
|132-133
|v
|34
|-
|134
|v or w
|34
|-
|135
|w
|34
|-
|136
|w or x
|34
|-
|137-138
|x
|34
|-
|139
|x or y
|34
|-
|140
|y
|34
|-
|141
|y or z
|34
|-
|142-143
|z
|34
|-
|144
|z or 2
|34 or 35
|-
|145-255
|2
|35
|}

== References ==
<references />

{{Bitcoin Core documentation}}

Template:Infobox company

2015-12-13T19:21:09Z

Wargo: Do not include defunct companies into main category.

{{Infobox|title={{{name|{{{title|{{PAGENAME}}}}}}}}|image={{{image|}}}|caption1={{{caption|}}}
|content1=Trading name|data1={{{trading_name|}}}
|content2=Native name|data2={{{native_name|}}}
|content3=Traded as|data3={{{traded_as|}}}
|content4=Industry|data4={{{industry|}}}
|content5=Founded|data5={{{foundation|}}}
|content6=Defunct|data6={{{defunct|}}}
|content7=Headquarters|data7={{{location|}}}
|content8=Founder(s)|data8={{{founder|}}}
|content9=Key people|data9={{{keypeople|{{{owner|}}}}}}
|content10=Members|data10={{{members|}}}
|content11=Parent|data11={{{parent|}}}
|content12=Subsidiaries|data12={{{subsidiaries|}}}
|content16=Revenue|data16={{#if:{{{revenue_year|}}}|{{{revenue_btc|}}} BTC ({{{revenue_year}}}) {{{revenue_usd|}}} USD ({{{revenue_year}}})|}}
|content17=Operating income|data17={{#if:{{{oi_year|}}}|{{{oi_btc|}}} BTC ({{{oi_year}}}) {{{oi_usd|}}} USD ({{{oi_year}}})|}}
|content18=Net income|data18={{#if:{{{ni_year|}}}|{{{ni_btc|}}} BTC ({{{ni_year}}}) {{{ni_usd|}}} USD ({{{ni_year}}})|}}
|content19=Total assets|data19={{{assets|{{#if:{{{assets_year|}}}|{{{assets_btc|}}} BTC ({{{assets_year}}}) {{{assets_usd|}}} USD ({{{assets_year}}})|}}}}}
|content20=Total equity|data20={{#if:{{{equity_year|}}}|{{{equity_btc|}}} BTC ({{{equity_year}}}) {{{equity_usd|}}} USD ({{{equity_year}}})|}}
|content21=Employees|data21={{{employees|}}}
|content22=Trading pairs|data22={{{pairs|}}}
|content24=Website|data24={{{website|}}}
|foot={{{bottom|}}}{{SocialMedia|facebook={{{facebook|}}}|btctid={{{btctid|{{{bitcointalk|}}}}}}|subreddit={{{subreddit|}}}|twitter={{{twitter|}}}|youtube={{{youtube|}}}|bitcoinwiki={{{bitcoinwiki|}}}}}
}}<includeonly>{{#if:{{{defunct|}}}|[[Category:Defunct companies]]|[[Category:Companies]]}}</includeonly>

Category:Defunct companies

2015-12-13T19:13:39Z

Wargo: Created category

Companies that do not longer exists. It may take place due to bankrupcy, hacking, scams or resignation.
[[Category:Companies]]

Goxxed

2015-12-13T19:11:11Z

Wargo:

Goxxed is a loose slang term started in the Bitcoin community. It is a derogatory term and references [[Mt. Gox]]. In February 2014, the once largest Bitcoin Exchange in the world, Mt. Gox went offline and filed bankruptcy proceedings thereafter. However before that event they had removed bitcoin withdrawals from their platform. This event happened roughly 9 months following their Fiat Withdrawals being frozen. Many members of the Bitcoin Community lost trust and favor with Mt. Gox after those actions, and many members resorted to selling their 'Gox Coins' for reduced value in efforts to retrieve liquidity that was locked in the site) This category has been created to assign all to all BTC companies that have been shut down, filed for bankruptcy or no longer continue operations.

[[Category:Mt._Gox]]

User talk:Unichange.me

2015-12-13T19:09:02Z

Wargo: Unneeded redirect

CoinTouch

2015-12-13T19:07:53Z

Wargo:

'''[https://www.cointouch.com/ CoinTouch]''' is a London-based decentralised [[Bitcoin]] [[Exchanges|exchange]]. The service finds connections on Facebook and/or Google+ who trade cryptocurrency.<ref name=bitcoinmagazine/> By allowing direct trading between users, CoinTouch helps avoid the risk of storing cash or bitcoins with a centralised exchange.<ref name=bitcoinmagazine/> CoinTouch does not charge fees, and registration is a simple, one-click process.

==History==

CoinTouch launched on January 29, 2014 for bitcoin trading. <ref>{{cite web | archiveurl=http://web.archive.org/web/20140129122820/http://www.cointouch.com/ | archivedate=January 29, 2014 | url=http://www.cointouch.com/ | publisher=CoinTouch | title=CoinTouch}}</ref>

On March 12, 2014, CoinTouch added support for a number of [[Altcoin|altcoins]]. <ref>{{cite web | archiveurl=http://web.archive.org/web/20140313170013/https://www.cointouch.com/ | archivedate=March 13, 2014 | url=http://www.cointouch.com/ | publisher=CoinTouch | title=CoinTouch}}</ref>

==References==

<references>
<ref name=bitcoinmagazine>{{cite news|url=http://bitcoinmagazine.com/11308/cointouch-friends-buy-sell-bitcoin/|title = CoinTouch – Do Your Friends Buy and Sell Bitcoin?|last = Hofman|first = Adam|date = March 20, 2014|accessdate = March 20, 2014 | work=Bitcoin Magazine }}</ref>
</references>

==External links==
* [https://www.cointouch.com/ CoinTouch - Find friends of friends that trade crypto currency]
* [http://www.crunchbase.com/company/cointouch CrunchBase Profile]

[[Category:Local]]
[[Category:Directories]]
[[Category:Exchanges]]

Category:Trading

2015-12-13T19:05:33Z

Wargo: Created category

Pages about [[trade|trading]] Bitcoins.

Btc.sx

2015-12-13T19:04:40Z

Wargo: Red links

{{Infobox company
| image = [[File:Btc.sx Logo 2014.png|220px|link=https://btc.sx]]
| type = [[Private company|Private]]
| name = Btc.sx
| trading_name = Btc.sx
| industry=[[Trade | FX Trading]], Brokerage, Financial Services
| location = [[London]]
| foundation = May, 2013
| key_people = Joseph Lee (Founder and [[CEO]]), George Samman (Co-Founder), Vincent Hoong (Co-Founder)
| area_served = Worldwide
| pairs= USD/BTC
| website=https://btc.sx
}}

'''Btc.sx''' is a multinational company that engages in leveraged [[bitcoin]] [[trade | trading]] and [[wikipedia:brokerage|brokerage]]. The company offers a trading platform in [[digital currency]] derivatives such as [[wikipedia:margin trading|margin trading]] to retail traders. It was founded in 2013 and is headquartered in London's Silicon Roundabout. ZDNet reports Btc.sx to be one of the first bitcoin companies that voided the necessity of all other currencies other than Bitcoin.<ref>[http://www.zdnet.com/startup-opens-bitcoin-only-margin-trading-platform-7000019715/ ZDNet - Startup opens Bitcoin-only margin trading platform]</ref> The company was launched from [[wikipedia:Sydney|Sydney]], [[wikipedia:Australia|Australia]], and is run by CEO Joseph Lee who co-founded the company alongside George Samman and Vincent Hoong.<ref>[https://btc.sx/about/team/ | accessdate=2014-08-21 Btc.sx - About the Btc.sx Team]</ref> Shortly after its launch, Lee moved operations to [[London]] favouring a dual incorporation model between [[Wikipedia:Singapore|Singapore]] and [[Wikipedia:United Kingdom|United Kingdom]].<ref>[http://www.afr.com/p/business/enterprise/tech_start_ups_leave_oz_over_tax_YHf6ExICdaRAyopKKiZ2zI Australian Financial Review - Tech start-ups leave Oz over tax]</ref> The company also has operations in [[Wikipedia:New York|New York]].

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

Users of Btc.sx can open long and short positions using the proprietary trading platform. A corresponding buy and sell order is then placed out to market at a matching exchange with or without leverage. All positions opened will have a corresponding position placed out to market meaning that any profits gained or losses generated from market movements will be passed on directly to the client.

===Position Deposits===

Trading at Btc.sx is done on a pre-paid basis. In order to open a position, a deposit is taken which acts as collateral. This collateral will act as an equivalent of a margin call. This is the price at which a position will be automatically liquidated if losses accrue to the deposited amount. The margin call is shown as a stop price when the position is opened. A larger deposit will enable a bigger stop distance to be chosen. This can result in larger losses if the price moves against the desired direction.

===Features===
Leverage - 10:1, 5:1, 2:1 
Volatility Multiplier - 15% 
Execution Type - at best execution over ECN 
Minimum Trade Size - $5 equates to ~$50 Trade at 10:1 
Maximum Trade Size - $1000 equates to ~$10,000 Trade at 10:1<ref>[https://btc.sx/about/fees/ Btc.sx - Trading Fee Schedule]</ref>

==Fees==

===Transaction Fees===

====BTC====

Deposit - zero fees (minimum of 0.001 Btc) 
Withdrawal - zero fees (minimum of 0.001 Btc)

Funds are deposited once 3 [[confirmation|confirmations]] are recieved, this is a process that typically takes 30 minutes.

====USD====

Btc.sx does not accept fiat. All positions deposits are in Bitcoin.

===Trade Fees===

Open and Close - 0.5% 
Gap Losses - zero

==Risk Matrix==

As well as magnifying trading gains, losses can similarly be multiplied. For beginners, it is widely reccomended that trading with a smaller amount of leverage will result in a lower risk whilst learning about the platform while trading. Despite its higher minimum deposit, potential losses will be minimised due to the unlikely nature that a stop limit will be reached.<ref>[https://support.btc.sx/hc/en-gb/articles/201070362-What-is-Leveraged-Trading- Btc.sx - What is Leveraged Trading?]</ref>

{| class="wikitable"
|-
! Leverage || Stop Distance || Risk || Return (Profit or Loss) || Minimum Deposit
|-
| 10:1 || Small || High || High || $5
|-
| 5:1 || Medium || Medium || Medium || $10
|-
| 2:1 || Large || Low || Low || $20
|}

==Reception==

Following the [[Mt. Gox]] collapse, Btc.sx announced a new exchange partnership with [[Bitstamp]] now placing its orders out to market.<ref>[https://btc.sx/news/normal-trading-resumed/ Btc.sx - Normal Trading Resumed]</ref> The trading platform announced in March 2014 the brokerage of over $40m in brokered transactions.<ref>[http://www.coindesk.com/btc-sx-resumes-trading-mt-gox-induced-freeze/ CoinDesk - Bitcoin Derivatives Platform BTC.SX Resumes Trading After Mt Gox-Induced Freeze]</ref>

==Capital investments==

In April 2014, Btc.sx recieved 500 bitcoins from the seed accelerator, [[SeedCoin]] in its first fund raising round.<ref>[http://www.coindesk.com/seedcoin-gives-btc-sx-500-bitcoins-funding/ CoinDesk - Trading Site BTC.SX Receives 500 Bitcoins in Seedcoin Funding Round]</ref> The company has recieved a total of US$0.45 million investment as a result of initial capital injections and its equity fundraising activities.<ref>[http://www.zdnet.com/startup-opens-bitcoin-only-margin-trading-platform-7000019715/ ZDNet - Startup opens Bitcoin-only margin trading platform]</ref>

==Service disruptions==

In February 2014 [[Mt. Gox]] was struck by a theft, it was the world's largest bitcoin exchange and at its peak handled 70% of all bitcoin trades.<ref>[http://blogs.wsj.com/briefly/2014/02/25/5-things-about-mt-goxs-crisis/ 5 things about Mt. Gox's crisis]</ref> The loss of 750,000 bitcoins (at the time worth over $350m) triggered immediate insolvency and caused its subsequent collapse.<ref>[http://www.theguardian.com/technology/2014/feb/25/bitcoin-exchange-mtgox-offline-amid-rumours-of-theft The Guardian - Bitcoin exchange MtGox offline amid rumours of theft]</ref> Following a trading suspension issued by Btc.sx, it was revealed that Btc.sx had partnered with [[Mt. Gox]] to offer its [[wikipedia:brokerage|brokered]] trading service and suffered from undisclosed losses as a result of the collapse.<ref>[http://www.coindesk.com/bitcoin-derivatives-market-btc-sx-suspends-trading-amid-turmoil-partner-mt-gox/ CoinDesk - Bitcoin Derivatives Market Btc.sx Suspends Trading Amid Turmoil at Partner Mt. Gox]</ref>

==Regulation==

Btc.sx operates in a climate of regulatory uncertainty with no specific laws enforced to provide protection to its clients globally. The New York State Department of Financial Services who is overseen by Superintendent Benjamin Lawsky hopes to be the first regulatory body to provide a full framework for [[virtual currency]] businesses.<ref>[http://www.dfs.ny.gov/about/press2014/pr1407171.html New York State Department of Financial Services - NY DFS RELEASES PROPOSED BITLICENSE REGULATORY FRAMEWORK FOR VIRTUAL CURRENCY FIRMS]</ref> The DFS guidelines are percieved by many bitcoin companies to be overbearing with fierce opposition coming from [[Jeremy Allaire]], CEO of bitcoin startup [[Circle (company)|Circle]].<ref>[http://www.coindesk.com/circle-bitlicense-block-new-york-customers/ CoinDesk - Circle: BitLicense Would Force Us to Block New York Customers]</ref>. With operations in New York, the BitLicense regulations will directly affect Btc.sx and similar bitcoin businesses.

==External links==
*[https://btc.sx Official Website: Btc.sx Bitcoin Trading]

==References==
<references />

[[Category:Trading]]

London

2015-12-13T18:59:50Z

Wargo: Delete

{{PfD|Broken redirect}}
#REDIRECT [[United Kingdom]]

TØ

2015-12-13T18:59:32Z

Wargo: Delete

{{PfD|Broken redirect}}
#redirect [[t0]]

Madrid

2015-12-13T18:58:03Z

Wargo: Delete

{{PfD|Broken redirect}}
#REDIRECT [[Spain]]

Moon

2015-12-13T18:56:06Z

Wargo: Delete

{{PfD|Broken redirect}}
#redirect [[November 2013 bubble]]

Paris

2015-12-13T18:55:10Z

Wargo: Delete

{{PfD|Broken redirect}}
#REDIRECT [[France]]

List of Decentralized Autonomous Corporations

2015-12-13T18:53:54Z

Wargo: Delete

{{PfD|Broken redirect. Unneeded, but can point [[Distributed_Autonomous_Community_/_Decentralized_Application|here]]}}
#redirect [[Decentralized Autonomous Corporation]]

Autonomous Application

2015-12-13T18:51:07Z

Wargo: Delete

{{PfD|Broken redirect}}
#REDIRECT [[Decentralized Application]]

Catenography

2015-12-13T18:48:00Z

Wargo: Delete

{{PfD|Broken redirect}}
#redirect [[Block chain archaeology]]

Bruxelles

2015-12-13T18:46:54Z

Wargo: Delete

{{PfD|Broken redirect}}
#REDIRECT [[Belgium]]

Brussel

2015-12-13T18:46:46Z

Wargo: Delete

{{PfD|Broken redirect}}
#REDIRECT [[Belgium]]

Brussels

2015-12-13T18:46:09Z

Wargo: Delete

{{PfD|Broken redirect}}
#REDIRECT [[Belgium]]

Block hashing algorithm

2015-12-12T16:27:58Z

Wargo: Formatting

Bitcoin mining uses the [[hashcash]] proof of work function; the hashcash algorithm requires the following parameters: a service string, a nonce, and a counter. In bitcoin the service string is encoded in the block header data structure, and includes a version field, the hash of the previous block, the root hash of the merkle tree of all transactions in the block, the current time, and the difficulty. Bitcoin stores the nonce in the extraNonce field which is part of the coinbase transaction, which is stored as the left most leaf node in the merkle tree (the coinbase is the special first transaction in the block). The counter parameter is small at 32-bits so each time it wraps the extraNonce field must be incremented (or otherwise changed) to avoid repeating work.
The basics of the hashcash algorithm are quite easy to understand and it is described in more detail [[hashcash|here]].
When mining bitcoin, the hashcash algorithm repeatedly hashes the block header while incrementing the counter & extraNonce fields. Incrementing the extraNonce field entails recomputing the merkle tree, as the coinbase transaction is the left most leaf node. The block is also occasionally updated as you are working on it.

A block header contains these fields:
{| class="wikitable"
|-
! Field
! Purpose
! Updated when...
! Size (Bytes)
|-
|Version
|Block version number
|You upgrade the software and it specifies a new version
|4
|-
|hashPrevBlock
|256-bit hash of the previous block header
|A new block comes in
|32
|-d
|hashMerkleRoot
|256-bit hash based on all of the transactions in the block
|A transaction is accepted
|32
|-
|Time
|Current timestamp as seconds since 1970-01-01T00:00 UTC
|Every few seconds
|4
|-
|Bits
|Current [[target]] in compact format
|The [[difficulty]] is adjusted
|4
|-
|Nonce
|32-bit number (starts at 0)
|A hash is tried (increments)
|4
|}

The body of the block contains the transactions. These are hashed only indirectly through the Merkle root. Because transactions aren't hashed directly, hashing a block with 1 transaction takes exactly the same amount of effort as hashing a block with 10,000 transactions.

The compact format of target is a special kind of floating-point encoding using 3 bytes mantissa, the leading byte as exponent (where only the 5 lowest bits are used) and its base is 256.
Most of these fields will be the same for all users. There might be some minor variation in the timestamps. The nonce will usually be different, but it increases in a strictly linear way. "Nonce" starts at 0 and is incremented for each hash. Whenever Nonce overflows (which it does frequently), the extraNonce portion of the generation transaction is incremented, which changes the Merkle root.

Moreover, it is extremely unlikely for two people to have the same Merkle root because the first transaction in your block is a generation "sent" to one of ''your'' unique Bitcoin addresses. Since your block is different from everyone else's blocks, you are (nearly) guaranteed to produce different hashes. Every hash you calculate has the same chance of winning as every other hash calculated by the network.

Bitcoin uses: SHA256(SHA256(Block_Header)) but you have to be careful about byte-order.

For example, this python code will calculate the hash of the block with the smallest hash as of June 2011, [http://blockexplorer.com/block/00000000000000001e8d6829a8a21adc5d38d0a473b144b6765798e61f98bd1d Block 125552]. The header is built from the six fields described above, concatenated together as little-endian values in hex notation:
<source lang="python">
>>> import hashlib
>>> header_hex = ("01000000" +
"81cd02ab7e569e8bcd9317e2fe99f2de44d49ab2b8851ba4a308000000000000" +
"e320b6c2fffc8d750423db8b1eb942ae710e951ed797f7affc8892b0f1fc122b" +
"c7f5d74d" +
"f2b9441a" +
"42a14695")
>>> header_bin = header_hex.decode('hex')
>>> hash = hashlib.sha256(hashlib.sha256(header_bin).digest()).digest()
>>> hash.encode('hex_codec')
'1dbd981fe6985776b644b173a4d0385ddc1aa2a829688d1e0000000000000000'
>>> hash[::-1].encode('hex_codec')
'00000000000000001e8d6829a8a21adc5d38d0a473b144b6765798e61f98bd1d'
</source>

==Endianess==
Note that the hash, which is a 256-bit number, has lots of leading zero bytes when stored or printed as a big-endian hexadecimal constant, but it has trailing zero bytes when stored or printed in little-endian. For example, if interpreted as a string and the lowest (or start of) the string address keeps lowest significant byte, it is little-endian.

The output of [http://blockexplorer.com blockexplorer] displays the hash values as big-endian numbers; notation for numbers is usual (leading digits are the most significant digits read from left to right).

For another example, [http://pastebin.com/bW3fQA2a here] is a version in plain C without any optimization, threading or error checking.

Here is the same example in plain PHP without any optimization.
<source lang="php">
<?
//This reverses and then swaps every other char
function SwapOrder($in){
$Split = str_split(strrev($in));
$x='';
for ($i = 0; $i < count($Split); $i+=2) {
$x .= $Split[$i+1].$Split[$i];
}
return $x;
}

//makes the littleEndian
function littleEndian($value){
return implode (unpack('H*',pack("V*",$value)));
}

$version = littleEndian(1);
$prevBlockHash = SwapOrder('00000000000008a3a41b85b8b29ad444def299fee21793cd8b9e567eab02cd81');
$rootHash = SwapOrder('2b12fcf1b09288fcaff797d71e950e71ae42b91e8bdb2304758dfcffc2b620e3');
$time = littleEndian(1305998791);
$bits = littleEndian(440711666);
$nonce = littleEndian(2504433986);

//concat it all
$header_hex = $version . $prevBlockHash . $rootHash . $time . $bits . $nonce;

//convert from hex to binary
$header_bin = hex2bin($header_hex);
//hash it then convert from hex to binary
$pass1 = hex2bin( hash('sha256', $header_bin ) );
//Hash it for the seconded time
$pass2 = hash('sha256', $pass1);
//fix the order
$FinalHash = SwapOrder($pass2);

echo $FinalHash;
?>
</source>

[[Category:Technical]]

User:X6763

2015-12-11T20:51:33Z

Wargo: Changed forum link

==Freelance==
I'm avaialble for software development work. I accept both Bitcoins and USD as payment.
* Languages - Clojure, Java, Python, JavaScript
* Web development frameworks - Ring/Compojure, Django, Drupal

==Interests==
* Bitcoin
* Decentralized DNS
* Software development
* Information security
* Android

==Products==
===BitcoinCrypto library===
* Forum post - https://www.bitcointalk.org/index.php?topic=3875.0
* Repository (docs) - https://github.com/x6763/BitcoinCrypto

==Contact==
* email: 0x6763@gmail.com

Contributors Award participant: 12FVT5Kduf6KSXFmGEAetsqxhMk22ngWpu

[[Category:Freelancers]]
[[Category:Freelancers-Software Development]]

Man page

2015-12-11T20:19:07Z

Wargo: Changed forum link

This page is for frequently asked questions that do not yet appear in the main [[FAQ]].

It's also a place for questions in progress, so feel free to ask new questions, or answer and/or refine existing answers.

== Ask your question here: ==
How much electrical energy per transaction is projected?

== Answered Questions ==

=== How does it work (for non-geeks) ===

====Why can't somebody just create a version of the software that gives you extra bitcoins?====

When you spend some bitcoins, the software on your machine has to prove to the software running on everybody else's machine that those bitcoins are valid.

How does it do that? Well, it is a little bit complicated; you've got to understand how bitcoins are created, and how they are traded.

First, how they're created: 25 bitcoins are created approximately every 10 minutes. Everybody who is trying to create bitcoins is in a race to try to find those 25 bitcoins; they are really hard to find, but, once found, it is easy to verify that, yes, indeed, your bitcoin software found them, so you get to spend them.

Second, how they're traded: Imagine you did find 25 bitcoins (well, your computer found them by running the bitcoin software for a few months or a year-- they are not easy to find, and are harder to find the more people who are looking for them). You trade them to me by sending them to my bitcoin address. Inside the software, a messages is created and then broadcast to everybody that says "These 25 bitcoins that we all agree are valid are hereby officially traded to somebody else (me-- well, one of my bitcoin receiving addresses, actually)."

Now I've got them. If you try to trade those same 25 bitcoins to somebody else, it won't work-- everybody running Bitcoin sees all the trades, so if you try to spend the same coins a second time everybody else's software will reject your attempt to cheat.

And that's it-- that's how it works. Bitcoins are scarce because only about 25 are created every ten minutes. And you can't claim to have more than you really have because everybody else can check to see if your coins really were created by the "race" process, or if they were from valid trades.

=== Uncatagorized ===

==== Why did this generation give me more bitcoins than normal (like 25.075)? ====

You collected a [[transaction fee]].

==== Why must users back up their wallets every 100 actions? ====

Bitcoin transactions send bitcoins to a specific public key. A Bitcoin address is an encoded hash of a public key. In order to use received bitcoins, you need to have the private key matching the public key you received with. This is sort of like a super long password associated with an account (public key). Your Bitcoin wallet contains all of the private keys necessary for spending your received transactions. If you delete your wallet without a backup, then you no longer have the authorization information necessary to claim your coins, and the coins associated with those keys are lost forever.

Creating a new address generates a new pair of public and private keys, which are added to your wallet. Each keypair is mostly random numbers, so they cannot be known prior to generation. If you backup your wallet and then create a new address, the keypair associated with the new address will not be in the old wallet because the new keypair is only know ''after'' creating it. Any coins received at this address will be lost if you restore from the backup.

The situation is made somewhat more confusing because the receiving addresses shown in the UI are not the only keys in your wallet. Each Bitcoin generation is given a new public key, and, more importantly, each sent transaction also sends a random number of bitcoins back to yourself at a new key. When sending bitcoins to anyone, you generate a new keypair for yourself and simultaneously send bitcoins to your new public key and the actual recipient's public key. This is an anonymity feature -- it makes tracking Bitcoin transactions much more difficult.

So if you create a backup, send some bitcoins, and then restore from the backup, some bitcoins will be lost. Bitcoin has not deleted any keys (keys are ''never'' deleted) -- it has created a new key that is not in your old backup and then sent bitcoins to it.

To mitigate this problem, the wallet contains a pool of 100 queued keys. When you need an address for whatever reason (send, "new address", generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose bitcoins.

Linux users can setup cron by running 'crontab -e' and adding this line:
01 */1 * * * /usr/local/bin/backupwallet.sh

backupwallet.sh:
<pre>#!/usr/bin/env bash

GPGU="My GPG User"

TS=$(date "+%Y%m%d-%H-%M")

WALLET=/tmp/wallet${TS}
WALLET_E=/tmp/wallet${TS}.crypt

~/bin/bitcoind backupwallet $WALLET
/usr/bin/gpg -r "$GPGU" --output $WALLET_E --encrypt $WALLET
~/bin/s3cmd put $WALLET_E s3://NAME_OF_MY_S3_BUCKET
rm $WALLET $WALLET_E</pre>

The shell script does:
* Call bitcoind backupwallet to create a time/date-stamped wallet file.
* GPG encrypt the wallet with my public key.
* Copy the result to an off-machine backup location.

It's using Amazon S3, which is itself redundantly backed up to multiple geographic locations automatically. Replace the s3cmd with an scp to copy somewhere if you're not an S3 user; you could even ftp somewhere, since the wallet is encrypted it doesn't matter if somebody is eavesdropping

==== How many nodes are there? ====

You can get a rough estimate by counting the number of users on the [irc://irc.lfnet.org/bitcoin #bitcoin] channel at irc.lfnet.org. Most Bitcoin nodes are constantly connected to this channel while running, though Bitcoin can be configured not to do so. A more accurate number can be gotten by running Bitcoin nonstop for a few days and then using [https://github.com/gavinandresen/bitcointools bitcointools] to analyze your addr.dat file. This shows the "last seen" times for ''all'' Bitcoin nodes.

=== Economics ===

==== I've lost my wallet, is there a way to recreate the lost coins in the system? ====
No, coins that are lost are lost forever.
The lost coins will not be recovered or regenerated at any time.

==== Where does the value of Bitcoin stem from? What backs up Bitcoin? ====

Bitcoin has value because it is accepted as payment by many. The initial market value was achieved when people speculated, that because of its properties, the currency would be accepted by others later on.

When we say that a currency is backed up by gold, we mean that there's a promise in place that you can exchange the currency for gold. In a sense, you could say that Bitcoin is "backed up" by the price tags of merchants and currency exchangers - a price tag is a promise to exchange goods for a specified amount of currency. Of course, price tags may or may not be as long-term promises as those made by central banks or governments.

It's a common misconception that Bitcoins gain their value from the cost of electricity required to generate them. Cost doesn't equal value - hiring 1,000 men to shovel a big hole in the ground may be costly, but not valuable. Also, even though scarcity is a critical requirement for a currency to be useful, it alone doesn't make anything valuable. Your fingerprints are scarce, but that doesn't mean they have any exchange value.

At the time of this writing, Bitcoin's chain of proof is the result of over 6 quadrillion cryptographically secure, verified calculations carried out by many independent computers. This large and growing input of energy and technology is part of Bitcoin's value, and represents a substantial investment of resources by Bitcoin users in creating the benefits of a trustworthy medium of exchange.

==== Isn't the minting process a waste of resources? ====

All currencies need a method for regulating the money supply and creating circulation. To make Bitcoin secure, a large amount of computer work is required. The Bitcoin process for introducing new coins into circulation is designed to make the currency secure by encouraging users to perform the necessary computational work by awarding the role of introducing new coins into circulation in rough proportion the amount of computer power contributed to this goal.

=== Technical ===

==== Can generating nodes charge different transaction fees, or is this enforced by the network? ====

Currently a generating node can charge whatever [[transaction fee]] they want. A transaction that doesn't pay the fee won't be included in any blocks produced by that node, but it will appear in later blocks by cheaper generators.

It is [https://bitcointalk.org/index.php?topic=165.msg1595#msg1595 possible] for the network to enforce a fee rate, but this is not currently implemented. If [[Satoshi]] tried to implement this, only ''generating'' nodes would have a vote in whether the change would be accepted, so the change would have to be beneficial in some way to generators (ie, not too low).

==== Does including more transactions in your block slow down your hashing rate? ====

Not at all. You're hashing the block header, which contains only a fixed-size hash of all the transactions.

==== Why is it using so much CPU? ====

If you have "Generate coins" turned on, Bitcoin will calculate millions of [[hash|hashes]] per second in an attempt to solve the current [[block]]. This will use all of your idle CPU time, but Bitcoin runs at a low priority, so none of your other programs should be slowed down. Turning off coin generation should eliminate most CPU usage.

==== Why can't it be doing something useful for humanity instead? ====

[[hash|SHA-256 hashing]] has very specific properties that we need. In particular, it generates (with predictable CPU required) numbers that are for all practical purposes purely random, but in a way that is easily verifiable. There are no known "beneficial" calculations that could replace this.

This CPU time and electricity is not entirely wasted, though: it helps protect the network from attack.

==== How much network traffic does the bitcoin client generate? ====

Almost none. These statistics were recorded before the outgoing connection limit was reduced from 15 to 8, so the current usage is probably even lower:

* Bytes sent without Bitcoin: 2475590 (2.4MiB) per day
* Bytes received without Bitcoin: 2798454 (2.7MiB) per day
* Bytes sent with Bitcoin (not port forwarded): 2210854 (2.1MiB) per day
* Bytes received with Bitcoin (not port forwarded): 4699445 (4.5MiB) per day
* Bytes sent with Bitcoin (port forwarded): 20879040 (19.9MiB) per day
* Bytes received with Bitcoin (port forwarded): 10954438 (10.4MiB) per day

==== Can we expand the transaction protocol so it includes a message as well as an amount? ====

The current protocol is scripted and could already be used with arbitrary comment-like data. However:
* This is considered an abuse of the system, as the transactions/blockchain are intended only for the actual financial exchange.
* Your transaction will be non-standard.
* Even if miners accept your transaction, they will probably expect a larger fee.
* [[ECDSA]] (the public-key algorithm used by Bitcoin) doesn't support encryption, so you'll have to use something else if you want encryption.

There has been some work toward a [https://gist.github.com/4120476 payment protocol] to make transactions more user-friendly including message support, but it has not reached maturity yet.

==== What happens when two nodes generate a block at the same time? ====

This is very unlikely to happen but if it does: The tiebreak is which block the NEXT block builds on.

Each node sends out it's 'winning' block. Some nodes on the network will hear about 'block A' first and assume it is the winning block, and some will hear about 'block B' first and assume it is the winning block. Then each 'half' will proceed hashing from there trying to generate the next block as normal.
If a machine with 'block B' as its predecessor wins the next race by generating 'block C', it becomes the official winner, and the nodes who were working on A give up and start on C. (In this case the generator of 'block A' might be disappointed, because he thought he generated some coins, but he didn't because the network decided his block was no longer valid.)

Note: block A and block B will usually contain the same list of transactions. Transactions not included will be made available to other future blocks for inclusion into the chain.

==== What happens if someone sends me some coins but I am not connected? ====

Any transfer to a 'valid' address should be successful.
You don't need to have a client running to receive bitcoins.
Once you create an address, any coins sent to it will just sit there waiting for you to spend them.

==== Can I start bitcoind without it becoming a daemon process? ====

No. That is expected to be added to the client at some point.

=== Technical (Windows) ===

==== Why am I not downloading any blocks? ====

Add bitcoin.exe to the "Excluded processes" list of Microsoft Security Essentials.

=== Developing ===

==== Is there a mailing list? ====
Yes. http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-list

==== Is there a test network? ====
Yes, run Bitcoin or bitcoind with the -testnet switch (beginning with version 0.3.14).

There is a -testnet version of the Bitcoin Faucet at https://freebitcoins.appspot.com/TEST/.

Note that there are 3 versions of the testnet (which are tied to specific client versions), and the Faucet uses only the most recent.

==== How do I build bitcoin? ====
Forum thread on building v0.3: https://bitcointalk.org/index.php?topic=298.msg2366#msg2366
There are some [http://heliacal.net/~solar/bitcoin/bitcoin-linuxbuild.pdf Build notes for linux type systems (pdf)]

== See Also ==

* [[FAQ]]

[[Category:Technical]]

Changelog

2015-12-11T20:16:11Z

Wargo: Changed forum link

This page aggregates the changelogs that have been posted on the forum for the Bitcoin releases.
Note that some download links are not longer valid as highly insecure versions may have been deleted, or links may have changed.

This page hasn't been updated for a while. Changelogs for newer versions as well as historical release notes can be found at bitcoin.org: https://bitcoin.org/en/version-history and/or through github: https://github.com/bitcoin/bitcoin/tree/master/doc/release-notes

=Changelogs=

https://bitcoin.org/en/release/v0.7.1
==0.7.X==

===0.7.1<ref>[https://bitcoin.org/en/release/v0.7.1 0.7.1 release announcement]</ref>===

New features:

* Added a boolean argument to the RPC stop command, if true sets -detachdb to create standalone database .dat files before shutting down.

* -salvagewallet command-line option, which moves any existing wallet.dat to wallet.{timestamp}.dat and then attempts to salvage public/private keys and master encryption keys (if the wallet is encrypted) into a new wallet.dat. This should only be used if your wallet becomes corrupted, and is not intended to replace regular wallet backups.

* Import $DataDir/bootstrap.dat automatically, if it exists.

==0.6.X==
After 0.6.3, all subsequent releases are stable maintenance releases, 0.7.0 is based on 0.6.3.

===0.6.3<ref>[https://bitcointalk.org/index.php?topic=89877.0 0.6.3 release announcement]</ref>===
Bitcoin version 0.6.3 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.3/

This is a bug-fix release, with no new features.

Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

CHANGE SUMMARY

Fixed a serious denial-of-service attack that could cause the
bitcoin process to become unresponsive. Thanks to Sergio Lerner
for finding and responsibly reporting the problem. (CVE-2012-3789)

Optimized the process of checking transaction signatures, to
speed up processing of new block messages and make propagating
blocks across the network faster.

Fixed an obscure bug that could cause the bitcoin process to get
stuck on an invalid block-chain, if the invalid chain was
hundreds of blocks long.

Bitcoin-Qt no longer automatically selects the first address
in the address book (Issue #1384).

Fixed minimize-to-dock behavior of Bitcon-Qt on the Mac.

Added a block checkpoint at block 185,333 to speed up initial
blockchain download.

===0.6.2<ref>[https://bitcointalk.org/index.php?topic=80187.0 0.6.2 release announcement]</ref>===
Bitcoin version 0.6.2 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.2/

This is a bug-fix and code-cleanup release, with no major new features.

Please report bugs using the github issue tracker at:
https://github.com/bitcoin/bitcoin/issues

NOTABLE CHANGES

Much faster shutdowns. However, the blkindex.dat file is no longer
portable to different data directories by default. If you need a
portable blkindex.dat file then run with the new -detachdb=1 option
or the "Detach databases at shutdown" GUI preference.

Fixed https://github.com/bitcoin/bitcoin/issues/1065, a bug that
could cause long-running nodes to crash.

Mac and Windows binaries are compiled against OpenSSL 1.0.1b (Linux
binaries are dynamically linked to the version of OpenSSL on the system).

CHANGE SUMMARY

Use 'git shortlog --no-merges v0.6.0..' for a summary of this release.

Source codebase changes:
- Many source code cleanups and warnings fixes. Close to building with -Wall
- Locking overhaul, and several minor locking fixes
- Several source code portability fixes, e.g. FreeBSD

JSON-RPC interface changes:
- addmultisigaddress enabled for mainnet (previously only enabled for testnet)

Network protocol changes:
- protocol version 60001
- added nonce value to "ping" message (BIP 31)
- added new "pong" message (BIP 31)

Backend storage changes:
- Less redundant database flushing, especially during initial block download
- Shutdown improvements (see above)

Qt user interface:
- minor URI handling improvements
- progressbar improvements
- error handling improvements (show message box rather than console exception,
etc.)
- by popular request, make 4th bar of connection icon green

===0.6.1===
Never released

===0.6.0<ref>[https://bitcointalk.org/index.php?topic=74737.0 0.6.0 release announcement]</ref>===
Bitcoin version 0.6.0 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/

This release includes more than 20 language localizations.
More translations are welcome; join the
project at Transifex to help:
https://www.transifex.net/projects/p/bitcoin/

Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

Project source code is hosted at github; we are no longer
distributing .tar.gz files here, you can get them
directly from github:
https://github.com/bitcoin/bitcoin/tarball/v0.6.0 # .tar.gz
https://github.com/bitcoin/bitcoin/zipball/v0.6.0 # .zip

For Ubuntu users, there is a ppa maintained by Matt Corallo which
you can add to your system so that it will automatically keep
bitcoin up-to-date. Just type
sudo apt-add-repository ppa:bitcoin/bitcoin
in your terminal, then install the bitcoin-qt package.

KNOWN ISSUES

Shutting down while synchronizing with the network
(downloading the blockchain) can take more than a minute,
because database writes are queued to speed up download
time.

NEW FEATURES SINCE BITCOIN VERSION 0.5

Initial network synchronization should be much faster
(one or two hours on a typical machine instead of ten or more
hours).

Backup Wallet menu option.

Bitcoin-Qt can display and save QR codes for sending
and receiving addresses.

New context menu on addresses to copy/edit/delete them.

New Sign Message dialog that allows you to prove that you
own a bitcoin address by creating a digital
signature.

New wallets created with this version will
use 33-byte 'compressed' public keys instead of
65-byte public keys, resulting in smaller
transactions and less traffic on the bitcoin
network. The shorter keys are already supported
by the network but wallet.dat files containing
short keys are not compatible with earlier
versions of Bitcoin-Qt/bitcoind.

New command-line argument -blocknotify=<command>
that will spawn a shell process to run <command>
when a new block is accepted.

New command-line argument -splash=0 to disable
Bitcoin-Qt's initial splash screen

validateaddress JSON-RPC api command output includes
two new fields for addresses in the wallet:
pubkey : hexadecimal public key
iscompressed : true if pubkey is a short 33-byte key

New JSON-RPC api commands for dumping/importing
private keys from the wallet (dumprivkey, importprivkey).

New JSON-RPC api command for getting information about
blocks (getblock, getblockhash).

New JSON-RPC api command (getmininginfo) for getting
extra information related to mining. The getinfo
JSON-RPC command no longer includes mining-related
information (generate/genproclimit/hashespersec).

NOTABLE CHANGES

BIP30 implemented (security fix for an attack involving
duplicate "coinbase transactions").

The -nolisten, -noupnp and -nodnsseed command-line
options were renamed to -listen, -upnp and -dnsseed,
with a default value of 1. The old names are still
supported for compatibility (so specifying -nolisten
is automatically interpreted as -listen=0; every
boolean argument can now be specified as either
-foo or -nofoo).

The -noirc command-line options was renamed to
-irc, with a default value of 0. Run -irc=1 to
get the old behavior.

Three fill-up-available-memory denial-of-service
attacks were fixed.

NOT YET IMPLEMENTED FEATURES

Support for clicking on bitcoin: URIs and
opening/launching Bitcoin-Qt is available only on Linux,
and only if you configure your desktop to launch
Bitcoin-Qt. All platforms support dragging and dropping
bitcoin: URIs onto the Bitcoin-Qt window to start
payment.

PRELIMINARY SUPPORT FOR MULTISIGNATURE TRANSACTIONS

This release has preliminary support for multisignature
transactions-- transactions that require authorization
from more than one person or device before they
will be accepted by the bitcoin network.

Prior to this release, multisignature transactions
were considered 'non-standard' and were ignored;
with this release multisignature transactions are
considered standard and will start to be relayed
and accepted into blocks.

It is expected that future releases of Bitcoin-Qt
will support the creation of multisignature transactions,
once enough of the network has upgraded so relaying
and validating them is robust.

For this release, creation and testing of multisignature
transactions is limited to the bitcoin test network using
the "addmultisigaddress" JSON-RPC api call.

Short multisignature address support is included in this
release, as specified in BIP 13 and BIP 16.

==0.5.X==
After 0.5.1, all subsequent releases are stable maintenance releases, 0.6.0 is based on 0.5.1.

===0.5.5<ref>[https://bitcointalk.org/index.php?topic=79651 0.4.6/0.5.5 release announcement]</ref>===
bitcoind and Bitcoin-Qt version 0.5.5 are now available for download at:
Windows: installer | zip (sig)
Source: tar.gz
bitcoind and Bitcoin-Qt version 0.6.0.7 are also tagged in git, but it is recommended to upgrade to 0.6.1.

These are bugfix-only releases.

Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.

BUG FIXES

Version 0.6.0 allowed importing invalid "private keys", which would be unspendable; 0.6.0.7 will now verify the private key is valid, and refuse to import an invalid one
Verify status of encrypt/decrypt calls to detect failed padding
Check blocks for duplicate transactions earlier. Fixes #1167
Upgrade Windows builds to OpenSSL 1.0.1b
Set label when selecting an address that already has a label. Fixes #1080 (Bitcoin-Qt)
JSON-RPC listtransactions's from/count handling is now fixed
Optimize and fix multithreaded access, when checking whether we already know about transactions
Fix potential networking deadlock
Proper support for Growl 1.3 notifications
Display an error, rather than crashing, if encoding a QR Code failed (0.6.0.7)
Don't erroneously set "Display addresses" for users who haven't explicitly enabled it (Bitcoin-Qt)
Some non-ASCII input in JSON-RPC expecting hexadecimal may have been misinterpreted rather than rejected
Missing error condition checking added
Do not show green tick unless all known blocks are downloaded. Fixes #921 (Bitcoin-Qt)
Increase time ago of last block for "up to date" status from 30 to 90 minutes
Show a message box when runaway exception happens (Bitcoin-Qt)
Use a messagebox to display the error when -server is provided without providing a rpc password
Show error message instead of exception crash when unable to bind RPC port (Bitcoin-Qt)
Correct sign message bitcoin address tooltip. Fixes #1050 (Bitcoin-Qt)
Removed "(no label)" from QR Code dialog titlebar if we have no label (0.6.0.7)
Removed an ugly line break in tooltip for mature transactions (0.6.0.7)
Add missing tooltip and key shortcut in settings dialog (part of #1088) (Bitcoin-Qt)
Work around issue in boost::program_options that prevents from compiling in clang
Fixed bugs occurring only on platforms with unsigned characters (such as ARM).
Rename make_windows_icon.py to .sh as it is a shell script. Fixes #1099 (Bitcoin-Qt)
Various trivial internal corrections to types used for counting/size loops and warnings

===0.5.4<ref>[https://bitcointalk.org/index.php?topic=76808.0 0.5.4 release announcement]</ref>===
Bitcoin version 0.5.4 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.4/
NOTE: 0.5.4rc3 is being renamed to 0.5.4 final with no changes.

This is a bugfix-only release in the 0.5.x series, plus a few protocol updates.

Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

Stable source code is hosted at Gitorious:
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.4#.tar.gz

PROTOCOL UPDATES

BIP 16: Special-case "pay to script hash" logic to enable minimal validation of new transactions.
Support for validating message signatures produced with compressed public keys.

BUG FIXES

Build with thread-safe MingW libraries for Windows, fixing a dangerous memory corruption scenario when exceptions are thrown.
Fix broken testnet mining.
Stop excess inventory relay during initial block download.
When disconnecting a node, clear the received buffer so that we do not process any already received messages.
Yet another attempt at implementing "minimize to tray" that works on all operating systems.
Fix Bitcoin-Qt notifications under Growl 1.3.
Increase required age of Bitcoin-Qt's "not up to date" status from 30 to 90 minutes.
Implemented missing verifications that led to crash on entering some wrong passphrases for encrypted wallets.
Fix default filename suffixes in GNOME save dialog.
Make the "Send coins" tab use the configured unit type, even on the first attempt.
Print detailed wallet loading errors to debug.log when it is corrupt.
Allocate exactly the amount of space needed for signing transactions, instead of a fixed 10k buffer.
Workaround for improbable memory access violation.
Check wallet's minimum version before trying to load it.
Remove wxBitcoin properly when installing Bitcoin-Qt over it. (Windows)
Detail reorganization information better in debug log.
Use a messagebox to display the error when -server is provided without configuring a RPC password.
Testing suite build now honours provided CXXFLAGS.
Removed an extraneous line-break in mature transaction tooltips.
Fix some grammatical errors in translation process documentation.

===0.5.3<ref>[https://bitcointalk.org/index.php?topic=68895.0 0.5.3 release announcement]</ref>===
Bitcoin version 0.5.3 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/

This is a bugfix-only release based on 0.5.1.
It also includes a few protocol updates.

Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

Stable source code is hosted at Gitorious:
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.3#.tar.gz

PROTOCOL UPDATES

BIP 30: Introduce a new network rule: "a block is not valid if it contains a transaction whose hash already exists in the block chain, unless all that transaction's outputs were already spent before said block" beginning on March 15, 2012, 00:00 UTC.
On testnet, allow mining of min-difficulty blocks if 20 minutes have gone by without mining a regular-difficulty block. This is to make testing Bitcoin easier, and will not affect normal mode.

BUG FIXES

Limit the number of orphan transactions stored in memory, to prevent a potential denial-of-service attack by flooding orphan transactions. Also never store invalid transactions at all.
Fix possible buffer overflow on systems with very long application data paths. This is not exploitable.
Resolved multiple bugs preventing long-term unlocking of encrypted wallets
(issue #922).
Only send local IP in "version" messages if it is globally routable (ie, not private), and try to get such an IP from UPnP if applicable.
Reannounce UPnP port forwards every 20 minutes, to workaround routers expiring old entries, and allow the -upnp option to override any stored setting.
Skip splash screen when -min is used, and fix Minimize to Tray function.
Do not blank "label" in Bitcoin-Qt "Send" tab, if the user has already entered something.
Correct various labels and messages.
Various memory leaks and potential null pointer deferences have been fixed.
Handle invalid Bitcoin URIs using "bitcoin://" instead of "bitcoin:".
Several shutdown issues have been fixed.
Revert to "global progress indication", as starting from zero every time was considered too confusing for many users.
Check that keys stored in the wallet are valid at startup, and if not, report corruption.
Enable accessible widgets on Windows, so that people with screen readers such as NVDA can make sense of it.
Various build fixes.
If no password is specified to bitcoind, recommend a secure password.
Automatically focus and scroll to new "Send coins" entries in Bitcoin-Qt.
Show a message box for --help on Windows, for Bitcoin-Qt.
Add missing "About Qt" menu option to show built-in Qt About dialog.
Don't show "-daemon" as an option for Bitcoin-Qt, since it isn't available.
Update hard-coded fallback seed nodes, choosing recent ones with long uptime and versions at least 0.4.0.
Add checkpoint at block 168,000.

===0.5.2<ref>[https://bitcointalk.org/index.php?topic=60146.0 0.5.2 release announcement]</ref>===
Bitcoin version 0.5.2 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.2/

This is a bugfix-only release based on 0.5.1.

Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

Stable source code is hosted at Gitorious:
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.2#.tar.gz

BUG FIXES

Check all transactions in blocks after the last checkpoint (0.5.0 and 0.5.1 skipped checking ECDSA signatures during initial blockchain download).
Cease locking memory used by non-sensitive information (this caused a huge performance hit on some platforms, especially noticable during initial blockchain download; this was
not a security vulnerability).
Fixed some address-handling deadlocks (client freezes).
No longer accept inbound connections over the internet when Bitcoin is being used with Tor (identity leak).
Re-enable SSL support for the JSON-RPC interface (it was unintentionally disabled for the 0.5.0 and 0.5.1 release Linux binaries).
Use the correct base transaction fee of 0.0005 BTC for accepting transactions into mined blocks (since 0.4.0, it was incorrectly accepting 0.0001 BTC which was only meant to be relayed).
Don't show "IP" for transactions which are not necessarily IP transactions.
Add new DNS seeds (maintained by Pieter Wuille and Luke Dashjr).

===0.5.1<ref>[https://bitcointalk.org/index.php?topic=54717.0 0.5.1 release announcement]</ref>===
Bitcoin version 0.5.1 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.1/

This is a bugfix-only release.

This release includes 13 translations, including 5 new translations:
Italian, Hungarian, Ukranian, Portuguese (Brazilian) and Simplified Chinese.
More translations are welcome; join the project at Transifex if you can help:
https://www.transifex.net/projects/p/bitcoin/

Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

Project source code is hosted at github; we are no longer
distributing .tar.gz files here, you can get them
directly from github:
https://github.com/bitcoin/bitcoin/tarball/v0.5.1 # .tar.gz
https://github.com/bitcoin/bitcoin/zipball/v0.5.1 # .zip

For Ubuntu users, there is a new ppa maintained by Matt Corallo which
you can add to your system so that it will automatically keep
bitcoin up-to-date. Just type
sudo apt-add-repository ppa:bitcoin/bitcoin
in your terminal, then install the bitcoin-qt package.

BUG FIXES

Re-enable SSL support for the JSON-RPC interface (it was unintentionally
disabled for the 0.5.0 release binaries).

The code that finds peers via "dns seeds" no longer stops bitcoin startup
if one of the dns seed machines is down.

Tooltips on the transaction list view were rendering incorrectly (as black boxes
or with a transparent background).

Prevent a denial-of-service attack involving flooding a bitcoin node with
orphan blocks.

The wallet passphrase dialog now warns you if the caps lock key was pressed.

Improved searching in addresses and labels in bitcoin-qt.

===0.5.0<ref>[https://bitcointalk.org/index.php?topic=52480.0 0.5.0 release announcement]</ref>===
Bitcoin version 0.5.0 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.0/

The major change for this release is a completely new graphical interface that uses the Qt user interface toolkit.

This release include German, Spanish, Spanish-Castilian, Norwegian and Dutch translations. More translations are welcome; join the project at Transifex if you can help:
https://www.transifex.net/projects/p/bitcoin/

Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

For Ubuntu users, there is a new ppa maintained by Matt Corallo which you can add to your system so that it will automatically keep bitcoin up-to-date. Just type "sudo apt-add-repository ppa:bitcoin/bitcoin" in your terminal, then install the bitcoin-qt package.

MAJOR BUG FIX (CVE-2011-4447)

The wallet encryption feature introduced in Bitcoin version 0.4.0 did not sufficiently secure the private keys. An attacker who
managed to get a copy of your encrypted wallet.dat file might be able to recover some or all of the unencrypted keys and steal the
associated coins.

If you have a previously encrypted wallet.dat, the first time you run bitcoin-qt or bitcoind the wallet will be rewritten, Bitcoin will
shut down, and you will be prompted to restart it to run with the new, properly encrypted file.

If you had a previously encrypted wallet.dat that might have been copied or stolen (for example, you backed it up to a public
location) you should send all of your bitcoins to yourself using a new bitcoin address and stop using any previously generated addresses.

Wallets encrypted with this version of Bitcoin are written properly.

Technical note: the encrypted wallet's 'keypool' will be regenerated the first time you request a new bitcoin address; to be certain that the
new private keys are properly backed up you should:

1. Run Bitcoin and let it rewrite the wallet.dat file

2. Run it again, then ask it for a new bitcoin address.
Bitcoin-Qt: Address Book, then New Address...
bitcoind: run the 'walletpassphrase' RPC command to unlock the wallet, then run the 'getnewaddress' RPC command.

3. If your encrypted wallet.dat may have been copied or stolen, send all of your bitcoins to the new bitcoin address.

4. Shut down Bitcoin, then backup the wallet.dat file.
IMPORTANT: be sure to request a new bitcoin address before backing up, so that the 'keypool' is regenerated and backed up.

"Security in depth" is always a good idea, so choosing a secure location for the backup and/or encrypting the backup before uploading it is recommended. And as in previous releases, if your machine is infected by malware there are several ways an attacker might steal your bitcoins.

Thanks to Alan Reiner (etotheipi) for finding and reporting this bug.

MAJOR GUI CHANGES

"Splash" graphics at startup that show address/wallet/blockchain loading progress.

"Synchronizing with network" progress bar to show block-chain download progress.

Icons at the bottom of the window that show how well connected you are to the network, with tooltips to display details.

Drag and drop support for bitcoin: URIs on web pages.

Export transactions as a .csv file.

Many other GUI improvements, large and small.

RPC CHANGES

getmemorypool : new RPC command, provides everything needed to construct a block with a custom generation transaction and submit a solution

listsinceblock : new RPC command, list transactions since given block

signmessage/verifymessage : new RPC commands to sign a message with one of your private keys or verify that a message signed by the private key associated with a bitcoin address.

GENERAL CHANGES

Faster initial block download.

==0.4.X==
After 0.4.0, all subsequent releases are stable maintenance releases, 0.5.0 is based on 0.4.0.

===0.4.6<ref>[https://bitcointalk.org/index.php?topic=79651 0.4.6/0.5.5 release announcement]</ref>===
bitcoind version 0.4.6 is now available for download at:
Windows: installer | zip (sig)
Source: tar.gz
bitcoind and Bitcoin-Qt version 0.6.0.7 are also tagged in git, but it is recommended to upgrade to 0.6.1.

These are bugfix-only releases.

Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.

BUG FIXES

Version 0.6.0 allowed importing invalid "private keys", which would be unspendable; 0.6.0.7 will now verify the private key is valid, and refuse to import an invalid one
Verify status of encrypt/decrypt calls to detect failed padding
Check blocks for duplicate transactions earlier. Fixes #1167
Upgrade Windows builds to OpenSSL 1.0.1b
Set label when selecting an address that already has a label. Fixes #1080 (Bitcoin-Qt)
JSON-RPC listtransactions's from/count handling is now fixed
Optimize and fix multithreaded access, when checking whether we already know about transactions
Fix potential networking deadlock
Proper support for Growl 1.3 notifications
Display an error, rather than crashing, if encoding a QR Code failed (0.6.0.7)
Don't erroneously set "Display addresses" for users who haven't explicitly enabled it (Bitcoin-Qt)
Some non-ASCII input in JSON-RPC expecting hexadecimal may have been misinterpreted rather than rejected
Missing error condition checking added
Do not show green tick unless all known blocks are downloaded. Fixes #921 (Bitcoin-Qt)
Increase time ago of last block for "up to date" status from 30 to 90 minutes
Show a message box when runaway exception happens (Bitcoin-Qt)
Use a messagebox to display the error when -server is provided without providing a rpc password
Show error message instead of exception crash when unable to bind RPC port (Bitcoin-Qt)
Correct sign message bitcoin address tooltip. Fixes #1050 (Bitcoin-Qt)
Removed "(no label)" from QR Code dialog titlebar if we have no label (0.6.0.7)
Removed an ugly line break in tooltip for mature transactions (0.6.0.7)
Add missing tooltip and key shortcut in settings dialog (part of #1088) (Bitcoin-Qt)
Work around issue in boost::program_options that prevents from compiling in clang
Fixed bugs occurring only on platforms with unsigned characters (such as ARM).
Rename make_windows_icon.py to .sh as it is a shell script. Fixes #1099 (Bitcoin-Qt)
Various trivial internal corrections to types used for counting/size loops and warnings

===0.4.5===
(No known forum post.)

===0.4.4<ref>[https://bitcointalk.org/index.php?topic=70566.0 0.4.4 release announcement]</ref>===
Bitcoin version 0.4.4 is now available for download at:
http://luke.dashjr.org/programs/bitcoin/files/bitcoind-0.4.4/

This is a bugfix-only release based on 0.4.0.

Please note that the wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.

Please report bugs for the daemon only using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

Stable source code is hosted at Gitorious:
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.4.4#.tar.gz

BUG FIXES

Limit the number of orphan transactions stored in memory, to prevent a potential denial-of-service attack by flooding orphan transactions. Also never store invalid transactions at all.
Fix possible buffer overflow on systems with very long application data paths. This is not exploitable.
Resolved multiple bugs preventing long-term unlocking of encrypted wallets (issue #922).
Only send local IP in "version" messages if it is globally routable (ie, not private), and try to get such an IP from UPnP if applicable.
Reannounce UPnP port forwards every 20 minutes, to workaround routers expiring old entries, and allow the -upnp option to override any stored setting.
Various memory leaks and potential null pointer deferences have been
fixed.
Several shutdown issues have been fixed.
Check that keys stored in the wallet are valid at startup, and if not,
report corruption.
Various build fixes.
If no password is specified to bitcoind, recommend a secure password.
Update hard-coded fallback seed nodes, choosing recent ones with long uptime and versions at least 0.4.0.
Add checkpoint at block 168,000.

===0.4.3<ref>[https://bitcointalk.org/index.php?topic=57734.0 0.4.3 release announcement]</ref>===
bitcoind version 0.4.3 is now available for download at:
http://luke.dashjr.org/programs/bitcoin/files/bitcoind-0.4.3/ (until Gavin uploads to SourceForge)

This is a bugfix-only release based on 0.4.0.

Please note that the wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.

Please report bugs for the daemon only using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

Stable source code is hosted at Gitorious:
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.4.3#.tar.gz

BUG FIXES

Cease locking memory used by non-sensitive information (this caused a huge performance hit on some platforms, especially noticable during initial blockchain download).
Fixed some address-handling deadlocks (client freezes).
No longer accept inbound connections over the internet when Bitcoin is being used with Tor (identity leak).
Use the correct base transaction fee of 0.0005 BTC for accepting transactions into mined blocks (since 0.4.0, it was incorrectly accepting 0.0001 BTC which was only meant to be relayed).
Add new DNS seeds (maintained by Pieter Wuille and Luke Dashjr).

===0.4.2===
(No known forum post.)

===0.4.1<ref>[https://bitcointalk.org/index.php?topic=52503.0 0.4.1 release announcement]</ref>===
Bitcoin version 0.4.1 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.1/

This is a bugfix only release based on 0.4.0.

Please report bugs by replying to this forum thread.

MAJOR BUG FIX (CVE-2011-4447)

The wallet encryption feature introduced in Bitcoin version 0.4.0 did not sufficiently secure the private keys. An attacker who
managed to get a copy of your encrypted wallet.dat file might be able to recover some or all of the unencrypted keys and steal the
associated coins.

If you have a previously encrypted wallet.dat, the first time you run wxbitcoin or bitcoind the wallet will be rewritten, Bitcoin will
shut down, and you will be prompted to restart it to run with the new, properly encrypted file.

If you had a previously encrypted wallet.dat that might have been copied or stolen (for example, you backed it up to a public
location) you should send all of your bitcoins to yourself using a new bitcoin address and stop using any previously generated addresses.

Wallets encrypted with this version of Bitcoin are written properly.

Technical note: the encrypted wallet's 'keypool' will be regenerated the first time you request a new bitcoin address; to be certain that the
new private keys are properly backed up you should:

1. Run Bitcoin and let it rewrite the wallet.dat file

2. Run it again, then ask it for a new bitcoin address.
wxBitcoin: new address visible on main window
bitcoind: run the 'walletpassphrase' RPC command to unlock the wallet, then run the 'getnewaddress' RPC command.

3. If your encrypted wallet.dat may have been copied or stolen, send all of your bitcoins to the new bitcoin address.

4. Shut down Bitcoin, then backup the wallet.dat file.
IMPORTANT: be sure to request a new bitcoin address before backing up, so that the 'keypool' is regenerated and backed up.

"Security in depth" is always a good idea, so choosing a secure location for the backup and/or encrypting the backup before uploading it is recommended. And as in previous releases, if your machine is infected by malware there are several ways an attacker might steal your bitcoins.

Thanks to Alan Reiner (etotheipi) for finding and reporting this bug.

===0.4.0<ref>[https://bitcointalk.org/index.php?topic=45410.0 0.4 release announcement]</ref>===
Bitcoin version 0.4.0 is now available for download at:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.0/

The main feature in this release is wallet private key encryption;
you can set a passphrase that must be entered before sending coins.
See below for more information; if you decide to encrypt your wallet,
WRITE DOWN YOUR PASSPHRASE AND PUT IT IN A SECURE LOCATION. If you
forget or lose your wallet passphrase, you lose your bitcoins.
Previous versions of bitcoin are unable to read encrypted wallets,
and will crash on startup if the wallet is encrypted.

Also note: bitcoin version 0.4 uses a newer version of Berkeley DB
(bdb version 4.8) than previous versions (bdb 4.7). If you upgrade
to version 0.4 and then revert back to an earlier version of bitcoin
the it may be unable to start because bdb 4.7 cannot read bdb 4.8
"log" files.

Notable bug fixes from version 0.3.24:

Fix several bitcoin-becomes-unresponsive bugs due to multithreading
deadlocks.

Optimize database writes for large (lots of inputs) transactions
(fixes a potential denial-of-service attack)

Wallet Encryption

Bitcoin supports native wallet encryption so that people who steal your
wallet file don't automatically get access to all of your Bitcoins.
In order to enable this feature, choose "Encrypt Wallet" from the
Options menu. You will be prompted to enter a passphrase, which
will be used as the key to encrypt your wallet and will be needed
every time you wish to send Bitcoins. If you lose this passphrase,
you will lose access to spend all of the bitcoins in your wallet,
no one, not even the Bitcoin developers can recover your Bitcoins.
This means you are responsible for your own security, store your
passphrase in a secure location and do not forget it.

Remember that the encryption built into bitcoin only encrypts the
actual keys which are required to send your bitcoins, not the full
wallet. This means that someone who steals your wallet file will
be able to see all the addresses which belong to you, as well as the
relevant transactions, you are only protected from someone spending
your coins.

It is recommended that you backup your wallet file before you
encrypt your wallet. To do this, close the Bitcoin client and
copy the wallet.dat file from ~/.bitcoin/ on Linux, /Users/(user
name)/Application Support/Bitcoin/ on Mac OSX, and %APPDATA%/Bitcoin/
on Windows (that is /Users/(user name)/AppData/Roaming/Bitcoin on
Windows Vista and 7 and /Documents and Settings/(user name)/Application
Data/Bitcoin on Windows XP). Once you have copied that file to a
safe location, reopen the Bitcoin client and Encrypt your wallet.
If everything goes fine, delete the backup and enjoy your encrypted
wallet. Note that once you encrypt your wallet, you will never be
able to go back to a version of the Bitcoin client older than 0.4.

Keep in mind that you are always responsible for your own security.
All it takes is a slightly more advanced wallet-stealing trojan which
installs a keylogger to steal your wallet passphrase as you enter it
in addition to your wallet file and you have lost all your Bitcoins.
Wallet encryption cannot keep you safe if you do not practice
good security, such as running up-to-date antivirus software, only
entering your wallet passphrase in the Bitcoin client and using the
same passphrase only as your wallet passphrase.

See the doc/README file in the bitcoin source for technical details
of wallet encryption.

==0.3.X==

===0.3.24<ref>[https://bitcointalk.org/index.php?topic=27187.0 0.3.24 release announcement]</ref>===
Bitcoin v0.3.24 is now available for download at
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.24/

This is another bug fix release. We had hoped to have wallet encryption ready for release, but more urgent fixes for existing clients were needed -- most notably block download problems were getting severe. Wallet encryption is ready for testing at https://github.com/bitcoin/bitcoin/pull/352 for the git-savvy, and hopefully will follow shortly in the next release, v0.4.

Notable fixes in v0.3.24, and the main reasons for this release:

F1) Block downloads were failing or taking unreasonable amounts of time to complete, because the increased size of the block chain was bumping up against some earlier buffer-size DoS limits.

F2) Fix crash caused by loss/lack of network connection.

Notable changes in v0.3.24:

C1) DNS seeding enabled by default.

C2) UPNP enabled by default in the GUI client. The percentage of bitcoin clients that accept incoming connections is quite small, and that is a problem. This should help. bitcoind, and unofficial builds, are unchanged (though we encourage use of "-upnp" to help the network!)

C3) Initial unit testing framework. Bitcoin sorely needs automated tests, and this is a beginning. Contributions welcome.

C4) Internal wallet code cleanup. While invisible to an end user, this change provides the basis for v0.4's wallet encryption.

===0.3.23<ref>[https://bitcointalk.org/index.php?topic=16553.0 0.3.23 release announcement]</ref>===
Win32, Linux, MacOSX and source releases for bitcoin v0.3.23 have been uploaded to
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.23/

This is another quick bugfix release, trying to deal with the influx of new bitcoin users.

Main items of note:

* P2P connect-to-node logic changed to reduce timeout a bit. The network saw a huge influx of new users, who do not permit incoming connections. This change is a short-term hack, to more quickly hunt for useful P2P connections. Better "leaf node" logic is in the works, but this should let us limp along until then. One may use -upnp to properly forward ports, and help the network.
* Transaction fee reduced to 0.0005 for new transactions
* Client will relay transactions with fees as low as 0.0001 BTC

===0.3.22<ref>[https://bitcointalk.org/index.php?topic=12269.0 0.3.22 release announcement]</ref>===
Download URL: https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.22/

This is largely a bugfix and TX fee schedule release. We also hope to make 0.3.23 a quick release, to fix problems that the network has seen due to explosive growth in the past week.

Notable changes:
* Client will accept and relay TX's with 0.0005 BTC fee schedule (users still pay 0.01 BTC per kb, until next version)
* Non-standard transactions accepted on testnet
* Source code tree reorganized (prep for autotools build)
* Remove "Generate Coins" option from GUI, and remove 4way SSE miner. Internal reference CPU miner remains available, but users are directed to external miners for best hash production.
* IRC is overflowing. Client now bootstraps to channels #bitcoin00 - #bitcoin99
* DNS names now may be used with -addnode, -connect (requires -dns to enable)

RPC changes:
* 'listtransactions' adds 'from' param, for range queries
* 'move' may take account balances negative
* 'settxfee' added, to manually set TX fee

===0.3.21<ref>[https://bitcointalk.org/index.php?topic=6642.0 0.3.21 release announcement]</ref>===
Binaries for Bitcoin version 0.3.21 are available at:
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.21/

Changes and new features from the 0.3.20 release include:

* Universal Plug and Play support. Enable automatic opening of a port for incoming connections by running bitcoin or bitcoind with the - -upnp=1 command line switch or using the Options dialog box.

* Support for full-precision bitcoin amounts. You can now send, and bitcoin will display, bitcoin amounts smaller than 0.01. However, sending fewer than 0.01 bitcoins still requires a 0.01 bitcoin fee (so you can send 1.0001 bitcoins without a fee, but you will be asked to pay a fee if you try to send 0.0001).

* A new method of finding bitcoin nodes to connect with, via DNS A records. Use the -dnsseed option to enable.

For developers, changes to bitcoin's remote-procedure-call API:

* New rpc command "sendmany" to send bitcoins to more than one address in a single transaction.

* Several bug fixes, including a serious intermittent bug that would sometimes cause bitcoind to stop accepting rpc requests.

* -logtimestamps option, to add a timestamp to each line in debug.log.

* Immature blocks (newly generated, under 120 confirmations) are now shown in listtransactions.

===0.3.20.2<ref>[https://bitcointalk.org/index.php?topic=4167.0 0.3.20.2 release announcement]</ref>===
The maxsendbuffer bug (0.3.20.1 clients not being able to download the block chain from other 0.3.20.1 clients) was only going to get
worse as people upgraded, so I cherry-picked the bug fix and created a minor release yesterday.

The Amazon Machine Images I used to do the builds are available:

ami-38a05251 Bitcoin-v0.3.20.2 Mingw (Windows; Administrator password 'bitcoin development')
ami-30a05259 Bitcoin_0.3.20.2 Linux32
ami-8abc4ee3 Bitcoin_0.3.20.2 Linux64

(mac build will be done soon)

If you have already downloaded version 0.3.20.1, please either add this to your bitcoin.conf file:

maxsendbuffer=10000
maxreceivebuffer=10000

... or download the new version.

===0.3.20.1===
(No known forum post.)

===0.3.20<ref>[https://bitcointalk.org/index.php?topic=2953.0 0.3.20 release announcement]</ref>===
Please checkout the git integration branch from:

https://github.com/bitcoin/bitcoin

... and help test. The new features that need testing are:

* -nolisten : https://github.com/bitcoin/bitcoin/pull/11
* -rescan : scan block chain for missing wallet transactions
* -printtoconsole : https://github.com/bitcoin/bitcoin/pull/37
* RPC gettransaction details : https://github.com/bitcoin/bitcoin/pull/24
* listtransactions new features : https://github.com/bitcoin/bitcoin/pull/10

Bug fixes that also need testing:

* -maxconnections= : https://github.com/bitcoin/bitcoin/pull/42
* RPC listaccounts minconf : https://github.com/bitcoin/bitcoin/pull/27
* RPC move, add time to output : https://github.com/bitcoin/bitcoin/pull/21
* ...and several improvements to --help output.

This needs more testing on Windows! Please drop me a quick private message, email, or IRC message if you are able to do some testing. If you find bugs, please open an issue at:

https://github.com/bitcoin/bitcoin/issues

===0.3.19<ref>[https://bitcointalk.org/index.php?topic=2228.0 0.3.19 release announcement]</ref>===
There's more work to do on DoS, but I'm doing a quick build of what I have so far in case it's needed, before venturing into more complex ideas. The build for this is version 0.3.19.

- Added some DoS controls
As Gavin and I have said clearly before, the software is not at all resistant to DoS attack. This is one improvement, but there are still more ways to attack than I can count.

I'm leaving the -limitfreerelay part as a switch for now and it's there if you need it.

- Removed "safe mode" alerts
"safe mode" alerts was a temporary measure after the 0.3.9 overflow bug. We can say all we want that users can just run with "-disablesafemode", but it's better just not to have it for the sake of appearances. It was never intended as a long term feature. Safe mode can still be triggered by seeing a longer (greater total PoW) invalid block chain.

===0.3.18<ref>[https://bitcointalk.org/index.php?topic=2162.0 0.3.18 release announcement]</ref>===

Changes:
* Fixed a wallet.dat compatibility problem if you downgraded from 0.3.17 and then upgraded again
* IsStandard() check to only include known transaction types in blocks
* Jgarzik's optimisation to speed up the initial block download a little

The main addition in this release is the Accounts-Based JSON-RPC commands that Gavin's been working on (more details at https://bitcointalk.org/index.php?topic=1886.0).
* getaccountaddress
* sendfrom
* move
* getbalance
* listtransactions

===0.3.17<ref>[https://bitcointalk.org/index.php?topic=1946.0 0.3.17 release announcement]</ref>===

Version 0.3.17 is now available.

Changes:
* new getwork, thanks m0mchil
* added transaction fee setting in UI options menu
* free transaction limits
* sendtoaddress returns transaction id instead of "sent"
* getaccountaddress <account>

The UI transaction fee setting was easy since it was still there from 0.1.5 and all I had to do was re-enable it.

The accounts-based commands: move, sendfrom and getbalance <account> will be in the next release. We still have some more changes to make first.

===0.3.16===

Never released.

===0.3.15<ref>[https://bitcointalk.org/index.php?topic=1780.0 0.3.15 release announcement]</ref>===

* paytxfee switch is now per KB, so it adds the correct fee for large transactions
* sending avoids using coins with less than 6 confirmations if it can
* BitcoinMiner processes transactions in priority order based on age of dependencies
* make sure generation doesn't start before block 74000 downloaded
* bugfixes by Dean Gores
* testnet, keypoololdest and paytxfee added to getinfo

===0.3.14<ref>[https://bitcointalk.org/index.php?topic=1528.0 0.3.14 release announcement]</ref>===

Version 0.3.14 is now available
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.14/

Changes:
* Key pool feature for safer wallet backup
Gavin Andresen:
* TEST network mode with switch -testnet
* Option to use SSL for JSON-RPC connections on unix/osx
* validateaddress RPC command
eurekafag:
* Russian translation

===0.3.13<ref>[https://bitcointalk.org/index.php?topic=1327.0 0.3.13 release announcement]</ref>===

Version 0.3.13 is now available. You should upgrade to prevent potential problems with 0/unconfirmed transactions. Note: 0.3.13 prevents problems if you haven't already spent a 0/unconfirmed transaction, but if that already happened, you need 0.3.13.2.

Changes:
* Don't count or spend payments until they have 1 confirmation.
* Internal version number from 312 to 31300.
* Only accept transactions sent by IP address if -allowreceivebyip is specified.
* Dropped DB_PRIVATE Berkeley DB flag.
* Fix problem sending the last cent with sub-cent fractional change.
* Auto-detect whether to use 128-bit 4-way SSE2 on Linux.
Gavin Andresen:
* Option -rpcallowip= to accept json-rpc connections from another machine.
* Clean shutdown on SIGTERM on Linux.

Download:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.13/

(Thanks Laszlo for the Mac OSX build!)

Note:
The SSE2 auto-detect in the Linux 64-bit version doesn't work with AMD in 64-bit mode. Please try this instead and let me know if it gets it right:
http://www.bitcoin.org/download/bitcoin-0.3.13.1-specialbuild-linux64.tar.gz

You can still control the SSE2 use manually with -4way and -4way=0.

Version 0.3.13.2 (SVN rev 161) has improvements for the case where you already had 0/unconfirmed transactions that you might have already spent. Here's a Windows build of it:
http://www.bitcoin.org/download/bitcoin-0.3.13.2-win32-setup.exe

===0.3.12<ref>[https://bitcointalk.org/index.php?topic=999.0 0.3.12 release announcement]</ref>===

Version 0.3.12 is now available.

Features:
* json-rpc errors return a more standard error object. (thanks to Gavin Andresen)
* json-rpc command line returns exit codes.
* json-rpc "backupwallet" command.
* Recovers and continues if an exception is caused by a message you received. Other nodes shouldn't be able to cause an exception, and it hasn't happened before, but if a way is found to cause an exception, this would keep it from being used to stop network nodes.

If you have json-rpc code that checks the contents of the error string, you need to change it to expect error objects of the form {"code":<number>,"message":<string>}, which is the standard. See this thread:
https://bitcointalk.org/index.php?topic=969.0

Download:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.12/

=References=
<references/>

Talk:Miner fees

2015-12-11T20:08:58Z

Wargo: Changed forum link

== Questions ==

It's theoretically possible for transactions per block to become so high, that in order to get in a block at all you have to put in a transaction fee, right? Well what happens, in that environment, if I put a transaction fee of 0, and my transaction is never ever picked up? How would I correct that situation?

If I increased the transaction fee amount, and tried again, and that one went through, would an attacker then be able to create his own block, with the first payment inside? Or is there a way to revoke transactions permanently before they end up in a block? Is there a 'deadline' on a signed transaction? i.e. 'after block X, this transaction would not be valid'?
:See https://www.bitcointalk.org/index.php?topic=3411.0 [[User:Theymos|theymos]] 20:13, 17 February 2011 (GMT)
::That link is broken. [[User:Swiftpaw|Swiftpaw]] 23:08, 4 September 2011 (GMT)

Transactions are confusing me as well. Along with the above question which was a great one to ask, another one I have is that if transactions are the incentive for miners to create blocks in the block chain, and blocks which aren't in the chain aren't verified to have occurred and thus prevent counterfeiting, then what happens in the future when it becomes incredibly hard to create blocks? If transaction fees are designed to deal with this problem, how can they do that when the difficulty of mining blocks increases exponentially? Wouldn't that mean that the fees will get unbearable, or do I have the exponential function labelled backwards? If the response to that, which would create a huge problem, is that instead the fees vs. computing power costs mathematically designed to level off at a comfortable ratio, at least given the future predictions of electricity + computing costs, and the difficulty of creating blocks stops increasing very much as you approach infinity on the exponential curve, won't that mean that computing power has a chance of vastly overcoming the computing difficulties? If the entire bitcoin model is ultimately dependent on the difficulty of computing, then you can try as hard as you can to predict computing and electricity cost, but of course your predictions will be off and you will eventually have to re-adjust your math as reality veers away from your predicted path, right? So no matter what "computing difficulty" does, if it increases exponentially (y), levels off (x), or if it is instead some fairly linear function, won't re-adjusting it always be a problem? Thanks! ^^ [[User:Swiftpaw|Swiftpaw]] 23:08, 4 September 2011 (GMT)

I asked this over at the [http://bitcoin.stackexchange.com/questions/570/is-there-a-way-to-undo-transactions-with-a-too-low-fee Bitcoin Q&A site] (should be open to the public in about 2-3 days). [[User:Ripper234|Ripper234]] 23:26, 4 September 2011 (GMT)

Talk:Tor

2015-12-11T18:51:44Z

Wargo: Changed forum link

== Proposal to rename/split Tor page ==

Much of the content here details information that is irrelevant to the subject of Bitcoin. I propose we create a separate wiki page for "Freenode" as that is what the main topic appears to be. We can keep a Tor page for issues related to Tor/Bitcoin and hidden service fallback nodes.

As an aside note we ought to, at the very least, trim down the mIRC section. It is after all, a shareware product. There are more appropriate free open source alternatives that already have SASL support built-in or have implementations that are not broken.

(note1 from ptmhd - i'm back on the wiki editing, i will trim the irc part to bare minimum (also because it is now much easier to setup)

== Tor + Firefox ==

I recommend to start with the Vidalia Bundle.
There Tor comes with a graphical control centre + Tor button for Firefox.
the Tor button is a plugin that allows you with 1 click to turn on/off the Tor routing for Firefox.

== Tor + Bitcoin ==

using Bitcoin with Tor is easy. All you need is to check the proxy option. The predefined values in Bitcoin match the Tor settings. As Bitcoin only saves from & to addresses (and no IP addresses), you should be pretty safe. Tor however does not fix the traceability of BTC from one address to other.

== Tor + IRC (mIRC) ==

This is worked for me on two different computers, drop me a message on Bitcoin forum if you need help.

== additional content? ==

some user started creating a tor page under his user space:
https://en.bitcoin.it/wiki/User:Sawzall/Tor

maybe there's some stuff you guys can pull in from there...

also, xchat instructions for using over tor can be nice to have too. not everyone uses mirc, you know. :)

--[[User:Nanotube|Nanotube]] 05:39, 9 January 2011 (GMT)

There's a bounty for the article at https://bitcointalk.org/index.php?topic=2602
Thanks for the link to Sawzall's Tor page. I did not know that.
I shouldn't probably edit directly the main article either and should write it in my user space first.
I have no wiki writing habbits :(
As for the xchat, I do not do IRC since I left school and installed it after 7 years only to write the Freenode + Tor + SASL howto.

--[[User:Ptmhd|Ptmhd]] 18:20, 12 January 2011 (GMT)

== hidden services ==

rather than trying to keep a separate list of bitcoind as hidden services, it's probably better to link to the existing list of [[fallback nodes]], which already has a few tor hidden services listed.

In addition, the bitcoin client does not resolve dns, so if you have any nodes added whose dns/.onion addresses are not resolved the connection will fail. You can find an explanation and instructions here https://bitcointalk.org/index.php?topic=59.0;all#msg14635

== Configuration tips ==

In torrc:
CircuitBuildTimeout 30 #Picks faster nodes
LearnCircuitBuildTimeout 0 #Enables the above setting
MaxCircuitDirtiness 1200 #The number of seconds between each enforced IP change.
#Increasing it can be good in some cases.
WarnUnsafeSocks 0 #Tor doesn't like the way Bitcoin makes requests, and spams
#the log about it. This stops that behavior.

* Privoxy is better than Polipo in every way. It has powerful privacy-assisting options (some disabled by default), and it can almost replace Torbutton on non-Firefox browsers. Firefox doesn't need Privoxy ''or'' Polipo because it can handle SOCKS5 natively.
* The most secure browser configuration is Firefox + Torbutton. You must use either Privoxy or Torbutton.
* Use standalone Tor, which outputs Tor's log to a console. ''Nearly all problems can be quickly solved by looking at the log.''
* The official Vidalia bundles install two torrc files in different locations. One of these is useless. (Can't remember which one.)

Summary: The Tor bundles suck. [[User:Theymos|theymos]] 09:21, 9 January 2011 (GMT)

* for the benefit of all users that run windows, would like to use Bitcoin client + IRC + browse the web via Tor, what would you recommend?
[[User:Ptmhd|Ptmhd]] 23:42, 12 January 2011 (GMT+1)
::Just download the expert bundle, make the torrc modifications I suggested (except the MaxCircuitDirtiness one), run it, and connect Bitcoin to localhost:9050. Same for IRC. If having the Tor window open all the time annoys you, minimize it to the tray with [http://www.abstractpath.com/powermenu/ PowerMenu]. There are also command-line options to tor.exe that [https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#HowdoIrunmyTorrelayasanNTservice create a Tor NT service] -- this is a good idea if you run Tor constantly.

::I never tried using IRC over Tor, so I can't recommend any particular IRC client. As a general rule, however, programs meant to be [http://portableapps.com/ portable] provide better anonymity.

::For browsing, download [http://portableapps.com/apps/internet/firefox_portable Firefox Portable] and install [https://addons.mozilla.org/en-US/firefox/addon/2275/ Torbutton] on it. Privoxy/Polipo are not necessary. [[User:Theymos|theymos]] 08:45, 13 January 2011 (GMT)

== tor hidden service ==

"For clients, hidden services are more secure than encrypted Tor HTTPS connections because the destination's ISP isn't involved as they are in the HTTPS case."

the isp isn't receiving https traffic, but the timing attacks don't rely on the protocol being https. how can the destination isp or the final relay not aid in a timing attack?

Poclbm

2015-12-10T21:07:21Z

Wargo: Updated links

'''poclbm''' ('''Python OpenCL bitcoin miner''') was a program that used the [[OpenCL miner|OpenCL]] framework to allow [[mining]] on a graphics card. It was the first open source GPU mining software to be produced.

==Download==
*[https://github.com/downloads/m0mchil/poclbm/poclbm_py2exe_20120920.7z Latest miner]
*[https://github.com/m0mchil/poclbm/ Sources]

==Flags to Use==

===Flags List===
{| class="wikitable"
|-
! Command line flags !! Flags descriptions
|-
| -version || Show program's version number and exit
|-
| -h, --help || Show help message and exit
|-
| -u USER, --user=USER || Set user name
|-
| --pass=PASSWORD || Set password
|-
| -o HOST, --host=HOST || Set RPC host (without 'http://')
|-
| -p PORT, --port=PORT || Set RPC port
|-
| -r RATE, --rate=RATE || Set hash rate display interval in seconds, default=1
|-
| -f FRAMES, --frames=FRAMES || Will try to bring single kernel execution to 1/frames seconds, default=30. Increase this for less desktop lag
|-
| -d DEVICE, --device=DEVICE || Set used device by id, by default asks for device
|-
| -a ASKRATE, --askrate=ASKRATE || Set how many seconds between getwork requests, default 5, max 10
|-
| -w WORKSIZE, --worksize=WORKSIZE || Set work group size, default is maximum returned by opencl
|-
| -v, --vectors || Enable vectors, which is faster on some cards.
|-
| --verbose || Enable verbose output, suitable for redirection to log file
|-
| --platform=PLATFORM || Set used platform by id
|-
| -s SLEEPTIME || Sleep for the specified number of seconds between iterations (default 0). Increase this to reduce hashing performance if your temperatures are too high.
|}

===Usage Tips===

ATI/AMD Radeon HD 5xxx cards (for example, HD 5770): use '-v -w128'

('-v -f10 -w128' works even better for HD5770.)

If you find the desktop laggy while mining, use '-f60'. This may decrease performance slightly.

Please update this section if you find better settings, or good settings for a card not listed here.

==FAQ==
[https://bitcointalk.org/index.php?topic=1334.0 Introductory post FAQ.]

==Founder==
[https://bitcointalk.org/index.php?action=profile;u=33 m0mchil]

==Guides and Installation==

===Windows===
[http://www.newslobster.com/random/how-to-get-started-using-your-gpu-to-mine-for-bitcoins-on-windows How to get started using your GPU to mine for Bitcoins on Windows]

===Ubuntu===
[https://www.bitcointalk.org/?topic=2636 Easy Ubuntu python OpenCL mining setup]

===Gentoo===
An poclbm ebuild can be found in the [[Gentoo|Gentoo Bitcoin]] overlay [https://gitorious.org/bitcoin/gentoo here]

===OpenSUSE===

This works on 11.4, 12.1 and should work on other versions - just replace the "12.1" in the repo URLs with your version number. This also assumes that you are already familiar with running getting the BitCoin client running (to run the GUI version on OpenSUSE you will need `libqt4-x11` or `libqt4-x11-32bit` installed).

Add the Python devel repo:

<code># zypper ar -r http://download.opensuse.org/repositories/devel:/languages:/python/openSUSE_12.1/devel:languages:python.repo</code>

and this user repo, which provides PyOpenCL (take a moment to appreciate this because if "scorot" didn't package it this would be a lot harder):

<code># zypper ar -r http://download.opensuse.org/repositories/home:/scorot/openSUSE_12.1/home:scorot.repo</code>

and finally this repo, which is needed for the previous to work (replace i586 with x86_64 if you're 64-bit):

<code># zypper ar -r http://download.nvidia.com/opensuse/12.1/ nvidia-i586</code>

Refresh your repos:

<code># zypper ref</code>

You will asked to accept the repo keys, respond with 'a' each time.

Install PyOpenCL:

<code># zypper in python-opencl</code>

Get the latest version of poclbm with git (`zypper in git-core` if you don't have git installed):

<code>$ git clone git://github.com/m0mchil/poclbm.git</code>

This will create a poclbm folder in your current directory. Change to it:

<code>$ cd poclbm</code>

And run it:

<code>$ python poclbm.py --device=0 http://user:pass@api.example.org:8332 [add whatever other flags you use]</code>

==License==
public domain<ref name="license">[http://github.com/m0mchil/poclbm/blob/master/LICENSE License file on github]</ref>

==See Also==

* [[poclbm-gui]] GUI frontend
* A highly efficient version: [[poclbm-mod]] by [[Bitcoin Pool]]
* [[Pooled mining]]
* [[Why a GPU mines faster than a CPU]]

==External Links==

* [http://github.com/m0mchil/poclbm Poclbm] project page on GitHub
* [https://bitcointalk.org/index.php?topic=1334 Project Thread]
* [http://www.bitcoinmining.com/bitcoin-mining-software/ Bitcoin Mining Software]

==References==
<references />

[[Category:Miners]]
[[Category:Free Software]]
[[Category:License/Public Domain]]
[[Category:Open Source]]
{{lowercase}}

XKCD Pool

2015-12-10T20:59:21Z

Wargo:

{{infobox company|name=XKCD Pool
|trading_name=XKCD Pool
|industry=[[Mining pool]]
|foundation=April 11, 2011
|defunct=2011
|owner=betawaffle
}}
'''XKCD Pool''' was a [[Pooled mining|mining pool]] by and for fans of the ''xkcd'' webcomic and its forum community. Randall Munroe, creator of ''xkcd'', has participated. The service was opened on April 11th, 2011. A web presence for the pool has never been established.<ref name="github">[https://github.com/betawaffle/poclbm Modified version for poclbm]</ref>
==See Also==

* [[Pooled Mining]]

==References==
<references />

[[Category:Pool Operators]]
{{Pools}}

Bitcoin faucet

2015-12-10T20:49:32Z

Wargo: General term

Bitcoin faucets are sites to earn some bitcoins for free. They usually needs address entry and captcha filling. You can revisit faucets every given time to get more.

First faucet was operated by [[User:Gavinandresen|Gavin Andresen]], however it is not functioning as of Jan 30 2013.

For [[Testnet]] there exist different faucets that is working which gives out coins for people who want to do tests on the Testnet.

[[Category:Services]]

Internationalization

2015-12-10T20:43:29Z

Wargo: Updated

== Bitcoin and '''internationalization''' (i18n) ==
Bitcoin is a global currency. Support for [[wikipedia:Internationalization_and_localization|internationalization and localization]] follows:

===Bitcoin.org===
The [http://www.bitcoin.org homepage] the Bitcoin project website has many [[Bitcoin.org translations|translations]].

===Bitcoin.it Wiki===
The multi-lingual scheme for this Wiki is described on [[Bitcoin.it Wiki]].

===Bitcoin client===
The [[Original_Bitcoin_client|original bitcoin client]] software supports ten languages, as-of version 0.3.20<ref>[https://bitcointalk.org/index.php?topic=3773.0;all Bitcoin Translation Room]</ref>

Changes can be made on [https://www.transifex.com/bitcoin/bitcoin/ Transifex] and generated source files are stored in src/qt/locale/ and compiled into Qt executable.

===Bitcoin forum - bitcointalk===
Local subforums are available on [[BitcoinTalk]]: https://bitcointalk.org/index.php#5

==References==
<references />

Bitcoin.org translations

2015-12-10T20:33:05Z

Wargo: Update - bitcoin.org now uses Transifex for translations

You can translate [http://bitcoin.org bitcoin.org] website using [https://www.transifex.com/projects/p/bitcoinorg/ Transifex].

==See Also==
* [[Internationalization]]
* https://github.com/bitcoin-dot-org/bitcoin.org#how-to-translate

Help:Installing Bitcoin Core

2015-12-10T19:33:32Z

Wargo: /* Getting my first coins */ This faucet doesn't exist for over 3 years and there are much more faucets now.

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

Download Windows Bitcoin Wallet at [https://bitcoin.org/en/download http://bitcoin.org/en/download] available in 64bit and 32bit.

[[File:Bitcoin-qt-welcome-install.jpeg|frame|none|Welcome Wizard Screen]]

Click Next to start installation.

[[File:Bitcoin-qt-location-install.jpg|frame|none|Destination Folder Screen]]

(Optional) Choose preferred directory then click Next.

[[File:Bitcoin-qt-start-menu-folder.jpg|frame|none|Choose Start Menu Screen]]

Click Install.

[[File:Bitcoin-qt-installation-complete.jpg|frame|none|Installation Screen]]

Wait until installation completes then click Next.

[[File:Bitcoin-qt-finish-install.jpg|frame|none|Finish Screen]]

Click Finish to start Bitcoin Wallet.

[[File:Bitcoin-qt-data-directory.jpg|frame|none|Welcome Screen of Bitcoin Core Wallet]]

On the first load, Bitcoin QT will asked you to choose directory where your Bitcoin block chain and wallet.dat will be stored. Click OK when done.

== For Mac OS Computers ==
Download Mac Bitcoin Wallet at http://bitcoin.org/en/download and expand the disk image.

[[File:BcOSX.png|frame|none|Contents of the Bitcoin disk image after expansion]]

Drag the Bitcoin icon to the desired install location, and double-click the icon to run the application.

== Initialization ==

The Bitcoin window will open and connections will start up in minutes. The blocks will begin downloading.

At this point, it is recommended to encrypt your wallet before receiving any bitcoins. Encrypting later may leave earlier addresses vulnerable to theft in the case that the system is compromised. This can be done from the Settings menu using the Encrypt Wallet function.

[[File:Bitcoin-qt-main-window.jpg|frame|none|Main window]]
[[File:Bitcoin-qt-preferences.jpg|frame|none|Preferences window on Windows]]

Your wallet will automatically have your first bitcoin address.

[[File:Bitcoin-qt-receiving-address.jpg|frame|none|Receive coins window]]

== Getting my first coins ==

You can get your first coins from [[Bitcoin Faucet|Bitcoin faucets]] which gives small amount of BTC for free.

The client will eventually show the transaction.

[[File:Bitcoin-qt-receive-transaction.png|frame|none]]

After about one hour the transaction should get 6 confirmations. You are able to spend the coins once the transaction shows at least 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:Bitcoin-qt-receive-transaction-confirmed.png|frame|none|Transaction once confirmed]]

* The [[Trade]] article shows hundreds of merchants who accept bitcoins.

== Buying Bitcoins ==

Bitcoins can be bought from individuals, on trading exchanges or from other online services. See the main page about [[Buying bitcoins|Buying Bitcoins]] for more information.

== 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|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.
* Leaving Bitcoin open improves connectivity for the network and ensures that you don't fall behind on the block chain. Also see [[FAQ#Do_I_need_to_configure_my_firewall_to_run_bitcoin?|the FAQ about port forwarding]]

Proceed to the [[Introduction|introduction]]

== Technical ==
=== Block chain ===
The [[block chain]] is a never-ending 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 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 mined 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]]

[[de:Erste Schritte]]
[[zh-cn:入门]]

{{Bitcoin Core documentation}}

Mark Karpelès

2015-12-10T19:11:34Z

Wargo: {{Mt._Gox}}

{{Infobox person|name=Mark Karpelès|image=[[File:MagicalTux.jpg|256px]]
|names=MagicalTux
|born={{birth date and age|1985|6|1}}
|active=2010–2014
|notableworks=[[Bitcoin Wiki]] [[QBitcoin]]
|knownfor=[[Mt. Gox]]
|twitter=MagicalTux
|reddit=MagicalTux
|bitcointalk=2134
|bitcoinwiki=MagicalTux
}}'''Mark Marie Robert Karpelès''',<ref name="US Bankruptcy Court case 14-31229-sgj15">{{cite document|title=Declaration of Mark Marie Mark Karpeles |url=http://www.scribd.com/doc/211626536/Karpeles-Declaration|publisher=US Bankruptcy Court for the Northern District of Texas Dallas Division|accessdate=13 March 2014|page=1|format=PDF}} The document, signed by "Robert Marie Mark Karpeles", was published by ''Ars Technica'' on the Scribd website, and according to ''Ars Technica'' is a court document filed in US Bankruptcy Court.</ref><ref name=farivar2014>{{cite news | url=http://arstechnica.com/tech-policy/2014/03/mtgox-files-for-us-bankruptcy-protection-to-put-ongoing-lawsuits-on-hold/ | work=Ars Technica | title=MtGox files for US bankruptcy protection to put lawsuits on hold | first=Cyrus | last=Farivar | date=2014-03-10 }}</ref> also sometimes known by his online alias '''MagicalTux''', was the CEO of [[Mt. Gox]].<ref name=copainsdavant>{{cite web|url= http://copainsdavant.linternaute.com/p/mark-robert-karpeles-4285933 |title= Mark Robert KARPELÈS, 28 ans (TOKYO, CHATILLON SUR MARNE, PARIS) |work= Copains d'avant – L'Internaute |publisher= CCM Benchmark Group |language= French |accessdate= 2014-02-27}}</ref><ref>{{cite news|url= http://www.forbes.com/sites/leoking/2014/02/26/mt-gox-ceo-mark-karpeles-i-am-still-in-japan/ |title= Mt. Gox CEO Mark Karpeles: 'I am still in Japan' |date= 2014-02-26 |work= Forbes |last= King |first= Leo |accessdate= 2014-02-27}}</ref>

==Early life and education==
Karpelès was born in Chenôve, France in 1985, the child of Anne Karpelès, a geologist.<ref name=lejsl>{{cite news|url= http://www.lejsl.com/saone-et-loire/2014/03/01/un-qi-superieur-a-la-moyenne |work= Le Journal de Saône et Loire |date= 2014-01-03 |first= Vincent |last= Gautronneau |language= French |title= Le génie côte-d'orien qui fait trembler le net }}</ref> He was raised in Dijon.<ref name=lejsl/><ref name=mick2014>{{cite news|last= Mick |first= Jason |date= March 5, 2014 |title= Bitcoin King: Mt. Gox CEO Mark Karpelès' History of Arrests, Firings |url= http://www.dailytech.com/Bitcoin+King+Mt+Gox+CEO+Mark+Karpels+History+of+Arrests+Firings/article34442.htm |newspaper= DailyTech |location= |publisher= |accessdate= March 9, 2014 }}</ref> Between 1995 and 2000, Karpelès was educated at Collège Prieuré de Binson in Châtillon-sur-Marne and Prieuré De Binson in Dormans.<ref name=copainsdavant>{{cite web|url= http://copainsdavant.linternaute.com/p/mark-robert-karpeles-4285933 |title= Mark Robert KARPELÈS, 28 ans (TOKYO, CHATILLON SUR MARNE, PARIS) |work= Copains d'avant – L'Internaute |publisher= CCM Benchmark Group |language= French |accessdate= 2014-02-27}}</ref> He then spent one year at Lycée Claude Bernard in Paris, before completing his education in 2003 at Lycée Louis Armand in Paris.<ref name=copainsdavant/>

According to Jason Mick of Dailytech, Karpelès was found guilty of a financial computer crime and of money transfer fraud when he was a teenager. The court apparently gave him a 3 month suspended sentence and no criminal record.<ref name=mick2014/> This was later confirmed by [[Ashley Barr]], a former [[Mt. Gox]] employee.<ref>{{cite reddit|r=Bitcoin|id=3fe92x|title=I'm Ashley Barr, A.K.A "Adam Turner", the first Mt.Gox employee, and alleged DPR (:/). AMA|date=1 August 2015|post=https://www.reddit.com/r/Bitcoin/comments/3fe92x/im_ashley_barr_aka_adam_turner_the_first_mtgox/ctnwmr1}}</ref>

In 2009, Karpelès moved to Japan.<ref>{{cite news|work= The Wall Street Journal |title= Bitcoin's Mt. Gox: a look at the man in charge |first= Eleanor |last= Warnock |first2= Takashi |last2= Mochizuki |date= 2014-02-28 |url= http://online.wsj.com/news/articles/SB10001424052702304071004579407022025451070 }}</ref><ref>{{cite news|url= http://www.20minutes.fr/high-tech/1309930-20140227-mtgox-mark-karpeles-entrepreneur-francais-coeur-scandale-bitcoin |title= MtGox: Mark Karpèles, un "supergeek" français au cœur du scandale bitcoin |work= 20 Minutes |language= French |date= 2014-02-27 |last= Philippe |first= Berry |accessdate= 2014-02-27}}</ref>

==Career==
According to Karpelès' LinkedIn page, he worked from 2003 to 2005 at Linux Cyberjoueurs as a software developer and network administrator.<ref name=li>{{cite web | url=http://jp.linkedin.com/in/karpeles | title=日本 Mark Karpelès | publisher=LinkedIn | last=Karpeles | first=Mark | accessdate=2014-02-27}}</ref> Karpelès is a PHP developer, and has contributed to the language's official repository of extensions with proctitle,<ref>{{cite web|url=http://pecl.php.net/package/proctitle|title=PECL :: Package :: proctitle|publisher=|accessdate=24 February 2015}}</ref> which allows the name of the current process to be changed on Linux systems.

Karpelès founded [[Tibanne Co.]] in 2009. He is CEO.<ref>http://www.cnbc.com/id/101486280</ref><ref>{{cite web|url=http://www.businessweek.com/articles/2013-05-31/a-bitcoin-exchange-goes-for-respectability|title=A Bitcoin Exchange Goes for Respectability|author=David Meyer|work=Businessweek.com|accessdate=24 February 2015}}</ref> He was a founding member of the [[Bitcoin Foundation]], created in 2012 with a mission to standardize and promote Bitcoin, and served on its board until February 2014.<ref>{{cite news | url=http://www.reuters.com/article/2014/02/24/mtgox-bitcoinfoundation-idUSL3N0LT15X20140224 | work=Reuters | date=February 23, 2014 | title=Mt. Gox resigns from Bitcoin Foundation | accessdate=25 February 2014 }}</ref><ref>{{cite web|url=http://www.pcworld.com/article/2100720/mt-gox-quits-bitcoin-foundation-board.html|title=Mt. Gox quits Bitcoin Foundation board|date=24 February 2014|work=PCWorld|accessdate=24 February 2015}}</ref><ref>{{cite web|url=http://www.forbes.com/sites/jonmatonis/2012/09/27/bitcoin-foundation-launches-to-drive-bitcoins-advancement/|title=Bitcoin Foundation Launches To Drive Bitcoin's Advancement|author=Jon Matonis|date=27 September 2012|work=Forbes|accessdate=24 February 2015}}</ref>

According to a joint report by Cyrus Farivar of Ars Technica and Pierre Alonso of Le Monde, Karpelès was found guilty of fraud when he was tried in absentia in France in 2010. He also admitted to having "pirated" a server to French authorities. He was sentenced to a year in jail but has not yet served his sentence.<ref>{{cite news |last=Farivar |first=Cyrus |date=August 1, 2014 |title=Why the head of Mt. Gox Bitcoin exchange should be in jail |url=http://arstechnica.com/tech-policy/2014/08/why-the-head-of-mt-gox-bitcoin-exchange-should-be-in-jail/ |newspaper=Ars Technica |location= |publisher= |accessdate=August 1, 2014 }}</ref><ref>{{cite news |last=Alonso |first=Pierre |date=August 1, 2014 |title=En France, le passé trouble de l’ancien " baron du bitcoin " |trans_title=Old bitcoin baron's old trouble in France |url=http://www.lemonde.fr/pixels/article/2014/08/01/en-france-le-passe-trouble-de-l-ancien-baron-du-bitcoin_4464044_4408996.html |language=French |newspaper=Le Monde |location= |publisher= |accessdate=August 1, 2014 }}</ref>

[[Ross Ulbricht]], while on trial for operating the undercover [[Silk Road]] marketplace, claimed that the pseudonymous "Dread Pirate Roberts" behind Silk Road was not him but Mark Karpelès.<ref name=ccnews2015>{{cite web|title=UNDERCOVER SILK ROAD AGENT BELIEVED DREAD PIRATE ROBERTS (DPR) TO BE MARK KARPELES OF MT. GOX|url=https://www.cryptocoinsnews.com/undercover-silk-road-agent-believed-dread-pirate-roberts-dpr-to-be-mark-karpeles-mt-gox/|accessdate=16 January 2015}}</ref> Karpelès publicly denied the claim on Twitter,<ref>{{cite web
| title =Mark Karpeles on Twitter: "This is probably going to be disappointing for you, but I am not and have never been Dread Pirate Roberts."
| url = https://twitter.com/MagicalTux/status/555892860654862337
| date = January 15, 2015
| accessdate = January 28, 2015}}</ref> and Ulbricht was eventually found guilty.<ref name="ars-conviction">{{cite web|date=4 February 2015|accessdate=4 February 2015|first=Joe|last=Mullin|work=Ars Technica|title=Ulbricht guilty in Silk Road online drug-trafficking trial|url=http://arstechnica.com/tech-policy/2015/02/ulbricht-guilty-in-silk-road-online-drug-trafficking-trial/}}</ref>

===Bitcoin Wiki===
In 2010, Karpelès reopened the [[Bitcoin Wiki]] with MediaWiki. Karpelès's MediaWiki and [[Martti Malmi]]'s dokuwiki sites coexisted briefly before it was evident that the community preferred MediaWiki.<ref>[https://en.bitcoin.it/w/index.php?title=User_talk:Taras&diff=55065&oldid=54906 Post to User talk:Taras by theymos]</ref> All pages on the dokuwiki instance were copied to the MediaWiki one in 2010 and in 2015 the a project to import the complete history of those pages began.<ref>[[Bitcoin Wiki:dokuwiki]]</ref>

Karpelès also created [[CryptoPayment]], a MediaWiki extension that was used by the Bitcoin Wiki for several years. The extension granted editing rights to users who paid a small anti-spam fee.{{citation needed}}

Shortly after reopening the Bitcoin Wiki, Karpelès added a [[Bitcoin Map]] tool to it.<ref name="bm">[https://en.bitcoin.it/w/index.php?title=Bitcoin_Map&diff=600&oldid=579 Bitcoin Map] on the [[Bitcoin Wiki]] in 2010</ref> The map plotted nodes geographically<ref name="bm"/> and a still of it was featured on the [[Main Page]] for years.

===Mt. Gox===
Karpelès acquired 88% of the Tokyo-based company [[Mt. Gox]] from programmer [[Jed McCaleb]] in 2011.<ref>{{cite web|url=http://dealbook.nytimes.com/2014/02/28/mt-gox-files-for-bankruptcy/|title=Erosion of Faith Was Death Knell for Mt. Gox
|author= Rachel Abrams Matthew Goldstein and Hiroko Tabuchi |work=The New York Times|accessdate=24 February 2015}}</ref><ref>{{cite web| date=April 1, 2013|last=Jeffries|first=Adrianne|title=Barons of Bitcoin|url=http://www.theverge.com/2013/4/1/4154500/mt-gox-barons-of-bitcoin|work=The Verge|accessdate=13 March 2014}}</ref><ref>http://online.wsj.com/article/BT-CO-20140310-712183.html</ref> Mt. Gox filed for bankruptcy in Japan on February 28, 2014 and for [[wikipedia:Chapter 15, Title 11, United States Code|Chapter 15]] bankruptcy in the United States (Texas) in March 2014.<ref name="US Bankruptcy Court case 14-31229-sgj15">{{cite document|title=Declaration of Mark Marie Mark Karpeles |url=http://www.scribd.com/doc/211626536/Karpeles-Declaration|publisher=US Bankruptcy Court for the Northern District of Texas Dallas Division|accessdate=13 March 2014|page=1|format=PDF}} The document, signed by "Robert Marie Mark Karpeles", was published by ''Ars Technica'' on the Scribd website, and according to ''Ars Technica'' is a court document filed in US Bankruptcy Court.</ref><ref>{{cite web|url=http://www.wired.com/wiredenterprise/2014/03/gox-texas/|title=Bitcoin Exchange Mt. Gox Files for U.S. Bankruptcy as Death Spiral Continues|work=WIRED|accessdate=24 February 2015}}</ref><ref>{{cite web|title=Mt. Gox files for Chapter 15 in U.S.|url=http://www.marketwatch.com/story/mt-gox-files-for-chapter-15-in-us-2014-03-10|work=Market Watch|accessdate=13 March 2014}}</ref>

Karpelès was subpoenaed by the [[wikipedia:United States Department of the Treasury|United States Department of the Treasury]]'s [[wikipedia:Financial Crimes Enforcement Network|Financial Crimes Enforcement Network]] to appear in Washington, D.C. to provide testimony on April 18, 2014. Karpelès, in a court filing by Mt. Gox lawyers, responded that he does not have a lawyer for this matter and therefore declined to appear.<ref>{{cite web|url=http://www.reuters.com/article/2014/04/15/us-bitcoin-mtgox-idUSBREA3E02S20140415|title=Mt. Gox founder won't appear in U.S. for questions about bankruptcy case|work=Reuters|accessdate=24 February 2015}}</ref><ref>{{cite web|url=http://www.cnet.com/news/mt-gox-founder-wont-attend-bitcoin-exchanges-bankruptcy-hearing/|title=Mt. Gox founder won't attend US bankruptcy hearing|publisher=CBS Interactive|work=CNET|accessdate=24 February 2015}}</ref> Karpelès instead sought to appear in D.C. to testify on May 5, 2014.<ref>{{cite web|url=http://www.computerworld.com/s/article/9247673/Mt._Gox_seeks_postponement_of_CEO_s_U.S._court_deposition?taxonomyId=17|title=Mt. Gox seeks postponement of CEO's U.S. court deposition|author=John Ribeiro|date=15 April 2014|work=Computerworld|accessdate=24 February 2015}}</ref><ref>{{cite web|url=http://www.bbc.com/news/technology-27032221|title=BBC News - MtGox chief refuses to go to Bitcoin bankruptcy hearing|work=BBC News|accessdate=24 February 2015}}</ref>{{clarification needed}}

==References==
<references/>
{{Mt._Gox}}
{{article}}
[[Category:Mt. Gox]]
[[Category:People]]
[[Category:Criminals]]
{{wp|Mark_Karpelès}}

Goxsh

2015-12-10T19:10:12Z

Wargo: {{Mt._Gox}}

{{infobox software
|image=[[File:Goxsh.png|200px]]
|name=goxsh
|author=ahihi
|developer=Optonic
|language=Python
|released=June 17, 2011
|stable=0.25 August 18, 2011
}}'''goxsh''' was an open source command-line frontend to the [[MtGox|Mt. Gox Bitcoin Exchange]] written in Python.

This tool was first announced by ahihi on June 17, 2011.<ref>{{cite btct|id=18311|title=goxsh — command-line frontend to Mt. Gox|date=17 June 2011}}</ref> Six weeks later, Optonic forked the project and continued development.<ref>{{cite btct|id=33017|title=New goxsh fork|date=30 July 2011}}</ref>

==External Links==

* Original [https://github.com/ahihi/goxsh goxsh] project on GitHub
* Optonic's fork of [https://github.com/Optonic/goxsh goxsh] on GitHub
* [http://www.goxsh.info/ goxsh] homepage

==References==
<references />

{{Mt._Gox}}
[[Category:Mt. Gox]]
[[Category:Barely notable subjects]]
[[Category:Open source software]]
{{stub}}
{{article}}
{{lowercase}}