https://tests.bitcoin.it/w/api.php?action=feedcontributions&user=Kiba&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-29T10:25:26ZUser contributionsMediaWiki 1.30.0https://tests.bitcoin.it/w/index.php?title=Securing_your_wallet&diff=2977Securing your wallet2011-01-30T16:28:47Z<p>Kiba: /* Linux solution */</p>
<hr />
<div>==Introduction==<br />
<br />
Wallet security can be broken down into two independent goals:<br />
# Protecting your wallet against loss.<br />
# Protecting your wallet against theft.<br />
<br />
In the case that your current wallet hasn't been protected adequately (e.g. put online with a weaker password):<br />
# Making a new secure wallet, using appropriate long-term protection.<br />
<br />
==Technical Background==<br />
<br />
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.<br />
<br />
The wallet contains a pool of queued keys. By default there are 100 keys in the keypool. The size of the pool is configurable using the undocumented "--keypool" command line argument. 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.<br />
<br />
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 more than 100 new addresses, the keypair associated with the newest addresses will not be in the old wallet because the new keypairs are only known after creating them. Any coins received at these addresses will be lost if you restore from the backup.<br />
<br />
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 some 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.<br />
<br />
So if you create a backup, do more than 100 things that cause a new key to be used, 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.<br />
<br />
== Making a new wallet ==<br />
<br />
In the case that a wallet has been distributed, or stored, in a (real or potential) compromised state, it is wise to create a new wallet and transfer the full balance of Bitcoins to an address contained only in the newly created wallet.<br />
<br />
For example, this will be necessary if one created a wallet with a password of 12 characters, as suggested. However a few years have passed and the wallet is now more easily compromised. Just re-encrypting isn't secure. One needs to make a new wallet and make the old wallet worthless (spending the funds to the new wallet).<br />
<br />
==Making a secure workspace==<br />
<br />
===Linux===<br />
<br />
The first step is to make a [http://www.howtogeek.com/howto/ubuntu/add-a-user-on-ubuntu-server/ new user,] so type:<br />
<br />
sudo adduser new_user_name<br />
<br />
when you get to the prompt 'Enter the new value, or press ENTER for the default', just keep hitting ENTER.<br />
<br />
Then switch user to the new user. To get to the new user you can use the switch user icon for your system, which on Ubuntu is in the 'System/Quit' screen, or if there is no switch icon on your system you can log out and log back in as the new user. Then click on a folder in the new user to display the file browser, then keep going up folders until you see the new user home directory, then right click to bring up the Properties dialog, then click on the Permissions tab, then in the Others section, set the folder access to None.<br />
<br />
For secure browsing, open Firefox, and then go into the Edit menu and click Preferences. Starting from the left, click on the General tab, and in the 'Startup/When Firefox starts' pop up menu, choose 'Show a Blank Page'. Then click on the Content tab, and deselect 'Load images automatically' and deselect 'Enable Javascript'. Then click on the Privacy tab, and in the 'History/Firefox will' pop up menu, choose 'Never remember history'. Then click on the Security tab, and in the Passwords section, deselect 'Remember passwords for sites' and deselect 'Use a master password'. Then click on the Advanced tab, then click on the Update tab, and then in the 'Automatically check for updates to' section, deselect 'Add-ons' and 'Search Engines'.<br />
<br />
When javascript is disabled, the [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.19/bitcoin-0.3.19-linux.tar.gz/download linux download page] will not download automatically, so you'll have to click on the 'direct link' part of the "Problems with the download? Please use this 'direct link' or try another mirror." line.<br />
<br />
After you've made your secure new user, to maintain security you should use it only for bitcoin.<br />
<br />
== Locating BitCoin's data directory ==<br />
<br />
=== Windows ===<br />
<br />
Go to Start -> Run (or press WinKey+R) and run this:<br />
<br />
explorer %APPDATA%\BitCoin<br />
<br />
BitCoin's data folder will open. For most users, this is the following locations:<br />
<br />
C:\Documents and Settings\YourUserName\Application data\BitCoin (XP)<br />
<br />
C:\Users\YourUserName\Appdata\Roaming\BitCoin (Vista and 7)<br />
<br />
"AppData" and "Application data" are hidden by default.<br />
<br />
=== Linux ===<br />
<br />
By default BitCoin will put its data here:<br />
<br />
~/.bitcoin/<br />
<br />
You need to do a "ls -a" to see directories that start with a dot.<br />
<br />
If that's not it, you can do a search like this:<br />
<br />
find / -name wallet.dat -print 2>/dev/null<br />
<br />
=== Mac ===<br />
<br />
By default BitCoin will put its data here:<br />
<br />
~/Library/Application Support/Bitcoin/<br />
<br />
==Backup==<br />
<br />
The only file you need to back up is "wallet.dat". Ensure that BitCoin is closed, copy this file somewhere else, encrypt it, and put it somewhere safe. Ideally, you would put this file in two places: one nearby, and one 100+ miles away.<br />
<br />
You can use the [[api|backupwallet]] JSON-RPC command to back up without shutting down Bitcoin.<br />
<br />
=== General Solutions ===<br />
<br />
Your wallet.dat file is not encrypted by BitCoin. Anyone who can access it can easily steal all of your coins. Use one of these encryption programs if there is any chance someone might stumble upon your wallet.<br />
* [http://www.7-zip.org/ 7-zip] - Supports strongly-encrypted archives.<br />
* [http://www.axantum.com/axcrypt/ AxCrypt]<br />
* [http://www.truecrypt.org/ TrueCrypt] - Volume-based on-the-fly encryption (for advanced users)<br />
* [http://www.rarlab.com/ WinRar] - Commonly used archive software that supports verification records and encryption.<br />
<br />
There is also a list of [[OpenSourceEncryptionSoftware|open source encryption software.]]<br />
<br />
==== Password Strength ====<br />
Brute-force password cracking has come a long distance, a previously thought secure password of random [a-Z] [0-9] [!-~] of 8 characters long can be trivially solved now (using appropriate hardware)... The recommended length is '''at least''' 12 characters long.<br />
<br />
If you use keyfiles in addition to a password, it is unlikely that your encrypted file can ever be cracked using brute force methods, even 10 years from now when even a 12 character password might be too short.<br />
<br />
Assume that any encrypted files you store online (eg. gmail, Dropbox) will be stored somewhere forever and can never be erased.<br />
<br />
==== Storage of Archive ====<br />
One of the most simple places to store a appropriately encrypted archive of your wallet.dat file is to email yourself the archive. Services like gmail.com use very comprehensive distributed networks that make the loss of data very unlikely. One can even encrypt the name of the files withing the archive, and name the archive something less inviting, such as: 'personal notes' or 'car insurance'.<br />
<br />
Another solution is to use a file storage service like [http://www.dropbox.com Dropbox] and [http://en.wikipedia.org/wiki/Comparison_of_online_backup_services others], including the more secure [http://www.spideroak.com SpiderOak].<br />
<br />
=== Linux solution ===<br />
<br />
Linux users can setup cron by running 'crontab -e' and adding this line:<br />
<br />
01 */1 * * * /usr/local/bin/backupwallet.sh<br />
<br />
This cron line runs backupwallet.sh at the 01 minute of every hour. Remember to add a newline after the last line of the crontab file, or else the last line won't run.<br />
<br />
backupwallet.sh:<br />
<br />
#!/bin/bash<br />
<br />
TS=$(date "+%Y%m%d-%H-%M")<br />
WALLET=/tmp/wallet${TS}<br />
WALLET_E=/tmp/wallet${TS}.crypt<br />
<br />
if<br />
echo -n making backup...<br />
bitcoind backupwallet $WALLET <br />
[[ ! -s "$WALLET" ]]<br />
then echo failed<br />
elif<br />
echo done<br />
echo -n encrypting....<br />
! gpg -r myusername --output $WALLET_E --encrypt $WALLET<br />
then echo failed<br />
elif<br />
echo done<br />
echo -n copying to distant server...<br />
! scp $WALLET_E user@myserver.org:~/wallets/<br />
then echo failed<br />
else echo done<br />
fi<br />
<br />
rm -f $WALLET $WALLET_E<br />
<br />
The shell script:<br />
<br />
* Calls bitcoind backupwallet to create a time/date-stamped wallet.<br />
* GPG encrypts the wallet with your public key.<br />
* Copies the result to a backup location.<br />
<br />
[[Category:Technical]]<br />
<br />
==Restore==<br />
<br />
Assuming your backup is recent enough that you haven't used up all of your keypool... restoring a wallet no a new (or old) location and rescanning the block chain should leave you with all your coins. Just follow these steps:<br />
* Quit bitcoin(d).<br />
* Copy your backed up wallet.dat into your bitcoin profile directory.<br />
* If copying into existing profile, delete file ''blkindex.dat'', to make the client rescan the block chain.<br />
And you'll be good as new.<br />
<br />
==Erasing Plain Text Wallets==<br />
<br />
A good practice is to keep at least two wallets, one as a "current account" for everyday transactions and one as a "savings account" where you store the majority of your Bitcoins. <br />
<br />
The "savings account" wallet should be backed up in encrypted form only and all plaintext copies of this wallet should be erased. In case someone gains unauthorised access to your computer (either by physically stealing it or by exploiting a system vulnerability via the internet), they will only be able to spend the coins in your "current account" wallet.<br />
<br />
In most operating systems, including Windows, Linux, and Mac OS X, simply deleting a wallet.dat file will ''not'' generally destroy it. It is likely that advanced tools can still be used to recover the wallet.dat file, even after it has been deleted.<br />
<br />
The Linux '''shred''' command can be used to overwrite the wallet file with random data prior to deleting; this particular copy of the file will then be practically impossible to recover. Using shred (and similar tools on Windows) however does not guarantee that still other copies don't exist somewhere hidden on your HD. That will depend on your system configuration and what packages you have installed. Some system restore and backup tools, for instance, create periodic snapshots of your filesystem, duplicating your wallet.dat.<br />
<br />
For Windows, the built-in command ''cipher /w'' will shred all previously-deleted files. [http://www.cylog.org/utilities/cybershredder.jsp CyberShredder] can securely deleted individual files.<br />
<br />
==eWallet==<br />
<br />
Storing bitcoins with an [[eWallet]] provider incurs risks as well.<br />
<br />
==See Also==<br />
<br />
* [[Data directory]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Securing_your_wallet&diff=2976Securing your wallet2011-01-30T16:28:30Z<p>Kiba: /* Linux solution */</p>
<hr />
<div>==Introduction==<br />
<br />
Wallet security can be broken down into two independent goals:<br />
# Protecting your wallet against loss.<br />
# Protecting your wallet against theft.<br />
<br />
In the case that your current wallet hasn't been protected adequately (e.g. put online with a weaker password):<br />
# Making a new secure wallet, using appropriate long-term protection.<br />
<br />
==Technical Background==<br />
<br />
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.<br />
<br />
The wallet contains a pool of queued keys. By default there are 100 keys in the keypool. The size of the pool is configurable using the undocumented "--keypool" command line argument. 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.<br />
<br />
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 more than 100 new addresses, the keypair associated with the newest addresses will not be in the old wallet because the new keypairs are only known after creating them. Any coins received at these addresses will be lost if you restore from the backup.<br />
<br />
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 some 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.<br />
<br />
So if you create a backup, do more than 100 things that cause a new key to be used, 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.<br />
<br />
== Making a new wallet ==<br />
<br />
In the case that a wallet has been distributed, or stored, in a (real or potential) compromised state, it is wise to create a new wallet and transfer the full balance of Bitcoins to an address contained only in the newly created wallet.<br />
<br />
For example, this will be necessary if one created a wallet with a password of 12 characters, as suggested. However a few years have passed and the wallet is now more easily compromised. Just re-encrypting isn't secure. One needs to make a new wallet and make the old wallet worthless (spending the funds to the new wallet).<br />
<br />
==Making a secure workspace==<br />
<br />
===Linux===<br />
<br />
The first step is to make a [http://www.howtogeek.com/howto/ubuntu/add-a-user-on-ubuntu-server/ new user,] so type:<br />
<br />
sudo adduser new_user_name<br />
<br />
when you get to the prompt 'Enter the new value, or press ENTER for the default', just keep hitting ENTER.<br />
<br />
Then switch user to the new user. To get to the new user you can use the switch user icon for your system, which on Ubuntu is in the 'System/Quit' screen, or if there is no switch icon on your system you can log out and log back in as the new user. Then click on a folder in the new user to display the file browser, then keep going up folders until you see the new user home directory, then right click to bring up the Properties dialog, then click on the Permissions tab, then in the Others section, set the folder access to None.<br />
<br />
For secure browsing, open Firefox, and then go into the Edit menu and click Preferences. Starting from the left, click on the General tab, and in the 'Startup/When Firefox starts' pop up menu, choose 'Show a Blank Page'. Then click on the Content tab, and deselect 'Load images automatically' and deselect 'Enable Javascript'. Then click on the Privacy tab, and in the 'History/Firefox will' pop up menu, choose 'Never remember history'. Then click on the Security tab, and in the Passwords section, deselect 'Remember passwords for sites' and deselect 'Use a master password'. Then click on the Advanced tab, then click on the Update tab, and then in the 'Automatically check for updates to' section, deselect 'Add-ons' and 'Search Engines'.<br />
<br />
When javascript is disabled, the [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.19/bitcoin-0.3.19-linux.tar.gz/download linux download page] will not download automatically, so you'll have to click on the 'direct link' part of the "Problems with the download? Please use this 'direct link' or try another mirror." line.<br />
<br />
After you've made your secure new user, to maintain security you should use it only for bitcoin.<br />
<br />
== Locating BitCoin's data directory ==<br />
<br />
=== Windows ===<br />
<br />
Go to Start -> Run (or press WinKey+R) and run this:<br />
<br />
explorer %APPDATA%\BitCoin<br />
<br />
BitCoin's data folder will open. For most users, this is the following locations:<br />
<br />
C:\Documents and Settings\YourUserName\Application data\BitCoin (XP)<br />
<br />
C:\Users\YourUserName\Appdata\Roaming\BitCoin (Vista and 7)<br />
<br />
"AppData" and "Application data" are hidden by default.<br />
<br />
=== Linux ===<br />
<br />
By default BitCoin will put its data here:<br />
<br />
~/.bitcoin/<br />
<br />
You need to do a "ls -a" to see directories that start with a dot.<br />
<br />
If that's not it, you can do a search like this:<br />
<br />
find / -name wallet.dat -print 2>/dev/null<br />
<br />
=== Mac ===<br />
<br />
By default BitCoin will put its data here:<br />
<br />
~/Library/Application Support/Bitcoin/<br />
<br />
==Backup==<br />
<br />
The only file you need to back up is "wallet.dat". Ensure that BitCoin is closed, copy this file somewhere else, encrypt it, and put it somewhere safe. Ideally, you would put this file in two places: one nearby, and one 100+ miles away.<br />
<br />
You can use the [[api|backupwallet]] JSON-RPC command to back up without shutting down Bitcoin.<br />
<br />
=== General Solutions ===<br />
<br />
Your wallet.dat file is not encrypted by BitCoin. Anyone who can access it can easily steal all of your coins. Use one of these encryption programs if there is any chance someone might stumble upon your wallet.<br />
* [http://www.7-zip.org/ 7-zip] - Supports strongly-encrypted archives.<br />
* [http://www.axantum.com/axcrypt/ AxCrypt]<br />
* [http://www.truecrypt.org/ TrueCrypt] - Volume-based on-the-fly encryption (for advanced users)<br />
* [http://www.rarlab.com/ WinRar] - Commonly used archive software that supports verification records and encryption.<br />
<br />
There is also a list of [[OpenSourceEncryptionSoftware|open source encryption software.]]<br />
<br />
==== Password Strength ====<br />
Brute-force password cracking has come a long distance, a previously thought secure password of random [a-Z] [0-9] [!-~] of 8 characters long can be trivially solved now (using appropriate hardware)... The recommended length is '''at least''' 12 characters long.<br />
<br />
If you use keyfiles in addition to a password, it is unlikely that your encrypted file can ever be cracked using brute force methods, even 10 years from now when even a 12 character password might be too short.<br />
<br />
Assume that any encrypted files you store online (eg. gmail, Dropbox) will be stored somewhere forever and can never be erased.<br />
<br />
==== Storage of Archive ====<br />
One of the most simple places to store a appropriately encrypted archive of your wallet.dat file is to email yourself the archive. Services like gmail.com use very comprehensive distributed networks that make the loss of data very unlikely. One can even encrypt the name of the files withing the archive, and name the archive something less inviting, such as: 'personal notes' or 'car insurance'.<br />
<br />
Another solution is to use a file storage service like [http://www.dropbox.com Dropbox] and [http://en.wikipedia.org/wiki/Comparison_of_online_backup_services others], including the more secure [http://www.spideroak.com SpiderOak].<br />
<br />
=== Linux solution ===<br />
<br />
Linux users can setup cron by running 'crontab -e' and adding this line:<br />
<br />
01 */1 * * * /usr/local/bin/backupwallet.sh<br />
<br />
This cron line runs backupwallet.sh at the 01 minute of every hour. Remember to add a newline after the last line of the crontab file, or else the last line won't run.<br />
<br />
backupwallet.sh:<br />
<br />
#!/bin/bash<br />
<br />
TS=$(date "+%Y%m%d-%H-%M")<br />
WALLET=/tmp/wallet${TS}<br />
WALLET_E=/tmp/wallet${TS}.crypt<br />
<br />
if<br />
echo -n making backup...<br />
bitcoind backupwallet $WALLET <br />
[[ ! -s "$WALLET" ]]<br />
then echo failed<br />
elif<br />
echo done<br />
echo -n encrypting....<br />
! gpg -r myusername --output $WALLET_E --encrypt $WALLET<br />
then echo failed<br />
elif<br />
echo done<br />
echo -n copying to distant server...<br />
! scp $WALLET_E user@myserver.org:~/wallets/<br />
then echo failed<br />
else echo done<br />
fi<br />
<br />
rm -f $WALLET $WALLET_E<br />
<br />
The shell script:<br />
<br />
* Calls bitcoind backupwallet to create a time/date-stamped wallet.<br />
* GPG encrypts the wallet with your public key.<br />
* Copies the result to a backup location.<br />
<br />
[[Category:Technical]]<br />
<br />
==Restore==<br />
<br />
Assuming your backup is recent enough that you haven't used up all of your keypool... restoring a wallet no a new (or old) location and rescanning the block chain should leave you with all your coins. Just follow these steps:<br />
* Quit bitcoin(d).<br />
* Copy your backed up wallet.dat into your bitcoin profile directory.<br />
* If copying into existing profile, delete file ''blkindex.dat'', to make the client rescan the block chain.<br />
And you'll be good as new.<br />
<br />
==Erasing Plain Text Wallets==<br />
<br />
A good practice is to keep at least two wallets, one as a "current account" for everyday transactions and one as a "savings account" where you store the majority of your Bitcoins. <br />
<br />
The "savings account" wallet should be backed up in encrypted form only and all plaintext copies of this wallet should be erased. In case someone gains unauthorised access to your computer (either by physically stealing it or by exploiting a system vulnerability via the internet), they will only be able to spend the coins in your "current account" wallet.<br />
<br />
In most operating systems, including Windows, Linux, and Mac OS X, simply deleting a wallet.dat file will ''not'' generally destroy it. It is likely that advanced tools can still be used to recover the wallet.dat file, even after it has been deleted.<br />
<br />
The Linux '''shred''' command can be used to overwrite the wallet file with random data prior to deleting; this particular copy of the file will then be practically impossible to recover. Using shred (and similar tools on Windows) however does not guarantee that still other copies don't exist somewhere hidden on your HD. That will depend on your system configuration and what packages you have installed. Some system restore and backup tools, for instance, create periodic snapshots of your filesystem, duplicating your wallet.dat.<br />
<br />
For Windows, the built-in command ''cipher /w'' will shred all previously-deleted files. [http://www.cylog.org/utilities/cybershredder.jsp CyberShredder] can securely deleted individual files.<br />
<br />
==eWallet==<br />
<br />
Storing bitcoins with an [[eWallet]] provider incurs risks as well.<br />
<br />
==See Also==<br />
<br />
* [[Data directory]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=User:Kiba&diff=2916User:Kiba2011-01-29T00:41:20Z<p>Kiba: </p>
<hr />
<div>Contributors Award participant: 14ySrd81yHFEXCT4xsgdEuE5xgLxHik5HN<br />
<br />
'''Kiba''':<br />
<br />
<tt><br />
Here is what I can do:<br />
1. Programming in Ruby, and Javascript. I spent much of my time in those two languages. Other languages I could handle: Python, java. Other language, I barely touch: C. I am perfectly suitable for creating small scripts, little web projects, and anything that's not too aglorithmtic or required advanced mathematics.<br />
2. Writing. I recently got paid for an article. Might be worth hiring.<br />
3. Art. So-so.<br />
</tt><br />
<br />
==External Links==<br />
<br />
* [http://www.bitcoin.org/smf/index.php?topic=2815.0 Looking for Jobs]<br />
<br />
[[Category:Freelancers]]<br />
[[Category:Freelancers-Fine Art]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=User:Kiba&diff=2915User:Kiba2011-01-29T00:28:51Z<p>Kiba: I actually don't do graphic design</p>
<hr />
<div>Contributors Award participant: <a href='bitcoin:?addr=14ySrd81yHFEXCT4xsgdEuE5xgLxHik5HN' id='lnk014ySrd81yHFEXCT4xsgdEuE5xgLxHik5HN'>14ySrd81yHFEXCT4xsgdEuE5xgLxHik5HN</a><br />
<br />
'''Kiba''':<br />
<br />
<tt><br />
Here is what I can do:<br />
1. Programming in Ruby, and Javascript. I spent much of my time in those two languages. Other languages I could handle: Python, java. Other language, I barely touch: C. I am perfectly suitable for creating small scripts, little web projects, and anything that's not too aglorithmtic or required advanced mathematics.<br />
2. Writing. I recently got paid for an article. Might be worth hiring.<br />
3. Art. So-so.<br />
</tt><br />
<br />
==External Links==<br />
<br />
* [http://www.bitcoin.org/smf/index.php?topic=2815.0 Looking for Jobs]<br />
<br />
[[Category:Freelancers]]<br />
[[Category:Freelancers-Fine Art]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=User:Kiba&diff=2914User:Kiba2011-01-29T00:28:22Z<p>Kiba: </p>
<hr />
<div>Contributors Award participant: 14ySrd81yHFEXCT4xsgdEuE5xgLxHik5HN<br />
<br />
'''Kiba''':<br />
<br />
<tt><br />
Here is what I can do:<br />
1. Programming in Ruby, and Javascript. I spent much of my time in those two languages. Other languages I could handle: Python, java. Other language, I barely touch: C. I am perfectly suitable for creating small scripts, little web projects, and anything that's not too aglorithmtic or required advanced mathematics.<br />
2. Writing. I recently got paid for an article. Might be worth hiring.<br />
3. Art. So-so.<br />
</tt><br />
<br />
==External Links==<br />
<br />
* [http://www.bitcoin.org/smf/index.php?topic=2815.0 Looking for Jobs]<br />
<br />
[[Category:Freelancers]]<br />
[[Category:Freelancers-Graphic Design]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2885Running Bitcoin2011-01-28T20:17:29Z<p>Kiba: /* Sample Bitcoin.conf */</p>
<hr />
<div>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).<br />
==Command-line arguments==<br />
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:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-? This help message<br />
==Bitcoin.conf Configuration File==<br />
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.<br />
<br />
The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.<br />
<br />
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.<br />
{|<br />
! Operating System<br />
! Default bitcoin datadir<br />
! Typical path to configuration file<br />
|-<br />
| Windows<br />
| %APPDATA%\Bitcoin\<br />
| :\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf<br />
|-<br />
| Linux<br />
| $HOME/.bitcoin/<br />
| /Users/username/.bitcoin/bitcoin.conf<br />
|-<br />
| Mac OSX<br />
| $HOME/Library/Application Support/Bitcoin/<br />
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf<br />
|}<br />
==Sample Bitcoin.conf==<br />
Here is a sample bitcoin.conf file, containing every option set to its default value.<br />
<br />
# bitcoin.conf configuration file. Lines beginning with # are comments.<br />
<br />
<br />
# Network-related settings:<br />
<br />
# Run on the test network instead of the real bitcoin network.<br />
#testnet=1<br />
<br />
# Connect via a socks4 proxy<br />
#proxy=127.0.0.1:9050<br />
<br />
# Use as many addnode= settings as you like to connect to specific peers<br />
#addnode=69.164.218.197<br />
#addnode=10.0.0.2:8333<br />
<br />
# ... or use as many connect= settings as you like to connect ONLY<br />
# to specific peers:<br />
#connect=69.164.218.197<br />
#connect=10.0.0.1:8333<br />
<br />
# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to<br />
# find other peers.<br />
#noirc=1<br />
<br />
# Maximum number of inbound+outbound connections.<br />
#maxconnections=<br />
<br />
<br />
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)<br />
<br />
# server=1 tells Bitcoin to accept JSON-RPC commands.<br />
#server=1<br />
<br />
# You must set rpcuser and rpcpassword to secure the JSON-RPC api<br />
#rpcuser=Ulysseys<br />
#rpcpassword=YourSuperGreatPasswordNumber_385593<br />
<br />
# How many seconds bitcoin will wait for a complete RPC HTTP request.<br />
# after the HTTP connection is established. <br />
rpctimeout=30<br />
<br />
# By default, only RPC connections from localhost are allowed. Specify<br />
# as many rpcallowip= settings as you like to allow connections from<br />
# other hosts (and you may use * as a wildcard character):<br />
#rpcallowip=10.1.1.34<br />
#rpcallowip=192.168.1.*<br />
<br />
# Listen for RPC connections on this TCP port:<br />
rpcport=8332<br />
<br />
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind<br />
# running on another host using this option:<br />
rpcconnect=127.0.0.1<br />
<br />
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate<br />
# with Bitcoin -server or bitcoind<br />
#rpcssl=1<br />
<br />
# OpenSSL settings used when rpcssl=1<br />
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH<br />
rpcsslcertificatechainfile=server.cert<br />
rpcsslprivatekeyfile=server.pem<br />
<br />
<br />
# Miscellaneous options<br />
<br />
# Set gen=1 to attempt to generate bitcoins<br />
gen=0<br />
<br />
# Use SSE instructions to try to generate bitcoins faster.<br />
#4way=1<br />
<br />
# Pre-generate this many public/private key pairs, so wallet backups will be valid for<br />
# both prior transactions and several dozen future transactions.<br />
keypool=100<br />
<br />
# Pay an optional transaction fee every time you send bitcoins. Transactions with fees<br />
# are more likely than free transactions to be included in generated blocks, so may<br />
# be validated sooner.<br />
paytxfee=0.00<br />
<br />
# Allow direct connections for the 'pay via IP address' feature.<br />
#allowreceivebyip=1<br />
<br />
<br />
# User interface options<br />
<br />
# Start Bitcoin minimized<br />
#min=1<br />
<br />
# Minimize to the system tray<br />
#minimizetotray=1<br />
{{fromold|running_bitcoin}}<br />
[[Category:Technical]][[Category:Developer]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2884Running Bitcoin2011-01-28T20:14:21Z<p>Kiba: /* Sample Bitcoin.conf */</p>
<hr />
<div>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).<br />
==Command-line arguments==<br />
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:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-? This help message<br />
==Bitcoin.conf Configuration File==<br />
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.<br />
<br />
The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.<br />
<br />
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.<br />
{|<br />
! Operating System<br />
! Default bitcoin datadir<br />
! Typical path to configuration file<br />
|-<br />
| Windows<br />
| %APPDATA%\Bitcoin\<br />
| :\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf<br />
|-<br />
| Linux<br />
| $HOME/.bitcoin/<br />
| /Users/username/.bitcoin/bitcoin.conf<br />
|-<br />
| Mac OSX<br />
| $HOME/Library/Application Support/Bitcoin/<br />
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf<br />
|}<br />
==Sample Bitcoin.conf==<br />
Here is a sample bitcoin.conf file, containing every option set to its default value.<br />
<br />
# bitcoin.conf configuration file. Lines beginning with # are comments.<br />
<br />
<br />
# Network-related settings:<br />
<br />
# Run on the test network instead of the real bitcoin network.<br />
#testnet=1<br />
<br />
# Connect via a socks4 proxy<br />
#proxy=127.0.0.1:9050<br />
<br />
# Use as many addnode= settings as you like to connect to specific peers<br />
#addnode=69.164.218.197<br />
#addnode=10.0.0.2:8333<br />
<br />
# ... or use as many connect= settings as you like to connect ONLY<br />
# to specific peers:<br />
#connect=69.164.218.197<br />
#connect=10.0.0.1:8333<br />
<br />
# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to<br />
# find other peers.<br />
#noirc=1<br />
<br />
# Maximum number of inbound+outbound connections.<br />
#maxconnections=<br />
<br />
<br />
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)<br />
<br />
# server=1 tells Bitcoin to accept JSON-RPC commands.<br />
#server=1<br />
<br />
# You must set rpcuser and rpcpassword to secure the JSON-RPC api<br />
#rpcuser=Ulysseys<br />
#rpcpassword=YourSuperGreatPasswordNumber_385593<br />
<br />
# How many seconds bitcoin will wait for a complete RPC HTTP request.<br />
# after the HTTP connection is established. <br />
rpctimeout=30<br />
<br />
# By default, only RPC connections from localhost are allowed. Specify<br />
# as many rpcallowip= settings as you like to allow connections from<br />
# other hosts (and you may use * as a wildcard character):<br />
#rpcallowip=10.1.1.34<br />
#rpcallowip=192.168.1.*<br />
<br />
# Listen for RPC connections on this TCP port:<br />
rpcport=8332<br />
<br />
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind<br />
# running on another host using this option:<br />
rpcconnect=127.0.0.1<br />
<br />
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate<br />
# with Bitcoin -server or bitcoind<br />
#rpcssl=1<br />
<br />
# OpenSSL settings used when rpcssl=1<br />
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH<br />
rpcsslcertificatechainfile=server.cert<br />
rpcsslprivatekeyfile=server.pem<br />
<br />
<br />
# Miscellaneous options<br />
<br />
# Set gen=1 to attempt to generate bitcoins<br />
gen=0<br />
<br />
# Use SSE instructions to try to generate bitcoins faster.<br />
#4way=1<br />
<br />
# Pre-generate this many public/private key pairs, so wallet backups will be valid for<br />
# both prior transactions and several dozen future transactions.<br />
keypool=100<br />
<br />
# Pay an optional transaction fee every time you send bitcoins. Transactions with fees<br />
# are more likely than free transactions to be included in generated blocks, so may<br />
# be validated sooner.<br />
paytxfee=0.00<br />
<br />
# Allow direct connections for the 'pay via IP address' feature.<br />
#allowreceivebyip=1<br />
<br />
<br />
# User interface options<br />
<br />
# Start Bitcoin minimized<br />
#min=1<br />
<br />
# Minimize to the system tray<br />
#minimizetotray=1<br />
[[Category:Technical]][[Category:Developer]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2883Running Bitcoin2011-01-28T20:13:17Z<p>Kiba: /* Sample Bitcoin.conf */</p>
<hr />
<div>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).<br />
==Command-line arguments==<br />
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:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-? This help message<br />
==Bitcoin.conf Configuration File==<br />
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.<br />
<br />
The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.<br />
<br />
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.<br />
{|<br />
! Operating System<br />
! Default bitcoin datadir<br />
! Typical path to configuration file<br />
|-<br />
| Windows<br />
| %APPDATA%\Bitcoin\<br />
| :\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf<br />
|-<br />
| Linux<br />
| $HOME/.bitcoin/<br />
| /Users/username/.bitcoin/bitcoin.conf<br />
|-<br />
| Mac OSX<br />
| $HOME/Library/Application Support/Bitcoin/<br />
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf<br />
|}<br />
==Sample Bitcoin.conf==<br />
Here is a sample bitcoin.conf file, containing every option set to its default value.<br />
<br />
# bitcoin.conf configuration file. Lines beginning with # are comments.<br />
<br />
<br />
# Network-related settings:<br />
<br />
# Run on the test network instead of the real bitcoin network.<br />
#testnet=1<br />
<br />
# Connect via a socks4 proxy<br />
#proxy=127.0.0.1:9050<br />
<br />
# Use as many addnode= settings as you like to connect to specific peers<br />
#addnode=69.164.218.197<br />
#addnode=10.0.0.2:8333<br />
<br />
# ... or use as many connect= settings as you like to connect ONLY<br />
# to specific peers:<br />
#connect=69.164.218.197<br />
#connect=10.0.0.1:8333<br />
<br />
# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to<br />
# find other peers.<br />
#noirc=1<br />
<br />
# Maximum number of inbound+outbound connections.<br />
#maxconnections=<br />
<br />
<br />
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)<br />
<br />
# server=1 tells Bitcoin to accept JSON-RPC commands.<br />
#server=1<br />
<br />
# You must set rpcuser and rpcpassword to secure the JSON-RPC api<br />
#rpcuser=Ulysseys<br />
#rpcpassword=YourSuperGreatPasswordNumber_385593<br />
<br />
# How many seconds bitcoin will wait for a complete RPC HTTP request.<br />
# after the HTTP connection is established. <br />
rpctimeout=30<br />
<br />
# By default, only RPC connections from localhost are allowed. Specify<br />
# as many rpcallowip= settings as you like to allow connections from<br />
# other hosts (and you may use * as a wildcard character):<br />
#rpcallowip=10.1.1.34<br />
#rpcallowip=192.168.1.*<br />
<br />
# Listen for RPC connections on this TCP port:<br />
rpcport=8332<br />
<br />
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind<br />
# running on another host using this option:<br />
rpcconnect=127.0.0.1<br />
<br />
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate<br />
# with Bitcoin -server or bitcoind<br />
#rpcssl=1<br />
<br />
# OpenSSL settings used when rpcssl=1<br />
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH<br />
rpcsslcertificatechainfile=server.cert<br />
rpcsslprivatekeyfile=server.pem<br />
<br />
<br />
# Miscellaneous options<br />
<br />
# Set gen=1 to attempt to generate bitcoins<br />
gen=0<br />
<br />
# Use SSE instructions to try to generate bitcoins faster.<br />
#4way=1<br />
<br />
# Pre-generate this many public/private key pairs, so wallet backups will be valid for<br />
# both prior transactions and several dozen future transactions.<br />
keypool=100<br />
<br />
# Pay an optional transaction fee every time you send bitcoins. Transactions with fees<br />
# are more likely than free transactions to be included in generated blocks, so may<br />
# be validated sooner.<br />
paytxfee=0.00<br />
<br />
# Allow direct connections for the 'pay via IP address' feature.<br />
#allowreceivebyip=1<br />
<br />
<br />
# User interface options<br />
<br />
# Start Bitcoin minimized<br />
#min=1<br />
<br />
# Minimize to the system tray<br />
#minimizetotray=1<br />
[[Category:Technicals]][[Category:Developers]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2882Running Bitcoin2011-01-28T20:12:41Z<p>Kiba: /* Sample Bitcoin.conf */</p>
<hr />
<div>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).<br />
==Command-line arguments==<br />
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:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-? This help message<br />
==Bitcoin.conf Configuration File==<br />
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.<br />
<br />
The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.<br />
<br />
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.<br />
{|<br />
! Operating System<br />
! Default bitcoin datadir<br />
! Typical path to configuration file<br />
|-<br />
| Windows<br />
| %APPDATA%\Bitcoin\<br />
| :\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf<br />
|-<br />
| Linux<br />
| $HOME/.bitcoin/<br />
| /Users/username/.bitcoin/bitcoin.conf<br />
|-<br />
| Mac OSX<br />
| $HOME/Library/Application Support/Bitcoin/<br />
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf<br />
|}<br />
==Sample Bitcoin.conf==<br />
Here is a sample bitcoin.conf file, containing every option set to its default value.<br />
<br />
# bitcoin.conf configuration file. Lines beginning with # are comments.<br />
<br />
<br />
# Network-related settings:<br />
<br />
# Run on the test network instead of the real bitcoin network.<br />
#testnet=1<br />
<br />
# Connect via a socks4 proxy<br />
#proxy=127.0.0.1:9050<br />
<br />
# Use as many addnode= settings as you like to connect to specific peers<br />
#addnode=69.164.218.197<br />
#addnode=10.0.0.2:8333<br />
<br />
# ... or use as many connect= settings as you like to connect ONLY<br />
# to specific peers:<br />
#connect=69.164.218.197<br />
#connect=10.0.0.1:8333<br />
<br />
# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to<br />
# find other peers.<br />
#noirc=1<br />
<br />
# Maximum number of inbound+outbound connections.<br />
#maxconnections=<br />
<br />
<br />
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)<br />
<br />
# server=1 tells Bitcoin to accept JSON-RPC commands.<br />
#server=1<br />
<br />
# You must set rpcuser and rpcpassword to secure the JSON-RPC api<br />
#rpcuser=Ulysseys<br />
#rpcpassword=YourSuperGreatPasswordNumber_385593<br />
<br />
# How many seconds bitcoin will wait for a complete RPC HTTP request.<br />
# after the HTTP connection is established. <br />
rpctimeout=30<br />
<br />
# By default, only RPC connections from localhost are allowed. Specify<br />
# as many rpcallowip= settings as you like to allow connections from<br />
# other hosts (and you may use * as a wildcard character):<br />
#rpcallowip=10.1.1.34<br />
#rpcallowip=192.168.1.*<br />
<br />
# Listen for RPC connections on this TCP port:<br />
rpcport=8332<br />
<br />
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind<br />
# running on another host using this option:<br />
rpcconnect=127.0.0.1<br />
<br />
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate<br />
# with Bitcoin -server or bitcoind<br />
#rpcssl=1<br />
<br />
# OpenSSL settings used when rpcssl=1<br />
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH<br />
rpcsslcertificatechainfile=server.cert<br />
rpcsslprivatekeyfile=server.pem<br />
<br />
<br />
# Miscellaneous options<br />
<br />
# Set gen=1 to attempt to generate bitcoins<br />
gen=0<br />
<br />
# Use SSE instructions to try to generate bitcoins faster.<br />
#4way=1<br />
<br />
# Pre-generate this many public/private key pairs, so wallet backups will be valid for<br />
# both prior transactions and several dozen future transactions.<br />
keypool=100<br />
<br />
# Pay an optional transaction fee every time you send bitcoins. Transactions with fees<br />
# are more likely than free transactions to be included in generated blocks, so may<br />
# be validated sooner.<br />
paytxfee=0.00<br />
<br />
# Allow direct connections for the 'pay via IP address' feature.<br />
#allowreceivebyip=1<br />
<br />
<br />
# User interface options<br />
<br />
# Start Bitcoin minimized<br />
#min=1<br />
<br />
# Minimize to the system tray<br />
#minimizetotray=1</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2881Running Bitcoin2011-01-28T20:09:31Z<p>Kiba: /* Bitcoin.conf Configuration File */</p>
<hr />
<div>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).<br />
==Command-line arguments==<br />
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:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-? This help message<br />
==Bitcoin.conf Configuration File==<br />
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.<br />
<br />
The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.<br />
<br />
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.<br />
{|<br />
! Operating System<br />
! Default bitcoin datadir<br />
! Typical path to configuration file<br />
|-<br />
| Windows<br />
| %APPDATA%\Bitcoin\<br />
| :\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf<br />
|-<br />
| Linux<br />
| $HOME/.bitcoin/<br />
| /Users/username/.bitcoin/bitcoin.conf<br />
|-<br />
| Mac OSX<br />
| $HOME/Library/Application Support/Bitcoin/<br />
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf<br />
|}<br />
==Sample Bitcoin.conf==<br />
Here is a sample bitcoin.conf file, containing every option set to its default value.<br />
<br />
# bitcoin.conf configuration file. Lines beginning with # are comments.<br />
<br />
<br />
# Network-related settings:<br />
<br />
# Run on the test network instead of the real bitcoin network.<br />
#testnet=1<br />
<br />
# Connect via a socks4 proxy<br />
#proxy=127.0.0.1:9050<br />
<br />
# Use as many addnode= settings as you like to connect to specific peers<br />
#addnode=69.164.218.197<br />
#addnode=10.0.0.2:8333<br />
<br />
# ... or use as many connect= settings as you like to connect ONLY<br />
# to specific peers:<br />
#connect=69.164.218.197<br />
#connect=10.0.0.1:8333<br />
<br />
# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to<br />
# find other peers.<br />
#noirc=1<br />
<br />
# Maximum number of inbound+outbound connections.<br />
#maxconnections=<br />
<br />
<br />
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)<br />
<br />
# server=1 tells Bitcoin to accept JSON-RPC commands.<br />
#server=1<br />
<br />
# You must set rpcuser and rpcpassword to secure the JSON-RPC api<br />
#rpcuser=Ulysseys<br />
#rpcpassword=YourSuperGreatPasswordNumber_385593<br />
<br />
# How many seconds bitcoin will wait for a complete RPC HTTP request.<br />
# after the HTTP connection is established. <br />
rpctimeout=30<br />
<br />
# By default, only RPC connections from localhost are allowed. Specify<br />
# as many rpcallowip= settings as you like to allow connections from<br />
# other hosts (and you may use * as a wildcard character):<br />
#rpcallowip=10.1.1.34<br />
#rpcallowip=192.168.1.*<br />
<br />
# Listen for RPC connections on this TCP port:<br />
rpcport=8332<br />
<br />
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind<br />
# running on another host using this option:<br />
rpcconnect=127.0.0.1<br />
<br />
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate<br />
# with Bitcoin -server or bitcoind<br />
#rpcssl=1<br />
<br />
# OpenSSL settings used when rpcssl=1<br />
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH<br />
rpcsslcertificatechainfile=server.cert<br />
rpcsslprivatekeyfile=server.pem<br />
<br />
<br />
# Miscellaneous options<br />
<br />
# Set gen=1 to attempt to generate bitcoins<br />
gen=0<br />
<br />
# Use SSE instructions to try to generate bitcoins faster.<br />
#4way=1<br />
<br />
# Pre-generate this many public/private key pairs, so wallet backups will be valid for<br />
# both prior transactions and several dozen future transactions.<br />
keypool=100<br />
<br />
# Pay an optional transaction fee every time you send bitcoins. Transactions with fees<br />
# are more likely than free transactions to be included in generated blocks, so may<br />
# be validated sooner.<br />
paytxfee=0.00<br />
<br />
# Allow direct connections for the 'pay via IP address' feature.<br />
#allowreceivebyip=1<br />
<br />
<br />
# User interface options<br />
<br />
# Start Bitcoin minimized<br />
#min=1<br />
<br />
# Minimize to the system tray<br />
#minimizetotray=1</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2880Running Bitcoin2011-01-28T20:04:46Z<p>Kiba: /* Bitcoin.conf Configuration File */</p>
<hr />
<div>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).<br />
==Command-line arguments==<br />
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:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-? This help message<br />
==Bitcoin.conf Configuration File==<br />
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.<br />
<br />
The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.<br />
<br />
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.<br />
{|<br />
! Operating System<br />
! Default bitcoin datadir<br />
! Typical path to configuration file<br />
|-<br />
| Windows<br />
| %APPDATA%\Bitcoin\<br />
| :\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf<br />
|-<br />
| Linux<br />
| $HOME/.bitcoin/<br />
| /Users/username/.bitcoin/bitcoin.conf<br />
|-<br />
| Mac OSX<br />
| $HOME/Library/Application Support/Bitcoin/<br />
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf<br />
|}</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2879Running Bitcoin2011-01-28T20:00:45Z<p>Kiba: /* Bitcoin.conf Configuration File */</p>
<hr />
<div>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).<br />
==Command-line arguments==<br />
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:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-? This help message<br />
==Bitcoin.conf Configuration File==<br />
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.<br />
<br />
The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.<br />
<br />
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.</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2878Running Bitcoin2011-01-28T20:00:30Z<p>Kiba: /* Command-line arguments */</p>
<hr />
<div>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).<br />
==Command-line arguments==<br />
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:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-? This help message<br />
==Bitcoin.conf Configuration File==</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2876Running Bitcoin2011-01-28T19:59:37Z<p>Kiba: </p>
<hr />
<div>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).<br />
==Command-line arguments==<br />
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:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-? This help message</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=2875Running Bitcoin2011-01-28T19:58:24Z<p>Kiba: Created page with "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 (cal..."</p>
<hr />
<div>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).</div>Kibahttps://tests.bitcoin.it/w/index.php?title=The_Bitcoin_Times&diff=2817The Bitcoin Times2011-01-27T02:49:54Z<p>Kiba: Created page with "'''The Bitcoin Times''' is a magazine created by fabianhjr to cover the various aspect of Bitcoin."</p>
<hr />
<div>'''The Bitcoin Times''' is a magazine created by fabianhjr to cover the various aspect of Bitcoin.</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Myths&diff=1218Myths2011-01-03T21:46:08Z<p>Kiba: Created page with "People have several common misconception about how bitcoin really work. This page address these misconceptions. ==Bitcoin is Backed by CPU Cycles== Bitcoin is not backed by any..."</p>
<hr />
<div>People have several common misconception about how bitcoin really work. This page address these misconceptions.<br />
<br />
<br />
==Bitcoin is Backed by CPU Cycles==<br />
Bitcoin is not backed by anything. It is a commodity in its own right. Is gold backed by anything? No! It's just gold. Same thing with bitcoin.</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Currency_exchange&diff=1069Currency exchange2010-12-31T16:44:26Z<p>Kiba: /* History of fraud */</p>
<hr />
<div>{{stub}}<br />
<br />
Exchanging bitcoins for other forms of currency brings up some issues regarding chargeback fraud. Specifically, payment methods such as credit cards, and PayPal, can be reversed up to 90 days after the transaction took place. In contrast, bitcoin is a "hard currency", once you spend bitcoins, you cannot get them back by 'pulling' from your side. Thus, when you trade bitcoin for a 'soft' currency like paypal or credit card, you open yourself up to the risk of chargeback after you send bitcoin. The buyer may initiate a chargeback by claiming non-receipt of goods, or if a stolen account was used, the real account owner will initiate the process once he notices a charge he didn't make. As a result, it is strongly recommended to not trade 'soft' currency for 'hard' currency with people you do not know or trust. <br />
<br />
==History of fraud==<br />
<br />
The two major exchanges, [[Bitcoin Market]] and [[Mtgox]], were hit with a wave of PayPal scams in October 2010, where one or a group of individuals used stolen PayPal accounts to fund their exchange accounts to buy bitcoins. This has caused the freezing of the Mtgox paypal account<ref>http://www.bitcoin.org/smf/index.php?topic=1419.0</ref>, and a suspension of new user registration on [[Bitcoin Market]]<ref>http://www.bitcoin.org/smf/index.php?topic=1461.0</ref>. These freezing of accounts cause liquidity problem for the bitcoin economy as it become much more difficult to exchange dollars into bitcoin. Eventually, solutions like [[bitcoin-otc]] arise that take care of these liquidity problem.<br />
<br />
==See also==<br />
<br />
* [[Category:Bitcoin exchanges]]<br />
<br />
==References==<br />
<references/></div>Kibahttps://tests.bitcoin.it/w/index.php?title=Proof_of_work&diff=1044Proof of work2010-12-31T04:54:09Z<p>Kiba: moved Proof-of-work to Proof of work over redirect</p>
<hr />
<div>{{stub}}<br />
<br />
A '''proof-of-work''' is the verifiable result obtained through a given work. Anyone should be able to make sure that a given share of work was accomplished.<br />
<br />
This is used in bitcoin for blocks generation. The block hash itself is a proof-of-work, proving whoever generated that block deserves the associated transaction fees and reward.<br />
<br />
== Example ==<br />
<br />
Let's say our base work is "Hello world" and our work is to find a hash starting with "000". We are going to increase a value hashes alongside "Hello world" (nonce) until we reach our goal.<br />
<br />
Hello world ! 0 : 3f6fc92516327a1cc4d3dca5ab2b27aeedf2d459a77fa06fd3c6b19fb609106a<br />
Hello world ! 1 : b5690c48c2d0a09481186aaa99e4e090901ff2ac4d572e6706dfd30eefc22a27<br />
Hello world ! 2 : 5b6fd9c27fcb54ca23404d9428f081b7c9280ba6370e33a6a20b16f40ce76320<br />
Hello world ! 3 : 9c5d769416aa0ca894abf22bd17bd30fbb6959291423ae1903a9f86a1fe7ce78<br />
Hello world ! 4 : 4efc65df7933e4f5cc21947c61d5cc6bd11d644794bfa210603b0547c4b1cc3e<br />
Hello world ! 5 : 441b15b67d791620cd50ea537144e3115422e33bdb1b1b9b110d3265f7a9199b<br />
Hello world ! 6 : d368331386f0cf773ad53910fefcef4bdceeb526e408d3fbc9408d6f6e481ca4<br />
Hello world ! 7 : 013cc9722f38d2eb6186b75e2e7cbe6e7818e0612a2774d4400416b17ae03b87<br />
Hello world ! 8 : 3a92631799b478c3bcc554df8401b09900fbdb58cc0e58efe711cc475ee097b3<br />
Hello world ! 9 : 66658881696164fcb04f32ec505bb5e515000a85baf691beb63fc9d3f4d0fee2<br />
....<br />
Hello world ! 88 : 80d009db72c6ad35241bb3dbac77cbe177c6a803fe67527c159dbfaf2cbf9f5c<br />
Hello world ! 89 : a5b1e789f691f9793f8a84f8ebae3d8e28d49cbe0eeea2da621cd409e3bdee2b<br />
Hello world ! 90 : 4eba5b2459caac3d9ff3b787aaa5cac481aaa4a0232fbbe02a8ee4d1101c2ca2<br />
Hello world ! 91 : c811722c68b53614d58d37dcad9d540c2bce9f85b5ccae94424ff4716eea1765<br />
Hello world ! 92 : e30c716fccda22f394a8e80a2670b97968b5416b8b39e2061a7b7d1a9f41e0a9<br />
Hello world ! 93 : 965425c39d4e24c532721d7f7b77a00b31b0c0d0e316d46240c4e6bec9c09f65<br />
Hello world ! 94 : 7090a0e5d88cff635e42ea33fcd6091a058e9cdd58ab8cd5c21c1c70421e35c6<br />
Hello world ! 95 : b74f3b2cf1061895f880a99d1d0249a8cedf223d3ed061150548aa6212c88d43<br />
Hello world ! 96 : 447ca2fa886965af084808d22116edde4383cbaa16fd1fbcf3db61421b9990b9<br />
Hello world ! 97 : 000ba61ca46d1d317684925a0ef070e30193ff5fa6124aff76f513d96f49349d<br />
<br />
And here we are. Now we just have to let the network know our block, made of "Hello world" and 97, won. In bitcoin things are a bit more complex, especially since the header contains the [http://en.wikipedia.org/wiki/Merkle_tree merkle tree] which depends on the included transactions, which includes the transaction to ourself (which uses a different address each time, thru making the header unique).<br />
<br />
[[Category:Vocabulary]]<br />
<br />
[[fr:Preuve de travail]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Proof-of-work&diff=1045Proof-of-work2010-12-31T04:54:09Z<p>Kiba: moved Proof-of-work to Proof of work over redirect</p>
<hr />
<div>#REDIRECT [[Proof of work]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Talk:Proof_of_work&diff=1046Talk:Proof of work2010-12-31T04:54:09Z<p>Kiba: moved Talk:Proof-of-work to Talk:Proof of work</p>
<hr />
<div>==page rename suggestion==<br />
I think page should be renamed to "Proof of work". There's no reason this has to be a hyphenated one-word. --[[User:Nanotube|Nanotube]] 08:02, 26 December 2010 (GMT)</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Talk:Proof-of-work&diff=1047Talk:Proof-of-work2010-12-31T04:54:09Z<p>Kiba: moved Talk:Proof-of-work to Talk:Proof of work</p>
<hr />
<div>#REDIRECT [[Talk:Proof of work]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Category_talk:Bitcoin_markets&diff=1042Category talk:Bitcoin markets2010-12-31T04:52:31Z<p>Kiba: /* Suggestion to rename category bitcoin-markets to bitcoin-exchanges */</p>
<hr />
<div>==Suggestion to rename category bitcoin-markets to bitcoin-exchanges==<br />
<br />
Suggest to rename this category to "Bitcoin exchanges", since, say, biddingpond is also a 'bitcoin market'. "Market" is too broad, given that this category is clearly intended for just the exchanges. --[[User:Nanotube|Nanotube]] 07:36, 26 December 2010 (GMT)<br />
:That was intended. 04:52, 31 December 2010 (GMT)</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Cpu_Miner&diff=1038Cpu Miner2010-12-31T04:50:36Z<p>Kiba: moved Cpu-miner to Cpu Miner</p>
<hr />
<div>{{stub}}'''cpu-miner''' is a Bitcoin cpu miner created by jgarzik. It receives work through the standard JSON-RPC 'getwork' command, and supports several algorithms for doing encryption required to build a block.<br />
<br />
==Algorithms==<br />
*'''c:''' Linux kernel (but not restricted to Linux) implementation of SHA256.<br />
*'''4way:''' 128-bit SSE2 optimizations which are already available as a compile-time option on the classic Bitcoin client.<br />
*'''via:''' Implementation of the Padlock encryption optimizations on VIA CPUs.<br />
*'''cryptopp:''' C/C++ Implementation from the Crypto++ library.<br />
*'''cryptopp_asm32:''' 32-bit assembly implementation from the Crypto++ library.<br />
<br />
==See also==<br />
<br />
* [[Pooled Mining]]<br />
<br />
==External Links==<br />
<br />
* [https://github.com/jgarzik/cpuminer Github repository with cpuminer code]<br />
* [http://www.bitcoin.org/smf/index.php?topic=1925.0 Forum thread with announcement and discussion]<br />
<br />
[[Category:Bitcoin miners]]<br />
[[Category:Mining]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Cpu-miner&diff=1039Cpu-miner2010-12-31T04:50:36Z<p>Kiba: moved Cpu-miner to Cpu Miner</p>
<hr />
<div>#REDIRECT [[Cpu Miner]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Talk:Cpu_Miner&diff=1040Talk:Cpu Miner2010-12-31T04:50:36Z<p>Kiba: moved Talk:Cpu-miner to Talk:Cpu Miner</p>
<hr />
<div>==rename page==<br />
<br />
this page name shouldn't really have a hyphen in it... i don't see the jgarzik cpu miner being referred to anywhere as 'cpu-miner'. maybe 'cpuminer' (name of github repo), or just 'cpu miner'...</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Talk:Cpu-miner&diff=1041Talk:Cpu-miner2010-12-31T04:50:36Z<p>Kiba: moved Talk:Cpu-miner to Talk:Cpu Miner</p>
<hr />
<div>#REDIRECT [[Talk:Cpu Miner]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Bitcoin_Market&diff=841Bitcoin Market2010-12-26T07:00:12Z<p>Kiba: </p>
<hr />
<div>The '''Bitcoin Market''' is a [[bitcoin]] [[currency exchange]] site owned and operated by dwdollar. It supports PayPal, Moneybookers, Pecunix, and Liberty Reserve. Currently, due to PayPal chargeback issues, registration is closed. Users who have gained some trust on the [[Bitcoin forum]] can contact dwdollar for an account. Unlike [[MtGox]], exchanges are done directly with individual users.<br />
==External links==<br />
*[https://www.bitcoinmarket.com/ Bitcoin Market]<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Bitcoin_Market&diff=839Bitcoin Market2010-12-26T06:59:43Z<p>Kiba: </p>
<hr />
<div>The '''Bitcoin Market''' is a [[bitcoin]] [[currency exchange]] site owned and operated by dwdollar. It supports PayPal, Moneybookers, Pecunix, and Liberty Reserve. Currently, due to PayPal chargeback issues, registration is closed. Users who have gained some trust on the [[Bitcoin forum]] can contact dwdollar for an account.<br />
==External links==<br />
*[https://www.bitcoinmarket.com/ Bitcoin Market]<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Bitcoin_Market&diff=791Bitcoin Market2010-12-24T17:46:48Z<p>Kiba: </p>
<hr />
<div>The '''Bitcoin Market''' is a [[bitcoin]] [[currency exchange]] site owned and operated by dwdollar. Currently, it is closed to registration.<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Bitcoin_Market&diff=709Bitcoin Market2010-12-22T20:50:50Z<p>Kiba: </p>
<hr />
<div>The '''Bitcoin Market''' is a [[bitcoin]] [[currency exchange]] site owned and operated by dwdollar.<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Bitcoin_Market&diff=708Bitcoin Market2010-12-22T20:50:28Z<p>Kiba: </p>
<hr />
<div>The '''Bitcoin Market''' is a [[bitcoin]] currency exchange owned and operated by dwdollar.<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Bitcoin_Market&diff=707Bitcoin Market2010-12-22T20:49:58Z<p>Kiba: Created page with "The '''Bitcoin Market''' is a bitcoin currency exchange owned and operated by dwdollar."</p>
<hr />
<div>The '''Bitcoin Market''' is a [[bitcoin]] currency exchange owned and operated by dwdollar.</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Chrome_Bitcoin_Extension&diff=706Chrome Bitcoin Extension2010-12-22T20:48:57Z<p>Kiba: </p>
<hr />
<div>The '''Chrome Bitcoin Extension''' is an addon for the chromium or chrome browser that make payment from the browser possible. Its development was funded by forum users, who made pledges totaling 300 BTC.</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Chrome_Bitcoin_Extension&diff=705Chrome Bitcoin Extension2010-12-22T20:46:59Z<p>Kiba: Created page with "The '''Chrome Bitcoin Extension''' is an addon for the chromium or chrome browser that make payment from the browser possible."</p>
<hr />
<div>The '''Chrome Bitcoin Extension''' is an addon for the chromium or chrome browser that make payment from the browser possible.</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Mt._Gox&diff=704Mt. Gox2010-12-22T20:44:53Z<p>Kiba: /* Wallet/Banking */</p>
<hr />
<div>{{stub}}<br />
'''MtGox''' is the most widely used [[bitcoin]] [[currency exchange]] market. It deals mainly in LRUSD. Historically, due to the way that mtgox works, it have higher exchange volume than any markets in the bitcoin economy.. This is mainly because mtgox requires all traders to deposit balances with mtgox. In turns, it make trading on the market instant. MtGox is run by Jed.<br />
==Trading==<br />
MtGox takes a 0.65% commission fee everytime you make a successful trade on the market.<br />
== Wallet/Banking ==<br />
MtGox also operate as a wallet/banking services similar to [[MyBitcoin]]. It also offer merchant services.<br />
<br />
==History==<br />
Mtgox went online on July 18, 2010.<ref>[http://www.bitcoin.org/smf/index.php?topic=444.0 MtGox announcement on forum]</ref><br />
<br />
On October 10, 2010 MtGox announced that their Paypal account had been suspended as a result of a scammer using stolen Paypal accounts to transfer funds to MtGox. Fraudulent Paypal transactions and chargebacks were also reported by Bitcoin Market customers around this time. Mtgox switched from Paypal to Liberty Reserve as the main funding option as a result of this attack. Former Paypal customers still had the possibility to withdraw their USD using alternative methods.<br />
<br />
==Links==<br />
<br />
* [http://mtgox.com mtgox website]<br />
==References==<br />
<references/><br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=BTCex&diff=703BTCex2010-12-22T20:41:15Z<p>Kiba: </p>
<hr />
<div>'''btcex''' is a Russian [[bitcoin]] [[currency exchange]] site. They trade Russian Rubes, Yandex Money, Webmoney and Japanese Yen for bitcoin.<br />
==External links==<br />
*[https://btcex.com/ btcex]<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=BTCex&diff=702BTCex2010-12-22T20:40:55Z<p>Kiba: </p>
<hr />
<div>'''btcex''' is a Russian [[bitcoin]] [[currency exchange]] site. They trade in Russian Rubes, Yandex Money, Webmoney and Japanese Yen.<br />
==External links==<br />
*[https://btcex.com/ btcex]<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=BTCex&diff=701BTCex2010-12-22T20:38:14Z<p>Kiba: </p>
<hr />
<div>'''btcex''' is a Russian [[bitcoin]] [[currency exchange]] site.<br />
==External links==<br />
*[https://btcex.com/ btcex]<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=BTCex&diff=677BTCex2010-12-22T00:22:40Z<p>Kiba: </p>
<hr />
<div>'''btcex''' is a Russian bitcoin currency market site.<br />
==External links==<br />
*[https://btcex.com/ btcex]<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=BTCex&diff=654BTCex2010-12-21T07:56:48Z<p>Kiba: Created page with "'''btcex''' is a Russian bitcoin exchange site. Category:Bitcoin markets"</p>
<hr />
<div>'''btcex''' is a Russian bitcoin exchange site.<br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Bitcoin_Charts&diff=653Bitcoin Charts2010-12-21T07:55:55Z<p>Kiba: </p>
<hr />
<div>'''Bitcoin Charts''', run and maintained by tcatm, is a collection of statistic and graph about the bitcoin economy. They covers three exchange sites, [[MtGox]], [[Bitcoin Market]], and [[btcex]].<br />
==External links==<br />
*[http://bitcoincharts.com/markets/ Bitcoin Charts site]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Mt._Gox&diff=652Mt. Gox2010-12-21T07:54:19Z<p>Kiba: /* Trading */</p>
<hr />
<div>{{stub}}<br />
'''MtGox''' is the most widely used [[bitcoin]] [[currency exchange]] market. It deals mainly in LRUSD. Historically, due to the way that mtgox works, it have higher exchange volume than any markets in the bitcoin economy.. This is mainly because mtgox requires all traders to deposit balances with mtgox. In turns, it make trading on the market instant. MtGox is run by Jed.<br />
==Trading==<br />
MtGox takes a 0.65% commission fee everytime you make a successful trade on the market.<br />
== Wallet/Banking ==<br />
MtGox also operate as a wallet/banking services similar to [[MyBitcoin]].<br />
<br />
==History==<br />
Mtgox went online on July 18, 2010.<ref>[http://www.bitcoin.org/smf/index.php?topic=444.0 MtGox announcement on forum]</ref><br />
<br />
On October 10, 2010 MtGox announced that their Paypal account had been suspended as a result of a scammer using stolen Paypal accounts to transfer funds to MtGox. Fraudulent Paypal transactions and chargebacks were also reported by Bitcoin Market customers around this time. Mtgox switched from Paypal to Liberty Reserve as the main funding option as a result of this attack. Former Paypal customers still had the possibility to withdraw their USD using alternative methods.<br />
<br />
==Links==<br />
<br />
* [http://mtgox.com mtgox website]<br />
==References==<br />
<references/><br />
[[Category:Bitcoin markets]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Gavin_Andresen&diff=651Gavin Andresen2010-12-21T07:44:15Z<p>Kiba: </p>
<hr />
<div>'''Gavin Andresen''' is a senior [[bitcoin]] developer who also operate services like the [[Bitcoin Faucet]] and [[Clearcoin]].<br />
[[Category:Bitcoiners]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Gavin_Andresen&diff=650Gavin Andresen2010-12-21T07:43:14Z<p>Kiba: </p>
<hr />
<div>'''Gavin Andresen''' is a senior [[bitcoin]] developer who also operate services like the [[Bitcoin facuet]] and [[Clearcoin]].<br />
[[Category:Bitcoiners]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Gavin_Andresen&diff=649Gavin Andresen2010-12-21T07:42:27Z<p>Kiba: </p>
<hr />
<div>'''Gavin Andresen''' is a senior [[bitcoin]] developer who also operate services like the [[Bitcoin Facuet]] and [[Clearcoin]].<br />
[[Category:Bitcoiners]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Gavin_Andresen&diff=648Gavin Andresen2010-12-21T07:41:56Z<p>Kiba: </p>
<hr />
<div>'''Gavin Andresen''' is a senior bitcoin developer who also operate services like the [[Bitcoin Facuet]] and [[Clearcoin]].<br />
[[Category:Bitcoiners]]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Bitcoin_Charts&diff=647Bitcoin Charts2010-12-21T07:40:33Z<p>Kiba: </p>
<hr />
<div>'''Bitcoin Charts''', run and maintained by tcatm, is a collection of statistic and graph about the bitcoin economy.<br />
==External links==<br />
*[http://bitcoincharts.com/markets/ Bitcoin Charts site]</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Bitcoin_Charts&diff=646Bitcoin Charts2010-12-21T07:40:03Z<p>Kiba: Created page with "'''Bitcoin Charts''', run and maintained by tcatm, is a collection of statistic and graph about the bitcoin economy."</p>
<hr />
<div>'''Bitcoin Charts''', run and maintained by tcatm, is a collection of statistic and graph about the bitcoin economy.</div>Kibahttps://tests.bitcoin.it/w/index.php?title=Mt._Gox&diff=645Mt. Gox2010-12-21T07:38:42Z<p>Kiba: </p>
<hr />
<div>{{stub}}<br />
'''MtGox''' is the most widely used [[bitcoin]] [[currency exchange]] market. It deals mainly in LRUSD. Historically, due to the way that mtgox works, it have higher exchange volume than any markets in the bitcoin economy.. This is mainly because mtgox requires all traders to deposit balances with mtgox. In turns, it make trading on the market instant. MtGox is run by Jed.<br />
==Trading==<br />
MtGox takes a 0.65% commission fee everytime you make a successful trade on the market.<br />
<br />
==History==<br />
Mtgox went online on July 18, 2010.<ref>[http://www.bitcoin.org/smf/index.php?topic=444.0 MtGox announcement on forum]</ref><br />
<br />
On October 10, 2010 MtGox announced that their Paypal account had been suspended as a result of a scammer using stolen Paypal accounts to transfer funds to MtGox. Fraudulent Paypal transactions and chargebacks were also reported by Bitcoin Market customers around this time. Mtgox switched from Paypal to Liberty Reserve as the main funding option as a result of this attack. Former Paypal customers still had the possibility to withdraw their USD using alternative methods.<br />
<br />
==Links==<br />
<br />
* [http://mtgox.com mtgox website]<br />
==References==<br />
<references/><br />
[[Category:Bitcoin markets]]</div>Kiba