Wallet won't sync - Beginners Guide to Bitcoin, Blockchain ...

Is there any way to make an ABC node sync faster? Anything really?

This has been so painful to use that I'm likely killing it altogether. It has been for days on and off and I already had blockchain data from bitcoin core Qt stored up to mid 2017.
Now it is stuck syncing with the network in jan 2016 with an ETA of 11 days.
Anything to make this faster? Do -rescan -reindex do anything useful at all?
EDIT: I'm not a really "upgrade" guy so I never upgrade unless I need to, so I was still using windows 8.0 with a lot of "capped" stuff to improve security and speed. It so happens that one of the problems there was that windows 8.0 was NOT ending properly the client when closing it and I needed to manually kill it (also RAM handling was poorer). After some research I decided to upgrade to windows 10 (still possible to get for free even if you had a windows 8.0 license like mine for when it comes installed in your machine already - send a msg here if you want to know the best procedure).
Windows 10 properly handles ending the process, cleaning up RAM, and calling it back. Also, it seems to consume less resources to run ABC client. Just some hints here: windows 10 now uses PowerShell, not the old command shell, but PowShell does not accept commands such as -rescan -reindex as a default, so if you need to run a batch or start the client (or anything else like compiling c/c++ libraries, etc, etc) call cmd.exe instead, not worth the pain to read power shell documentation to execute pedestrian commands.
submitted by rdar1999 to btc [link] [comments]

Lore v2 QT on Raspberry Pi

