Bitcoind – Commands, RPC Protocol, Install Server ...

Litecoin mining!

Since the litecoin community is growing, I've decided to introduce /litecoinmining, a place for all discussion revolving mining litecoins!

What are recommended bitcoin.conf settings when using c-lightning?

I'm running full (non-pruned) bitcoin core 0.20 on Ubuntu 18. My current bitcoin.conf is:
txindex=1 listenonion=0 server=1 rpcuser=xxx rpcpassword=xxx rpcthreads=1 
If I use c-lightning, what changes do I need to make to the above file? Thanks in advance.
submitted by 1Tim1_15 to lightningnetwork [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:
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]

Miners, signal what you want!

F2pool may have started signaling for Emergent Consensus and SegWit as an April fools joke, but its actually a great idea. Tell us what you want! EC != BU. You can signal for EBx/ADy from any client. If you want a compromise, SIGNAL IT.
You can manually override the "nVersion" bits and the miner coinbase string in BU via bitcoin-cli or bitcoin.conf settings (or modify them in the pool software)...
submitted by thezerg1 to btc [link] [comments]

Has bitcoin classic abandoned the 2MB fork in favor of BU

The latest commit to bitcoin Classic github seems to suggest they are adopting BU ideas instead of 2MB HF.
from GitHub Commit text:
This removes BIP109, 2MB blocksize proposal. In its pace I insert the concept of market equilibrium based blocksizing. Technically this means;
Classic chose to use -blocksizeacceptlimit as a descriptive name, but for compatibility with BU has an alias for its -excessiveblocksize. Values are in whole megabytes, but floating point values are accepted with an accuracy up to 100KB. So, you can have "3.5" as blocksizeacceptlimit. This value will be put in the coinbase-comment as "EB3.5" in this example.
In short; Miners can continue to use the -blockmaxsize argument or bitcoin.conf setting to limit the size of blocks they generate! All nodes can also use the -blocksizeacceptlimit option to limit the size of the blocks accepted from (other) miners.
zander committed 9 days ago
submitted by marouf33 to btc [link] [comments]

New to Namecoin, seeking a little guidance

Oi, so I've been mining Bitcoins for a few weeks and want to migrate a few over the Namecoin to register a .bit domain for me an my lads. Problem is, the Namecoin software throws "Bitcoin: Warning: Please check that your computer's date and time are correct. If your clock is wrong Bitcoin will not work properly." I synced my system time with M$ and - same gig; no dice. EDIT: restarted my system, ran NC fresh before any BC software... 20 minutes later, a simple blank console. No input possible. On the upside, GUIMiner seems to be mining sans-errors... but how do I check my address/balance without input, eh?
Am I doing something wrong here? I have bitcoin.conf set up properly (I think) and my BT miner has been accruing me satoshis for awhile now... Anyways, besides these practical issues I have some technical issues that have been left unanswered by the dot-bit wiki as of yet if anyone'd like to take a crack at answering them:
Being new to Namecoin, I'm still quite muddy on if it's more convenient to simply pay BTC to a registrar or do the do myself. Any help is, as always, much appreciated. Thanks, lads v lasses
submitted by w1AQ-59G to Namecoin [link] [comments]

Bitcoin price caused @CMEGroup to set new daily trading records for its Bitcoin Futures this week, the company conf… - Crypto Dynamic Info - Whales's

Posted at: February 22, 2019 at 08:26PM
Bitcoin price caused @CMEGroup to set new daily trading records for its Bitcoin Futures this week, the company conf…
Automate your Trading via Crypto Bot :
Join Telegram Channel for FREE Crypto Bot: Crypto Signal
submitted by cryptotradingbot to cryptobots [link] [comments]

installing BU, cannot find instructions on setting up conf files /r/bitcoin_unlimited

installing BU, cannot find instructions on setting up conf files /bitcoin_unlimited submitted by BitcoinAllBot to BitcoinAll [link] [comments]

