Bitcoin Wiki - User contributions [en]

Brasil Bitcoin Market

2012-02-29T15:19:05Z

Humilulo:

A [[currency exchange]] site serving those trading between bitcoins and the following currencies:

* BRL (Brazilian Real)

The language supported by the site is Portugese.

The service was first seen in September, 2011.

Payments are sent and received through, MoIP (Money over IP) which transacts using the bank wire network.

As of February 2012, Brasil Bitcoin Market has not been in operation since November 10, 2011.

==See Also==

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

==External Links==

* [https://bbmarket.com.br Brasil Bitcoin Market] web site

==References==
<References />

[[Category:Exchanges]]

Nonce

2012-02-29T14:30:58Z

Humilulo: "the the" --> "the"

The "nonce" in a bitcoin [[block]] is a 32-bit (4-byte) field whose value is set so that the [[hash]] of the block will contain a run of zeros. The rest of the fields may not be changed, as they have a defined meaning.

Any change to the block data (such as the nonce) will make the block hash completely different. Since it is [[wikipedia:Cryptographic hash function|believed infeasible]] to predict which combination of bits will result in the right hash, many different nonce values are tried, and the hash is recomputed for each value until a hash containing the required number of zero bits is found. As this iterative calculation requires time and resources, the presentation of the block with the correct nonce value constitutes [[proof of work]].

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

Tonal Bitcoin

2012-02-27T15:41:54Z

Humilulo: added spaces between digits in decimal column to add digit grouping so readers can much more easily count the digits.

Tonal Bitcoin is a representation of the Bitcoin network aimed toward the minority of people who use the Tonal number system.
This is an alternative to decimal and the metric system, which improves usability drastically by allowing for infinite binary division.
For more information on the Tonal system in general, please see [http://www.lulu.com/product/file-download/tonal-system/10991091 the book].

Please note, that all numbers of TBC and its divisions/multipliers are written in [http://en.wikipedia.org/wiki/Tonal_System Tonal], not decimal.
This means that instead of counting 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10-- you count: 0, 1, 2, 3, 4, 5, 6, 7, 8, , 9, , , , , , 10. Some higher-value digits may require installing a [http://luke.dashjr.org/education/tonal/glyphs/fonts/ font].

{| border="1" style="text-align:right;font-family:Console, Luxi Mono, fixed"
|- style="background-color:silver"
! Abbreviation
! Pronunciation
! [[Tonal BitCoin|Tonal (TBC)]]
! Decimal (BTC)
|-
|
| Tam-BitCoin
| 1 0000 0000     
| 2 814 749.767 106 56
|-
| ᵇTBC
| Bong-BitCoin
| 1 0000     
| 42.949 672 96
|-
| ᵐTBC
| Mill-BitCoin
| 1000     
| 2.684 354 56
|-
| ˢTBC
| San-Bitcoin
| 100     
| 0.167 772 16
|-
| ᵗTBC
| Ton-BitCoin
| 10     
| 0.010 485 76
|-
| TBC
| BitCoin*
| 1     
| 0.000 655 36
|-
| TBCᵗ
| BitCoin-ton
| 0.1   
| 0.000 040 96
|-
| TBCˢ
| BitCoin-san
| 0.01  
| 0.000 002 56
|-
| TBCᵐ
| BitCoin-mill
| 0.001 
| 0.000 000 16
|-
| TBCᵇ
| BitCoin-bong
| 0.0001
| 0.000 000 01
|}

<small>* Tonal BitCoin and Decimal BitCoin can be differentiated by the pronunciation of the numbers. "One bitcoin", "two bitcoin", etc is decimal, but "an bitcoin", "de bitcoin" is tonal.</small>

The total number of Tonal BitCoins ever (analogous to the 21mil BTC) is just over 7.75059 tam-bitcoin.

== Compatible Clients ==

While all BitCoin clients will correctly approximate values in decimal bitcoin, actual Tonal compatibility is sparse.

* [[Spesmilo]], despite its name, can be configured to display TBC

== Guessing TBC or BTC ==

Given variable 'value' in base units (uBTCents/TBCᵇ), one can guess whether it is properly Decimal BitCoin or Tonal BitCoin with the following pseudo-code:

if ( ! ( this % 0x10000 ) )
Choose Tonal BitCoin
if ( ! ( this % 1000000 ) )
Choose Decimal BitCoin
if ( ! ( this % 0x100 ) )
Choose Tonal BitCoin

=== Python ===

<pre>import math

def formatBTC(n, addSign = False):
s = "%0.2f BTC" % (math.ceil(n * 100) / 100.,)
if addSign and n >= 0:
s = "+" + s
return s

def Bitcoin2BTC(n):
return n / 100000000.

toTonalDict = dict(((57, u'\ue9d9'), (65, u'\ue9da'), (66, u'\ue9db'), (67, u'\ue9dc'), (68, u'\ue9dd'), (69, u'\ue9de'), (70, u'\ue9df'), (97, u'\ue9da'), (98, u'\ue9db'), (99, u'\ue9dc'), (100, u'\ue9dd'), (101, u'\ue9de'), (102, u'\ue9df')))

def formatTBC(n, addSign = False):
s = "%x" % n
n %= 1
if n:
s += '.'
while n:
n *= 16
s += "%x" % n
n %= 1
s = unicode(s).translate(toTonalDict)
s += " TBC"
if addSign and n >= 0:
s = "+" + s
return s

def Bitcoin2TBC(n):
return n / 65536.

def formatBitcoin(n, addSign = False):
if not n % 0x10000:
return formatTBC(Bitcoin2TBC(n), addSign);
if not n % 1000000:
return formatBTC(Bitcoin2BTC(n), addSign);
if not n % 0x100:
return formatTBC(Bitcoin2TBC(n), addSign);
s = "%d uBTCents" % (n,);
if addSign and n > 0:
s = "+" + s;
return s;</pre>

== Criticism ==

* [[User:Davout|Davout]] has to google this page each time someone mentions an amount in tonal bitcoin

=== Can be done without funny characters ===

The tonal notation requires extra fonts. Within the programming community there is a widely accepted convention for hexadecimal notation: use A-F for the higher order digits. Thus, one counts 0,1,2,3, ... , 9,A,B,C,D,E,F,10,11 .... There are even two conventions, (which are lacking in tonal) for distinguishing a base-16 number from a decimal. The C convention prefixes 0x and the Motorola convention suffixes h. So, the number san, 256 (decimal) would be written 0x100 or 100h. In tonal notation, it would only be written 100, and thus potentially confused with decimal 100 which is 0x64.

Thus programming notation accomplishes the same goals as tonal notation with no requirement for changing fonts, thus is more suited to wide usage. Further the prefix and suffix conventions lead to less ambiguity.

Bitcoin Core

2012-02-27T15:33:55Z

Humilulo: /* Features */ fixed 'uBTC' technicality. now correctly shows 'µBTC' instead.

'''Bitcoin-Qt''' is an MIT-licenced Qt4 GUI for the original [[Bitcoin]] codebase. Initially designed by John Smith, it is now maintained by the [[developers]] of the [[bitcoind|original Bitcoin client]]., which it has been bundled in since version 0.5.

==Features==
* Compatibility with Linux (both GNOME and KDE), Mac OS X and Windows
* All functionality of the original wxWidgets client
* User friendly, tabbed interface
* Asks for confirmation before sending coins
* CSV export of transactions
* Clearer transaction list with status icons and real-time filtering
* Progress bar on initial block download
* Languages: Dutch, English, German
* Sendmany support in UI (send to multiple recipients in one transaction)
* Multiple [[Units|unit]] support, can show subdivided bitcoins (mBTC, µBTC) for users that like large numbers (currently only decimal units)
* Splash screen that details progress

==Current version==
Source code (and build instructions for supported platforms) can be found at the [https://github.com/bitcoin/bitcoin Bitcoin GitHub page].

==External Links==

* [https://forum.bitcoin.org/index.php?topic=15276.0 Forum thread] (includes screenshots)
* [https://github.com/laanwj/bitcoin-qt Bitcoin-Qt development GitHub repository]
* [https://github.com/bitcoin/bitcoin Original Bitcoin codebase GitHub repository]

==See also==

* [[QBitcoin]]
* [[bitcoind]]

[[Category:User Interfaces]]
[[Category:Frontends]]
[[Category:Free Software]]
[[Category:Open Source]]

Running Bitcoin

2011-07-12T17:49:21Z

Humilulo: /* Bitcoin.conf Configuration File */

There are two variations of the official bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called [[bitcoind]]). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

__TOC__
==Command-line arguments==

Give Bitcoin (or bitcoind) the -? or –help argument and it will print out a list of the most commonly used command-line arguments and then exit:

Usage:
bitcoin [options]
bitcoin [options] <command> [params] Send command to -server or bitcoind
bitcoin [options] help List commands
bitcoin [options] help <command> Get help for a command
Options:
-conf=<file> Specify configuration file (default: bitcoin.conf)
-gen Generate coins
-gen=0 Don't generate coins
-min Start minimized
-datadir=<dir> Specify data directory
-proxy=<ip:port> Connect through socks4 proxy
-addnode=<ip> Add a node to connect to
-connect=<ip> Connect only to the specified node
-nolisten Don't accept connections from outside
-noupnp Don't attempt to use UPnP to map the listening port
-upnp Attempt to use UPnP to map the listening port
-paytxfee=<amt> Fee per KB added to transactions you send
-server Accept command line and JSON-RPC commands
-daemon Run in the background as a daemon and accept commands
-testnet Use the test network
-port=<port> Connect to the Network from <port> (default: 8333; 18333 for testnet)
-rpcuser=<user> Username for JSON-RPC connections
-rpcpassword=<pw> Password for JSON-RPC connections
-rpcport=<port> Listen for JSON-RPC connections on <port> (default: 8332)
-rpcallowip=<ip> Allow JSON-RPC connections from specified IP address
-rpcconnect=<ip> Send commands to node running on <ip> (default: 127.0.0.1)
-keypool=<n> Set key pool size to <n> (default: 100)
-rescan Rescan the block chain for missing wallet transactions
-rpcssl Use OpenSSL (https) for JSON-RPC connections
-? This help message

==Bitcoin.conf Configuration File==
All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin [[data directory]], but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.
{|
! Operating System
! Default bitcoin datadir
! Typical path to configuration file
|-
| Windows
| %APPDATA%\Bitcoin\
| (XP) C:\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf
(Vista, 7) C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf
|-
| Linux
| $HOME/.bitcoin/
| /home/username/.bitcoin/bitcoin.conf
|-
| Mac OSX
| $HOME/Library/Application Support/Bitcoin/
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf
|}

==Sample Bitcoin.conf==
Here is a sample bitcoin.conf file, containing every option set to its default value.

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=1

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
# find other peers.
#noirc=1

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin to accept JSON-RPC commands.
#server=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
#rpcuser=Ulysseys
#rpcpassword=YourSuperGreatPasswordNumber_385593

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*

# Listen for RPC connections on this TCP port:
rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate bitcoins
gen=0

# Use SSE instructions to try to generate bitcoins faster.
#4way=1

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=100

# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
paytxfee=0.00

# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

==Platforms==
===Windows===

====Start automatically====
To configure the Bitcoin client to start automatically:

Settings -> Options

then mark the checkbox titled:
[X] Start Bitcoin on window system startup
[[{{ns:file}}:Client_Settings_Options.png]]

====Generate on startup====
To configure the Bitcoin client so that mining on startup is automatic:
Configure bitcoin.conf as follows:
gen=1

===Mac===

===Linux===
[[Category:Technical]][[Category:Developer]]

Running Bitcoin

2011-07-12T17:48:49Z

Humilulo: /* Bitcoin.conf Configuration File */

There are two variations of the official bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called [[bitcoind]]). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

__TOC__
==Command-line arguments==

Give Bitcoin (or bitcoind) the -? or –help argument and it will print out a list of the most commonly used command-line arguments and then exit:

Usage:
bitcoin [options]
bitcoin [options] <command> [params] Send command to -server or bitcoind
bitcoin [options] help List commands
bitcoin [options] help <command> Get help for a command
Options:
-conf=<file> Specify configuration file (default: bitcoin.conf)
-gen Generate coins
-gen=0 Don't generate coins
-min Start minimized
-datadir=<dir> Specify data directory
-proxy=<ip:port> Connect through socks4 proxy
-addnode=<ip> Add a node to connect to
-connect=<ip> Connect only to the specified node
-nolisten Don't accept connections from outside
-noupnp Don't attempt to use UPnP to map the listening port
-upnp Attempt to use UPnP to map the listening port
-paytxfee=<amt> Fee per KB added to transactions you send
-server Accept command line and JSON-RPC commands
-daemon Run in the background as a daemon and accept commands
-testnet Use the test network
-port=<port> Connect to the Network from <port> (default: 8333; 18333 for testnet)
-rpcuser=<user> Username for JSON-RPC connections
-rpcpassword=<pw> Password for JSON-RPC connections
-rpcport=<port> Listen for JSON-RPC connections on <port> (default: 8332)
-rpcallowip=<ip> Allow JSON-RPC connections from specified IP address
-rpcconnect=<ip> Send commands to node running on <ip> (default: 127.0.0.1)
-keypool=<n> Set key pool size to <n> (default: 100)
-rescan Rescan the block chain for missing wallet transactions
-rpcssl Use OpenSSL (https) for JSON-RPC connections
-? This help message

==Bitcoin.conf Configuration File==
All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin [[data directory]], but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.
{|
! Operating System
! Default bitcoin datadir
! Typical path to configuration file
|-
| Windows
| %APPDATA%\Bitcoin\
| (XP) C:\Documents and Settings\username\Application Data\Bitcoin
(Vista, 7) C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf
|-
| Linux
| $HOME/.bitcoin/
| /home/username/.bitcoin/bitcoin.conf
|-
| Mac OSX
| $HOME/Library/Application Support/Bitcoin/
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf
|}

==Sample Bitcoin.conf==
Here is a sample bitcoin.conf file, containing every option set to its default value.

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=1

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
# find other peers.
#noirc=1

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin to accept JSON-RPC commands.
#server=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
#rpcuser=Ulysseys
#rpcpassword=YourSuperGreatPasswordNumber_385593

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*

# Listen for RPC connections on this TCP port:
rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate bitcoins
gen=0

# Use SSE instructions to try to generate bitcoins faster.
#4way=1

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=100

# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
paytxfee=0.00

# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

==Platforms==
===Windows===

====Start automatically====
To configure the Bitcoin client to start automatically:

Settings -> Options

then mark the checkbox titled:
[X] Start Bitcoin on window system startup
[[{{ns:file}}:Client_Settings_Options.png]]

====Generate on startup====
To configure the Bitcoin client so that mining on startup is automatic:
Configure bitcoin.conf as follows:
gen=1

===Mac===

===Linux===
[[Category:Technical]][[Category:Developer]]