 Show Posts
|
|
Pages: [1] 2 3 »
|
|
thanks for the great answer.
|
|
|
|
|
I have 2 separate nodes (version 26) running, each using their own wallet.dat file. the wallet.dat files have the same keys though.
if i migrate the legacy wallet on one of the nodes does it affect the other node's wallet? meaning do the legacy wallet's keys become invalid at all?
|
|
|
|
i mostly use linux but wanted a copy on a Windows machine in case a family member needed to access it since linux would be totally foreign to them. I'm laughing now because it probably doesn't matter what OS it's on. Bitcoin will harder to explain to them than linux  Anyway, i had the blockchain on another hard drive separate from the Windows OS that just had files/documents on it (formatted as NTFS too). I did have that location in the config file. So from the comments here i decided to just move the blockchain files to the Windows default location and now Bitcoin is running without a problem with the pruned blockchain. A little annoyed it didnt work the way I wanted it, but I'll call it a win nonetheless. |
|
|
|
|
I'm using a pruned blockchain with bitcoin core version26 without any issues. I copied the blocks and chainstate folders and wallet.dat file over to another computer. but when i start bitcoin core it tells me i need to reindex the blockchain which will redownload the entire blockchain.
copying a pruned blockchain like this should work right?
|
|
|
|
Have you tried to use bitcoin-cli help instead of using -? it might only show limited commands compared to using "help".
"bitcoin-cli help" was it. it's funny because i has tried "bitcoin-cli --help" but that just gives the abbreviated list too. thanks for confirming my memory! |
|
|
|
running bitcoind -? or bitcoin-cli -? at the command line used to give me a pretty exhaustive list of options. I am noticing now many are now not listed (dumpwallet, getblockcount,getaddressbylabel,sendtoaddress,etc.) i found them here https://developer.bitcoin.org/reference/rpc/index.htmlBut why were they removed from the help pages? Or am I missing something. Back 3-4 years ago this is how I learned to use bitcoin at the command line. |
|
|
|
|
I've been running Bitcoin Core using bitcoind -daemon for the last few years. I have it running on my RaspberryPi and yes it uses the config file at ~/.bitcoin. I have the maxconnections set here to 30. Bitcoind always adhered to the maxconnections setting.
Just this week I decided to use bitcoin-qt (for the first time in a while) to teach someone about Bitcoin. So I shutdown bitcoind and started bitcoin-qt. Bitcoin-Qt always created a config file at ~/.config/Bitcoin/Bitcoin-Qt.conf. When I noticed the number of connections going higher than I set it, I thought I needed to add a maxconnections setting to that bitcoin-qt.conf file.
But I am realizing now that the bitcoin-qt.conf isn't the place to manually add settings. I guess it contains changes settings strictly made in the GUI. I decided to delete the current bitcoin-qt.conf file and restarted bitcoin-qt. It regenerated that bitcoin-qt.conf file and then somehow magically now it is adhering to the original maxconnections setting. Maybe the file was corrupt or something(?)
Anyway thanks for feedback, it helped me get back on track.
|
|
|
|
|
yes i've shutdown and restarted but it is still ignoring the max setting.
and i just dont want over a 100 people accessing my network.
|
|
|
|
|
I have maxconnections=20 set in the bitcoin-qt.conf file but it seems to ignore the setting. right now network connections at 48 inbound and 10 outbound.
When i run it as bitcoind, instead of using bitcoin-qt, the maxconnections works fine, but that is in a different config file.
|
|
|
|
Most sites don't update the total size, so the longer ago someone typed it, the smaller the number.
I currently have 4.6GB chainstate and 420 GB blocks.
thanks for the verification on your data |
|
|
|
|
im running a full node on my raspberry pi and currently the blockchain data directories are taking up 425GB of space.
about 421GB in the blocks directory and 4.6GB in the chainstate directory.
i see on websites like ycharts dot com that the current blockchain size is about 396GB.
what can explain the difference in my copy?
|
|
|
|
It likely wasn't re-downloading anything (unless you are saying you observed network activity). Rather it was re-applying the chainstate updates that were lost during the power loss. These chainstate updates are cached in memory before being committed to disk, so a sudden power loss will lose those updates. These updates are the effect of processing blocks - it's really just re-processing those blocks. The caching is done for performance since waiting for things to flush to disk can be a significant bottleneck in syncing.
interesting. so does the cache get written to disk only when there is a proper shutdown or at some preset intervals? maybe based on the amount RAM the system has? |
|
|
|
|
running v.0.21.0 on my raspberry pi4. had to pull the power supply because the OS froze for some reason. after it booted back up and i restarted bitcoin core i noticed it was re-downloading about 200 or so blocks to get current. i was only down for maybe 15 minutes. does bitcoin core not save recent block history?
|
|
|
|
|
thanks for the advice. i never thought abut doing this before. worked out well.
|
|
|
|
I think mempool.space is the best fee estimator and mempool visualization interface. It is simple to understand and the fee suggested is usually correct. That being said, almost every website o overestimate fees. Usually this is good because transactions do not get stuck, the problem is that people end up paying higher fees. Personally, I try to see the mempool and look for the smallest fee rate possible to pay to get into the top 1mb jn the mempool . I did an estimator that does that, but It is suggesting slightly higher fees when mempool is empty (need to fix that) https://bitcoindata.science/plot-your-transaction-in-mempool.htmlyes i stumbled upon mempool.space yesterday. i agree, nice interface and easy to understand. i switched to using estimaterawfee and looks like it suggests fees closer to what i see on mempool.space |
|
|
|
This is simply because not all nodes have the exact same mempool.
And mostly all of these estimators are based from their node's mempool, some are considering the last few blocks.
So even if it's based from "estimatesmartfee", you'll likely get a different results.
Moreover, the sites that you've motioned likely have their own algorithm on estimating transaction fee.
looks like using the economical option for estimatesmartfee gives a much lower fee estimate. i guess that option may just look at the last few blocks like you mention. where the conservative option looks at a longer block history. may take longer time period to adjust...im guessing |
|
|
|
|
ok copied over to other node, re-scanned about 550 blocks (took a few seconds) and showed correct balance! thanks
so really i can just make one copy of my wallet.dat file, keep it offline for years potentially. Then copy it back to an active node if ever the active wallet.dat becomes corrupted or entire device blows up.
no need to make a copy of the wallet.dat file once a month or after every new transaction?
|
|
|
|
Yes, but make sure that Bitcoin Core isn't running while copying and pasting the file.
It's fine for non-HD wallet too.
It will trigger a 'rescan' that could take a while to complete though.
Also, do not do that if your client was pruned because it will sync from scratch unless you still have the blocks where your wallet's inputs are.
not pruned. full blockchain on both nodes. i'll give it a go. thanks I should be able to send/receive BTC from both nodes right? and each of the wallet.dat files should show all transactions made no matter what node they were made on? am i thinking about that right? |
|
|
|
|
can i copy the wallet.dat generated by one node to use on another node? i think since it is an HD wallet it should be okay.
i really just want to be able to see my wallet balance on each separate device i am running nodes on.
would also act like a back up too i guess right?
|
|
|
|
|
