Bitcoin Sign up or log in to customize your list._ Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top up vote 1 down vote favorite I installed bitcoind on my ubuntu server awhile ago.How do I go about uninstalling it properly?Do i just delete the ~/.bitcoin folder?bitcoind linux up vote 1 down vote If you installed with a deb package, you can use apt-get to remove it: sudo apt-get remove bitcoind Did you find this question interesting?Try our newsletter Sign up for our newsletter and get our top new questions delivered to your inbox ().up vote 0 down vote That will remove your wallet.dat, bitcoin.conf and all the blockchain info, but you will also want to remove the bitcoin directory which was also downloaded and if you added bitcoind to your path you'l want to remove that as well.Your Answer Sign up or log in Sign up using Google Sign up using Email and Password Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for?Browse other questions tagged bitcoind linux or ask your own question.Ask Ubuntu Sign up or log in to customize your list._ Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top up vote 1 down vote favorite I recently installed Bitcoin Core on my Ubuntu 16.04 system.It's taking up too much disk space.How do I completely uninstall the software and remove data to free up my hard drive space?uninstall bitcoin up vote 1 down vote Remove bitcoin: sudo apt-get remove bitcoind Alternatively, you could just disable bitcoind from starting at startup: sudo systemctl disable bitcoind Remove extra files: If you remove your .bitcoin directory, you are removing your wallets/addresses and access to any BTC in those wallets, as well as the blockchain history.When you run bitcoind, it typically creates a .bitcoin directory in the home directory of the running user.

Depending on your setup, this could be a user named bitcoin, or be your user.rm -rf /path/to/.bitcoind/ If you're not sure where this path is, you could run the following commands to help find it: sudo updatedb sudo locate .bitcoind More specifically, the blocks take up a lot of space and are found in .bitcoind/blocks/.bitcoin mining with teslaBrowse other questions tagged uninstall bitcoin or ask your own question.đào bitcoin bằng cpuThe Classic project maintains a package repository at launchpad.net/~bitcoinclassic/+archive/ubuntu/bitcoinclassic/ if you have other Bitcoin repositories or clients installed, you should remove these using the package management features.litecoin rise in priceIf you are certain you do not have any other bitcoin installed, you may skip directly ahead to the installation.

You can check if there is any bitcoin packages installed by running; If the output lists a bitcoin-qt or bitcoind package, you have some other Bitcoin software installed.If neither of these are returned in your listing, you can skip directly ahead to the installation.We will now remove the software, this will only remove the conflicting parts.The personal data, like a wallet or the blockchain-data will not be removed.Before we start, please ensure that your bitcoind or bitcoin-qt application is not running (shut it down cleanly as necessary).Then remove its package by running: Continue only if the removal of the package(s) was successful!As a next step, remove other Bitcoin software repositories, as their packages may conflict with those of Classic.For example, if you have the Bitcoin Core PPA installed previously, you can remove it as follows: Running the apt-cache policy | grep bitcoin command should now produce an empty output.You are now ready to install the Classic PPA and software packages.

The following command will install the repository information for Bitcoin Classic: If that is successful, you should update the available package information using There are two software packages which you can install: You can install either or both of these with: They can also be installed together (although only one of them can be run at a time).After installation, you should have the respective binary package installed in /usr/bin/ Prebuilt binaries are also provided in compressed tar archives (.tgz) for 32- and 64-bit Linux systems.Attempting to run the 64-bit binaries on a 32-bit machine will fail.If in doubt, you can check your Linux using If the output is x86_64 you should obtain the 64-bit version, otherwise the 32-bit version.Without going into full details, the installation steps are as follows: Download the appropriate tar archive.The "Download" link at downloads will take you to the latest release, where you should find .tar.gz files for 32- and 64 bit Linux systems.

