Always gets 'Corrupted block database detected' with DB ...

How to increase dbcache in Bitcoin Core on mac? /r/Bitcoin

How to increase dbcache in Bitcoin Core on mac? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Bitcoin Core 0.14.1: The default `-dbcache` has also been changed in this release to 450MiB.

Always good news for big blockers when Core increases their default CONOP definition.
submitted by pointbiz to btc [link] [comments]

Bitcoin Core 0.14.1: The default `-dbcache` has also been changed in this release to 450MiB. /r/btc

Bitcoin Core 0.14.1: The default `-dbcache` has also been changed in this release to 450MiB. /btc submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Bitcoin Node Download >3 weeks

I’m downloading a node from bitcoin dot org and it took a couple days to get to 50%. Now, assuming the blocks are getting full, it’s taking 3 weeks to finish supposedly. I’m downloading on a new laptop via high speed internet to an external hard drive of 1TB.
Edit: I’m not interested in pruning blocks btw.
Is there something I’m doing wrong here?
submitted by thevenano to Bitcoin [link] [comments]

Bitcoin Fullnode Install Guide for Dummies ;-)

Bitcoin Fullnode Install Guide for Dummies ;-)
Feel free to stop at Level 0 or Level 1, which is fine. More advanced configs are offered to those with more tech savvy. This guide, obviously assumes a Windows 10 install, but other OSes work fine, just find a different guide. BTW, the "For Dummies" is a callback to a set of "tech" books in the 90's intended to be as easy as possible. It is in jest and not intended to insult the reader. Finally, if you dislike the formatting, a well formatted copy can be found here
There is a fairly small subset of Bitcoin users that run a full node. I think the idea of running a full node has gotten a bad rap over the years since there is so much talk about running on a Raspberry Pi, or getting zippy SSDs. Although all of this can be fun, it is often not really required at all. Here are some ways to run a full node starting with the very simple. I'll get into more complex configs, but these are all optional.

Tech Skill Level: 0 (the basics)

  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
In many cases, thats it. If your running a new machine with a fairly good internet connection, 8 or 9 hours will be enough to complete the "Initial Block Download" (IBD). This may fill up your drive a bit, but again, on most new machines, 300 GB of space isn't that hard to come by.

Tech Skill Level: 1 (encrypted wallet)

One thing we left out in the level-0 exercise is encrypting your wallet. It's easy enough to do well, but a bit more difficult to do right. The main challenge is that humans generate really poor passwords. If you want a good password, the best way is to use something called "diceware". Basically, you just grab 4 or 5 dice and each throw of the dice represents a certain word on a special list. The throw {1,4,5,3,1} for example would be the word camping on the EFF-diceware-wordlist. So you repeat this a few times until you have a list of 8 or so words which becomes the passphrase you use to encrypt your wallet. Write it down, it is always hard to remember at first. So at level-1 your list becomes:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Choose Encrypt Wallet from the Settings menu
  5. Enter your 8 word (or so) passphrase generated using the Diceware method

Wallet Encryption Dialog

Tech Skill Level: 2 (enable pruning if needed)

Though I said "300 GB of space isn't hard to come by", some times it actually is. If space is an issue, a simple way to fix it is to tell bitcoin to simple take less space. This is called "pruning" and can take that number from 300 GB down to below 5 GB. If you can't find 5 GB, then you'll have to read ahead to level-4 to add USB storage. But the good news is, enabling pruning is pretty easy, we just add another step to our working list:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Choose Options from the Settings menu
  6. Choose Prune block storage to: and select the max size for the blocks to use
  7. Exit and restart the bitcoin application for the changes to take effect

Pruning Dialog
Note, even setting this to 1 GB will still leave you with about a 4.5 GB install. The blocks take up a lot of space, but the chainstate and other folders eat up at least 3.5 GB and they can't be pruned. Also, be aware, to disable pruning requires you to perform the entire IBD again. While pruned some other functions my be disabled as well, so just know that pruning does limit some functionality.

Tech Skill Level: 3 (verify the installer)

Although this is arguably something that should be done at level-0, some find the intricacies of comparing hash (thumbprint) values to be tedious and beyond the scope of a beginner. You will find these types of hash compares suggested quite often as a way to prevent running tainted programs. Programs are often tainted by bad disk or network performance, but most often, taint is malicious code inserted by viruses or malware. This is a way to guard yourself against those types of attacks.
What I cover here is a very basic comparison on the certificate, but a more thorough verification advised by mosts uses a program called Gpg4Win, and is beyond the scope of this beginners guide. But regardless, most users should strive to do this minimum level of validation.
  1. Download Bitcoin Core
  2. Launch the downloaded installer
  3. When prompted "Do you want to allow..." click Show more details
  4. In the details section select Show information about the publisher's certificate
  5. In the certificate window select the Details tab
  6. In the Details tab Subject should start with "CN = Bitcoin Core Code Signing Association"
  7. Ensure Thumbprint in Details reads ea27d3cefb3eb715ed214176a5d027e01ba1ee86
  8. If the checks pass, click OK to exit the certificate window and Yes to allow the installer to run.
  9. Launch the installed "Bitcoin Core" app and let it run overnight
  10. Do the wallet encryption steps here if you wish
  11. Do the optional pruning steps here if you wish