To follow up to mindphuk's excellent piece on building the headless client on Raspberry Pi (https://www.reddit.com/blackcoin/comments/6gkjrw/wip_blackpi_a_stake_device_based_on_raspberry/), I thought if anyone was interested I'd show you how to get the full QT version running on the Pi on the Jessie with Pixel desktop. This works and has been soak tested for several days now on a standard Raspberry Pi 3. I have since added some coins and it stakes a handful of times a day.
Running staking Lore clients paves the way for some of the future use cases of BLK utilising the Bitcoin 0.12 (and newer) core tech, including colored coins. So I'm going to leave this one going indefinitely to kickstart the number of Lore clients staking. It's certainly not mandatory but it will be good in the longer term to have a nice distribution of Lore staking clients.
The cross-compile which lets you create binaries for multiple platforms didn't work for the QT version on the Pi, so there is more to do than just running the binary unfortunately, as below. There are folks working on some much cleaner solutions than this for the Pi, with a custom front end, and where you won't have to do any mucking about. That is coming soon. In the meantime, if you enjoy a fiddle with such things, here's how to get this QT client working on your Pi.
These instructions assume you are starting from scratch with a completely blank OS.
Download Jessie with Pixel from: http://downloads.raspberrypi.org/raspbian/images/raspbian-2017-07-05/2017-07-05-raspbian-jessie.zip
Note they have since (August 2017) released a version called 'Stretch' which does not work with this guide. I'll see if I can come up with something new for that at some point and link to it here when I have. In the meantime the guide should work with the Jessie image above.
Unzip the file and extract the .img file to burn it onto Fresh SD card to boot from (to be safe, use 16GB or larger), using a tool like win32diskimager or Etcher.
Assuming you have keyboard/mouse and monitor plugged into your pi, boot it up and the Jessie Desktop will show.
Before we do anything else, you should increase the default swap size on the pi, as compiling certain libraries can exhaust the RAM and get stuck otherwise. To do this, launch a Terminal window and type:
sudo nano /etc/dphys-swapfile 
and Change the CONF_SWAPSIZE from 100 to:
Exit nano with control + x to write out the file.
Then, run the following to restart the swapfile manager:
sudo /etc/init.d/dphys-swapfile stop sudo /etc/init.d/dphys-swapfile start 
Now, launch the browser and download the Lore 2.12 binaries for ARM here: https://mega.nz/#!k2InxZhb!iaLhUPreA7LZqZ-Az-0StRBUshSJ82XjldPsvhGBBH4 (Version with fee fix from 6 September 2017)
(If you prefer to compile it yourself instead, it is possible by following the instructions in the original article by Mindphuk just taking into account this is the newer version of the Lore client than when that was written (https://github.com/janko33bd/bitcoin/releases) and the versions of Boost and the Berkeley DB need to be the same as below.)
Double click the zip and extract the Lore binary files. Yes, at the moment they are all called 'bitcoin', not 'blackcoin' or 'Lore' - this is because the code derives from a recent bitcoin core implementation so this has not yet been updated. You can place these wherever you like.
In the Terminal window, change directory to where you put the binaries, e.g.:
cd Downloads/lore-raspberrypi-armv7-jessie-pixel chmod +x * 
That marks the binaries as executable.
Now, we need the Boost libraries installed for any of the Lore binaries to work. The project was done with Boost 1.62.0. Unfortunately the Jessie repository only goes up to 1.55, so we need to download and build 1.62 manually on the device.
wget https://sourceforge.net/projects/boost/files/boost/1.62.0/boost_1_62_0.tar.gz/download tar -xvzf download cd boost_1_62_0 sudo ./bootstrap.sh sudo ./b2 install 
(This will take almost 2 hours. Have a nice cup of tea and a sit down.)
When I came to run the binaries, I found they couldn't find Boost. Running this command fixes that:
sudo ldconfig 
Now we are going to install the packages which aren't already included in the default OS installation which the binaries need in order to run:
sudo apt-get install qrencode libprotobuf-dev libevent-pthreads-2.0-5 
Now we need to install the Berkeley Database version 6.2.23. This is the version Lore v2 uses. Bitcoin still uses 4.8 which is 10 years old! This doesn't take too long.
wget http://download.oracle.com/berkeley-db/db-6.2.23.tar.gz tar -xvzf db-6.2.23.tar.gz cd db-6.2.23/build_unix ../dist/configure --prefix=/usr --enable-compat185 --enable-dbm --disable-static --enable-cxx 
I find this next section of the Berkeley instructions worked better just switching to root, which can be fudged by running sudo su before the rest:
sudo su make make docdir=/usshare/doc/db-6.2.23 install chown -v -R root:root /usbin/db_* /usinclude/db{,_185,_cxx}.h /uslib/libdb*.{so,la} /usshare/doc/db-6.2.23 
Now we're going to go up a couple of directories to where the binaries were:
cd ../.. 
Then run the client!
And there you have it. Should hopefully end up looking a bit like this: http://imgur.com/a/eEHGa
Using the Bootstrap can save a while syncing. Download it at: https://www.reddit.com/blackcoin/comments/6b3imq/blackcoin_bootstrapdat_up_to_block_1631800
Place the bootstrap.dat file into the ~/.lore directory.
Run ./bitcoin-qt again, it will say 'Importing Blocks' rather than 'Synchronising with Network'. My pi sync'ed fully in about 5-6 hours.
If you want peace of mind that Lore will always start on bootup into the Jessie w/Pixel desktop (i.e. after a power cycle), then you need to create a .desktop file in the following place.
sudo nano ~/.config/autostart/Lore.desktop 
And in it, enter the following (tailoring the Exec line below to the whereabouts of your bitcoin-qt file):
[Desktop Entry] Name=Blackcoin Lore Comment=Mining without the waste Exec=/home/pi/Downloads/lore-raspberrypi-armv7-jessie-pixel/bitcoin-qt Type=Application Encoding=UTF-8 Terminal=false Categories=None; 
Power usage and payback time
After a good while leaving it going by itself, the CPU load averages got down to almost zero, all of the time. Idling, the Pi uses a bit less than 3 watts. This means it would take two weeks to use one 1Kw/h of electricity.
If you pay e.g. 12.5 cents a unit, that's what you'd expect this to cost to run in a fortnight. That's around $0.25 a month or $3 a year. Green and cheap and helping to secure the BLK network. I paid for the year's worth of electricity in 2 days staking with 25k BLK. Makes mining look silly, huh? ;)
Securing your Pi
With staking, your wallet needs to be unlocked and as such, the keys to your wallet are on the device. In a clean and newly installed environment as described above, and if you don't allow others to use your device and there is no other software or nasties running on it, there is no real cause for concern. However, there are some basic security precautions you can take.
Firstly, if you have enabled SSH and are playing with your pi across your LAN (or worse, the Internet), you should immediately change the password for the default 'pi' user (which is preconfigured to be 'raspberry'). Simply log in as normal, then type:
You'll be prompted to enter the old and the new passwords.
Security by default
Your Pi is likely, by default, to not be exposed to incoming connections from the outside world because your router is likely generating a private address range for your LAN (192.168.x.x or 10.0.x.x or 172.x.x.x) which means all incoming connections are effectively blocked at the router anyway unless you set up a 'port forward' record to allow packets arriving on certain ports to be forwarded to a specific internal IP address.
As for accessing your Pi across the internet, if you have set up a port forward, this likely has security ramifications. Even basic old fashioned protocols have proven in recent times to have uncaught flaws, so it's always advisable to lock down your device as much as possible, and even if you only plan to access the Pi over your LAN, install a firewall to configure this. I used one called ufw, because it's literally an uncomplicated firewall.
sudo apt-get install ufw sudo ufw allow from to any port 22 sudo ufw --force enable 
This allows just port 22 (SSH) to be open on the Pi to any device on my LAN's subnet (192.168.0.x). You can change the above to a single IP address if paranoid, or add several lines, if you want to lock it down to your LAN and a specific external static IP address (e.g. a VPN service you use). To find out what subnet your router uses, just type:
and you'll see on the interface you are using (either hard wired or wifi) the 192.168 or 10. or 172. prefix. Change the above rule so it matches the first two octets correctly (e.g. if you're on a 10.0. address).
You may already use VNC to access your Pi's desktop across your LAN, this uses port 5900. Add a line like above to lock it down to an internal address. It's not a good idea to expose this port to the wider world because those connections are not encrypted and potentially could be subjected to a MITM attack.
You can query the status of the firewall like this:
ufw status 
And of course, try connecting remotely once you change the rules to see what works. You should consult the official documentation for further options: https://help.ubuntu.com/community/UFW
Back up & Recovery
There are again many ways to tackle this so I'll just speak about my basic precautions in this regard. Don't take it as a be-all-and-end-all!
The wallet.dat file is the key file (literally) containing all the private/public keys and transactions. This can be found in:
You can navigate there using Jessie w/Pixel's own file manager or in a terminal window (cd ~/.lore). You can copy this file or, if you'd rather keep a plain text file of all your public and private keys, use the 'dumpwallet' command in the console. In Lore, go to Help > Debug Window > Console and type 'dumpwallet myfilename' where myfilename is the file you want it to spit out with all your keys in it. This file will end up in the same place you launch bitcoin-qt from.
The instructions earlier on, when running Lore for the first time intentionally left out encrypting your wallet.dat file because in order for the wallet to stake upon startup, it needs to have a decrypted key already. This isn't perfect, but after a power cycle, it would never stake unless you left it decrypted. So the best practice here is as soon as the wallet.dat file has left your device, i.e. you copy it to a USB stick for example, put it in an encrypted folder or drive (or both).
In Windows, one way is to use Bitlocker drive encryption for the entire drive. You should follow the instructions here to encrypt your flash drive before your wallet.dat is on there, and don't forget the password!!
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself: http://www.belightsoft.com/products/conceale   There are almost certainly free packages with similar functionality, I have just used that one for years.
Either way, if you want to just make sure your USB drive is encrypted, you can do so in one-click in Finder before you put the sensitive files on it: http://lifehacker.com/encrypt-a-usb-stick-in-finder-with-a-click-1594798016
Note that these disk encryption methods may mean having to access the USB stick on a PC or Mac in order to retrieve the files in the event of a disaster. Be aware this may mean exposing them to more security issues if your computer is in any way compromised or someone nefarious has access to your computer. There are more 'manual' ways of backing up and recovering, such as literally writing down private/public key pairs which this guide doesn't go into, but may suit you better if paranoid about your setup.
The wallet.dat file has everything in it you need to recover your wallet, or if you used 'dumpwallet', the file you saved out has all the keys.
Wallet.dat method: Install Lore as normal then replace any auto-generated wallet.dat in ~/.lore directory with your backup. If a lot of time has elapsed and many transactions have occurred since your backup, launch lore with:
./bitcoin-qt -rescan 
And if that doesn't do the job, do a full reindex of the blockchain:
./bitcoin-qt -reindex 
If you used the dumpwallet command, install Lore then place the file containing all the keys that you saved out in the same directory as bitcoin-qt. In Lore, go to Help > Debug Window > Console and type 'importwallet myfilename' where myfilename is that file containing all the keys. The wallet should automatically rescan for transactions at that point and you should be good to go.
There are a million ways to do effective security and disaster recovery, but I hope this shows you a couple of basic precautionary ways. There are discussions about better ways to stake without compromising too much security which are happening all the time and developments in this regard will happen in time.
In the meantime, feel free to comment with your best practices.
submitted by patcrypt to blackcoin [link] [comments]

