Nihilo Coin is easy to use, with a great development & research team behind it who are focused on bringing advanced technology and unique features to our community, which creates a stable network for web 3.0 infrastructure. Welcome to the future....
Bitcoin-qt.exe (BitcoinCash wallet) flagged as malware by Kaspersky Antivirus.
This just happened. This software was installed months ago, signatures verified so it's from the devs... Maybe someone should notify Kaspersky of this? Unless this is a real trojan ? If it keeps getting flagged and I can't create an exception, I'll have to stop running a full node. file: D:\BitcoinCash\bitcoin-qt.exe Object name: Trojan.MSIL.Cryptos.ddoi Object type: Trojan program This is BUcash v184.108.40.206 I've posted on KAV forums, waiting to see what they have to say about this. The unfortunate thing is I've been unsuccessful at creating an exclusion in the antivirus settings, so it keeps getting flagged.
Trying to salvage some coins from 2013. Core (bitcoin-qt.exe v0.8.1-beta on Windows 8.1) is taking weeks to DL the blockchain as expected but keeps crashing now. Can I upgrade to a newer version without losing what I've gotten already (about 75% complete)?
Currently there are 134305 blocks remaining. When I start it up it works pretty smoothly for a while but then slows down. I leave it running while I'm gone but the last several days when I've come back it has crashed and gives me an I/O error, and I have to hit OK then start it back up. It does appear to be further along when I start it back up but not by a whole lot. So this has really slowed my progress. It's reindexed about 75% though, and so I don't want to start over from the beginning. The drive it is on has ~400gb of free space so that's not the issue. I have 8gb of memory, and the task manager says bitcoin is taking up about 500mb, but it's using 60-85% of my cpu at a time. If I download a newer version of core, I can just copy/paste the old wallet.dat file, right? But wouldn't it have to start downloading the entire blockchain again from the beginning? If so, is there any quicker method? While typing this, it crashed twice. It only runs for about 10 minutes. The version I have doesn't have any settings I can change. I read that there's a db size limit you can change in later versions that could help. This one does have a "debug window" with a command line console but I don't really know what to do with it. Here is a list of available commands: ￼
Trying to salvage some coins from 2013. Core (bitcoin-qt.exe v0.8.1-beta on Windows 8.1) is taking weeks to DL the blockchain as expected but keeps crashing now. Can I upgrade to a newer version without losing what I've gotten already (about 75% complete)? /r/Bitcoin
Hi guys, I'm fairly new to Bitcoins and I'm already scared that I've lost my wallet. I used bitcoin-qt.exe to create a new one, let it sync, then transferred some funds over to it. Since then, every time I try to run it, it just crashes instantly. I'm running Windows 8.1 and neither the 32-bit nor 64-bit versions of bitcoin-qt work at all. If I debug with Visual Studio 2012: it displays the following error:
Unhandled exception at 0x00B906CA in bitcoin-qt.exe: 0xC0000005: Access violation reading location 0x00000004.
I tried using Bitcoin Armory and that won't work either. Is there any alternative Bitcoin client or some method I can use to recover my wallet and its bitcoins? I am desperate for help. Thank you so much. Edit: Apparently version 0.9.3 works fine. I'm going to see if I can recover my wallet with this version. Edit: I uninstalled absolutely everything related to Bitcoin, deleted everything except my wallet, torrented bootstrap.dat, installed Bitcoin 0.10.0, and it works now, but it won't seem to recognize my wallet backup, even running with -rescan. I'll try some more. Thanks for the help though, you guys.
Batch script to create pruned block data from full block data
TLDR; Produce a pruned block directory from a full block directory without copying any extra block data I have a full node, but at times I want to run in a VM or on a RPi or something. Normally I have to clone my whole 300 GB block directory, enable pruning, then point bitcoin-qt.exe to the clone to finally arrive at a small 4 GB datadir. I found it frustrating that I was doing this 295 GB of pointless copy operations since once I enable pruning, the old blocks are discarded. I was also discouraged at the fact that .\Bitcoin\testnet3\blocks\blk00186.dat is different (by checksum) in a pruned and non-pruned directory. So I finally came up with an answer. Basically, I copy over the latest few blk*.dat and rev*.dat files, then just make empty copies of the other blk*.dat and rev*.dat files. Then once bitcoin-qt.exe launches, it discards the empty files and rewrites the few files it needs. For Windows, it looks something like this: set /a "sum=0" for /f %%I in ('dir /s /b /o:-n %full_blk%\blk*.dat') do ( set size=%%~zI set blkdat=%%~nxI set revdat=!blkdat:blk=rev! if !sum! GTR !pruned_mb! ( echo.> %pruned_blk%\!blkdat! echo.> %pruned_blk%\!revdat! ) else ( copy %full_blk%\!blkdat! %pruned_blk%\!blkdat! copy %full_blk%\!revdat! %pruned_blk%\!revdat! ) set /a "sum=!sum! -1 + !size!/(1024*1024)" ) I can stamp out a pruned blocks directory from my full blocks directory in seconds. Much easier... well for me. Here's the source, but no guarantees. Just food for thought.
I already downloaded the blockchain. How do I tell Core to use that copy?
I was previously using bitcoin-qt.exe, emulated on my Linux machine. I have lost the ability to emulate that. (I won't go into details.) I therefore downloaded the Ubuntu version of Bitcoin Core, and am about to try to install that. It is asking me where I want to download the entire 300 GB blockchain, again. I have already downloaded it. I don't have room on my computer to download a second copy of it. It's already taking up 300 GB of space on my harddrive. Do I have to delete my previous copy of the blockchain? Or can I tell Bitcoin Core where to find it, so that it doesn't have to redownload it all over again? (I am also hoping this will save time; but time is less important to me than disk space.)
Help setting up Bitcoin Core node with Tor hidden service
I am trying to run a full node with Bitcoin Core and get it running as a Tor hidden service but the steps I am following are from many sources and I feel like I have been missing steps in between, not to mention that my technical skills are fairly basic. Here's where I'm at (Windows):
I installed Bitcoin Core and downloaded the blockchain overnight, that all seems to be fine.
I downloaded the latest Tor Expert Bundle and extracted it.
There was a tutorial for making Tor run as a service that I started but the second step didn't work and I didn't find another tutorial.
I have read a lot of people saying what to add or adjust in the torrc file but the torrc file didn't exist until I created it, I found the torrc sample file but I am not sure which parts to enable to get it working right (created torrc but still empty).
I have run Tor and Bitcoin Core then selected the network setting to use separate SOCKS5 proxy to reach Tor hidden services and Bitcoin Core shows that it's connected to eight peers. There's some traffic but I am not certain that it is running properly or through Tor as a hidden service.
Can someone please tell me if I've missed something or if I've done it right then how to check that I have? Thanks! Update: Currently I have a "work-around" by running tails in a VM and running bitcoin-qt inside that. Because it's a livecd if it gets shutdown for any reason I'd have to set it up each time so I would still like to get the full node running with Tor on Windows. I am using bitcoin-qt.exe from the Windows installation of Bitcoin Core and using any combination of the network settings to get it to use Tor and it does connect to onion addresses, sometimes one or two and the remaining of the eight are normal nodes. I can't figure out how to make Bitcoin Core only connect Tor nodes instead of none or a mixture. Update 2: Instead of using the Tails in a VM workaround, I have the windows Bitcoin Core Node running properly over Tor now. I still have to wait a few days at least to see if I can get more than two incoming connections. I read in many places that port 8333 had to be opened in order to receive incoming connections but I have been assured that doesn't apply to onion nodes and that checking getnetworkinfo with bitcoin-qt console shows onion as reachable is proof. There was also an issue with Tor not working with the CookieAuth when that set was added to torrc. Simply CookieAuthFile needed to be added. I'm adding these notes in case any other windows user has trouble getting their node running with Tor. SYD4uo was a huge help and I appreciate those others that took the time to give advice. Cheers! This was also very helpful
Running a full node over private VPN. Is there a guide?
Hi, I've setup an OpenVPN server on a VPS. I am running a full node on my personal computer with only outbound connections and without inbound / incoming connections, because my ISP doesn't let me port forward any ports. I've connected to my VPN as a client, and have enabled port forwarding on it by doing so:
/etc/sysctl.conf: net.ipv4.ip_forward = 1
Despite this, I'm unable to still have incoming connections over port 8333 even after being connected over the VPN. Are there any other iptable settings to be done for Post routing and pre routing? Is there any available guide for this? Kindly help me out with this if anyone has setup one already. Note: I'm running an OpenVPN access droplet on DigitalOcean over Ubuntu. Also on my personal computer, my firewall is already configured to allow inbound and outbound traffic via port 8333 (tcp/udp) through bitcoin-qt.exe.
Understanding BIP149, redeployment of Segwit with BIP8
I recently published BIP149 and would like to take a few moments to explain the details of this proposal. BIP149 is a completely new deployment of segwit, which I propose if the current BIP9/BIP141/143/147 segwit deployment fails to lockin/activate by November 15th. BIP149 cannot be run on mainnet now, and there is code in the reference implementation to prevent it from running. It is incompatible with the current segwit deployment on purpose to remove unnecessary complications. Essentially, the idea is, if the current segwit deployment fails to activate by Nov 15th, we can release new software that has BIP149. This uses BIP8 to activate segwit by July 2018. Miners will still be able to trigger activation by 95% threshold signalling as normal. In the 8 months from November to July 2018, nodes will be able to upgrade to BIP149. If segwit is not MASF activated by July 2018, there will be enough of the economy running BIP149 that nodes can begin enforcement. What will actually happen is on the first retarget after July 4th, the BIP8 state machine will switch to LOCKED_IN status for two weeks, and then on the following retarget, ACTIVATION will occur. The rationale here is in 5 months we achieved 70% saturation of witness capable nodes, so by the time segwit timesout with all the urgency and demand people feel for segwit, we can expect them to upgrade at least as fast, if not much faster. I have spoken with a number of developers who think this is a reasonable assumption. Background, I had hoped to be able to release a BIP that can be deployed concurrently now with segwit, but, there are various technical complications in implementing it cleanly and making it easily reviewable. I had various feedback from others in previous iterations and in order to get the widest support from developers especially concerned with predictable results and thus safety, I came to the conclusion that the BIP will get the widest support by not attempting any shortcuts and by removing all complexity. I know many people want segwit now, but, I think we should just bite the bullet and do it the BIP149 way. I already made a shortcut BIP with BIP148. I will discuss the pros and cons at the end. Back to BIP149, this is a completely new redeployment with a new service bit NODE_UAWITNESS and new compact block protocol version - doing this avoids many gotchyas which I will explain below: Currently, segwit capable nodes advertize the NODE_WITNESS service bit and preferentially peer with other NODE_WITNESS nodes. Post activation, segwit-active nodes will then know who they should relay witness blocks to and who they should relay old style stripped blocks to. The assumption is if I am a NODE_WITNESS node and segwit has activated, then other NODE_WITNESS nodes will also be segwit activated. We cannot reuse NODE_WITNESS because when BIP149 activates, they would believe non-BIP149 NODE_WITNESS nodes were also active. Using a new service bit, and effectively starting a new deployment as if the previous deployment doesnt exist, is the most predictable and trouble free way to go about it. Additionally, BIP149 is compatible with existing mining software by reusing the "segwit" name and deployment chainparams (it's not possible to have two deployments with the same name, one expired and one pending/active, due to how versionbits is implemented). In short, if the current segwit deployment fails to activate, we can reuse parts to maintain compatibility, while changing the bare minimum to remove any conflicts with old nodes. It's clean, predictable and easy to review. BIP148 IS NOT BIP149 Remember BIP148 is exceptional, it's NOT what a usual UASF BIP should look like. A normal UASF if effectively activation on a predetermined date in the future (a flag day). BIP8 combines BIP9 miner signalling with a flagday if MASF does not occur. How is BIP149 different to BIP148? So BIP148 is a UASF which can be used in two ways. (a) The economy can run BIP148 and basically force miners to signal for segwit, thus activating the current segwit deployment. Or, (b) a majority of miners, 60% or so, could run it and censor other miners who do not signal segwit, thus causing the current segwit to deploy. In method (a) a chain split will occur if any miners do not upgrade, and given the fact there are always absentee miners and pool operators, this is quite likely. It's the economy vs hash power saying "if you dont signal, your blocks will not be worth anything because we will reject them". In the case of (b) you have a majority of hashpower, who could use their majority to orphan any non signalling miners. This isn't great but it's less disruptive than (a) because there is a majority hashpower definitely opted in. BIP149 on the other had does not guarantee a chain split since that could only happen if a miner deliberately takes action to manually create a segwit invalid block, which would be rejected by the economy. The incentives are different also, with BIP148 a chainsplit comes for free, regardless of if it lasts long or not. In BIP149, a miner would have to specifically take action to split and waste their money, which they could do at any time anyway. BIP149 is uncontroversial in the sense it is just a redeployment with guaranteed activation at the end, for a soft fork we are fairly sure people want and will upgrade to. The evidence is everywhere. UASFs deployed over a long time and a decent flagday are perfectly safe - all soft forks are enforced by nodes, even if activation is triggered by hashpower. Anyway, we've got 8 months from now to review and think about BIP149 - it cannot be deployed until November. If you would like to show support for BIP149, feel free to add the following to your bitcoin.conf
You can find the bitcoin.conf file here You can also just add this to a shortcut - create a shortcut (or edit the existing one you use) and add this to the end: -uacomment=UASF-SegWit-BIP149 e.g. (just add the property to the end like this): "C:\Program Files\Bitcoin\bitcoin-qt.exe" -uacomment=UASF-SegWit-BIP149 if you are using Windows. You can also just add uacomments as multiple command line/shortcut arguments like
Run a 0.14 Full-Node on RaspberryPi3 Pruned(less than 16GB SD needed)
Hi! Happy if this guide helps you. Tip if you want: 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v UPDATE 04/06/17 Add 'uacomment=UASF-SegWit-BIP148' into your bitcoin.conf if you want to signal UASF. UPDATE 03/13/17 ADDED a tl;dr; Version at the end of this Post. UPDATE 03/12/17: Just to test it - I reinstalled all on 8GB SD and it works as well. But maybe you should use at least 16GB for the beginning. Using a 128GB card for the first version was a little bit stupid - so I reinstalled everything on a 8GB SD card. Including Linux and a pruned blockchain - and it works. I used prune=550 and Jessie Lite (headless / command line) - without wallet and gui. The SD is almost full, but it works so far I also updated the whole manual a bit to make things more clear. Thank you for all your feedback! Just started my Bitcoin Node today and wanted to share the way I did it with people who are interested in running their own full node. It took some time to write everything down - hopefully correct so far. I am sure, many people around bitcoin are way more informed and educated as I am - I am the noob. So I wrote this manual to help users like me - noobs, to get started with a cheap, simple bitcoin node on raspberry pi. Have fun! I wanted to get my Raspberry Pi 3 working as a node to support the network. Actually the process of installing and running the node was more or less easy - but for Noobs (like I am) it might be a bit tricky to start the whole thing, because there are different ways. Did you - like me - think you would need +120GB on the raspi, external USB HDD to be a full node? You won't! If you have a Raspberry and you know what Bitcoin is, I guess, you are a little bit aware of linux, networks and of course bitcoin - so I won't go into detail too much. This guide is just a little helper to get a full node running on your raspberry pi. Thanks to the help of the nice people in this sub and of course the documentation by the developers, I got it working - and of course also special thanks to raspnode.com - as I followed their tutorial to start - I went some other ways here and there - so please read carefully. For the Part 2 I would suggest to have http://raspnode.com/diyBitcoin.html open and read through my manual. I split the tutorial in 2 Parts - PART ONE is about installing the client on your PC and downloading the Blockchain. PART TWO is about the setup of the raspberryPi and transferring the pruned blockchain to the pi and run it as a full node! The first thing to be aware of is: You actually need to download the whole blockchain to get this working - if you already have your bitcoin client synced on the PC / MAC great you can reuse it! Now you might think "but you said less than 16GB in the title!" Yes, but the good thing is you won't need to download it on your Raspberry, neither you need to sync it completely on your raspberry which took ages (weeks!) before. When you finished this Guide, you will just have a max. 4GB Blockchain on your Raspberry Pi - but it still is a full node! The magic word is Pruning. Maybe even a 8GB SD Card works just fine including Linux (jessie lite)! So, if you already have a full node on your PC - Great you can almost skip PART ONE - BUT have at how to Prune in PART ONE if you don't know about it. For PART TWO you'll need a Raspberry Pi 2 or 3 (I used 3) min. 8GB (works also) or better 16GB SD Card. (I used a 128GB for the first version of this manual - which is way too big)
This is the manual how to get started on you PC / MAC / Linux (I did it on Win7) Go to: https://bitcoin.org/en/download and download the core Client for your Machine (I used win64). Install it and configure it to save the Blockchaindata to the directory of your choice - so instead getting 120GB on your C drive, I would suggest to download it to another place like a USB drive. You can set this up during the install. Standard folder for the blockchain folder is "%APPDATA%\Bitcoin" on Windows. or you can do it after the install by creating a bitcoin.conf file inside your installation folder / or %APPDATA%\Bitcoin and add
to the file. Line by line. By the way here you could also just add dbcache - to use more memory to speed up the process a bit:
if you don't want to use the settings inside the program. (you can also set this inside the program under settings! If you have this inside the bitcoin.conf you will see the amount you set there from inside the program - it overrides the values) You can check inside the windows client under settings, if you can see a manual dbcache is set by having a look at the left footer area. When your dbcache value shows up, everything is fine. So the Blockchain download process will take time - maybe a few days! Depending on your machine, internet connection and HDD. The Blockchain is huge as it contains every single transaction of the past until today. You won't need to keep your PC running all the time, you can turn it off and on and it will resync automatically when you start bitcoin-qt.exe! Make sure to close the client always via "quit" - ctrl+q. After you have your bitcoin core installed, the blockchain downloaded and synced - you are ready to PRUNE! First - close the Client and let it close smoothly. After it is really closed you can follow these steps:
By pruning, your blockchain will dramatically shrink. From 120GB to just a few GB.
Be aware, that you will lose your Downloaded Blockchain as pruning will erase a big chunk of it! If you have enough space, you could of course keep the full blockchain saved somewhere on another HDD. You can prune by editing your bitcoin.conf file by adding:
I used prune=1024 - not sure where the differences are right now (min. prune=550). (for my 8GB version I used 550! I suggest to use this.) Save the bitcoind.conf file and restart your windows client. It will now clean up the Blockchain. So just the latest blocks are saved. The client should start without any problems. Maybe it takes some time to prune the blockchain data. Check if everything works normally (the client opens as usual, you can see an empty wallet) than close the client. Inside the Bitcoin Folder, you'll find two folders called:
those are the interesting folders containing the important data (now pruned) - and we will transfer those two to the raspberry later! Now you are good to start the raspi transfer explained in the next part.
Here is what I did: 1) I installed Raspian Pixel (https://www.raspberrypi.org/downloads/raspbian/) using a 128 GB SD - which is not needed because of "Pruning" - I think a 16GB card might work, too! (You can also install Raspian Jessie Lite - which saves you even more space, as it runs headless - only command line) (Updated: It is better to use Jessie Lite to save a lot of space - when you are fine with only command line) 2) I followed partly this tutorial to get everything running and setup:
Please have a look at it - I have copied the Headlines in capitals to let you know what I did, and what I skipped. On Tutorial Page: Start with RASPBIAN (OPTIONAL) CONFIG OPTIONS. Set You RasPi up including "EDITING FILES" to save your Layout at the tutorial page and come back here. I skipped the CONFIGURE USB AND SET AUTOMOUNT process, as we are going to use PRUNING to reduce the 120GB to a tiny filesize - so USB Devices are not needed here! It was necessary to ENLARGE SWAP FILE to install bitcoin core - otherwise it didn't went through which ended in a frozen raspi. So have a close look by following the raspnode tutorial at: ENLARGE SWAP FILE. I have my raspi running via cable to router - but you can also WiFi setup everything described under NETWORKING ON THE RASPBERRY PI. Now comes the interesting part: Follow the steps at DOWNLOADING BITCOIN CORE DEPENDENCIES - they work fine for 0.14.0 too. Git should be on Board already when you installed Pixel - otherwise you would need to install it.
sudo apt-get install git -y (only jessy lite)
I skipped the next command lines - as I don't use bitcoin-qt wallet. If you want to use it as wallet - do the step.
as I don't need the wallet functionality. I didn't need to use "MAKE" which saves you maybe up to 2.5 hours. instead you can just go ahead with:
sudo make install
(If I am wrong in doing so - please let me know) The install takes some time - and just a heads up: when it gets stuck somewhere - just redo the installation process - it took three times to went through - stuck at some processing. After the installation took place you can finally get your Raspberry Pi Node running in no time! To test if the the installation went through - you can just start bitcoind using:
than check if everything is working so far:
after a few seconds you should see version: etc... if not, something went wrong. Try to redo the steps in the raspnode tutorial. (don't give up if it failed - retry! Ask your questions here) IMPORTANT: you need to stop bitcoin on your raspberry now!
If you don't need an external USB Drive - what I hope - as we are going to use pruning just go ahead and skip the USB part and create a file inside (or follow the raspnode tutorial on how to setup the USB drive):
cd .bitcoin sudo nano bitcoin.conf
and enter the exact same pruning size you have used on your Desktop Machine to prune. I used 1024 but the minimum is 550. (used 550 for the 8GB SD card on PC and Raspberry)
That's it for the raspi. update: To signal UASF enter in a new line:
Now you have to transfer the two folders CHAINSTATE and BLOCKS from your PC bitcoind directory to your raspberry. I am using a program called "WINSCP" - it is free and easy to use: https://winscp.net/eng/download.php We need this to transfer the files to the Raspberry pi. Pretty sure you can also do it via SSH - but I am the noob. So let's keep it simple. Open Winscp and put in the IP Address of your Raspberry Pi, User and Password (same as in SSH) You should now see the directories on your Raspberry Pi. There is a folder called
enter it and you will see the two folders
blocks & chainstate
you can delete them on the raspberry as they have some data from your previous test inside. Make sure you can also see the bitcoin.conf file in that directory, which needs to contain the exact same prune line, like the one on your desktop machine. If not, make sure to edit it via SSH. The line "datadir=l:\yourfolder" is obviously not needed in the Raspberry bitcoin.conf file. Now grab the two folders CHAINSTATE and BLOCKS from your PC and copy them to your .bitcoind folder. I also copied banlist.dat, fee_estimation.dat, mempool.dat and peers.dat to the folder - not really knowing if needed! Not needed. The whole copy process might take some minutes (against some weeks in the old way). After copying is finished, you can now start bitcoind on the Raspberry.
the & symbol let you still use the command line while the process is running btw. The process - if succesfull - will take some time to finish.
Will give you some informations what is going on right now. When you can see, that it is checking the blocks, this is good! If you get an error - double check - if you have the correct prune size (same as on desktop machine) - in bitcoin.conf and that this file is inside .bitcoin on RaspberryPi. It took me some time, to find my mistakes. Congrats! You are almost a part of the network! To make your node now a fullnode, you will need to go to your router (often 192.168.1.1) and enable portforwarding for your raspberry pi - and open ports 8333 - that's it! You can now go to: https://bitnodes.21.co/nodes/ scroll down to "JOIN THE NETWORK" and check check if your node IP is connected! It will show up as soon as the blocks are checked and the raspi is running. Well done! Now you are running a full node, with a small Blockchain and got it working in Minutes, not weeks! I really hope, my little tutorial worked for you and your are part of the Node network now. If you have problems or I made a mistake in this helper tut, just let me know and I will try to make it better. Have fun and NODL! the noob tl;dr; (if you are a real noob start with the non-tl;dr version!) tl;dr; PART ONE 1) Download & install / setup bitcoincore @ https://bitcoin.org/de/download 2) change dbcache to something smaller than your memory and download the whole Blockchain (120GB). 3) create a file called bitcoin.conf put the line prune=550 (or higher) in to activate pruning on win inside %appData%/bitcoin 4) Open ports 8333 on your Router to make this a full node with a smaller Blockchain. You are running a full node on your PC. tl;dr; PART TWO 1) Install jessie lite and the needed dependencies on your SDCard - Raspberry ( >git clone -b 0.14 https://github.com/bitcoin/bitcoin.git )
see tutorial for more info.
2) create a file called bitcoin.conf inside .bitcoin and add the same prune=Number you had on your PC. 3) transfer the pruned folders BLOCKS and CHAINSTATE to the Raspberry Folder .bitcoin 4)Start "bitcoind &" 5) let everything sync 6) Make sure you have port 8333 opened on your router. You are running a full node on your Raspberry with a super small Blockchain (I put all on a 8GB SDcard) Tip if you want : 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v updated 03/12 - will update more, soon. updated 03/12.2 - I updated the whole process a bit and also added some improvements. updated 03/14/ Added a tl;dr version at the end.
How do you import a Bitcoin Core (QT)-made wallet.dat file into another wallet?
So I have a wallet.dat made a while ago and wanted to check what was in it, problem is it was made in the bitcoin core QT client, which I can't even load up because it occasionally freezes and usually won't even sync up, at an absurdly slow rate. When I replace that wallet file into the default data directory, and start bitcoin-qt.exe with the -rescan command, it just starts but no addresses show up in my wallet file and i noticed the wallet.dat file size changes when the bitcoin core client starts up, seemingly modifying something to make it slightly bigger, don't know why. How do I check this wallet.dat? I tried importing it into the latest electrum 3.2.3 wallet and it won't accept it.
Guide: How to run a full node on Windows when you have monthly bandwidth limits
I only get 200gb a month with my current ISP package, and so abandoned any hope of ever running a full node. But it turns out that my ISP doesn't count my usage during certain off-peak hours (in my case between 2:00 am and 8:00 am). Also upload bandwidth isn't counted at all during any time. So I did a little research and would like to share what I came up with to all of you out there with a similar predicament. 1) Check your usage page on your ISPs website It was only after looking at my current usage gauge that it was explained when and what actually counts towards my bandwidth limit. To my surprise, they stop counts between the wee hours of the night (which makes sense). 2) If you indeed have 'off-peak' allowances, download Bitcoin Core Make sure it's version 0.15 or higher. 3) Open up port 8333 I'm sure many of you know how to port-forward. If not, google those words along with your router model and there should be explanations readily available. 4) Give bitcoin-qt a test run and verify that you're visible to everyone Start downloading the first bit of 2009 blocks just to be sure everything will run fine later that night. While you're doing this, it's a good idea to make sure your node is visible by testing it here. 5) Run Windows Task Scheduler and set bitcoin to run at the beginning of your off-peak hours It was my first time using the Task Scheduler, but it was pretty intuitive to use for this basic use. You want to set up the basic task of running bitcoin-qt.exe at (e.g. 2:00 am) and choosing to repeat this task every 1 day. If you aren't going to be awake when your off-peak hours end, you may want to set the advanced setting of "Stopping this task if it runs longer than 4-8 hours". I realize that ideally you want to run your node for 6+ hours, but you can change this once you've downloaded the initial blockchain. And that's how to do it! I'll be trying this for the first time tonight and hope to become one of a minority of nodes run in Canada, even though I'll likely only be verifying transactions on the other side of the globe. Comments on how to improve this method are welcome.
Testnet.BitcoinReserve.ch is looking for a few good bug hunters. Offering $75 in BTC for fatal bugs and a sliding scale all the way down to $2 for minor typos. The first round of testing (see /BitcoinReserve) paid out over $350 to various testers. Bitcoin Reserve allows deposit and withdrawal of Bitcoin, conversion to/from dollars and payments to other members in USD or BTC. The system is currently running on Testnet3. I am the final and only arbiter of bounty payouts. The first person to find and report a particular bug will be paid a bounty. Subsequent reports on the same issue are helpful but will be paid a partial bounty only if they add worthwhile information. Be sure to include the URL and any supporting information with your bug reports: Bugs must be reproducible or otherwise independently observable (i.e. reviewing server logs). Larger bounties will be paid to the address you send me through a reddit personal message, smaller bounties will be paid through changetip. If bounty payouts end up exceeding 3 BTC, the contest will be paused as we examine what the hell is going on. Again, the website is https://testnet.bitcoinreserve.ch, Happy Hunting! Notes:
New BitcoinReserve accounts will be pre-loaded with 1 Testnet BTC you may do anything you like with (while supplies last). I am not a Windows user but a shortcut something like this should get you going with the green testnet Bitcoin-QT icon rather than the usual orange one: "C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -testnet Mycelium has a nice Testnet app for Android.
BitcoinReserve's email server is rather new, some email services have been sending our emails to spam folders. Please check there if communications are not appearing in your inbox as expected.
Bitcoin Withdrawals: Our current security strategy is to process these manually. There will be a delay between when you submit an external withdrawal and when it hits the blockchain.
BitcoinReserve supports a Shopping Cart API. Bounty payouts are increased 33% for bugs found over the SOAP interface (to compensate for the extra effort involved). The API is available only to Business members and setup is in the WebClient API section. Java and PHP libraries are available on GitHub. Examples for the PHP library are available here.
Is there anyway to force a refresh of one specific blknnnnn.dat file?
I have a corrupt blk00417.dat file and any read from it causes an issue. Is there a way to force a reload of this file without having to download the whole blockchain again? Thanks. EDIT: I meant 'is there any way' not 'is there anyway' of course. Just thought I'd point out my own typo in case it was annoying anyone else ;-) UPDATE: I'm currently running "C:\Program Files\Bitcoin\bitcoin-qt.exe" -checkblocks=0 -checklevel=0 to verify block locations in the block index. If that fails (I assume it will at the same place) I'll try a reindex and report back. UPDATE 2: This has finished - 5 days later. -checkblocks=0 and -checklevel=0 didn't take that long. Reindex started off fairly quickly, verifying what as in my blknnnnn.dat file then when it got to the block before the one I had the error in it had to then download that and every subsequent block.
Bitcoin Core (formerly Bitcoin-Qt) is the third Bitcoin client, developed by Wladimir van der Laan based on the original reference code by Satoshi Nakamoto. It has been bundled with bitcoind since version 0.5. Bitcoin-Qt has been rebranded to Bitcoin Core since version 0.9.0 .. Bitcoin Core can be used as a desktop client for regular payments or as a server utility for merchants and other ... Install Bitcoin-Qt Since version 0.9, Bitcoin-Qt was renamed to Bitcoin Core t o reduce confusion between Bitcoin-the-network and Bitcoin-the-software. Bitcoin Core is a full Bitcoin client. It is a thick client, meaning it requires the full blockchain (explained below) on local disk to operate and expose blockchain back to the network to help relay and verify transactions. Keep a copy (sync ... Recommended: Identify bitcoin-qt.exe related errors Important: Some malware camouflages itself as bitcoin-qt.exe, particularly when located in the C:\Windows or C:\Windows\System32 folder. Therefore, you should check the bitcoin-qt.exe process on your PC to see if it is a threat. We recommend Security Task Manager for verifying your computer's security. Bitcoin-qt.exe Datei Info. Der Prozess Bitcoin Core (GUI node for Bitcoin) oder Bitcoin Gold (GUI node for Bitcoin) gehört zur Software Bitcoin Core oder Bitcoin Gold der Firma Bitcoin.. Charakteristik: bitcoin-qt.exe gehört nicht zum Windows Betriebssystem und macht eher wenig Probleme. Bitcoin-qt.exe befindet sich in einem Unterordner von "C:\Programme" - für gewöhnlich C:\Programme ... ./bitcoin-qt Command-line arguments . These commands are accurate as of Bitcoin Core version v0.14.0. Command Description -? Print this help message and exit -version : Print version and exit -alertnotify=<cmd> Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message) -blocknotify=<cmd> Execute command when the best block changes (%s in ...
bitcoin qt generate coins bitcoin qr code generator php bitcoin generator v5.1.0 activation code bitcoin generator download bitcoin generator download no survey bitcoin generator download 2017 ... start "" "b3coin-qt.exe" -datadir=.\ -listen=0 It simply changes the storage data directory to the current one. Usually, the qt wallet stores its files in this single location for each type of ... bitcoin key database bitcoin key finder bitcoin key length bitcoin key algorithm bitcoin api key bitcoin alert key bitcoin alert key compromised bitcoin-all-key-generator bitcoin adder key bitcoin ... In this tutorial we are going to get our private keys from the bitcoin core wallet. This only works when you created the bitcoin address in the same wallet. ... Ever want to learn how to program bitcoin? This channel shows you the nuts and bolts of programming actual bitcoin transactions.