Certification Validation Windows
Note: The certificate used to sign the current Bitcoin installer is only valid from March 2020 to March 2021. After that point the thumbprint on the certificate will change. This is by design and intentional. If your reading this post after March 2021, then it is understood that the thumbprint has changed.

Tech Skill Level: 4 (use secondary storage)

We glossed over the "new machine with fairly good internet" part. Truth be known many people do not have fairly new machines, and find the IBD to take longer than the "over night" best wishes. For most people the slowdown is the disk access when calculating what is called chainstate. This requires fast random reads and writes to the disk. If you have an SSD disk, this will be no problem, but if you have a non-SSD "spinning" disk, random writes are always slow. Though an SSD will speed things up, they are pricey, so a nice middle ground may be a simple high-end USB key drive. You can get some with 10 to 15 MB/s random writes for $20 on Amazon. This is usually a order of magnitude faster than a "spinning" disk. And with pruning (see level-2), a small USB drive should be fine.
Once you decide on a drive, the tricky part will be to enable external storage. It requires editing a configuration file and adding a line. First, we want to create a directory on the key drive. You will need to determine the drive letter of your USB key drive. For the sake of this example, we will assume it is D:, but you must determine this yourself and correct the example. Once you know the drive letter, create a blank folder on the drive called Bitcoin. So for this example, creating Bitcoin on drive D: will create the path D:\Bitcoin. Once done, assuming that D: is your drive, here are the new steps including the edit of the configuration file:
  1. Download Bitcoin Core
  2. Launch the installer, verify it, then run it
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Do the optional pruning steps here if you wish
  6. Launch "Notepad" by typing "Notepad.exe" in the windows search bar then click Open
  7. Type the line datadir=D:\Bitcoin (depending on your drive letter) in the blank file
  8. Choose Save from the File menu in notepad
  9. Type %APPDATA%\Bitcoin\bitcoin.conf (note the percent signs) in the File name box
  10. Select All Files from the Save as type dropdown
  11. Click the Save button and overwrite the file if prompted
  12. Exit and restart the bitcoin application for the changes to take effect

Save As Dialog
Now that you've reached this level of technical expertise, there are many new configuration options that you can begin to modify if you wish. Most configuration data is contained in the bitcoin.conf file and learning how to maintain it is a key step for a node operator.

Tech Skill Level: 5 (all other customizations)

Here's a short list of various things you can ADD to your bitcoin.conf file. You generally just add a new line for each configuration settings.
  • addresstype=bech32
  • changetype=bech32
The addresstype / changetype allows your wallet to use the native-segwit (bech32) format. This is the most efficient and inexpensive way to spend bitcoin, and is a recommended configuration. The default uses something called p2sh-segwit which is more compatible with older wallets, but more expensive to spend.
  • minrelaytxfee=0.00000011
Changing the minrelaytxfee setting allows you to help propagate lower fee transactions. It will require more memory but TXN memory is capped at 300 MB by default anyways, so if you have enough memory, it is a good setting to choose.
  • dbcache=2048
The dbcache setting controls how many MB of memory the program will use for the chainstate database. Since this is a key bottleneck in the IBD, setting this value high (2048 MB) will greatly speed up the IBD, assuming you have the memory to spare
  • blocksdir=C:\Bitcoin
  • datadir=D:\Bitcoin
In level-4 we discussed moving the datadir to a fast external storage, but the majority of the space used for bitcoin is the blocks directory (blocksdir). Although you should always use for fastest storage for datadir, you are free to use slow storage for blocksdir. So if you only want to consume a small amount of your SSD (assumed D:) then you can keep your blocks on your slow "spinning" drive.
  • upnp=1
One of the harder challenges you may face running a node, is to get incoming connections. If you are lucky, you may find that your firewall and network HW support the uPnP protocol. If they do, this setting will allow bitcoin to configure uPnP to allow incoming connections to your node. Other methods exist to make your node reachable, but they are well beyond the scope of this guide.
submitted by brianddk to Bitcoin [link] [comments]

Bitcoin Core Synching does not inspire confidence.