Transaction with a very small fee stuck in mempool

I am using a recent version of the bitcoin core client on Windows. Bitcoin-qt.exe v0.15.0.1.
Accidentally sent a transaction with a small fee. This was about a week ago. It is stuck in the mempool, no miner wants to confirm it because of the low fee.
Last night, I tried to clear it off by starting up the bitcoin-qt.exe client with the --zapwallettxes=1 parameter. After rescannining for about 2 hours, it removed the unconfirmed transaction. I then closed the client and started it again without the zapwallettxes parameter, and everything looked good. However, this morning, I see the unconfirmed transaction came back.... Maybe since it is now in the mempool, it gets rebroadcasted to the clients?
How can I permanently remove the transaction?
I read that it may be possible to solve this by starting up the client with the zapwallettxes parameter and after the rescan completes, to transfer the full wallet balance to another fresh wallet, with a high fee.
submitted by unk1911 to Bitcoin [link] [comments]

Guide: How to redeem and sell bitcoin diamond (bcd) from ledger nano s (Segwit)

I spent two days to figure this out but I think I know how to solve this, just currently stuck and need your help! I had btc stored on a nano s segwit wallet before the fork.
Bitcoin diamond was forked from bitcoin on block #495866 (nov 24 2017) and launched the mainnet Jan 5 2018 (I think). There is currently very little information about this project and very little support on exchanges, wallets and mining. http://btcd.io
The only light wallet currently have a splitting tool is Bither for Android but they do not support Segwit. If you had your btc in a segwit wallet before the fork you can't use this method.
Otherwise follow this: https://steemit.com/bitcoin/@tiberiu/how-i-claimed-sbtc-super-bitcoin-from-my-paper-wallet Or this: https://www.reddit.com/BitcoinMarkets/comments/7oekie/guide_how_to_redeem_and_sell_all_bitcoin_fork/
You get 10 bcd for every btc and current price is 0.001 btc. That means you get $160/ forked btc which is 1% free money. Is it worth it? For me it is. You can use same method for both SBTC and BCD. Other methods can be used for BTX, BCX and BFX but have to wait for me. Need segwit support in Coinomi and/or Bither.
In my BCD case it was a bit more complicated but hopefully possible.
  1. Move btc from ledger nano to somewhere save
  2. Download the BIP39 converter (standalone version). Unplug your internet and run the html: https://github.com/iancoleman/bip39
  3. Enter your ledger 24 word mnemonic. Select BIP49 derivation path. Find your btc address that contained btc right before block 495866, copy private key. Use a block explorer: https://blockchain.info
  4. Find the tx ID that sent those btc and verify in bcd explorer if you have any bcd before you continue (click on the actual address will not work for some reason, shows empty). My tx had 3000 confirmations. http://explorer.btcd.io
  5. Now the complicated part =) You have to build bitcoin diamond core app from source because it doesn't exist yet: https://github.com/eveybcd/BitcoinDiamond
  6. I built it for windows x64 using this guide (by cloning bitcoin diamond from github instead of bitcoin when you come to that step). Took 1h.: https://github.com/bitcoin/bitcoin/blob/mastedoc/build-windows.md
  7. Actually quite cool you can run Ubuntu on Windows 10! You can build for 32 bit as well but not when you have installed dependencies for x64. The last step will copy the binaries to your windows folder: "make install DESTDIR=/mnt/c/workspace/bitcoindiamond"
  8. Run bitcoindiamond-qt in windows and let it sync with network. Took me 12h with fiber connection.
  9. Go to help and open console. If your wallet is encrypted, decrypt for 10min using: "walletpassphrase your-wallet-passphrase 600".
  10. Import old btc address as watch-only to check bcd balance. True means it will rescan the blockchain. Rescan took 1h with a decent PC (no SSD):
  11. If you see your BCD balance, now Import your btc private key into the watch-only address. No need to rescan again, thus "false".:
Ok here is where I'm stuck. I can see my balance but it's not spendable. I also tried to import private key directly (with sync) with empty core wallet but balance is still zero. It does not pick up the transaction! Anyone know how to solve this?
Rest of the guide when this is solved:
submitted by Joohansson to CryptoCurrency [link] [comments]

Re-sending a double-spent transaction?

So I recently found some bitcoin on a bitcoin-qt wallet that I hadn't used in a while. My plan was to send all of it to my coinbase account for now since I won't have access to this computer in a couple months. I first sent it using a stupidly low fee (something like 20 sat/byte) and it of course never got confirmed, so I abandoned the transaction using bitcoin-qt. I sent it again a couple days ago using a fee of about 400 sat/byte, but it still has 0 confirmations and https://bitcoinfees.earn.com/ suggests that I should really be using 630 sat/byte, at the time of this post at least.
The problem is that all of my transactions in bitcoin-qt were greyed out and I couldn't abandon the stuck one, so I ran the client again using -zapwallettxes, which cleared all of my transactions but now it says I have a balance of 0.00000000BTC!
Here is a link to the transaction. It mentions that it is a double-spent transaction, but I don't really care since I am trying to send all of the BTC from the wallet, so it can't exactly take more BTC than is actually there. I'm running a rescan of the blockchain right now but that obviously takes a while. Any tips on how to unstick this transaction?
submitted by Gabe_20 to Bitcoin [link] [comments]