Unpack it in a place of your choice.The software can be run from any ordinary user's folder.For example: cd /path/where/you/want/to/unpack tar xf bitcoin-1.x.y-linux64.tar.gz In the example above, x and y indicate software versions.This will create a versioned subfolder, e.g.bitcoin-1.x, containing the Classic software.Run the executable from its installation location (if necessary adapting your PATH setting) /path/where/you/unpacked/bitcoin-1.x.y/bin/bitcoin-qt The archives contain both the graphical and headless clients.The executables are contained in the bin subfolder: There are also other binaries such as the command line RPC client, bitcoin-cli.Jump to: , The data directory is the location where Bitcoin's data files are stored, including the wallet data file.Contents 1 2 3 4 5 Go to Start -> Run (or press WinKey+R) and run this: Bitcoin's data folder will open.For most users, this is the following locations: "AppData" and "Application data" are hidden by default.

You can also store Bitcoin data files in any other drive or folder.If you have already downloaded the data then you will have to move the data to the new folder.If you want to store them in D:\BitcoinData then click on "Properties" of a shortcut to bitcoin-qt.exe and add -datadir=D:\BitcoinData at the end as an example: Start Bitcoin, now you will see all the files are created in the new data directory.By default Bitcoin will put its data here: You need to do a "ls -a" to see directories that start with a dot.If that's not it, you can do a search like this: By default Bitcoin will put its data here: An overview of these is in [files.md] in the Bitcoin Core documentation.The data, index and log files are used by Oracle Berkeley DB, the embedded key/value data store that Bitcoin uses.Contains testnet versions of these files (if running with -testnet) [v0.8 and above] Contains blockchain data.[v0.8 and above] A LevelDB database with a compact representation of all currently unspent transaction outputs and some metadata about the transactions they are from.

The data here is necessary for validating new incoming blocks and transactions.It can theoretically be rebuilt from the block data (see the -reindex command line option), but this takes a rather long time.Without it, you could still theoretically do validation indeed, but it would mean a full scan through the blocks (7 GB as of may 2013) for every output being spent.[v0.8 and above] Contains "undo" data.You can see blocks as 'patches' to the chain state (they consume some unspent outputs, and produce new ones), and see the undo data as reverse patches.They are necessary for rolling back the chainstate, which is necessary in case of reorganizations.There is a torrent file that gets updated every few months that enables a much faster download of the blockchain.Once downloaded, the bootstrap.dat file can be placed in the root of the data directory, and Bitcoin Core 0.7.1 and above will automatically import it.NOTE: As of Bitcoin Core version 0.10.0 and later, the blockchain bootstrap torrent is slower than a direct download using the bitcoin P2P protocol & client.[2]

This section may be of use to you if you wish to send a friend the blockchain, avoiding them a hefty download.Other files and folders (blocks, blocks/index, chainstate) may be safely transferred/archived as they contain information pertaining only to the public blockchain.The database files in the "blocks" and "chainstate" directories are cross-platform, and can be copied between different installations.These files, known collectively as a node's "block database", represent all of the information downloaded by a node during the syncing process.In other words, if you copy installation A's block database into installation B, installation B will then have the same syncing percentage as installation A. This is usually far faster than doing the normal initial sync over again.However, when you copy someone's database in this way, you are trusting them absolutely.Bitcoin Core treats its block database files as 100% accurate and trustworthy, whereas during the normal initial sync it treats each block offered by a peer as invalid until proven otherwise.

If an attacker is able to modify your block database files, then they can do all sorts of evil things which could cause you to lose bitcoins.Therefore, you should only copy block databases from Bitcoin installations under your personal control, and only over a secure connection.Each node has a unique block database, and all of the files are highly connected.So if you copy just a few files from one installation's "blocks" or "chainstate" directories into another installation, this will almost certainly cause the second node to crash or get stuck at some random point in the future.If you want to copy a block database from one installation to another, you have to delete the old database and copy all of the files at once.Both nodes have to be shut down while copying.Only the file with the highest number in the "blocks" directory is ever written to.The earlier files will never change.Also, when these blk*.dat files are accessed, they are usually accessed in a highly sequential manner.Therefore, it's possible to symlink the "blocks" directory or some subset of the blk*.dat files individually onto a magnetic storage drive without much loss in performance (see Splitting the data directory), and if two installations start out with identical block databases (due to the copying described previously), subsequent runs of rsync will be very efficient.