Decided to sync the chain.
Bitcoin Core starts to freeze as soon as it reached 2015 blocks. It would get stuck on a given block for half an hour.
I tried to change the db cache from the UI settings panel.
Boom. UI becomes unresponsive. I killed the process.
Now its been 10 minutes. On the splash screen..
Reloading blocks. It says 100%... I have been waiting for 10 minutes at 100% !!!!!!!!!
So i write this post.
submitted by Mordan to Bitcoin [link] [comments]

Full node sync speed

I'm syncing a full node on a Raspberry pi 4 with 8GB memory, external disk drive (not ssd), broadband internet. It's going extremely slow--estimated time about 4 years.
Google has turned up all kinds of advice like setting:
dbcache=4096 (setting aside half my ram)
blocksonly=1
banscore=10
listen=0
par=-1
When I run top, I see bitcoin-qt is only using about 12% of the CPU. When it boots and is loading the block index, I see that go up to 100+%. So for whatever reason, it's not fully utilizing the CPU on the machine while processing blocks.
I tested my internet connection and have 56Mbps down, 6Mbps up.
My only theory is that the external hard drive is being the bottleneck. Is there anything else to do, or should I order a SSD?
submitted by non-moose to Bitcoin [link] [comments]

Test

Test
There is a fairly small subset of Bitcoin users that run a full node. I think the idea of running a full node has gotten a bad rap over the years since there is so much talk about running on a Raspberry Pi, or getting zippy SSDs. Although all of this can be fun, it is often not really required at all. Here are some ways to run a full node starting with the very simple. I'll get into more complex configs, but these are all optional.

Tech Skill Level: 0 (the basics)

  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
In many cases, thats it. If your running a new machine with a fairly good internet connection, 8 or 9 hours will be enough to complete the "Initial Block Download" (IBD). This may fill up your drive a bit, but again, on most new machines, 300 GB of space isn't that hard to come by.

Tech Skill Level: 1 (encrypted wallet)

One thing we left out in the level-0 exercise is encrypting your wallet. It's easy enough to do well, but a bit more difficult to do right. The main challenge is that humans generate really poor passwords. If you want a good password, the best way is to use something called "diceware". Basically, you just grab 4 or 5 dice and each throw of the dice represents a certain word on a special list. The throw {1,4,5,3,1} for example would be the word camping on the EFF-diceware-wordlist. So you repeat this a few times until you have a list of 8 or so words which becomes the passphrase you use to encrypt your wallet. Write it down, it is always hard to remember at first. So at level-1 your list becomes:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Choose Encrypt Wallet from the Settings Menu
  5. Enter your 8 word (or so) passphrase generated using the Diceware method

Wallet Encryption Dialog

Tech Skill Level: 2 (enable pruning if needed)

Though I said "300 GB of space isn't hard to come by", some times it actually is. If space is an issue, a simple way to fix it is to tell bitcoin to simple take less space. This is called "pruning" and can take that number from 300 GB down to below 5 GB. If you can't find 5 GB, then you'll have to read ahead to level-3 to add USB storage. But the good news is, enabling pruning is pretty easy, we just add another step to our working list:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Choose Options from the Settings Menu
  6. Choose Prune block storage to: and select the max size for the blocks to use
  7. Exit and restart the bitcoin application for the changes to take effect

Pruning Dialog
Note, even setting this to 1 GB will still leave you with about a 4.5 GB install. The blocks take up a lot of space, but the chainstate and other folders eat up at least 3.5 GB and they can't be pruned. Also, be aware, to disable pruning requires you to perform the entire IBD again. While pruned some other functions my be disabled as well, so just know that pruning does limit some functionality.

Tech Skill Level: 3 (verify the installer)

Although this is arguably something that should be done at level-0, some find the intricacies of comparing hash (thumbprint) values to be tedious and beyond the scope of a beginner. You will find these types of hash compares suggested quite often as a way to prevent running tainted programs. Programs are often tainted by bad disk or network performance, but most often, taint is malicious code inserted by viruses or malware. This is a way to guard yourself against those types of attacks. What I cover here is a very basic comparison on the certificate, but a more thorough comparison advised by mosts uses a program called Gpg4Win, and is beyond the scope of this beginners guide. But regardless, most users should strive to do this minimum level of validation.
  1. Download Bitcoin Core
  2. Launch the downloaded installer
  3. When prompted "Do you want to allow..." click Show more details
  4. In the details section select Show information about the publisher's certificate
  5. In the certificate window select the Details tab
  6. In the Details tab Subject should start with "CN = Bitcoin Core Code Signing Association"
  7. Also ensure Thumbprint reads ea27d3cefb3eb715ed214176a5d027e01ba1ee86
  8. If the checks pass, click OK to exit the certificate window and Yes to allow the installer to run.
  9. Launch the installed "Bitcoin Core" app and let it run overnight
  10. Do the wallet encryption steps here if you wish
  11. Do the optional pruning steps here if you wish

