thanks for the explanation If the person that wants to track you can monitor all traffic both to and from your IP without actually connecting to your node, then they can see every time you send a transaction without first receiving it.
i always thought the traffic between the nodes is also encrypted! is there any particular reason for not using a simple SSL encryption for this? No the traffic is not encrypted (yet). There is a BIP for encrypting this traffic, but it has not yet been implemented. As for why SSL isn't used, I don't know. this may be a little far fetched but isn't there a possibility of a man in the middle attack? i don't know what an attacker can gain from doing this except messing with one node but that is the first thing that comes to my mind with an un-encrypted communication.
No. Because of the signatures in a transaction, a man-in-the-middle attack can't do much. The attacker can't do much and can't change anything in transactions or blocks. |
|
|
|
Hi,
I am currently running a full node, and running out of space. For technical reasons I many not be able to upgrade to storage for a while.
1) If I have some more space on another partition, is there a way to tell Core to concatenate another chainstate folder(s) to the current one?
(So it will use the space I have on another partition).
No it is not possible. However, you can copy the entire data directory to another place and then start Bitcoin core with the command line option where <path> is the path to the moved data directory. 2) What are the consequences of using pruning? Will that impact my ability to send/receive txs, or it just means I can't fully verify everey tx?
No, pruning just means that old blocks are deleted. This only happens once they have been verified and validated. You will still be able to verify every block and transaction and you will still need to download every single block in the blockchain. Pruning also makes it so that you cannot bootstrap a new node, rescan your wallet, or keep the transaction index. It does not impact your ability to send and receive transactions. 3) What does the 'n' in "prune=<n>" stand for, and what is a good configuration to use?
Many thanks!
n is the amount of space in MB that you want to reserve for the block and undo files. The minimum is 550. This is to store at least two days of blocks and their corresponding undo files. |
|
|
|
Yep!
Thanks for your response.
But do you have a clue about this long waiting time?
Thanks again!
The fee was probably too low. According to https://bitcoinfees.21.co/, the recommended fee is ~80 satoshis/byte, you paid 50 satoshis/byte. |
|
|
|
In what Directory exactly i need to create the "bitcoin.conf" ?
In the data directory, the same place you found the debug.log file. This should be C:\Users\Peter\AppData\Roaming\Bitcoin |
|
|
|
24c0e3543b02442bbfb0e5f117029f921ffa41aed9fb3f32078b2552dfa79274 this is the offending txid  That block was orphaned, so any transactions coming from that coinbase (generation) transaction is invalid. |
|
|
|
|
What is the txid of that double spend? Is it confirmed? Are the transactions following that confirmed?
Otherwise, there isn't much that people can do here. Contact blockchain.info's support.
|
|
|
|
So it looks like you have corrupted block. Go to the data directory (the folder where you found the debug.log file). Then go to the Blocks folder inside of that and then delete the file named blk00443.dat. This should fix the problem, but Bitcoin Core will say that it needs to reindex the database. That can take a while, but it does not mean that the blockchain is being redownloaded. It will continue syncing on its own and should be able to catch up to the network. If you don't want all of the data that is downloaded, then you can enable pruning. Go to the data directory again and find or create the file named bitcoin.conf. Then add in the following line: This will prune the blockchain so that it only occupies a fixed size of a ~5 Gb (or something like that). If you do want to move to Electrum, you will have to get the private keys from your wallet if you have any Bitcoin there. If you have received Bitcoin on your Bitcoin Core wallet, you will need to do what I said above, or you can just delete the entire blocks folder. This is just so that the program can get started. Then you will have to extract the private keys. Go to Help > Debug Window and then the Console tab. Type in the box at the bottom Where <address> is the address that you want to get the private key of. This will reveal your private key. DO NOT SHARE THE PRIVATE KEY WITH ANYONE. Do this for every single address that has Bitcoin in your wallet. Then install Electrum. Create a new wallet (don't choose the option to import or restore anything). When the wallet is ready, go to Wallet > Private Keys > Sweep. This will open a box where you can sweep the Bitcoin into your wallet. This is recommended as the Bitcoin will be moved into your wallet, it doesn't keep the private key. Enter the private keys you exported and follow the instructions to sweep into your wallet. When you are done and have swept everything in, you can now clean up the space the Bitcoin Core took up and uninstall it. However, I recommend that you copy the wallet.dat file in the Data directory to a safe location, just in case. Then you can delete the data directory and uninstall Bitcoin Core. |
|
|
|
How come no one told this guy to do a -zapwallettx to remove all transactions and rescan? I have solved stuck transactions when it rarely happened to me (I was too cheap on the fee a couple times)
-zapwallettxes only works for transactions that you sent, not transactions that you receive. |
|
|
|
My error log is 3.42 MB.
When i post it here, i have an "413 Request Entity Too Large". In Pastebin is 512 KB allowed for normal members...
Now?
Post as much as you can starting from the bottom. Try to get the last couple of times that you tried to start it. Each line is dated, so try to get the last few days of the log. |
|
|
|
Yeah fair play I get ya. But what I am asking is this. Is it possible what he says? I mean without touching the bitcoin source code and hard forking or what ever? Before I rule it out I would like to know if it is technically possible and if so how  If it were possible, it would have already been done. In order to scale Bitcoin, we still need a fork, either a hard or soft fork. To do so would also require changing consensus and thus modify the source code. Furthermore, the solution would still need to be vetted by the current developers and detailed specifications of the thing must exist before people should even consider using whatever he creates for scaling BItcoin. |
|
|
|
Can you just post the contents? Such download sites can be suspicious. Just open the file in a text editor and copy and paste everything inside into a post here. If it doesn't fit, paste it into http://pastebin.com/ and post the pastebin link here. |
|
|
|
He's talking out of his ass.
hmm ok thanks but why? I mean can you elaborate  slightly please He has provided absolutely no details and only hype and claims that he can do it. There is nothing that indicates he knows what he is talking about nor that he actually has a solution. |
|
|
|
|
He's talking out of his ass.
|
|
|
|
|
Any hex can be converted into a private key, it's just a large number. However, if you are trying to get the private key of an address, it is not possible to do so.
|
|
|
|
Good point about pruning, I forgot that it was recently implemented. However, I'm fairly sure that even with Bitcoin Core running a pruned blockchain, you'd be using more disk space than just running Electrum (plus you'd have to sync up the blockchain everytime you'd want to send a transaction if the computer isn't being used as a full node).
That can be a nuisance, but it is the price of privacy and security. As for the extra load on the network, I meant that 30-40GB of bandwidth would be required to download the entire blockchain. I'm sure some full nodes are hosted on VPS' with limited bandwidth. Why use up bandwidth on these VPS full nodes if it isn't needed by using a wallet such as Electrum?
Those VPS nodes probably aren't accepting incoming connections. The DNS seeder will usually only hand out node's that have had a high uptime and thus most likely have a high bandwidth. Also, Electrum connects to specific Electrum servers, not random full nodes. Those servers are run by volunteers. Regarding the full node argument, I agree that more full nodes on the network is always a good thing, but the OP hasn't specified what sort of uptime their computer has. I wouldn't assume that their computer on enough to be a full node (nodes need to be on for at least 6 hours or so to be considered a full node IIRC). Additionally, we don't know if the OP has any sort of bandwidth limitations. If they do, running a full node probably isn't the best idea.
There is no time requirement to be a full node. A full node is any node that fully validates and verifies every single block and transaction it receives. Thus any time that Bitcoin Core is run, the computer is a full node. |
|
|
|
I wouldn't recommend the OP download Bitcoin Core. Even if they have the HDD space, why waste 30 to 40GB of drive space when you don't need to?
Just enable pruning and that is no longer a concern. Additionally, why put that unnecessary extra load on the network to download the blockchain?
Extra load on the network??? What the hell is that supposed to mean? A full node does a lot to help the network, even if it is pruned. It doesn't hurt; it helps. We need more full nodes, especially ones that accept incoming connections. |
|
|
|
|
You're a newbie. The other newbies may not necessarily understand what applying for a campaign is and may simply be adding the sig and thinking it will earn them money; it's hard to know if they actually are accepted.
Most campaigns won't accept newbies, and the ones that do, are ones that you don't want to be associated with if you post with decent quality, which it seems you kind of do. Just wait until you are a jr. member or member before joining.
You should not join a sig campaign as soon as possible. That is not the point of them. The point of sig campaigns is that it is an added bonus for posting, not an excuse to post more.
|
|
|
|
|
Show Posts
