https://tests.bitcoin.it/w/api.php?action=feedcontributions&user=Unthinkingbit&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-29T01:47:40ZUser contributionsMediaWiki 1.30.0https://tests.bitcoin.it/w/index.php?title=Software&diff=13445Software2011-07-22T21:14:06Z<p>Unthinkingbit: </p>
<hr />
<div>List of Bitcoin-related software. See also [[:Category:Software|Category:Software]].<br />
<br />
==Bitcoin clients==<br />
Bitcoin clients:<br />
*[[Original Bitcoin client|Bitcoin client]] - standard Bitcoin client, recommended for installation<br />
*[[bitcoind]] - GUI-less version of the standard Bitcoin client, providing [[API reference (JSON-RPC)|JSON-RPC]] interface (see also -server option of the standard client)<br />
Frontends to bitcoind:<br />
*[[BitcoinApp]] - RPC client for iOS devices (iPhone, iPad, iPodTouch)<br />
*[[Bitcoiner]] - Java RPC client (Android)<br />
*[[Bitcoin-js-remote]] - JavaScript RPC client, support for QR codes<br />
*[[Bitcoin-qt]] - C++/Qt based tabbed UI for Bitcoin, Linux/MacOSX/Windows, full-featured<br />
*[[Python Bitcoinclient]] - Python RPC client<br />
*[[Spesmilo]] - Python/PySide RPC client<br />
*[[Bitcoin-python]] - Python API<br />
*[[Java Bitcoin Client]] - Java API<br />
*[[Wallet.Net]] - Windows (soon to be cross platform) Full Featured, secure RPC client<br />
Alternative, experimental implementations:<br />
*[[BitDroid]] - Java client<br />
*[[Bitdollar]] - C++/Qt client, unstable beta version<br />
*[[BitCoinJ]] - Java client by Google, early development stage<br />
*[[Freecoin]] - C++ client, supports alternative currencies like [[Beertoken]]<br />
*[[Pycoin]] - Python client<br />
*[[QBitcoin]] - C++/Qt client, unfinished<br />
Frontends to eWallet:<br />
*[[BitPay]] - Android application<br />
<br />
==Bitcoin Trade Data==<br />
*[[Bitcoin Charts]] – Html website that has trading data for virtual all the bitcoin markets.<br />
*[[Bitcoinity]] - Html Ajax website that shows a live feed of [[MtGox]], [[TradeHill]], and [[BitMarket]].<br />
*[[MtGox Live]] - Html website that shows a live fee of [[MtGox]] trade data in an innovative chart form. (Must Use Chrome)<br />
*[[Preev]] - Bitcoin converter with live exchange rates.<br />
<br />
==Bitcoin software==<br />
<br />
Web interfaces for merchants:<br />
*[[MyBitcoin]] - Buy Now button to insert on websites<br />
*[[Bitcoin Evolution]] - Non wallet-based Buy Now button to insert into websites (handles sales tracking; client must be used for actual transaction)<br />
*[[Btceconomy]] - a JavaScript widget listing items for sale<br />
*[[Javascript Bitcoin Converter]] - currency conversion<br />
<br />
Web apps (opensource):<br />
*[[Bitcoin Central]] - currency exchange<br />
*[[Bitcoin Poker Room]] - poker site<br />
<br />
Browser extensions:<br />
*[[Bitcoin Extension]] - check balance and send bitcoins (Chrome)<br />
*[[Bitcoin Ticker]] - monitoring price (Chrome)<br />
*[[Bitcoin Prices (extension)]] - monitoring price (Firefox)<br />
*[[Bitcoin Tool]] - recognizes Bitcoin addresses on websites (Firefox, Chrome, IE)<br />
<br />
PC apps:<br />
*[[BTConvert]] - currency conversion<br />
*[[Sierra Chart MtGox Bridge]] - real-time charting<br />
*[[BitTicker]] - monitoring price (Mac OS X)<br />
*[[ToyTrader]] - a command line trading tool for [[MtGox]]<br />
<br />
Mobile apps:<br />
*[[Bitcoin Alert]] - monitoring price (Android)<br />
*[[BitcoinX]] - monitoring price (Android)<br />
*[[BtcMobile]] - monitoring price and mining pool statistics (iPhone/iPad, Android)<br />
*[[Miner Status]] - monitoring miner status (Android)<br />
*[[SMS Bitcoins]] - transactions by SMS<br />
*[[Bitcoin Wallet Balance]] - view your balance in real time on your android phone<br />
<br />
Other device apps:<br />
*[[Zen Cart Bitcoin Payment Module]] - a payment module that interacts with bitcoind for the Zen Cart eCommerce shopping chart<br />
<br />
Operating systems:<br />
*[[LinuxCoin]] - a lightweight Debian-based OS, with the Bitcoin client and GPU mining software<br />
<br />
Mining apps:<br />
*[[Poclbm]] - Python/OpenCL GPU miner ([[Poclbm-gui|GUI]])<br />
*[[Poclbm-mod]] - more efficient version of [[Poclbm]] ([[Poclbm-mod-gui|GUI]])<br />
*[[DiabloMiner]] - Java/OpenCL GPU miner ([[DiabloMiner.app|MAC OS X GUI]])<br />
*[[RPC Miner]] - remote RPC miner ([[RPCminer.app|MAC OS X GUI]])<br />
*[[Phoenix miner]] - miner<br />
*[[Cpu Miner]] - miner<br />
*[[Ufasoft miner]] - miner<br />
*[[Pyminer]] - Python miner, reference implementation<br />
*[[Remote miner]] - mining pool software<br />
*[[Poold]] - mining pool software<br />
*[[Open Source FGPA Bitcoin Miner]] - a miner that makes use of an FPGA Board<br />
<br />
Utilities, libraries, and interfaces:<br />
*[[Bitcointools]] - a set of Python tools accessing the transaction database and the wallet<br />
*[[Finance::MtGox]] - a Perl module which interfaces with the Mt. Gox API<br />
*[[BitcoinCrypto]] - a lightweight Bitcoin crypto library for Java/Android<br />
*[[Bitcoin Dissector]] - a wireshark dissector for the bitcoin protocol<br />
<br />
Lists of software:<br />
*[[BitGit]] - list of Bitcoin-related opensource projects hosted at Git<br />
<br />
Developer resources:<br />
*[[:Category:Developer|Category:Developer]]<br />
*[[:Category:Technical|Category:Technical]]<br />
*[[Original Bitcoin client/API calls list]]<br />
*[[API reference (JSON-RPC)]]<br />
<br />
Other:<br />
*[[Namecoin]] - a distributed naming system based on Bitcoin technology<br />
*[[Bitcoin Consultancy]] - an organization providing open source software and Bitcoin-related consulting<br />
*[[Open Transactions]] - a financial crypto and digital cash software library, complementary to Bitcoin<br />
*[[Moneychanger]] - Java-based GUI for [[Open Transactions]]<br />
*[http://btcnames.org/ BTCnames] - a webbased aliasing service which allows to handle unlimited names for your BTC deposit hashes<br />
*[[Devcoin]] - the open source developer coin</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=Securing_your_wallet&diff=2949Securing your wallet2011-01-30T01:41:43Z<p>Unthinkingbit: </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 />
<br />
WALLET=/tmp/wallet${TS}<br />
WALLET_E=/tmp/wallet${TS}.crypt<br />
<br />
bitcoind backupwallet $WALLET<br />
gpg -r myusername --output $WALLET_E --encrypt $WALLET<br />
scp $WALLET_E user@myserver.org:~/wallets/<br />
rm $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.</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=OpenSourceEncryptionSoftware&diff=2804OpenSourceEncryptionSoftware2011-01-26T19:12:41Z<p>Unthinkingbit: /* Examples */</p>
<hr />
<div>==dm-crypt==<br />
===Description===<br />
Dm-crypt is part of the Linux Kernel. Some distributions might not include it in their kernel configurations, however. It is a lot like TrueCrypt: it allows you to mount encrypted files or partitions and decrypt/encrypt them on-the-fly.<br />
===Manual setup===<br />
Your distro probably comes with a tool to simplify using dm-crypt. However, here is how you would manually mount a file-hosted dm-crypt volume. The [http://www.paranoiacs.org/~sluskyb/hacks/hashalot/ hashalot] tool is used to prompt you for and process your password. This is used both to create the device and access it:<br />
losetup /dev/loop0 ~/encrypted<br />
HASH=`hashalot -s InsertSaltHere sha256 | hexdump -e '32/1 "%02x"'`<br />
echo 0 `blockdev --getsize /dev/loop0` crypt aes-cbc-essiv:sha256 \<br />
$HASH 0 /dev/loop0 0 | dmsetup create dmDevice<br />
mount /dev/mapper/dmDevice /mnt/encrypted<br />
* Losetup makes the container file (~/encrypted in this case) act like a device.<br />
* The hashalot command prompts you for a password and then hashes it, adding the specified salt. The salt should be random, but it mustn't change.<br />
* The hexdump command puts the binary hashalot output into the format required for dm-crypt<br />
* Dm-crypt is set up on the /dev/loop0 device created by losetup. It uses the password hash created previously. The aes-cbc-essiv:sha256 encryption method is secure, though probably not as secure as Truecrypt's XTS method, which does not appear to be available in official kernel releases as far as I can tell. The dm-crypt device is created as /dev/mapper/dmDevice in this example.<br />
* The device is mounted. Before you do this for the first time, you need to run mke2fs. If you ever enter the wrong password, the device will appear to contain random data and attempting to mount it will fail.<br />
<br />
==eCryptfs==<br />
===Description===<br />
eCryptfs is a POSIX-compliant enterprise-class stacked cryptographic filesystem for Linux.<br />
===Download===<br />
[https://launchpad.net/ecryptfs Latest source link on right side of page.]<br />
<br />
[https://launchpad.net/ecryptfs/+download All downloads.]<br />
===Examples===<br />
Examples can be found in Damien Oh's article [http://www.makeuseof.com/tag/encrypt-your-files-in-linux-with-ecryptfs/ How To Encrypt Files in Linux with eCryptfs.]<br />
===FAQ===<br />
[http://ecryptfs.sourceforge.net/ecryptfs-faq.html FAQ]<br />
===HomePage===<br />
[https://launchpad.net/ecryptfs eCryptfs - Enterprise Cryptographic Filesystem]<br />
===License===<br />
[https://launchpad.net/ubuntu/natty/+source/ecryptfs-utils/+copyright GPL 2+]<br />
<br />
<br />
==OpenSSL==<br />
===Description===<br />
The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade, full-featured, and Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library.<br />
===Donation===<br />
[http://www.openssl.org/support/donations.html Donation page.]<br />
===Download===<br />
[http://www.openssl.org/source/ Source]<br />
===Examples===<br />
Based on Grondilu's [http://www.bitcoin.org/smf/index.php?topic=2458.msg33379#msg33379 post,] to encrypt the wallet, from a terminal in the bitcoin parent directory, type:<br />
<br />
openssl enc -aes256 -in ./.bitcoin/wallet.dat -out wallet.aes256<br />
<br />
From [http://www.madboa.com/people/paul/ Paul Heinlein's] [http://www.madboa.com/geek/openssl/ openssl command line how to,] to decode, add the '-d' option, set the '-in' option to the output file name, to type:<br />
<br />
openssl enc -d -aes256 -in wallet.aes256 -out wallet.dat<br />
<br />
===FAQ===<br />
[http://www.openssl.org/support/faq.html FAQ]<br />
===HomePage===<br />
[http://www.openssl.org OpenSSL Project]<br />
===License===<br />
[http://www.openssl.org/source/license.html Dual licensed under two BSD style open source licenses.]<br />
<br />
<br />
==True Crypt==<br />
===Description===<br />
Free open-source disk encryption software for Windows 7/Vista/XP, Mac OS X, and Linux. True Crypt creates a virtual encrypted disk within a file and mounts it as a real disk.<br />
===Documentation===<br />
[http://www.truecrypt.org/docs/ Documentation page.]<br />
===Donation===<br />
[http://www.truecrypt.org/donations/?lnk=5 Donation page.]<br />
===Download===<br />
[http://www.truecrypt.org/downloads Binaries]<br />
<br />
[http://www.truecrypt.org/downloads2 Source]<br />
===FAQ===<br />
[http://www.truecrypt.org/faq FAQ]<br />
===HomePage===<br />
[http://www.truecrypt.org/ TrueCrypt]<br />
===License===<br />
[http://www.truecrypt.org/legal/license True Crypt Open Source License.]<br />
<br />
<br />
[[Category:Technical]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=DiabloMiner&diff=2694DiabloMiner2011-01-24T09:40:17Z<p>Unthinkingbit: </p>
<hr />
<div>DiabloMiner is a Java GPU bitcoin miner that uses the OpenCL framework to quickly perform the hashing computations. Works on current Nvidia drivers and ATI Stream SDK 2.1.<br />
==Donation==<br />
Bitcoin address in the signature in the [http://www.bitcoin.org/smf/index.php?action=profile;u=1796 founder's page.]<br />
==Download==<br />
[http://adterrasperaspera.com/images/DiabloMiner.zip Newest binary.]<br />
<br />
[https://github.com/Diablo-D3/DiabloMiner/archives/master Source.]<br />
==Examples==<br />
From the introductory [http://www.bitcoin.org/smf/index.php?topic=1721.msg21054#msg21054 post,] to run type:<br />
<br />
"./DiabloMiner-YourOS.sh -u youruser -p yourpass" matching the user and pass set in your bitcoin.conf.<br />
<br />
<br />
To run on Windows you have to do something like:<br />
<br />
java -cp target\libs\*;target\DiabloMiner-0.0.1-SNAPSHOT.jar -Djava.library.path=target\libs\natives\windows com.diablominer.DiabloMiner.DiabloMiner -u youruser -p yourpassword<br />
==Founder==<br />
[http://www.bitcoin.org/smf/index.php?action=profile;u=1796 DiabloD3]<br />
==HomePage==<br />
[https://github.com/Diablo-D3/DiabloMiner Project Page]<br />
<br />
[http://www.bitcoin.org/smf/index.php?topic=1721.0 Project Thread]<br />
==License==<br />
[http://www.gnu.org/copyleft/gpl.html GPL]<br />
<br />
[[Category:Mining]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=OpenSourceEncryptionSoftware&diff=2688OpenSourceEncryptionSoftware2011-01-24T05:40:24Z<p>Unthinkingbit: </p>
<hr />
<div>==eCryptfs==<br />
===Description===<br />
eCryptfs is a POSIX-compliant enterprise-class stacked cryptographic filesystem for Linux.<br />
===Download===<br />
[https://launchpad.net/ecryptfs Latest source link on right side of page.]<br />
<br />
[https://launchpad.net/ecryptfs/+download All downloads.]<br />
===Examples===<br />
Examples can be found in Damien Oh's article [http://www.makeuseof.com/tag/encrypt-your-files-in-linux-with-ecryptfs/ How To Encrypt Files in Linux with eCryptfs.]<br />
===FAQ===<br />
[http://ecryptfs.sourceforge.net/ecryptfs-faq.html FAQ]<br />
===HomePage===<br />
[https://launchpad.net/ecryptfs eCryptfs - Enterprise Cryptographic Filesystem]<br />
===License===<br />
[https://launchpad.net/ubuntu/natty/+source/ecryptfs-utils/+copyright GPL 2+]<br />
<br />
<br />
==OpenSSL==<br />
===Description===<br />
The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade, full-featured, and Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library.<br />
===Donation===<br />
[http://www.openssl.org/support/donations.html Donation page.]<br />
===Download===<br />
[http://www.openssl.org/source/ Source]<br />
===Examples===<br />
From Grondilu's [http://www.bitcoin.org/smf/index.php?topic=2458.msg33379#msg33379 post,] to encrypt the wallet, from a terminal in bitcoin parent directory, type:<br />
<br />
openssl enc -aes256 -in ./bitcoin/wallet.dat -out wallet.dat.aes256<br />
<br />
From [http://www.madboa.com/people/paul/ Paul Heinlein's] [http://www.madboa.com/geek/openssl/ openssl command line how to,] to decode, add the '-d' option, set the '-in' option to the output file name, to type:<br />
<br />
openssl enc -d -aes256 -in wallet.dat.aes256 -out wallet.dat<br />
===FAQ===<br />
[http://www.openssl.org/support/faq.html FAQ]<br />
===HomePage===<br />
[http://www.openssl.org OpenSSL Project]<br />
===License===<br />
[http://www.openssl.org/source/license.html Dual licensed under two BSD style open source licenses.]<br />
<br />
<br />
==True Crypt==<br />
===Description===<br />
Free open-source disk encryption software for Windows 7/Vista/XP, Mac OS X, and Linux. True Crypt creates a virtual encrypted disk within a file and mounts it as a real disk.<br />
===Documentation===<br />
[http://www.truecrypt.org/docs/ Documentation page.]<br />
===Donation===<br />
[http://www.truecrypt.org/donations/?lnk=5 Donation page.]<br />
===Download===<br />
[http://www.truecrypt.org/downloads Binaries]<br />
<br />
[http://www.truecrypt.org/downloads2 Source]<br />
===FAQ===<br />
[http://www.truecrypt.org/faq FAQ]<br />
===HomePage===<br />
[http://www.truecrypt.org/ TrueCrypt]<br />
===License===<br />
[http://www.truecrypt.org/legal/license True Crypt Open Source License.]<br />
<br />
<br />
[[Category:Technical]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=OpenSourceEncryptionSoftware&diff=2687OpenSourceEncryptionSoftware2011-01-24T05:39:35Z<p>Unthinkingbit: </p>
<hr />
<div>Open source encryption software descriptions.<br />
==eCryptfs==<br />
===Description===<br />
eCryptfs is a POSIX-compliant enterprise-class stacked cryptographic filesystem for Linux.<br />
===Download===<br />
[https://launchpad.net/ecryptfs Latest source link on right side of page.]<br />
<br />
[https://launchpad.net/ecryptfs/+download All downloads.]<br />
===Examples===<br />
Examples can be found in Damien Oh's article [http://www.makeuseof.com/tag/encrypt-your-files-in-linux-with-ecryptfs/ How To Encrypt Files in Linux with eCryptfs.]<br />
===FAQ===<br />
[http://ecryptfs.sourceforge.net/ecryptfs-faq.html FAQ]<br />
===HomePage===<br />
[https://launchpad.net/ecryptfs eCryptfs - Enterprise Cryptographic Filesystem]<br />
===License===<br />
[https://launchpad.net/ubuntu/natty/+source/ecryptfs-utils/+copyright GPL 2+]<br />
<br />
<br />
==OpenSSL==<br />
===Description===<br />
The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade, full-featured, and Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library.<br />
===Donation===<br />
[http://www.openssl.org/support/donations.html Donation page.]<br />
===Download===<br />
[http://www.openssl.org/source/ Source]<br />
===Examples===<br />
From Grondilu's [http://www.bitcoin.org/smf/index.php?topic=2458.msg33379#msg33379 post,] to encrypt the wallet, from a terminal in bitcoin parent directory, type:<br />
<br />
openssl enc -aes256 -in ./bitcoin/wallet.dat -out wallet.dat.aes256<br />
<br />
From [http://www.madboa.com/people/paul/ Paul Heinlein's] [http://www.madboa.com/geek/openssl/ openssl command line how to,] to decode, add the '-d' option, set the '-in' option to the output file name, to type:<br />
<br />
openssl enc -d -aes256 -in wallet.dat.aes256 -out wallet.dat<br />
===FAQ===<br />
[http://www.openssl.org/support/faq.html FAQ]<br />
===HomePage===<br />
[http://www.openssl.org OpenSSL Project]<br />
===License===<br />
[http://www.openssl.org/source/license.html Dual licensed under two BSD style open source licenses.]<br />
<br />
<br />
==True Crypt==<br />
===Description===<br />
Free open-source disk encryption software for Windows 7/Vista/XP, Mac OS X, and Linux. True Crypt creates a virtual encrypted disk within a file and mounts it as a real disk.<br />
===Documentation===<br />
[http://www.truecrypt.org/docs/ Documentation page.]<br />
===Donation===<br />
[http://www.truecrypt.org/donations/?lnk=5 Donation page.]<br />
===Download===<br />
[http://www.truecrypt.org/downloads Binaries]<br />
<br />
[http://www.truecrypt.org/downloads2 Source]<br />
===FAQ===<br />
[http://www.truecrypt.org/faq FAQ]<br />
===HomePage===<br />
[http://www.truecrypt.org/ TrueCrypt]<br />
===License===<br />
[http://www.truecrypt.org/legal/license True Crypt Open Source License.]<br />
<br />
<br />
[[Category:Technical]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=OpenSourceEncryptionSoftware&diff=2686OpenSourceEncryptionSoftware2011-01-24T05:31:43Z<p>Unthinkingbit: Created page with "Open source encryption software descriptions. ==eCryptfs== ===Description=== eCryptfs is a POSIX-compliant enterprise-class stacked cryptographic filesystem for Linux. ===Downloa..."</p>
<hr />
<div>Open source encryption software descriptions.<br />
==eCryptfs==<br />
===Description===<br />
eCryptfs is a POSIX-compliant enterprise-class stacked cryptographic filesystem for Linux.<br />
===Download===<br />
[https://launchpad.net/ecryptfs Latest source link on right side of page.]<br />
<br />
[https://launchpad.net/ecryptfs/+download All downloads.]<br />
===Examples===<br />
Examples can be found in Damien Oh's article [http://www.makeuseof.com/tag/encrypt-your-files-in-linux-with-ecryptfs/ How To Encrypt Files in Linux with eCryptfs.]<br />
===FAQ===<br />
[http://ecryptfs.sourceforge.net/ecryptfs-faq.html FAQ]<br />
===HomePage===<br />
[https://launchpad.net/ecryptfs eCryptfs - Enterprise Cryptographic Filesystem]<br />
===License===<br />
[https://launchpad.net/ubuntu/natty/+source/ecryptfs-utils/+copyright GPL 2+]<br />
<br />
<br />
==OpenSSL==<br />
===Description===<br />
The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade, full-featured, and Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library.<br />
===Donation===<br />
[http://www.openssl.org/support/donations.html Donation page.]<br />
===Download===<br />
[http://www.openssl.org/source/ Source]<br />
===Examples===<br />
From Grondilu's [http://www.bitcoin.org/smf/index.php?topic=2458.msg33379#msg33379 post,] to encrypt the wallet, from a terminal in bitcoin parent directory, type:<br />
<br />
openssl enc -aes256 -in ./bitcoin/wallet.dat -out wallet.dat.aes256<br />
<br />
From [http://www.madboa.com/people/paul/ Paul Heinlein's] [http://www.madboa.com/geek/openssl/ openssl command line how to,] to decode, add the '-d' option, set the '-in' option to the output file name, to type:<br />
<br />
openssl enc -d -aes256 -in wallet.dat.aes256 -out wallet.dat<br />
===FAQ===<br />
[http://www.openssl.org/support/faq.html FAQ]<br />
===HomePage===<br />
[http://www.openssl.org OpenSSL Project]<br />
===License===<br />
[http://www.openssl.org/source/license.html Dual licensed under two BSD style open source licenses.]<br />
<br />
<br />
==True Crypt==<br />
===Description===<br />
Free open-source disk encryption software for Windows 7/Vista/XP, Mac OS X, and Linux<br />
===Documentation===<br />
[http://www.truecrypt.org/docs/ Documentation page.]<br />
===Donation===<br />
[http://www.truecrypt.org/donations/?lnk=5 Donation page.]<br />
===Download===<br />
[http://www.truecrypt.org/downloads Binaries]<br />
<br />
[http://www.truecrypt.org/downloads2 Source]<br />
===FAQ===<br />
[http://www.truecrypt.org/faq FAQ]<br />
===HomePage===<br />
[http://www.truecrypt.org/ TrueCrypt]<br />
===License===<br />
[http://www.truecrypt.org/legal/license True Crypt Open Source License.]<br />
<br />
<br />
[[Category:Technical]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=Securing_your_wallet&diff=2685Securing your wallet2011-01-24T05:27:09Z<p>Unthinkingbit: /* General Solutions */</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 />
== 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 />
<br />
WALLET=/tmp/wallet${TS}<br />
WALLET_E=/tmp/wallet${TS}.crypt<br />
<br />
bitcoind backupwallet $WALLET<br />
gpg -r myusername --output $WALLET_E --encrypt $WALLET<br />
scp $WALLET_E user@myserver.org:~/wallets/<br />
rm $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.</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=OpenCL_miner&diff=2678OpenCL miner2011-01-24T01:54:42Z<p>Unthinkingbit: </p>
<hr />
<div>{{stub}}<br />
An '''OpenCL miner''' is a bitcoin miner that uses the [http://en.wikipedia.org/wiki/OpenCL OpenCL framework] to perform the hashing computations. When used with a modern GPU, this can produce hash rates orders of magnitude higher than what can be achieved with a CPU. Hashing on a GPU requires an OpenCL or CUDA compatible graphics card.<br />
<br />
The python [[Poclbm]] open source OpenCL bitcoin miner was created by m0mchil<ref>[http://www.bitcoin.org/smf/index.php?topic=1334.0 m0mchil's announcement on the forum]</ref>. Subsequently the java [[DiabloMiner]] based on m0mchil's was created by Diablo-D3.<ref>[http://www.bitcoin.org/smf/index.php?topic=1721.0 Diablo's announcement on the forum]</ref><br />
<br />
See the [[Mining Hardware Comparison]] page for detailed statistics on the hash rates that can be achieved with various hardware.<br />
<br />
==External Links==<br />
<br />
* m0mchill's [http://github.com/m0mchil/poclbm poclbm] open source project.<br />
<br />
==References==<br />
<references/><br />
<br />
[[Category:Mining]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=OpenCL_miner&diff=2677OpenCL miner2011-01-24T01:54:13Z<p>Unthinkingbit: </p>
<hr />
<div>{{stub}}<br />
An '''OpenCL miner''' is a bitcoin miner that uses the [http://en.wikipedia.org/wiki/OpenCL OpenCL framework] to perform the hashing computations. When used with a modern GPU, this can produce hash rates orders of magnitude higher than what can be achieved with a CPU. Hashing on a GPU requires an OpenCL or CUDA compatible graphics card.<br />
<br />
The python [[Poclbm]] open source OpenCL bitcoin miner was created by m0mchil<ref>[http://www.bitcoin.org/smf/index.php?topic=1334.0 m0mchil's announcement on the forum]</ref>. Subsequently the Java [[DiabloMiner]] based on m0mchil's was created by Diablo-D3.<ref>[http://www.bitcoin.org/smf/index.php?topic=1721.0 Diablo's announcement on the forum]</ref><br />
<br />
See the [[Mining Hardware Comparison]] page for detailed statistics on the hash rates that can be achieved with various hardware.<br />
<br />
==External Links==<br />
<br />
* m0mchill's [http://github.com/m0mchil/poclbm poclbm] open source project.<br />
<br />
==References==<br />
<references/><br />
<br />
[[Category:Mining]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=Poclbm&diff=2676Poclbm2011-01-24T01:53:41Z<p>Unthinkingbit: Created page with "Poclbm (PyOpenCL bitcoin miner) is a python GPU bitcoin miner that uses the OpenCL framework to quickly perform the hashing computations. Works with AMD - 4xxx and up, Nvidia - ..."</p>
<hr />
<div>Poclbm (PyOpenCL bitcoin miner) is a python GPU bitcoin miner that uses the OpenCL framework to quickly perform the hashing computations. Works with AMD - 4xxx and up, Nvidia - 8xxx and up, video cards.<br />
==Download==<br />
[http://github.com/downloads/m0mchil/poclbm/poclbm_py2exe_20110104.7z Latest miner.]<br />
<br />
[https://github.com/m0mchil/poclbm/archives/master Sources.]<br />
==Examples==<br />
From the Known Settings part of the [http://www.bitcoin.org/smf/index.php?topic=1334.msg14875#msg14875 introductory post.]<br />
<br />
Windows 7 64, Stream 2.2, AMD 5[7-8]70<br />
<br />
Use '-v -w 128' with '-f 30' on 5770 (160 MHash), '-f 5' on 5870 (318 MHash)<br />
==FAQ==<br />
[http://www.bitcoin.org/smf/index.php?topic=1334.msg14875#msg14875 Introductory post FAQ.]<br />
==Founder==<br />
[http://www.bitcoin.org/smf/index.php?action=profile;u=33 m0mchil]<br />
==Guides==<br />
===Windows===<br />
[http://www.newslobster.com/random/how-to-get-started-using-your-gpu-to-mine-for-bitcoins-on-windows How to get started using your GPU to mine for Bitcoins on Windows]<br />
===Ubuntu===<br />
[http://www.bitcoin.org/smf/index.php?topic=2636 Easy Ubuntu python OpenCL mining setup]<br />
==HomePage==<br />
[https://github.com/m0mchil/poclbm Project Page]<br />
<br />
[http://www.bitcoin.org/smf/index.php?topic=1334.0 Project Thread]<br />
==License==<br />
Open source, but no mention of which open source license was found.<br />
<br />
[[Category:Mining]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=OpenCL_miner&diff=2675OpenCL miner2011-01-24T01:51:49Z<p>Unthinkingbit: </p>
<hr />
<div>{{stub}}<br />
An '''OpenCL miner''' is a bitcoin miner that uses the [http://en.wikipedia.org/wiki/OpenCL OpenCL framework] to perform the hashing computations. When used with a modern GPU, this can produce hash rates orders of magnitude higher than what can be achieved with a CPU. Hashing on a GPU requires an OpenCL or CUDA compatible graphics card.<br />
<br />
The python [[poclbm]] open source OpenCL bitcoin miner was created by m0mchil<ref>[http://www.bitcoin.org/smf/index.php?topic=1334.0 m0mchil's announcement on the forum]</ref>. Subsequently the Java [[DiabloMiner]] based on m0mchil's was created by Diablo-D3.<ref>[http://www.bitcoin.org/smf/index.php?topic=1721.0 Diablo's announcement on the forum]</ref><br />
<br />
See the [[Mining Hardware Comparison]] page for detailed statistics on the hash rates that can be achieved with various hardware.<br />
<br />
==External Links==<br />
<br />
* m0mchill's [http://github.com/m0mchil/poclbm poclbm] open source project.<br />
<br />
==References==<br />
<references/><br />
<br />
[[Category:Mining]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=DiabloMiner&diff=2662DiabloMiner2011-01-23T21:44:37Z<p>Unthinkingbit: </p>
<hr />
<div>DiabloMiner is a Java GPU bitcoin miner that uses the OpenCL framework to quickly perform the hashing computations. Works on current Nvidia drivers and ATI Stream SDK 2.1.<br />
==Donation==<br />
Bitcoin address: 1DbeWKCxnVCt3sRaSAmZLoboqr8pVyFzP1<br />
==Download==<br />
[http://adterrasperaspera.com/images/DiabloMiner.zip Newest Binary.]<br />
<br />
[https://github.com/Diablo-D3/DiabloMiner/archives/master Source.]<br />
==Examples==<br />
From the introductory [http://www.bitcoin.org/smf/index.php?topic=1721.msg21054#msg21054 post,] to run type:<br />
<br />
"./DiabloMiner-YourOS.sh -u youruser -p yourpass" matching the user and pass set in your bitcoin.conf.<br />
<br />
<br />
To run on Windows you have to do something like:<br />
<br />
java -cp target\libs\*;target\DiabloMiner-0.0.1-SNAPSHOT.jar -Djava.library.path=target\libs\natives\windows com.diablominer.DiabloMiner.DiabloMiner -u youruser -p yourpassword<br />
==Founder==<br />
[http://www.bitcoin.org/smf/index.php?action=profile;u=1796 DiabloD3]<br />
==HomePage==<br />
[https://github.com/Diablo-D3/DiabloMiner Project Page]<br />
<br />
[http://www.bitcoin.org/smf/index.php?topic=1721.0 Project Thread]<br />
==License==<br />
[http://www.gnu.org/copyleft/gpl.html GPL]<br />
<br />
[[Category:Mining]]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=DiabloMiner&diff=2658DiabloMiner2011-01-23T21:21:09Z<p>Unthinkingbit: Created page with "DiabloMiner is a Java GPU bitcoin miner that uses the OpenCL framework to quickly perform the hashing computations. Works on current Nvidia drivers and ATI Stream SDK 2.1. ==Don..."</p>
<hr />
<div>DiabloMiner is a Java GPU bitcoin miner that uses the OpenCL framework to quickly perform the hashing computations. Works on current Nvidia drivers and ATI Stream SDK 2.1.<br />
==Donation==<br />
Bitcoin address: 1DbeWKCxnVCt3sRaSAmZLoboqr8pVyFzP1<br />
==Download==<br />
[http://adterrasperaspera.com/images/DiabloMiner.zip Newest Binary.]<br />
<br />
[https://github.com/Diablo-D3/DiabloMiner/archives/master Source.]<br />
==Examples==<br />
From the introductory [http://www.bitcoin.org/smf/index.php?topic=1721.msg21054#msg21054 post,] to run type:<br />
<br />
"./DiabloMiner-YourOS.sh -u youruser -p yourpass" matching the user and pass set in your bitcoin.conf.<br />
<br />
<br />
To run on Windows you have to do something like:<br />
<br />
java -cp target\libs\*;target\DiabloMiner-0.0.1-SNAPSHOT.jar -Djava.library.path=target\libs\natives\windows com.diablominer.DiabloMiner.DiabloMiner -u youruser -p yourpassword<br />
==Founder==<br />
[http://www.bitcoin.org/smf/index.php?action=profile;u=1796 DiabloD3]<br />
==HomePage==<br />
[https://github.com/Diablo-D3/DiabloMiner Project Page]<br />
<br />
[http://www.bitcoin.org/smf/index.php?topic=1721.0 Project Thread]<br />
==License==<br />
[http://www.gnu.org/copyleft/gpl.html GPL]</div>Unthinkingbithttps://tests.bitcoin.it/w/index.php?title=OpenCL_miner&diff=2657OpenCL miner2011-01-23T21:16:43Z<p>Unthinkingbit: </p>
<hr />
<div>{{stub}}<br />
An '''OpenCL miner''' is a bitcoin miner that uses the [http://en.wikipedia.org/wiki/OpenCL OpenCL framework] to perform the hashing computations. When used with a modern GPU, this can produce hash rates orders of magnitude higher than what can be achieved with a CPU. Hashing on a GPU requires an OpenCL or CUDA compatible graphics card.<br />
<br />
The first open source OpenCL bitcoin miner was created by m0mchil<ref>[http://www.bitcoin.org/smf/index.php?topic=1334.0 m0mchil's announcement on the forum]</ref>. Subsequently the Java [[DiabloMiner]] based on m0mchil's was created by Diablo-D3.<ref>[http://www.bitcoin.org/smf/index.php?topic=1721.0 Diablo's announcement on the forum]</ref><br />
<br />
See the [[Mining Hardware Comparison]] page for detailed statistics on the hash rates that can be achieved with various hardware.<br />
<br />
==External Links==<br />
<br />
* m0mchill's [http://github.com/m0mchil/poclbm poclbm] open source project.<br />
<br />
==References==<br />
<references/><br />
<br />
[[Category:Mining]]</div>Unthinkingbit