Bitcoin Wiki - User contributions [en]

Network

2013-12-25T23:30:30Z

Lux: added definition of SPV clients, removed stale v0.3 information regarding getheaders, updated external links

Bitcoin uses a simple broadcast network to propagate transactions and blocks. All communications are done over TCP. Bitcoin is fully able to use ports other than 8333 via the -port parameter. IPv6 is [https://bitcointalk.org/index.php?topic=81378.0 suported] with Bitcoind/Bitcoin-Qt v0.7.

== Messages ==
* ''version'' - Information about program version and block count. Exchanged when first connecting.
* ''verack'' - Sent in response to a version message to acknowledge that we are willing to connect.
* ''addr'' - List of one or more IP addresses and ports.
* ''inv'' - "I have these blocks/transactions: ..." Normally sent only when a ''new'' block or transaction is being relayed. This is only a list, not the actual data.
* ''getdata'' - Request a single block or transaction by hash.
* ''getblocks'' - Request an ''inv'' of all blocks in a range.
* ''getheaders'' - Request a ''headers'' message containing all block headers in a range.
* ''tx'' - Send a transaction. This is sent only in response to a ''getdata'' request.
* ''block'' - Send a block. This is sent only in response to a ''getdata'' request.
* ''headers'' - Send up to 2,000 block headers. Non-generators can download the headers of blocks instead of entire blocks.
* ''getaddr'' - Request an ''addr'' message containing a bunch of known-active peers (for bootstrapping).
* ''submitorder'', ''checkorder'', and ''reply'' - Used when performing an [[IP address|IP transaction]].
* ''alert'' - Send a network alert.
* ''ping'' - Does nothing. Used to check that the connection is still online. A TCP error will occur if the connection has died.

More information and in-depth technical information is in the [[Protocol Specification]].

== Connection ==

To connect to a peer, you send a ''version'' message containing your version number, block count, and current time. The remote peer will send back a ''verack'' message and his own ''version'' message if he is accepting connections from your version. You will respond with your own ''verack'' if you are accepting connections from his version.

The time data from all of your peers is collected, and the median is used by Bitcoin for all network tasks that use the time (except for other version messages).

You then exchange ''getaddr'' and ''addr'' messages, storing all addresses that you don't know about. ''addr'' messages often contain only one address, but sometimes contain up to 1000. This is most common at the beginning of an exchange.

== Standard relaying ==

When someone sends a transaction, they send an ''inv'' message containing it to all of their peers. Their peers will request the full transaction with ''getdata''. If they consider the transaction valid after receiving it, they will also broadcast the transaction to all of their peers with an ''inv'', and so on. Peers ask for or relay transactions only if they don't already have them. A peer will never rebroadcast a transaction that it already knows about, though transactions will eventually be forgotten if they don't get into a block after a while. The sender and receiver of the transaction will rebroadcast, however.

Anyone who is generating will collect valid received transactions and work on including them in a block. When someone does find a block, they send an ''inv'' containing it to all of their peers, as above. It works the same as transactions.

Everyone broadcasts an ''addr'' containing their own IP address every 24 hours. Nodes relay these messages to a couple of their peers and store the address if it's new to them. Through this system, everyone has a reasonably clear picture of which IPs are connected to the network at the moment. After connecting to the network, you get added to everyone's address database almost instantly because of your initial ''addr''.

Network alerts are broadcast with ''alert'' messages. No ''inv''-like system is used; these contain the entire alert. If a received alert is valid (signed by one of the people with the private key), it is relayed to all peers. For as long as an alert is still in effect, it is rebroadcast at the start of every new connection.

== Initial block download ==

At the start of a connection, you send a ''getblocks'' message containing the hash of the latest block you know about. If the peer doesn't think that this is the latest block, it will send an ''inv'' that contains up to 500 blocks ahead of the one you listed. You will then request all of these blocks with ''getdata'', and the peer will send them to you with ''block'' messages. After you have downloaded and processed all of these blocks, you will send another ''getblocks'', etc., until you have all of the blocks.

== Thin SPV Clients ==

[[BIP 0037]] introduced support for thin or lite clients by way of Simple Payment Verification. SPV clients do not need to download the full block contents to verify the existence of funds in the blockchain, but rely on the chain of block headers and bloom filters to obtain the data they need from other nodes. This method of client communication allows high security trustless communication with full nodes, but at the expensive of some privacy as the peers can deduce which addresses the SPV client is seeking information about.

[[MultiBit]] and [[Bitcoin Wallet]] work in this fashion using the library [[bitcoinj]] as their foundation.

== Bootstrapping ==

You choose which peers to connect to by sorting your address database by the time since you last saw the address and then adding a bit of randomization.

Bitcoin has three methods of finding peers.

=== Addr ===

The ''addr'' messages described above create an effect similar to the IRC bootstrapping method. You know reasonably quickly whenever a peer joins, though you won't know for a while when they leave.

Bitcoin comes with a list of addresses known as "seed nodes". If you are unable to connect to IRC and you've never connected to the network before, the client will update the address database by connecting to one of the nodes from this list.

The -addnode command line option can be used to manually add a node. The -connect option can force bitcoin to connect only to a specific node.

=== DNS ===

Bitcoin looks up the IP Addresses of several host names and adds those to the list of potential addresses. This is the default seeding mechanism, as of v0.6.x and later.

=== IRC ===

As-of version 0.6.x of the Bitcoin client, IRC bootstrapping is no longer enabled by default. The information below is accurate for most versions prior.

Bitcoin joins a random channel between #bitcoin00 and #bitcoin99 on irc.lfnet.org. Your nick is set to an encoded form of your IP address. By decoding all the nicks of all users on the channel, you get a list of all IP addresses currently connected to Bitcoin.

For hosts that cannot make outbound connections on port 6667, the lfnet servers are also [[FAQ#Do_I_need_to_configure_my_firewall_to_run_bitcoin?|listening on port 7777]].

== Heartbeat ==

If thirty minutes or more has passed since the client has transmitted any messages it will transmit a message to keep the connection to the peer node alive.

If ninety minutes has passed since a peer node has communicated any messages, then the client will assume that connection has closed.

== See Also ==

* [[Protocol Specification]]
* [[Satoshi Client Node Discovery]]
* [http://bitcoinstatus.rowit.co.uk/ Historical Network Status (no longer updated)]
* [http://getaddr.bitnodes.io/ Bitnodes.io's network size estimate]

[[Category:Technical]]

[[pl:Sieć]]

List of address prefixes

2013-12-25T23:09:48Z

Lux: removed "dead" altcoin prefixes, added private key example for testnet

Blockchain-based currencies use addresses, which are a [[Base58Check encoding]] of some hash, typically that of a public key. The encoding includes a version byte, which affects the first character in the address. The following is a list of some prefixes which are in use.

{| class="wikitable"
|-
!Decimal version
!Leading symbol
!Use
!Example
|-
|0
|1
|Bitcoin pubkey hash
|<tt>17VZNX1SN5NtKa8UQFxwQbFeFc3iqRYhem</tt>
|-
|5
|3
|Bitcoin script hash
| 3EktnHQD7RiAE6uzMj2ZifT9YgRrkSgzQX
|-
|48
|L
|Litecoin pubkey hash
|<tt>LhK2kQwiaAvhjWY799cZvMyYwnQAcxkarr</tt>
|-
|52
|M or N
|Namecoin pubkey hash
|<tt>NATX6zEUNfxfvgVwz8qVnnw3hLhhYXhgQn</tt>
|-
|111
|m or n
|Bitcoin testnet pubkey hash
|<tt>mipcBbFg9gMiCh81Kj8tqqdgoZub1ZJRfn</tt>
|-
|128
|5
|Bitcoin Private key
|<tt>5Hwgr3u458GLafKBgxtssHSPqJnYoGrSzgQsPwLFhLNYskDPyyA</tt>
|-
|196
|2
|Testnet script hash
|
|-
|239
|9
|Testnet Private key
|<tt>92Pg46rUhgTT7romnV7iGW6W1gbGdeezqdbJCzShkCsYNzyyNcc</tt>
|}

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

Testnet

2013-12-25T22:53:43Z

Lux: reorganization of external links, added BTClook's testnet explorer

The '''testnet''' is an alternative Bitcoin [[block chain]], to be used for testing. This allows application developers or bitcoin testers to experiment, without having to use real bitcoins or worrying about breaking the main bitcoin chain.

Run bitcoin or bitcoind with the -testnet flag to use the testnet (or put testnet=1 in the bitcoin.conf file).

There have been three generations of testnet. Testnet2 was just the first testnet reset with a different genesis block, because people were starting to trade testnet coins for real money. '''Testnet3''' is the current test network. It was introduced with the 0.7 release, introduced a third genesis block, a new rule to avoid the "difficulty was too high, is now too low, and transactions take too long to verify" problem, and contains blocks with edge-case transactions designed to test implementation compatibility.

==Differences==
* Default Bitcoin network protocol listen port is 18333 (instead of 8333)
* Default RPC connection port is 18332 (instead of 8332)
* Bootstrapping IRC channel is #bitcoinTEST instead of #bitcoin (both on irc.lfnet.org). The built-in node list is disabled.
* A different value of ADDRESSVERSION field ensures no testnet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are 0x0B110907 (instead of 0xF9BEB4D9)
* Minimum [[difficulty]] of 1.0 on testnet is equal to difficulty of 0.5 on mainnet. This means that the mainnet-equivalent of any testnet difficulty is half the testnet difficulty. In addition, if no block has been found in 20 minutes, the difficulty automatically resets back to the minimum for a single block, after which it returns to its previous value.
* A new genesis block
* The IsStandard() check is disabled so that non-standard transactions can be experimented with.

==Genesis Block==

Testnet uses a different genesis block to the main network. You can find it [https://www.biteasy.com/testnet/blocks/000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943 here] or [http://blockexplorer.com/testnet/b/0 here].
The testnet was reset with a new genesis block for the 0.7 bitcoin release.

==External links==
* [https://bitcointalk.org/?topic=4483.0 Test Network forum topic]
* [http://faucet.xeno-genesis.com/ Mojocoin Testnet3 Faucet]
* [http://tpfaucet.appspot.com/ TP's TestNet Faucet]
* [https://freebitcoins.appspot.com/test/ Testnet Faucet (closed)]
* [http://testnet.btclook.com/ BTCLook Testnet Explorer]
* [https://www.biteasy.com/testnet/blocks Biteasy.com Testnet Blockexplorer]
* [http://pool.qdoop.net:18331/chain/Testnet3 Testnet3 ABE based Block Explorer]
* [http://blockexplorer.com/testnet Testnet Block Explorer]
* [https://sourceforge.net/projects/bitcoin/files/Bitcoin/testnet-in-a-box/ Testnet-In-A-Box self-contained testnet]
* [https://github.com/freewil/bitcoin-testnet-box Forked/Updated testnet-box]

[[Category:Technical]]
[[Category:Developer]]

Xtreme Miners Leopard

2013-12-25T08:57:35Z

Lux: Undo revision 43420 by Lux (talk)

{{delete|Astroturfing probable scam.}}

The Leopard is the 2.5 TH Miner from Xtreme Miners.

Xtreme Miners are the perfect combination of latest technology, most powerful hashing power on the market (compared to size and price), and futuristic design.

We offer 3 different types of miners, The Leopard is the smallest one (2,5 TH/s)
It works perfectly stable for 24 hours straight and longer.
The Leopards will start shipping January 2014.

Details:

- 2,5 TH/s

- Dimensions: 15“ x 13.3“ x 13.7“ (38cm x 34cm x 35cm)

- 28nm ASIC technology

- Silent Cooling

- In-built WiFi Connection (without Antenna)

- Less than 750 watt (0.3 per GH)

- 1 Year Guarantee

Price: $ 5.800

COMES WITH :

- Power Supply

- Free Remote Power Outlet & Smartphone App

- Free User Guide

- Free Personal Assistance for Setup

Deterministic wallet

2013-12-25T08:52:06Z

Lux: article rewrite, clarification of "type 2 wallets"

A deterministic wallet is a system of deriving keys from a single starting point known as a seed. The seed allows a user to easily back up and restore a wallet without needing any other information and can in some cases allow the creation of public addresses without the knowledge of the private key.

== Benefits ==

Early clients such as the [[Satoshi client]] generate a buffer of fresh random private keys to be used as receiving and [[change|change addresses]] in the future. This has the effect of invalidating backups after a short period when the keypool buffer (typically 100 addresses) is exhausted, deterministic wallets can generate an unlimited number of addresses on the fly and as such don't suffer from this issue. As the addresses are generated in a known fashion rather than randomly some clients can be used on multiple devices without the risk of losing funds. Users can conveniently create a single backup of the seed in a human readable format that will last the life of the wallet, without the worry of this backup becoming stale.

Certain types of deterministic wallet (BIP0032 and Armory) additionally allow for the complete separation of private and public key creation for greater security and convenience. In this model a server can be set up to only know the Master Public Key of a particular deterministic wallet. This allows the server to create as many public keys as is necessary for receiving funds, but a compromise of the MPK will not allow an attacker to spend from the wallet. They can alternatively be used in [[Electrum]] and [[Armory]] to enable completely offline storage and spending, where an offline computer knows the private key and an online one knows only the MPK. Transactions spending coins are ferried between the two computers via USB storage which avoids exposing the offline computer to a network-based attack.

==Types==

===Type 1 deterministic wallet===
A type 1 deterministic wallet is a simple method of generating addresses from a known starting string, as such it does not allow advanced features such as a Master Public Key. To generate a private key take SHA256(string + n), where n is an ASCII-coded number that starts from 1 and increments as additional keys are needed.

This type of wallet can be created by Casascius Bitcoin Address Utility.

===Type 2 hierarchical deterministic wallet===
This wallet type is described in [[BIP 0032]] and is fully implemented in [[Electrum]] and [[CarbonWallet]]. The seed is a random 128 bit value presented to the user as a 12 word mnemonic using common English words. The seed is used after 100,000 rounds of SHA256 to slow down attacks against weak user-chosen strings. [https://bitcointalk.org/index.php?topic=330672.msg3547258#msg3547258].

The initial description and workings of this wallet type is credited to Gregory Maxwell. [https://bitcointalk.org/index.php?topic=19137.msg239768#msg239768]

===Armory deterministic wallet===
[[Armory]] has its own Type-2 deterministic wallet format based on a "root key" and a "chain code." Earlier versions of Armory required backing up both the "root key" and "chaincode," while newer versions start deriving the chaincode from the private key in a non-reversible way. These newer Armory wallets (0.89+) only require the single, 256-bit root key. This older format is intended to be phased out in favor of the standard BIP0032 format. [https://bitcointalk.org/index.php?topic=351099.msg3770818#msg3770818]

Xtreme Miners Leopard

2013-12-25T07:45:00Z

Lux: astroturfing warning

'''This entry appears to be astroturfing, the company is likely untrustworthy. Use caution.''' [[User:Lux|Lux]] ([[User talk:Lux|talk]]) 07:45, 25 December 2013 (GMT)

-----------

The Leopard is the 2.5 TH Miner from Xtreme Miners.

Xtreme Miners are the perfect combination of latest technology, most powerful hashing power on the market (compared to size and price), and futuristic design.

We offer 3 different types of miners, The Leopard is the smallest one (2,5 TH/s)
It works perfectly stable for 24 hours straight and longer.
The Leopards will start shipping January 2014.

Details:

- 2,5 TH/s

- Dimensions: 15“ x 13.3“ x 13.7“ (38cm x 34cm x 35cm)

- 28nm ASIC technology

- Silent Cooling

- In-built WiFi Connection (without Antenna)

- Less than 750 watt (0.3 per GH)

- 1 Year Guarantee

Price: $ 5.800

COMES WITH :

- Power Supply

- Free Remote Power Outlet & Smartphone App

- Free User Guide

- Free Personal Assistance for Setup

User:XtremeMiners

2013-12-25T07:44:07Z

Lux: noting

'''This entry appears to be astroturfing, the company is likely untrustworthy. Use caution.''' [[User:Lux|Lux]] ([[User talk:Lux|talk]]) 07:44, 25 December 2013 (GMT)

-----------

Xtreme Miners take Bitcoin Mining to a whole other level.
Be a part of the future, and let us shape it – together!
Let us create a world where a decentralized currency rules, where you don’t have to confide your money to any bank or governmental institution.

Bitcoins have the ability to change the world forever, and you can participate in this change!

Let our Miners enthuse you, and let us welcome you into the future of Bitcoin Mining.

Visit us at www.xtrememiners.net

User talk:Nanotube

2013-12-25T07:41:38Z

Lux: /* Astroturfing removal */ new section

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

==Help Page==

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

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

== user access to modify pages ==

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

== Testing ==

Did you get an email notification about this?
Please leave a similar comment on my own talk page.

[[User:Ripper234|Ripper234]] ([[User talk:Ripper234|talk]]) 20:45, 30 April 2013 (GMT)

== Message text fix ==

Please [https://en.bitcoin.it/wiki/MediaWiki:Centralauth-groupname edit this page] and make it say something like "The bitcoin wikis", this will get the goofy wikimedia foundation text off the login screen. Thanks. --[[User:Gmaxwell|Gmaxwell]] ([[User talk:Gmaxwell|talk]]) 20:40, 9 May 2013 (GMT)
:: Thanks for the heads-up, done. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 23:32, 9 May 2013 (GMT)

== project:todo ==

Hi! I have some ideas for improving this wiki. See [[project:todo]]. I hope you like it. [[User:Guaka|Guaka]] ([[User talk:Guaka|talk]]) 12:27, 14 July 2013 (GMT)

== table sorting not working here ==
Why is it when I try to create a sortable table on: https://en.bitcoin.it/wiki/Comparison_of_mining_pools it doesn't work?

I even tested it out by copying and pasting this simple example "code": http://en.wikipedia.org/wiki/Help:Sorting

It did not show a sortable table even with the copying and pasting of the code. Is it possible that bitcoin.it is using an older version of wiki and that's why??

* What's the problem? The table on that page has always worked fine for sorting... --[[User:Luke-jr|Luke-jr]] ([[User talk:Luke-jr|talk]]) 21:05, 9 November 2013 (GMT)

== Astroturfing removal ==

Can the following be removed? They appear to be astroturfing of a very suspicious looking company. I can find no record of them existing outside of this wiki.

https://en.bitcoin.it/w/index.php?title=Xtreme_Miners_Tiger

https://en.bitcoin.it/w/index.php?title=Xtreme_Miners_Lion