There is absolutely no difference between a sending and receiving address, they are all the same. (It still confounds me as to why the core devs still label the addresses that way since it causes a lot of confusion.) - snip -
If I recall correctly, in Bitcoin Core, the "Sending Address" list is the list of other people's receiving addresses that your wallet has sent bitcoins to in the past. The "Receiving Addresses" are the addresses that you have generated in your wallet that you can give to people so that they can send bitcoins to you. Really?! I didn't know that. I thought that both lists were for the addresses in your wallet. I guess they need better labeling. OP, in that case, then you need to figure out who owns that address and kindly ask them for the Bitcoin back. If they are a trustworthy and honorable person, then they will return you the money. However, if it was a service, some services will delete old deposit addresses (since they intend for those addresses to be used only once) so the Bitcoin will be lost. Although if it is a service, it doesn't hurt to contact them and see if they can still send you back the Bitcoin.
|
|
|
And the chance of bitcointalk closing is quite low yup. many people considers bitcointalk.org to be the central (arguable, of course.) forum for anything related to bitcoin so I think this forum will continue to exist. not to mention that the owner of this forum have very little reason to close the site. The owner will never close the site(it always will generate a lot of income). Also, I don't think the forum will ever close down because of lack of people or interest. The only way this forum can get closed is if government gets cranky about bitcoins and decides to crush us all. However, this forum will face a competition after sometime from another emerging forum that is being run by someone(Roger Ver) who can well enough afford to give us a tough competition. If the forum has enough power it will stay on the net, even the government can't do something about. For example Wiki leaks - it is hosted in a secret place and the government can't really shut down a site without knowing where the server is. The server ip is public. The hosting is known and US based AFAIK. The government could shut it down, but they have no reason to. The identity of Theymos is known, and he is also known to have assisted the government with investigations by providing PMs to them regarding whoever it was they were investigating. (I think it was BFL).
|
|
|
yeah , since yesterday my 6th sense has been telling me that i need to update my bitcoin client.. it must be calculating the default fee amount based on old numbers ( if indeed that how it works )..
Anyhow I have updated the client now.
Also I used the recommended fee, i never changed any amounts with the fee.
The default fee estimation needs to have Bitcoin Core be running for a few hours before it can accurately estimate fees. You need to start up Bitcoin Core and let it run for a while (long enough for a few blocks) before its fee estimate will be accurate. Otherwise you need to set the fee manually.
|
|
|
I seen that, but I am not sure how to apply this on a mobile wallet. I can't seem to follow the same instruction or find where it would be similar. On the mobile wallet, slide in from the left and select Wallet Settings. Then Select Backup wallet and it will export your wallet file to a location on the phone. You can then go to that location and pull the file. It might be encrypted, so you will need to figure out how to decrypt it. I think the easiest way would be to just make a new wallet on blockchain.info with your desktop and import the wallet file so that you can export the unencrypted private keys.
|
|
|
Hi Guys,
I could really use some help trying to recover some bitcoins my father accidentally sent to his Bitcoin Wallet's local default sending address.
Are the bitcoins lost? or is it possible to recover them somehow? When checking on blockchain.info, the funds are visible but I have no idea how to recover them into the Bitcoin-Qt wallet. When referring to "sending address", there are receiving and sending address in the Bitcoin-Qt client, it has one address (you can have multiple) but this was the address he sent the funds to.
I thought it would be visible after his Bitcoin-Qt wallet synchronized but no luck. Unfortunately, the bitcoins did not come back to his wallet. This was done 2 days ago. If I look up the same address on blockchain, the exact amount is just sitting there.
Thanks, Brad
There is absolutely no difference between a sending and receiving address, they are all the same. (It still confounds me as to why the core devs still label the addresses that way since it causes a lot of confusion.) The bitcoin should still be in his wallet, and the balance should update, the only difference will be the transaction fee, so the Bitcoin should still be sendable. Can you give us the address and post a screenshot of his Bitcoin Core? And what OS and version of Bitcoin Core is he running?
|
|
|
IF it nevers goes through and disappears from the network will the BTC go back into my other wallet?
Yes. It will be as if it had never left the wallet.
|
|
|
Found Bitcoin-QT.
First I check the executable is there
from Mac OS dir $ ls Bitcoin-Qt
Then I run this
Bitcoin-Qt -zapwalletxes
I get this....
-bash: Bitcoin-Qt: command not found
I matched case on the ls, have to be missing something
try ./Bitcoin-Qt -zapwalletxes You're slow, we already go past that. The problem OP now has is that zapwallettxes is not removing his unconfirmed transactions. I have been thinking about it but I don't know why that is happening.
|
|
|
Hello everyone,
Just installed Bitcoin Core wallet on windows and the blockchain was 6 years and 50 weeks behind or so. The first 5 years went by fairly fast, however, the last year and 50 weeks are dreadfully slow and still going. There are 46 weeks left as I write this and it has been two days. There are 8 active connections to bitcoin network. Can anyone tell me why it is taking so long? How can I avoid this next time I set up another wallet, and can someone point me to a good tutorial on wallet management? Any information would be greatly appreciated.
Bitcoin core is a full node wallet. It needs to download the whole blockchain before it's able to work. Once it's done, you won't have to do it again, assuming you don't lose the data. The reason why it's taking so long is that we're talking about GBs of data and you probably have fewer peers available to download from compared to when you started. There are other wallets that do not need to download this huge chunk of data. They are called light wallets and you should look them up on bitcoin.org. Not only does it need to download huge amounts of data, the years closer to present have had fuller and fuller blocks due to more and more transactions. This means that the blocks from the recent year or two will be larger and thus take more time to download and index. OP, once the wallet is synced the first time, you don't need to do it again, provided that you don't delete the data directory.
|
|
|
try running it with -zapwallettxes=2 instead of just -zapwallettxes. I'm not sure if that will help.
|
|
|
Added this ./ to the front of Bitcoin-Qt -zapwalletxes
It launched Bitcoin-Qt.... no idea what is happening now.. hopefully launching with a delete on my unconfirmed txns
When everything loads, check the transaction history and all of the unconfirmed transactions that were there should be gone. Then you can shut down bitcoin core and restart it normally. Everything should work and you can then resend all of your transactions.
|
|
|
Found Bitcoin-QT.
First I check the executable is there
from Mac OS dir $ ls Bitcoin-Qt
Then I run this
Bitcoin-Qt -zapwalletxes
I get this....
-bash: Bitcoin-Qt: command not found
I matched case on the ls, have to be missing something
run it with ./ before bitcoin-qt.
|
|
|
Do i need to shutdown my bitcoin-qt client first? navigate to correct directory???
You shouldn't need to navigate to the directory, but bitcoin core needs to be shutdown first. I did shutdown the client, but getting command not found when I run from Terminal root dir Looked in /Library/Application Support for Bitcoin directory but cannot find it.... argh I think it should be in /applications, but I could be wrong. I don't use macs.
|
|
|
Do i need to shutdown my bitcoin-qt client first? navigate to correct directory???
You shouldn't need to navigate to the directory, but bitcoin core needs to be shutdown first.
|
|
|
running this from the debug window says method not found
bitcoind -zapwallettxes
Just run zapwallettxes (no dash, no bitcoind) Running Macbook Bitcoin-QT client, from debug window I type and get zapwallettxes Method not found (code -32601) whoops, sorry, you don't run that from the debug window. Actually, go to the terminal and run bitcoin-qt -zapwallettxes
|
|
|
running this from the debug window says method not found
bitcoind -zapwallettxes
Just run zapwallettxes (no dash, no bitcoind)
|
|
|
You have a low fee for a large transaction. You should expect to either wait a few days and it will confirm, or wait a few days and it should disappear from the network. If you want to keep it there and just wait, get the raw hex of the transaction and then rebroadcast that every few days. Or you can wait for it to disappear and then resend the transaction but with a higher fee.
|
|
|
Dumb github question, but is there as easy way to apply a pull request to a local clone of the git repo? I can't even figure out how to download a pull request as a unified diff, let alone how to pull it properly with git.
The github help tells me to browse to the pull request and click "command line" but I don't see such a link.
EDIT: And many thanks to bitsolutions for doing (and sharing) the necessary work - and of course to Alan and goatpig and all at ATI for their continuing work on Armory!
EDIT^2: I'm also being dumb as there's no way (I think) to download the actual pull request that goatpig reviewed, since pull requests are mutable (for obvious reasons). The change is small enough it's easy enough to review, though, so if you posted a diff that would be just as good. I'm still curious as to the answer to my question, though.
EDIT^3: nm, I found a (good enough) answer that at least allows me to download the diff: browse to the pull request and then edit the URL to add ".patch" or ".diff" to the end of the URL Ugh! Did I tell you I hate github? EDIT^4: But .patch and .diff give different results though (I don't think they're substantively different but am failing to see why both exist). BTW, did I tell you I hate github?
Create a local branch which tracks the branch which is being merged in the pull request. At the top it will say something like "merge <branch 1> from <branch 2>". You want to clone and track branch 2 locally. Then you can merge it locally into your master.
|
|
|
You are fine. It is either resyncing or reindexing. If you deleted the data directory at any time when you upgraded it, then you will need to do a full resync. If bitcoin core was open when the computer crashed, the databases could have gotten corrupted which would prompt a reindex of the database. Just wait for the bar to disappear, which can take a few hours to a few days depending on your computer. In that time, the bitcoin should show up. If you find that it is done syncing (green check mark in the corner and the green bar disappears) and that your balance is still incorrect, then your wallet is messed up.
BTW, you should have upgraded to the latest version 0.11.1.
|
|
|
I have some unconfirmed transactions that are sitting for hours. I want them gone, what can i do?
5b788baaf29eb5da59b01704179d5ebfb05f0ea3dea79482b76984b2001a7c4c-000
I don't want it pushed, i want it gone....
What wallet did you send the transaction from? Can I get my address private key off bitcoin-qt? Thinking a second strategy is to double spend with a bigger txn fee ahead of this transaction. If i can import my key into blockchain or some other wallet service i can double spend from there i think.... Open up the debug console, Help > Debug Window > console tab and then type into the box Where <address> is the address whose private key you want. If the wallet has a password on it, do walletpassphrase <passphrase> 120 where <passphrase> is the passphrase to your wallet BEFORE the command above. This will unlock your for 120 seconds so in that time you need to do the dumpprivkey to get the private key in Wallet Import Format.
|
|
|
It is a large transaction with a small fee. It is over 25 Kb. A good enough fee for that should be at least 0.0025 BTC, but the fee is only 0.0008, which is too small for a transaction of that size. It should confirm eventually. If the money is going to you, you could attempt a CPFP transaction to get it to confirm faster, or you can just wait for it to confirm normally.
Regardless of the fee, by my count also the originating address doesn't seam to have enough funds to cover all of the outputs. I doubt it will even get confirmed. That is not at all possible. No wallet would allow that, no node would relay the transaction, and blockchain.info would not accept that nor display the transaction. Your math is wrong. Looking at the fee that was included and the address' history of what appears to be multiple double spend attempts, I am not going to follow this transaction anymore.
Let me know if it ever confirms (it won't). ProfessionalGoogler, if you wanted to create a scam accusation, this address is all the proof you need: 17YEaLjrxygTBtm2aRgPmLvm8neUTkWmie
Please don't ask me any questions or debate this with me. I don't want to waste any more time on this.
Well I think it will confirm. There is no indication that there is a double spend yet.
|
|
|
|