[TUTORIAL:] Creating a custom wallet. Part 2: Read settings from bitcoin.conf.

For a number of reasons, I'm going to post directly to the source on github
This tutorial demonstrates how to dynamically read ~/.bitcoin/bitcoin.conf so authentication doesn't need to be hard coded into the application.
It still doesn't do anything useful, but we are getting there. First we need lay a foundation to work on.
If you find this useful, please tell others about this tutorial series and about this sub-reddit.
submitted by Joshka to BitcoinDevelopers [link] [comments]

How many confs would I have to wait to make sure TX was secure on bitcoin Unlimited's network if miners have AD set to 6?

How many confs would I have to wait to make sure TX was secure on bitcoin Unlimited's network if miners have AD set to 6? submitted by Hernzzzz to btc [link] [comments]

How many confs would I have to wait to make sure TX was secure on bitcoin Unlimited's network if miners have AD set to 6?

How many confs would I have to wait to make sure TX was secure on bitcoin Unlimited's network if miners have AD set to 6? submitted by BitcoinAllBot to BitcoinAll [link] [comments]

how to make transactions with 0 fee in bitcoin-qt? I've set 0 fee at configs and .conf file but whenever i send it sets an amount for fee.. (it's possible because wallet can do it)

submitted by intrd to Bitcoin [link] [comments]

[#94 Score:1 Comments:0] - can i still make transactions with 0 fee in bitcoin-qt? I've set 0 fee at configs and .conf file but whenever i send it sets an amount for fee..

submitted by Removal_Rover to remove [link] [comments]

A Closer Look Into "Who Funds Bitcoin Development?"

A Closer Look Into submitted by 1MightBeAPenguin to btc [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]

Is it safe to allow connections on port 8333 ?

I've just built a bitcoin core node with electrs and tor, on a spare dedicated machine. All seems good and I can connect a wallet from another machine running on the same network to the node.
However, I couldn't see my node from so I then tested port 8333 from but it said "connection refused".
After lots of research, I thought it must be something wrong with iptables and tried loads of different configs, but nothing helped.
I then found these:
Which led me to update bitcoin.conf by changing bind= to bind=, tested again and it's working inasmuch as the port can be seen (from and I think my core node is accepting incoming connections (which I think is what you're supposed to allow - right?).
I (also think I) understand that bind= (in bitcoin.conf) is only allowing traffic from localhost and that by changing it to is akin to wildcarding it to accept any IP, is that right?
Would appreciate someone setting me straight on this.
submitted by derrick-r to BitcoinBeginners [link] [comments]

Gridcoin "Fern" Release
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.



Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.


Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.


The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog



Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.







As a reminder:









Detailed Changelog

[] 2020-09-03, mandatory, "Fern"





submitted by jamescowens to gridcoin [link] [comments]

txindex=1 server=1 question (node, rpc)

Edit: solved! Just needed to wait for indexing to catch up
Hi all I'm trying to use btc-rpc-explorer
I have a full node via bitcoin qt. Can I use qt for block explorer?
I launch block explorer and I'm getting rpc error. The webpage states "check rpc connection info"
The github project states I need server=1 and txindex=1. Can I make qt run with these settings? I tried adding them to the .conf but how can I confirm qt is running with these options, in console somehow?
In case I can't use qt for this I downloaded bitcoind. It looks like I can start the daemon with txindex=1 and server=1 but still getting same connection problem with btc-rpc-explorer.
Do I have to do -reindex=1? Can I do that within qt? If not and I use bitcoin cli will it disrupt qt in any way?
Edit: this is on Ubuntu
submitted by redditor157b to Bitcoin [link] [comments]

Bitcoin-qt datadir alternative storage location

I tried asking this in the bitcoincore sub yesterday, but it only has a handful of members and got no answers, so i now try here.
When bitcoin-qt is first started, it asks for the location of datadir. If it is set to a custom location, it remembers it on subsequent launches. Where is this location stored, as no bitcoin.conf is generated in the default location, and i have not seen any other documentation to specify datadir except command line option and bitcoin.conf file?
submitted by varikonniemi to Bitcoin [link] [comments]