Certification Validation Windows
Note: The certificate used to sign the current Bitcoin installer is only valid from March 2020 to March 2021. After that point the thumbprint on the certificate will change. This is by design and intentional. If your reading this post after March 2021, then it is understood that the thumbprint has changed.

Tech Skill Level: 4 (use secondary storage)

We glossed over the "new machine with fairly good internet" part. Truth me known many people do not have fairly new machines, and find the IBD to take longer than the "over night" best wishes. For most people the slowdown is the disk access when calculating what is called chainstate. This requires fast random reads and writes to the disk. If you have an SSD disk, this will be no problem, but if you have a non-SSD "spinning" disk, random writes are always slow. Though an SSD will speed things up, they are pricey, so a nice middle ground may be a simple high-end USB key drive. You can get some with 10 to 15 MB/s random writes which is usually a order of magnitude faster than a "spinning" disk. And with pruning (see level-2), a small USB drive should be fine.
Once you decide on a drive, the tricky part will be to enable external storage. It requires editing a configuration file and adding a few lines. The configuration file needs to be in both the default directory, and USB key drive, but before we do that, we want to create a directory on the key drive. You will need to determine the drive letter of your USB key drive. For the sake of this example, we will assume it is D:, but you must determine this yourself and correct the example. Once you know the drive letter, create a blank folder on the drive called Bitcoin. So for this example, creating Bitcoin on drive D: will create the path D:\Bitcoin. Once done, assuming that D: is your drive, here are the steps to edit the two configuration files:
  1. Download Bitcoin Core
  2. Launch the installer, verify it, then run it
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Do the optional pruning steps here if you wish
  6. Launch "Notepad" by typing "Notepad.exe" in the windows search bar then click Open
  7. Type the line datadir=D:\Bitcoin (depending on your drive letter) in the blank file
  8. Choose Save from the File menu in notepad
  9. Type %APPDATA%\Bitcoin\bitcoin.conf (note the percent signs) in the File name box
  10. Select All Files from the Save as type dropdown
  11. Click the Save button and overwrite the file if prompted
  12. Exit and restart the bitcoin application for the changes to take effect

Save As Dialog
Now that you've reached this level of technical expertise, there are many new configuration options that you can begin to modify if you wish. Most configuration data is contained in the bitcoin.conf file and learning how to maintain it is a key step for a node operator.

Tech Skill Level: 5 (all other customizations)

Here's a short list of various things you can ADD to your bitcoin.conf file. You generally just add a new line for each configuration settings.
  • addresstype=bech32
  • changetype=bech32
The addresstype / changetype allows your wallet to use the native-segwit (bech32) format. This is the most efficient and inexpensive way to spend bitcoin, and is a recommended configuration. The default uses something called p2sh-segwit which is more compatible with older wallets, but more expensive to spend.
  • minrelaytxfee=0.00000011
Changing the minrelaytxfee setting allows you to help propagate lower fee transactions. It will require more memory but TXN memory is capped at 300 MB by default anyways, so if you have enough memory, it is a good setting to choose.
  • dbcache=2048
The dbcache setting controls how many MB of memory the program will use for the chainstate database. Since this is a key bottleneck in the IBD, setting this value high (2048 MB) will greatly speed up the IBD, assuming you have the memory to spare
  • blocksdir=C:\Bitcoin
  • datadir=D:\Bitcoin
In level-4 we discussed moving the datadir to a fast external storage, but the majority of the space used for bitcoin is the blocks directory (blocksdir). Although you should always use for fastest storage for datadir, you are free to use slow storage for blocksdir. So if you only want to consume a small amount of your SSD (assumed D:) then you can keep your blocks on your slow "spinning" drive.
  • upnp=1
One of the harder challenges you may face running a node, is to get incoming connections. If you are lucky, you may find that your firewall and network HW support the uPnP protocol. If they do, this setting will allow bitcoin to configure uPnP to allow incoming connections to your node.
submitted by brianddk to brianddk [link] [comments]

Running a Bitcoin node on a $11.99 SBC