Bircoins sent from wallet, not appearing in blockchain (almost 48hours)

Hello, I made some transactions from my Bitcoin QT wallet, like usual (I do it weekly) but the last transactions seems to be stucked. It is not showing in blockchain, I paid the fee, it shows in the otugoing transactions with ? mark and it is not appeared and no confirmations yet. it was happened on the 10th february, so like 2 days ago. Any idea? I updated the wallet, made a rescan and it seems it is not resolving the problem.
Any idea? Thanks!
submitted by grabbertdi to Bitcoin [link] [comments]

How to recover funds from a currupted bitcoin wallet Why the blocksize limit keeps BITCOIN free and decentralized Bitcoin Q&A: Orphaned blocks and stuck transactions How to run Bitcoin Core on external Hard Drive How to Recover & Reload a BITCOIN WALLET 0.8.1-beta Win 7

They are only needed for re-scanning missing transactions in a wallet, reorganizing to a different part of the chain, and serving the block ... This should only exist when bitcoin-qt is currently running. It contains information (BDB state) relating to your wallet. peers.dat Unknown whether this contains personally identifiable data. It may be safely deleted. Other files and folders (blocks ... After starting, Armory started scanning the transaction history. For some reason it stopped at 96% and when it hung there for a while I noticed that python was taking up 100% of its CPU thread. That's now already for 5-10 minutes, so I think it will last indefinitely, I will restart in a second if it persists. Bitcoin is a distributed, worldwide, decentralized digital money. Bitcoins are issued and managed without any central authority whatsoever: there is no government, company, or bank in charge of Bitcoin. You might be interested in Bitcoin if you like cryptography, distributed peer-to-peer systems, or economics. A large percentage of Bitcoin enthusiasts are libertarians, though people of all ... Open your wallet folder, right click wallet-qt.exe file and click on create shortcut. Now right click the shortcut file, click on properties and edit the field labeled as target. By default it should be something like this: "C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" Think of your Litecoin Wallet as a Bank. If the doors on the bank are left wide open then anyone can steal your coins. To secure your Litecoin Wallet completely you simply need to carry out the following 1) First of all make sure that your Wallet is encrypted. You can do this by clicking on Settings - Encrypt Wallet a

[index] [43772] [37769] [34750] [46879] [36772] [46187] [38024] [5095] [35577] [50003]

How to recover funds from a currupted bitcoin wallet

How To Double Spend Your Stuck Bitcoin Transaction with FSS-RBF - Duration: 8:22. m1xolyd1an 88,888 views. 8:22. How to Recover Missing Bitcoins / Not Showing Up While Wallet Syncing - Duration: ... Nur mit diesen Client (bitcoin-qt.exe) und TOR bist du recht sicher. Alles andere kann man ja ziemlich leicht im Netz sehen. Alles andere kann man ja ziemlich leicht im Netz sehen. Wo kauf ich ... How to recover data from a hard drive (stuck heads: buzzing, clicking, etc) - Duration: 10:28. ... How to Set Up a Bitcoin Mining Rig w/ BITMAIN ANTMINER U2 & CGMiner - Duration: 16:19. Rasim ... BITCOIN PRICE , BITCOIN FUTURE in doubt http://youtu.be/eO-yrpQpIT8 What is NAMECOIN BITCOIN'S First Fork http://youtu.be/oBkhPhu3_B4 Test Scanning Stainless... bitcoin p=np forum.bitcoin. pl bitcoin qt bitcoin qr code bitcoin qt synchronizing with network bitcoin qt wallet location bitcoin qt import wallet bitcoin qt synchronizing with network slow ...