Distortion with a Focusrite Scarlett Solo (3rd Gen)

EDIT2: I can find no pattern to this mind numbingly frustrating problem. Switching back and forth between devices and sample rates in Reaper is not solving the problem now. I have no clue what does it.
EDIT: Just FYI, it looks like changing the sample rate in /etc/pulse/pulse/daemon.conf didn't actually solve it, though it's only just happened for the first time in a long time. I did find that going BACK to ALSA in Reaper, changing the sample rate there, and then switching back to Pulse (still in Reaper) fixed it at least this time though, so anyone who comes across this can try that.
I'm running Ubuntu 20.04. I often deal with very fuzzy distortion from my Scarlett Solo audio interface (EDIT: the distortion is on the output, not the input). Sometimes I don't notice what causes it to start, but it does seem to have several causes. For example, Opening up PulseAudio Sound Control or opening/closing Reaper can cause it to start, and there doesn't seem to be a way to fix it besides restarting. Looks like it only affects PulseAudio, since selecting ALSA as my driver in Reaper does eliminate the distortion in Reaper, but I'm still stuck with the distortion everywhere else until I restart.
Here's what it sounds like:
(Original video for comparison, though I don't think you'll need it)
If I try to record the output to OBS, I get undistorted audio in the recording.
Any idea what's going on here, and how to prevent it?
Potentially relevant information:
This has happened regularly for a long time. Sorry if that makes it harder to diagnose. I just haven't had the energy to look into it until now.
I started with Ubuntu Studio 18.04. (This comes with JACK, and maybe there's a conflict there? I'm a terrible linux audio user, because I still haven't really figured out JACK.)
When I first installed the OS, I followed some tutorials to set up Ubuntu for Audio. (Many of the things were, apparently, not already set, even with Ubuntu Studio.) Unfortunately, I couldn't tell you what all I did. (It was a while ago, before I had the interface, iirc.)
Also, while I realize it wouldn't really come close to compensating folks for their time and effort, I'd love to tip a few dollars of Bitcoin Cash to anyone who can help me here, at least to show that I appreciate and value that time and effort. And of course, please feel free to point me towards required reading, or ask for more info I should provide. Thanks in advance!
Ubuntu 20.04
GTX 2070 Super
AMD 8320
Focusrite Scarlett Solo (3rd Gen)
submitted by AD1AD to linuxaudio [link] [comments]

Where does the Bitcoin-QT options dialog store options

When running Bitcoin-QT, there is an options dialog you can get to in the GUI under Settings. I've played with some of these settings and they don't store where I would expect. I've run some tests, on Windows 10, and it they are not housed in the bitcoin.conf file. What's more the settings persist if you change named conf files.
Is it housed in the registry or some other file on the filesystem?
submitted by brianddk to Bitcoin [link] [comments]

Over an hour 0 confirmations

I occasionally use bitcoin to fund some online entertainment. So, I’m not totally new. But I don’t ever remember going an hour with 0 confirmations. Should I be worried at this point or is this normal? The transaction was relatively small (less than $100 USD) and the fee was about what I remember them being in the past. I know transactions can take a while. I just don’t remember going this long without any confirmations.
Edit: it confirmed just a little while after posting this. And to clarify: it wasn’t the purchase of the BTC that took time, it was the transfer. Thank you all.
submitted by torchesXXtogether to BitcoinBeginners [link] [comments]

[ Bitcoin ] Anatomy of the Bitcoin Node filesystem

Topic originally posted in Bitcoin by brianddk [link]
There are man explanations like this, but this one is mine.
Just in case anyone was curious. I dug up some good posts on this and thought I'd distill it as best I could. I'll be using Windows file separators, but fee free to change them in your head.
If you name a -datadir argument, this is what will land there. If one is not named it defaults to %APPDATA%\Bitcoin
If you name a -blocksdir argument, this is what will land there. If one is not named it defaults to
  • \blocks\blk*.dat - The raw block data
  • \blocks\rev*.dat - The Undo files. List of spent UTXOs for each block
If you name a -main.walletdir argument, this is what will land there. If one is not named it defaults to \wallets or just if the wallets subdirectory doesn't exist.
  • \wallet.dat - The wallet file with private keys and UTXOs
  • \db.log - Database log of access to wallet
Note that -datadir, -blocksdir and -main.walletdir can all point to different storage. The things you need to keep in mind:
  1. -datadir should be your FASTEST storage
  2. -blocksdir should be your LARGEST storage
  3. -main.walletdir should be your most SECURE storage
As a footnote, testnet will through a testnet3\ in everything, and would require a -test.walletdir switch to set the wallet directory.
brianddk your post has been copied because one or more comments in this topic have been removed. This copy will preserve unmoderated topic. If you would like to opt-out, please send a message using [this link].
[deleted comment]
submitted by anticensor_bot to u/anticensor_bot [link] [comments]

Bitcoin BTC Trading Bot Cryptohopper Setup and Config 2020 Bitcoin BTC Trading Bot Cryptohopper Setup and Config 2020 5 Settings For Mining Cryptocurrency On Windows 10 - YouTube Litecoin Configuration on BATMTwo Bitcoin ATM - YouTube Beginner's guide to solo bitcoin and litecoin mining ...

Reset all settings changed in the GUI Many of the boolean options can also be set to off by specifying them with a "no" prefix: e.g. -nodnseed. Bitcoin.conf Configuration File . All command-line options (except for -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the ... Fine tune settings for what transactions your node will relay to peers. Accept Non-Standard Transactions Relay and mine non-standard transactions (testnet/regtest only.) Incremental Relay Fee Fee rate (in BTC/kB) used to define cost of relay, used for mempool limiting and BIP 125 replacement. Please provide a valid number (min: 0, max: ) Dust Relay Fee Fee rate (in BTC/kB) used to defined dust ... To sync faster I have updated my bitcoin.conf file by adding the node addresses. My latest config file is similar to this: testnet=1 regtest=0 dnsseed=0 upnp=0 setgenerate=1 blocksonly=1 server=1 addnode= addnode= addnode= addnode= addnode= maxconnections=15 minrelaytxfee=0.0001 maxmempool=200 maxreceiverbuffer=2500 ... While running Bitcoin Core GUI, open the Settings menu and choose Options. On the Main tab, click Start Bitcoin on system login. Click the Ok button to save the new settings. The next time you login to your desktop, Bitcoin Core GUI should be automatically started as an icon in the tray. If Bitcoin Core GUI does not automatically start, you may need to add it to an .xinit or .xsession file as ... There you can register and other settings from those given when starting the daemon. How it Works . Accordingly, the only thing you need to accept bitcoins is a bitcoin client on the server. It is called bitcoind, it’s just a console version of the client, with all the same familiar functionality. It works through the JSON-RPC protocol, is located under port 8332. All that remains after ...

[index] [40248] [7276] [5983] [46370] [23908] [13419] [48291] [28431] [32353] [25211]

Bitcoin BTC Trading Bot Cryptohopper Setup and Config 2020

How to configure Windows 10 for your Mining Rig to get the best hashrate in ethereum and more. Parts: MSI Pro Series Z270a: Intel Pent... Cryptohopper - a detailed settings and setup One of the best and easiest bots to set up & customize - Duration: 16:03. Donnyboy8 13,695 views Cryptohopper Setup and Configuration for 15% Weekly Gains Cryptocurrency and Bitcoin Trading Bot - Duration: 20:38 . ... Config Settings Daily Gains #Bittrex setup soon Kangaroo subscription ... This video is unavailable. Watch Queue Queue. Watch Queue Queue Newbie guide for those who want to try solo bitcoin and litecoin mining, using bfgminer and cgminer. The config files shown in the video are available in the...