Running a Bitcoin node on a $11.99 SBC
Just wanted to let you guys know that I'm successfully running a (pruned) Bitcoin node + TOR on a $11.99 single board computer (Rock Pi S).
The SBC contains a Rockchip RK3308 Quad A35 64bit processor, 512MB RAM, RJ45 Ethernet and USB2 port and I'm using a 64GB SDCard. It runs a version of Armbian (410MB free). There's a new version available that even gives you 480MB RAM, but I'm waiting for Bitcoin Core 0.19 before upgrading.
To speed things up I decided to run Bitcoin Core on a more powerful device to sync the whole blockchain to an external HDD. After that I made a copy and ran it in pruned mode to end up with the last 5GB of the blockchain. I copied the data to the SD card and ran it on the Rock Pi S. After verifying all blocks it runs very smoothly. Uptime at the moment is 15 days.
I guess you could run a full node as well if you put in a 512GB SDcard.
The Rock Pi S was sold out, but if anybody is interested, they started selling a new batch of Rock Pi S v1.2 from today.
Screenshot of resources being used
Bitcoin Core info
Around 1.5 GB is being transferred every day
---
Some links and a short How to for people that want to give it a try:
  1. This is the place where I bought the Rock Pi S.
  2. Here you find more information about Armbian on the Rock Pi S. Flash it to your SDCard. Follow these instructions.
  3. Disable ZRAM swap on Armbian. If you don't do this eventually Bitcoin Core will crash. nano /etc/default/armbian-zram-config ENABLED=false
  4. Enable SWAP on Armbian sudo fallocate -l 1G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile sudo swapon --show sudo cp /etc/fstab /etc/fstab.bak echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
  5. Set up UFW Firewall sudo ufw default deny incoming sudo ufw default allow outgoing sudo ufw allow ssh # we want to allow ssh connections or else we won’t be able to login. sudo ufw allow 8333 # port 8333 is used for bitcoin nodes sudo ufw allow 9051 # port 9051 is used for tor sudo ufw logging on sudo ufw enable sudo ufw status
  6. Add user Satoshi so you don't run the Bitcoin Core as root sudo adduser satoshi --home /home/satoshi --disabled-login sudo passwd satoshi # change passwd sudo usermod -aG sudo satoshi # add user to sudo group
  7. Download (ARM64 version) and install Bitcoin Core Daemon
  8. Download and install TOR (optional). I followed two guides. This one and this one.
  9. Create a bitcoin.conf config file in the .bitcoin directory. Mine looks like this: daemon=1 prune=5000 dbcache=300 maxmempool=250 onlynet=onion proxy=127.0.0.1:9050 bind=127.0.0.1 #Add seed nodes seednode=wxvp2d4rspn7tqyu.onion seednode=bk5ejfe56xakvtkk.onion seednode=bpdlwholl7rnkrkw.onion seednode=hhiv5pnxenvbf4am.onion seednode=4iuf2zac6aq3ndrb.onion seednode=nkf5e6b7pl4jfd4a.onion seednode=xqzfakpeuvrobvpj.onion seednode=tsyvzsqwa2kkf6b2.onion #And/or add some nodes addnode=gyn2vguc35viks2b.onion addnode=kvd44sw7skb5folw.onion addnode=nkf5e6b7pl4jfd4a.onion addnode=yu7sezmixhmyljn4.onion addnode=3ffk7iumtx3cegbi.onion addnode=3nmbbakinewlgdln.onion addnode=4j77gihpokxu2kj4.onion addnode=5at7sq5nm76xijkd.onion addnode=77mx2jsxaoyesz2p.onion addnode=7g7j54btiaxhtsiy.onion ddnode=a6obdgzn67l7exu3.onion
  10. Start Bitcoin Daemon with the command bitcoind -listenonion
Please note that I'm not a professional. So if anything above is not 100% correct, let me know and I will change it, but this is my setup at the moment.
submitted by haste18 to Bitcoin [link] [comments]

Mentor Monday, June 03, 2019: Ask all your bitcoin questions!

Ask (and answer!) away! Here are the general rules:
And don't forget to check out /BitcoinBeginners
You can sort by new to see the latest questions that may not be answered yet.
submitted by rBitcoinMod to Bitcoin [link] [comments]

Why my Bitcoin Core is using 60-70% of CPU when a few days ago was like 30%?

Why my Bitcoin Core is using 60-70% of CPU when a few days ago was like 30%?
Is something happening? My Bitcoin Core fullnode increased form 30% to 60-70% of CPU usage also on network and disk i/o.
Why is that?

https://preview.redd.it/dq4dv7keolq21.png?width=3258&format=png&auto=webp&s=06fd35a9982986ef714bdf17886fa003b7dcfb91
submitted by ivanulb to Bitcoin [link] [comments]

No inbound connections on my bitcoin full node with TOR

