Kevacoin source tree
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Wladimir J. van der Laan 1e92b27540
Merge pull request #6553
9 years ago
..
gitian-building
release-notes
Doxyfile
README.md
README_osx.txt
README_windows.txt
REST-interface.md
assets-attribution.md
bips.md
bitcoin_logo_doxygen.png
build-osx.md
build-unix.md
developer-notes.md
dnsseed-policy.md
files.md
gitian-building.md
init.md
multiwallet-qt.md
release-notes.md
release-process.md
shared-libraries.md
tor.md
translation_process.md
translation_strings_policy.md
travis-ci.txt
unit-tests.md

README.md

Bitcoin Core 0.11.99

Setup

Bitcoin Core is the original Bitcoin client and it builds the backbone of the network. However, it downloads and stores the entire history of Bitcoin transactions (which is currently several GBs); depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more.

Running

The following are some helpful notes on how to run Bitcoin on your native platform.

Unix

You need the Qt4 run-time libraries to run Bitcoin-Qt. On Debian or Ubuntu:

sudo apt-get install libqtgui4

Unpack the files into a directory and run:

  • bin/32/bitcoin-qt (GUI, 32-bit) or bin/32/bitcoind (headless, 32-bit)
  • bin/64/bitcoin-qt (GUI, 64-bit) or bin/64/bitcoind (headless, 64-bit)

Windows

Unpack the files into a directory, and then run bitcoin-qt.exe.

OSX

Drag Bitcoin-Qt to your applications folder, and then run Bitcoin-Qt.

Need Help?

Building

The following are developer notes on how to build Bitcoin on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.

Development

The Bitcoin repo's root README contains relevant information on the development process and automated testing.

Resources

Miscellaneous

License

Distributed under the MIT software license. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com), and UPnP software written by Thomas Bernard.