Interesting. Find the bitcoin.conf file if it exists. It should be in ~/.bitcoin if you didn't change the defaults. Make sure that there isn't something like in there. |
|
|
|
If you don't have a fully synced bitcoin core you can also use a 3rd party service like coinb.in that will let you go through all the steps of a raw transaction. So you can create, sign and broadcast, or in your case create, sign and not broadcast. You don't need to be synced to sign a transaction with bitcoin core. You can even sign offline. If you have just the unsigned transaction, you will need to be synced in order to sign. This is because the scriptPubKey of the output being spent is put inside the scriptsig for signing purposes. Software made specifically for offline signing will include that data in some way so that a sync is not needed. |
|
|
|
All the bitcoin was then transfer out to the following Bitcoin address: 1EYn2ct8hXw2nF4FTZuywtn7mjzUxD4x23
Guess that is their wallet and everything was transfer out from there.
Calling up the police, is there any help in this? and what police? Is there a group of people who do that?
The police as in actually the police, meaning the law enforcement in your area. I don't think it will be of much help since the police aren't trained in dealing with this and the thief is likely not in their jurisdiction to even investigate. |
|
|
|
All Bitcoin transactions are publicly available. If they are confirmed, then they are included in the blockchain forever. You can view these transactions in any block explorer, such as https://blockexplorer.com/. Because transactions are linked to each other, you can follow the transaction chain and see where the Bitcoin ends up. However, even if you are able to trace the Bitcoin to certain addresses, there is no guarantee that the people who control those addresses are the people who stole the Bitcoin. Furthermore, Bitcoin transactions cannot be reversed, so the likelihood of you recovering the Bitcoin is slim to none. |
|
|
|
- snip -
these IPs must be there somewhere in the code
- snip -
https://github.com/bitcoin/bitcoin/blob/05e1c85fb687c82ae477c72d4a7e2d6b0c692167/src/chainparams.cpp#L116vSeeds.push_back(CDNSSeedData("bitcoin.sipa.be", "seed.bitcoin.sipa.be", true)); // Pieter Wuille
vSeeds.push_back(CDNSSeedData("bluematt.me", "dnsseed.bluematt.me")); // Matt Corallo
vSeeds.push_back(CDNSSeedData("dashjr.org", "dnsseed.bitcoin.dashjr.org")); // Luke Dashjr
vSeeds.push_back(CDNSSeedData("bitcoinstats.com", "seed.bitcoinstats.com")); // Christian Decker
vSeeds.push_back(CDNSSeedData("xf2.org", "bitseed.xf2.org")); // Jeff Garzik
vSeeds.push_back(CDNSSeedData("bitcoin.jonasschnelli.ch", "seed.bitcoin.jonasschnelli.ch", true)); // Jonas Schnelli
If your node hasn't saved any previously connected nodes yet, then it can connect to these initially. Once you are connected to the network, your peer will collect connection information about other nodes. The next time it starts up, it will use its own list of known peers. If for some reason the node is unable to connect to one of the above DNS seeders, it will fall back to the list of IP addresses encoded in https://github.com/bitcoin/bitcoin/blob/master/src/chainparamsseeds.h. These are the hex representation of the IP's listed in https://github.com/bitcoin/bitcoin/blob/master/contrib/seeds/nodes_main.txt and https://github.com/bitcoin/bitcoin/blob/master/contrib/seeds/nodes_test.txt. The short answer is that they don't know before you attempt to use them. The private keys are a standard format, a base 63 number if I remember that right, and so all that is required of your private key (i.e. the generated secret from bitaddress.org) is that it's created in conformance with that pretty simple specification.
Private keys are always 256 bit numbers. The base doesn't matter. It only matters for encoding the private key to be easily transported. The standard Wallet Import Format uses Bitcoin's Base58Check encoding which encodes private keys, public key hashes, and script hashes in base58 along with an additional checksum and version number. |
|
|
|
|
Using Bitcoin Core, you can go to the debug console and sign a raw transaction with signrawtransaction. It will give you the raw hex for the transaction which can be broadcast, but does not need to.
|
|
|
|
|
Well you've certainly got corrupt blocks.
Check your antivirus, both whatever you installed (if you have one) and Windows defender. Make sure that the Bitcoin data directory is on the exemptions list. The antivirus may be flagging some things in the blocks and removing them thus causing corruption.
|
|
|
|
i´m not that stupid...
i have completely erased
C:\Users\ThisPC\AppData\Roaming\Bitcoin\
and also the
..\bitcoin-0.13.0-win64 folder
when i say Fresh, Clean install i mean Fresh Clean Install...
P.S. i´ve seen BitCoin 0.13 overwriting the dat files.
So why don't you post your debug.log? That way we can actually proceed in diagnosing the issue. |
|
|
|
why i get so many corrupted blocks?
i have 340.000 blocks.... from complete 0, everything New, Fresh, Clean install..
got stuck, "no new blocks downloaded, waited lots of hours, no new blocks."
did a -reindex and when processing blocks were done, 0.13 started to download from 175.000,
Overwriting Previous Downloaded Blocks, like if they are not there, like if they are all corrupted....
Again, I need to see the debug.log file. When you reindex, nothing is being redownloaded. When you uninstall and reinstall Bitcoin Core, none of the blockchain or wallet data is being deleted, so the new install will not have be redownloading anything. So, if you have a problem in the blockchain data, it will persist across installs unless you go and delete the blockchain. |
|
|
|
|
First of all, it isn't the wallet that is corrupt but rather Bitcoin Core's databases. They are two different things and have two different meanings.
Can you please post the debug.log?
Also, you are reindexing, you are not redownloading anything. Nothing is being downloading, the blocks are already on your disk and being reprocessed. In fact, I suspect that you somehow got a corrupt block and that is causing the problem.
|
|
|
|
|
Is it promoting you to reindex or does it just happen? If the latter, check whatever your are using to start bitcoin core that it doesn't have the -reindex option set.
|
|
|
|
Ehh. Doesn't really matter to me. WTF? Am I on everyone's ignore list? I just said that in post #13... the post before yours. Too bad you aren't the mod of this section so you could delete the duplication  Nah. Sometimes I just type slowly and don't see later responses. |
|
|
|
How do i open the port for outgoing connections?
I'm not quite sure as I am not particularly familiar with iptables. I do know that it's something like where the .... is stuff that I don't know. Try google, it's very helpful. |
|
|
|
Wait,you have become a Staff now.Congratulations ! Why does your status keeps on shifting from Moderator to some threads to Staff on others ?
Thanks. I got the position last night. On boards that a moderator moderates, you will see "Moderator". For me, that's in Tech Support. Elsewhere you will see the mods listed as staff (except for global mods and admins). |
|
|
|
I'm trying to recall where I saw a discussion about knightdk recently...  Was there one? Can I send you a PM sometime? (And no, it's not "change my user name" related  ) Me? Sure. |
|
|
|
|
You need to allow both incoming and outgoing connections to and from port 8333
|
|
|
|
Excellent advice with the Electrum! I have,however, come across an entirely new problem. I do not remember my wallet passphrase. I just sat here trying walletpassphrasechange <assumed pw> <new pw> over twenty times, and I cannot remember what I set it as. Is there any way to recover this? If not, have I lost all of that money?? If you do not know your passphrase, then nothing can be done, the bitcoin is lost. |
|
|
|
Yeah, I don't think your computer is powerful enough to run Bitcoin Core and sync in a reasonable amount of time. I recommend that you use a different, lightweight wallet such as Electrum. You will need to export the private key for your address and sweep the Bitcoin into an Electrum wallet. First, you will probably want to do this with your computer offline so that you aren't constantly downloading blocks. Next, start up Bitcoin Core. Go the Help > Debug Window and click on the Console tab. In the box at the bottom, type where <address> is the address that you received Bitcoin at. Hit enter. You should see a string in black appear with begins with a '5','K', or 'L'. This is your private key. DO NOT SHARE THIS WITH ANYONE. ANYONE WHO HAS IT CAN SPEND YOUR BITCOIN. Copy that string. Now stop Bitcoin Core and go back online. Next go to Electrum. Make a new Electrum wallet and follow the instructions for making a new wallet. Once the wallet is up, go to Wallet > Private Keys > Sweep and enter your private key into the text box. Click Sweep and all of your funds will go into Electrum now. You can and should use Electrum now as your wallet. Now to free up the space on your computer. You can uninstall Bitcoin Core. Then go to %appdata%/Bitcoin. Find the wallet.dat file . It contains the private key you just exported. You should hold onto that just in case. Put it in a safe location. Once you have secured the wallet.dat, you can just delete that entire folder and it will delete the blockchain and free up space. |
|
|
|
Hi m8s, ive a problem and i hope someone can help me there.
Yesterday 18.09.16 5pm i generate 7 Paperwallets and send Coins to one. I use it yesterday 3 times and send some coins out and today i do the same 2 times.
After that i had a bad idea and replace the file on my windows because i overwrite a key from a other adress i need so i replace it with a old one... After click "Yes" i realize that ive kill my new address from yesterday ... -.-
Is there any way to get the Private Key back from the Wallet ? Internet Cache or Temp Files or any other way maybe ?
Is there someone who can help me or have a working idea to get the private Key back ill pay him a bounty 0.2 BTC
All three browsers have software out there that can parse the password files. Technically you are only seeing your saved passwords, but some browsers do not know how to handle sites with public/private key pairs and you may see your private key listed as a username in the listing. If he didn't have save passwords enabled, then that is useless. Also, browsers won't recognize every single input field as something for passwords. I don't think that will be useful here. |
|
|
|
|
Show Posts