update: it's ok now, it only required some time. Also, looking at debug.log it won't show anything about inbound connections as I thought, it must be used `bitcoin-cli getpeerinfo` in order to get all the connections info (inbound + outbound)
Can someone connect to my node? u3ob433qu3ebkmsu.onion:8333
I'm behind a CG-NAT so I thought to use TOR to overcame it but still I have outbound connections but no inbound.
$ bitcoin-cli getnetworkinfo
{ "version": 180000, "subversion": "/Satoshi:0.18.0/", "protocolversion": 70015, "localservices": "000000000000040c", "localrelay": true, "timeoffset": 0, "networkactive": true, "connections": 10, "networks": [ { "name": "ipv4", "limited": true, "reachable": false, "proxy": "127.0.0.1:9050", "proxy_randomize_credentials": true }, { "name": "ipv6", "limited": true, "reachable": false, "proxy": "127.0.0.1:9050", "proxy_randomize_credentials": true }, { "name": "onion", "limited": false, "reachable": true, "proxy": "127.0.0.1:9050", "proxy_randomize_credentials": true } ], "relayfee": 0.00001000, "incrementalfee": 0.00001000, "localaddresses": [ { "address": "u3ob433qu3ebkmsu.onion", "port": 8333, "score": 4 } ], "warnings": "" } 
bitcoin.conf
server=1 daemon=1 # RPC rpcuser=***** rpcpassword=******* # TOR onlynet=onion proxy=127.0.0.1:9050 bind=127.0.0.1 dnsseed=0 dns=0 addnode=nkf5e6b7pl4jfd4a.onion addnode=yu7sezmixhmyljn4.onion # Raspberry Pi optimizations dbcache=100 maxorphantx=10 maxmempool=50 maxconnections=40 maxuploadtarget=5000 prune=6000 
submitted by LiL0u to Bitcoin [link] [comments]

Bitcoin Core 0.18.1 not connecting to peers after 60%+ sync

Hi, I am syncing Bitcoin Core 0.18.1 and initial sync it was pretty fast, "Progress increase per hour ~7%" after it gets to sync blocks from Jan 2018, is barely connecting to any peers, and if is connected to some peers download is like too slow, and it dissconnects to them sometimes is connected to 0 peers., and increased dbcache to 900MB.
Is there any nodes list so I can try and connect using console, or do you have any suggestion how to speed up syncing?
my internet speed connection 30Mbps,
PC:CPU: [[email protected]](mailto:[email protected]);RAM:8GB;HDD:500GB
https://imgur.com/a/gA1ffiT

EDIT:
problem solved by increasing dbcache to 4000MB, now the verification is going so fast, interesting how community with 1m+ members no one mentions dbcache is so important.

thanks
submitted by satoshi_nakamoto__ to Bitcoin [link] [comments]

Bitcoin node

I am downloading a full bitcoin node and after 5 days I’m at 63% but it seems to be taking even longer now. Is this normal? I know my internet connection isn’t the quickest 10-12mps and am using an old laptop i5 with 5gb ram.Any help much appreciated
submitted by Rico2095 to Bitcoin [link] [comments]

Please send me your debug.log files from the BSV and BCH stress tests

