So You will believe, ("Why not") , than Why Not God ?
I just told you exactly why not. As unlikely as it is that a person making a clichéd argument about the existence of god on an Internet forum would have a least one friend, the concept is at least self-consistent and is not logically or physically impossible, and hence is believable (albeit with some difficulty). The notion that the universe was created by an omnipotent God is another matter altogether, and in any case has nothing in common with belief in a random forum-user's friend, so it isn't a valid comparison in the first place.
|
|
|
I have a feeling this day will be remembered in bitcoin history. Things are going down real fast. I'll say it again. Get out of this fantasy delusion while you haven't lost it all yet.
You lost it all since you sold your coins at $10 lol. I can't believe you're still on here. No one takes you seriously. I do. I take kwukduck very seriously. he's so consistently and infallibly wrong. It's like Nostradamus and the Delphic Oracle had a baby on Opposite Day.
To the moon! ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
Sure, why not? If, however, you claim your friend created the entire universe, can perform miracles, is immortal, and has countless more implausible properties, well those are pretty good reasons not to believe you and instead conclude you're either lying or delusional.
|
|
|
I love vixens. Because they're so sweet and talented in their own way.
|
|
|
It has nothing to do with x emulation layer.
Yes it does, since it's the only tool that can do what you want. Are you even paying attention? What you're trying to do is completely unsupported. Bitcoin-Qt is not designed to work that way, nor can it easily be made to work that way under Windows.
|
|
|
$260. I've been convinced for nearly two weeks now that we're going to moon.
|
|
|
More specifically, the first contains a standard URI, and most QR code readers will recognise it as such and automatically pass the data to whatever the default program is for that protocol (in this case, whatever Bitcoin wallet (if any) you have installed). The second contains a bare Bitcoin address, which will not be understood by non-Bitcoin software.
|
|
|
You can't. New users are prohibited from posting links except to specific trusted sites.
Ignore notlist3d. Take note of the BIT-X advertisement in his signature. He is being paid to post replies, even on topics he knows nothing about. Advice from users with paid advertising signatures is often incorrect or misleading and should generally not be trusted.
|
|
|
There may be system specific reasons or hardware problems that are causing you to see corruption on power loss, they're certantly not expected or intended
Aren't they, though? NTFS isn't a proper journaling file system, after all. Of course, defective file management is clearly the fault of the operating system, and you'd think people would be grateful that Bitcoin Core can repair the resulting corruption in almost all cases, but they aren't. "It's too slow! You need to make Bitcoin Core run faster on defective systems!" ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif)
|
|
|
Can you explain how this works? How does it know there is a fork at all and which side it is on?
It knows there is a fork because it stores all orphaned or invalid blocks it receives. It specifically checks for either a major chain reorg (more than 6 blocks deep), or an invalid blockchain (one containing invalid blocks) with more proof-of-work than the best valid chain. Either of these conditions indicate that something has gone horribly wrong.
|
|
|
Bitcoin Core will automatically go into safe mode (which issues a warning and prevents new transactions being sent unless overridden) if it detects it is on the wrong side of a fork. This didn't happen in this case because Bitcoin Core (the later versions at least) wasn't on the wrong side hence there was no risk to users.
|
|
|
This may help; my bitcoin.conf file contains these flags: min=1 server=1 proxy=127.0.0.1:9050 onion=127.0.0.1:9050 listen=1 discover=1 Ah. I think listen and discover allows connections to bypass the proxy (I'm not 100% sure how these options interact).
|
|
|
If it's shutting down because of a logged error, the error in question will be at the very end of the log. Errors in the middle of the log are generally irrelevant (at least with regards to the shutdown), regardless of how numerous they are, since the program clearly continued running after them.
|
|
|
Those links are malware, and those errors don't mean you are double-spending, they mean that somebody on the network is trying to. Your node is simply rejecting those transactions as it should.
|
|
|
No, I only have 2 Onion nodes connected. The rest are IPv4.
If your IPv4 network has incoming connections, you're definitely not using Tor as an IPv4 proxy. As I said, I don't know why it says you are.
|
|
|
Sorry, I meant to say: Not having "--proxy" defined in my bitcoin.conf still makes `getnetworkinfo` show all the protocols using the the onion proxy. It shouldn't. I can't explain that. Or why (as I've just noticed) you've got 44 connections apparently over Tor. That can't be right. I'm confused about "--onion" and "--proxy". Are these options for incoming connections, outgoing connections, or both?
Both, although you obviously can't get incoming connections over IPv4/IPv6 without a public IP address, which you don't have if you're using Tor as a proxy. The only way you can get incoming connections through Tor is if you're hosting a hidden service.
|
|
|
I have set in my bitcoin.conf; however, I do not want non-Tor IPv4 or IPv6 going through it, yet why does it claim to be using the proxy for all protocols? Um, because that's what the proxy option is for? If you want to use Tor just to reach .onion nodes, and not as a proxy for other traffic, use the onion option instead, eg, onion=127.0.0.1:9050. (Naturally, connections to non-onion nodes will not be anonymised if you do this.)
|
|
|
Download the Linux .tgz file from bitcoin.org/en/download. In the bin folder of this tarball are all the binaries you need. Dump them in /usr/bin or some other suitable location and run bitcoin-qt (and create a desktop link to it if you feel like it). That guide is incorrect. There's no such thing as libqtgui4-gui. The required library is just libqt4gui, which you should already have anyway.
|
|
|
"Exactly what 'herbs' are in this herbal tea?"
|
|
|
About a zillion of them were registered in the past few days. No posts. Is this someone's idea of a joke I'm not getting or do they actually expect to sell them?
|
|
|
|