I'd like to do some analysis of block propagation and block validation performance during the stress test, and I need some data. Can you give me yours?
Specifically, I need ~/.bitcoin/debug.log files from as many different nodes as possible. II will be analyzing both BSV and BCH blockchains.
Just sending me a link to your debug.log file is sufficient. But if you want to help me out a little more, I would appreciate it if you can rename the files so that they include your node's IP address or another unique identifier of your choice, like so:
debug-85.230.89.116.log meta-85.230.89.116.txt 
or
debug-jtoomim-moseslake-busv.log meta-jtoomim-moseslake-bu.txt 
The meta files are for any human-readable information you want to include about your nodes, like
  1. CPU type
  2. RAM
  3. SSD? HDD?
  4. Location
  5. Bandwidth
  6. VPS or dedicated
  7. dbcache setting
  8. Whether ntpd or another clock sync method was correctly configured during the test
  9. IP address (if you're willing to share it publicly)
To check your system clock, you can use timedatectl status (Ubuntu) or ntpdate -q pool.ntp.org (most linux distros). My analysis depends on relatively accurate timestamps, so this is by far the most useful piece of information for me.
If you have any other data that you've collected, such as CPU usage statistics or bandwidth monitoring data, feel free to give me a link for that as well.
If you want to not post any of this publicly, you may email me at jATtoomDOTim and tell me which (meta-)data you want me to not repeat without permission.
If anyone else wants to look through this data, let me know and I will put it all in a public repository somewhere.
The intent is to do an analysis similar to the one I did for the Sep 1st stress test. I believe rinexc managed to log some stratum header information from SVPool, and we also saw 6 orphaned blocks from SVPool alone, plus quite a few from other pools, so I think there's going to be some interesting stuff to find here. I also have an analysis of an incomplete, early dataset here.
If your debug.log files are very large and you don't have a good way to get them to me, please message or email me with your ssh pubkey (ssh-keygen -t rsa; cat ~/.ssh/id_rsa.pub) and the file size, and I'll give you instructions on how to upload it to one of my servers.
submitted by jtoomim to btc [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.3.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.3.0.0, April 17, 2018) from:
 
https://www.bitcoinunlimited.info/download
 
This release is compatible with the Bitcoin Cash planned protocol upgrade that will take place on May 15th
 
The main changes of this release are:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.3.0.0.md
 
Ubuntu PPA is in the process of being updated.
submitted by s1ckpig to btc [link] [comments]

Guide to running bitcoind on a Raspberry Pi 4 (4gb ram) on an external hard drive

I have seen a lot of guides online but for a few reasons I thought it'd be good to share how I set up my full node (with relatively few headaches) and less than $150.

Stuff to get

  1. Raspberry Pi 4 (4gb ram is essential!) - $55
  2. Power cable for the raspberry pi - $10
  3. Case for the raspberry pi - $5 (optional, looks good and makes it easier to store)
  4. microHDMI to HDMI cable (needed to view desktop of raspberry pi) - $10
  5. SD Card, at least 8GB - ~$10+ (PS: you may also need a converter to read/write from your PC to the SD card).
  6. External hard drive, ideally at least a 1TB - $50+

Setup the Raspberry pi

  1. Download NOOBS and unzip it to SD card, and insert the SD card into the Raspberry Pi.
  2. Insert the SD card into the Raspberry Pi, and place the Raspberry Pi into its case. Connect the relevant cables, and plug in the power to the Raspberry Pi.
  3. Follow the instructions on screen to get Raspian up and running.

Configuring the External Hard Drive

  1. Turn off automount
  2. Configure the raspberry pi to mount the external hard drive where you want it. See this page on how to configure external hard drives for Raspberry Pis.

Download and configure bitcoin-core

  1. Go to bitcoin.org and download bitcoin-core.
  2. Follow the instructions here and install bitcoin-core.
  3. Create a directory called .bitcoin from the home directory.
  4. Create a file called bitcoin.conf in ~/.bitcoin. Add the following settings to it to ensure that you can process historical transactions:

server=1 txindex=1 rpcuser= rpcpassword= datadir= dbcache=2500 

Run bitcoind

  1. From the command line, run bitcoind -daemon
  2. Now you can run bitcoin-cli -getinfo or tail /debug.log to get info on how bitcoind is doing.
That should do it. Assuming a solid internet connection, you should be up and running relatively quickly (less than a day). If you need help, feel free to ask questions below. I'd be happy to help.
submitted by AdvancedStock3 to BlockchainDataScience [link] [comments]

Please set up your nodes to collect data for the stress test tomorrow.

Please make sure you have NTP or timesyncd installed and active, or another form of clock synchronization, and please enable debug=bench and do anything else you can think of to collect data on node performance.
The stress test is expected to be pretty big. The expected transaction throughput rate on this one is something like 250 tx/sec, which is likely to saturate ABC's net_processing code. It will be informative if we can collect some data on where exactly in the code the bottlenecks are. If you know how to compile from source, it would be great to compile bitcoind with profile symbols enabled (export CXXFLAGS="-pg -O2", I think, followed by "./bitcoind -daemon=0" -- profiling data won't be collected in daemon mode). Also, information on whether the UTXO cache and disk activity is the bottleneck will be helpful. Does dbcache=8192 help? If you have a ton of RAM, does cat ~/.bitcoin/chainstate/* >/dev/null help? (That would cache the DB at the OS level. Still uses leveldb, but no disk.) Do you see high disk tps with iostat? High iowait %?
Unfortunately, I'm extremely busy right now and won't have the time I wish I had to devote to this project, so if anybody else who has time who can make specific suggestions on how to implement the things above, that would be appreciated.
The thread for config options on the first stress test is here. Also, there's my writeup of the Sep 1st stress test results.
If any of you are running BSV nodes, please set those up for data logging too.
submitted by jtoomim to btc [link] [comments]

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]

How long needs a raspberry pi3+ to sync from 0 to full? I know because I did: Its 19 Days

So I got a Raspberry pi 3+ and a Samsung MU-PA500B SSD, installed a headless raspbian and bitcoin core and let it run on Dec 16 and today it finally finished syncing :)
My internet connection is a 100Mbit down / 20Mbit up cable line and this bitcoin.conf settings work best for me:
daemon=1
logips=1
maxconnections=40
maxuploadtarget=5000
txindex=1
rest=1
server=1
walletrbf=1
dbcache=100
I don't have swap and dbcache=100 lets the bitcoin core daemon use ~800MB of memory which works nice for the pi.
Lessons learned? Not really, running bitcoin core is easy as fuck, simply fire&forget, the fun part starts now when a personal electrum server and a lightning node will come on top, but however there indeed was a lesson I learnt: Don't use fancy shmancy file systems like btrfs on your ssd because creating of swap files is not supported and it took me hours to find out this simple fact^^
submitted by FieserKiller to Bitcoin [link] [comments]

Bitcoin core v18.0 keeps crashing on cloud server. Help.

I am trying to synchronize a full node on a Digital Ocean instance with 3GB of RAM and 300 GB disk space. However, I noticed that bitcoin core is crashing very frequently. From the instance monitoring, it seems like it's a RAM issue: https://imgur.com/a/KuMev4A
Thought that 3GB of RAM were more than enough but apparently not. What is the recommended RAM then?
Here is how I installed bitcoin core:
 wget https://bitcoincore.org/bin/bitcoin-core-0.18.0/bitcoin-0.18.0-x86_64-linux-gnu.tar.gz; tar -zxvf bitcoin-0.18.0-x86_64-linux-gnu.tar.gz; cp -r bitcoin-0.18.0/bin/* /uslocal/bin; 
My bitcoin.conf is:
 maxmempool=30000 mempoolexpiry=99999 minrelayfee=0 maxconnections=50 rest=1 txindex=1 dbcache=300 
I don't notice anything in debug.log: https://pastebin.com/SkrEzmTb
I don't have anything else running on this instance.
EDIT: after adding some swap memory, bitcoin core doesn't crash anymore but it seems to be synchronizing extremely slowly while RAM usage stays around 97%
EDIT2: replaced bitcoin.conf:
EDIT3: new bitcoin.conf
 rest=1 txindex=1 dbcache=2000 datadir=/mnt/volume_fra1_01/.bitcoin 
submitted by johnturtle to BitcoinBeginners [link] [comments]

Bitcoin Core painfully slow sync times + missing bitcoin.conf file?

So I've always had trouble syncing my bitcoin qt client, the times are painfully slow, (if it's even progressing at all) and I found out that the bitcoin.conf file is not created automatically and couldn't find out how to create one, there are so many flags to use. Any help?
submitted by BestServerNA to Bitcoin [link] [comments]

SECRET Modern Bunker Loaded Up With Supplies For Doomsday ... Memory hierarchy, cache memory MY FIRST FAIL ON YOUTUBE Getting your Private Keys from the Bitcoin Core wallet ... Sincronizando billetera y Reclamando LitecoinCash LCC acelerando proceso.

Bitcoin.org is a community funded project, donations are appreciated and used to improve the website. ... The default -dbcache has also been changed in this release to 450MiB. Users who currently set -dbcache to a high value (e.g. to keep the UTXO more fully cached in memory) should consider increasing this setting in order to achieve the same cache performance as prior releases. Users on low ... C:\Program Files\BitcoinCore>"C:\Program Files\BitcoinCore\bin\bitcoin-qt.exe" -debug -dbcache=1024 -txindex. The issue reproduced - CPU/HDD/NET utilization went to 0%, number of processed blocks got stuck, after graceful shutdown of BitcoinCore the block database is corrupted. Reduce ‘dbcache’ after full sync . Once Bitcoin Core is fully synced, we can reduce the size of the database cache. A bigger cache speeds up the initial block download, now we want to reduce memory consumption to allow LND and Electrs to run in parallel. We also now want to enable the node to listent to and relay transactions. As user “admin”, comment the following lines out (add a ... The very recently released bitcoin v0.6.0 has modified bdb cache settings (25 megabytes by default), and provides a way to change this via the command-line option -dbcache=N, with N a number in megabytes. This change caused a very significant speedup for synchronizing the block chain indeed. There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called bitcoind).They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files.

[index] [37679] [16802] [50340] [12281] [24195] [3826] [14436] [17628] [38599] [24166]

SECRET Modern Bunker Loaded Up With Supplies For Doomsday ...

Son mis primeros vídeos cualquier sugerencia o critica sera bien recibida, esta explicado mas o menos rápido ya que tenia un poco de prisa pero creo que esta bastante claro. litecoincash.conf ... HackerSploit is the leading provider of free Infosec and cybersecurity training. Our goal is to make cybersecurity training more effective and accessible to ... 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. ... How would you like to spend 30 days underground in an ATLAS Shelter with your family to win a years worth of survivals food and supplies? Watch this video fo... Vediamo come sincronizzare nel modo più veloce possibile il portafoglio Bitcoin Core ... in questo caso da opzioni del portafoglio alza dbcache a 4500 ( velocizza in maniera estrema sopratutto ...

#