Hi all,
I've been struggling with this problem for a few weeks now.
I have a DeepOnion QT wallet which worked fine untill somewhere mid october.
I was able to receive & send onions without any problem.
When I tried to send out some onions to a friend, I saw an "transaction failed" error for the first time.
I started to look why this happened.. And already got a lot of suggestions from other DO members.
- I can receive onions without any problem
- I cannot send out onions, no mather which amount or whatever address I try, not my own, not another address
- running checkwallet & repairwallet returns positive : so wallet should be fine
- dumping private key is not possible for my original address, but when I create a new address, this works
So, this is the stage i'm at right now :
1. Made backup from wallet trough wallet app (I have a backup from 06/11 & 16/11)
2. made a manual backup from wallet.dat file in %appdata%
3. removed all files in %appdata%
4. removed wallet directory
5. downloaded new version from website
6. re-installed wallet
7. launched wallet & closed it again
8. removed all files from %appdata%
9. re-opened wallet & overwritten wallet.dat file with backup
10. waited untill block syncing was done
11. unlocked my wallet, unchecked the "for staking only box" & tried to make a dumpprivkey DfbVmexCDLhbsSEGEjSXPAQXGhE7ECKghb = same error all over
12. tried (when searching arround) locking my wallet again & use the option walletpassphrase "passkey" 300 and again dumpprivkey = same error
Moving this wallet to another computer won't help because i'm pretty convinced that the problem lies within the wallet.dat file... and is certainly not an issue on my computer itself.
I have several other QT wallet for other coins, which work fine without issues.
So, really really looking for someone who encountered the same issue and got a fix for it.
Thanks in advance.
note: the one that solves my problem will receive onions for helping me out on this one !
It would be interesting to get a copy of the "Transaction that failed." |
|
|
|
There is a "Truism" that states: 'Make something fool-proof... and they'll just invent better fools'  It doesn't matter how many warnings people put up, or how simple you make something... someone will always find a way to screw it up... that's just human nature.  And you won't be able to stop the tide of scammers, hackers and thieves... wherever there is a dollar to be made... someone will always find a way to make it... that's just human nature. There is another saying that says "You can lead a horse to water, but you can't make it drink"... some people just don't want to take the time to read and learn, they just want their #freeMoney as quick as possible so they can move on to the next "ShitCoin"™ fork... okay, but seatbelts exist for a reason. |
|
|
|
Threads like this should cause every reader to pause and make sure it doesn't happen to YOU. Man that's over a hundred grand. At this point I am ONLY helping my family with BTC IF they get and use a hardware wallet, no exceptions! For now I am doing all the buying for them to protect them from newbie mistakes, and then mixing to their addresses. My family doesn't know I am Coin-Keeper but I am helping them with learning crypto. Seriously, 100 bucks for a hardware wallet and be done with these threads. Not one of my family has ever challenged me to remove the HW restriction/requirement for my helping them. They just give me fiat and I turn it into BTC for them. When they learn a bit more I'll step away and let my "pupils" stand on their own. LOL! OP I am sorry to have read this thread. You are not going to be the last to post one like it!
you bring up an interesting point, that it really seems like a mentor relationship is necessary to learn the art of bitcoin. unless someone had degrees in computer science and experience in crypto or some similar background, he might never really get the principles |
|
|
|
Obviously it's spam attack (most likely by BCH supporters) and i'm sure all transaction will be confirmed (or removed from mempool) eventually. Also, someday i'm sure the community will agree to increase blocksize or use 2nd layer as solution this isn't a conclusion that logically follows. a system designed for a max of 7 transactions per second, suddenly in the public eye, everyone wants in and wants a part of the action. look at the massive influx of newbies to this forum. they are also placing transactions. |
|
|
|
I am using Bitcoin Core as a wallet that holds some BTC that I would like to split for the various forks. If I understand correctly, I can send the BTC first to a new wallet (address) and then once the funds are transferred it would be safe to import the now "old" private keys to the new forked client wallet.
My question is, if I can simply rename the old wallet.dat to something else and let the core client create new wallet.dat file, is the new file considered the same as having brand new keys or would I need to completely uninstall the Bitcoin Core client and start from scratch?
So my plan would be to rename my current wallet.dat to something like wallet.old, restart the client and let it generate a new wallet.dat with new private keys and addresses. I could then write down one of the new bitcoin addresses, and then do the same thing but in reverse; rename the new wallet.dat to wallet.new, rename wallet.old back to wallet.dat, fire up the core client and then transfer the btc in the old wallet to my new address in the new wallet.dat file.
Does this process seem correct? Any help or suggestion are much appreciated as I think I understand how the process works but sometimes that can be dangerous.
i highlighted where you may have a misunderstanding. first from your current wallet, move all funds somewhere else. temporarily, but move them. wait until the transactions have cleared. then take your existing wallet.dat, enter console mode, dumprivatekeys. locate the text file generated. now you have a copy of the keys that you will be importing to a bitcoin cash wallet. I imported that text file to an excel worksheet. the reason is, the format of the lines and the data. I wanted to strip out just the private keys, from a file where there was ... "public key, field, field, private key." there were a lot of private keys that were irrelevant, like the latest batch of "reserve" addresses. although they are irrelevant, the entire list of private keys can be entered into the bitcoin cash wallet. it will just ignore the ones that have no value. i used the electron-cash wallet, and moved first just one address, verified the funds came up, then did a couple, then a couple more, then the whole batch. caution: the whole batch took a couple minutes to process. this is a conservative approach, where if there is a problem, it will be found out on maybe just the first test, before the large batch is entered into the new wallet. my first efforts were to use the bitcoin-abc full node, but that was way too much hassle. no reason at this time to run a full node for bitcoin-cash, and it was taking a long time to build the 130gb database/whatever it is. i wound up using the electron-cash spv wallet, which worked fine. |
|
|
|
This is batshit crazy. It requests the person wanting to claim his BTG enter his private keys into an app on an android phone. Nobody should every do that. |
|
|
|
You can easily download OCR reader from the google play or itunes stores, helps prevent errors by using the mobile devices camera to read and translate the characters correctly.
Sure can, give that scanned private key to whoever is operating the OCR reader app! No, please don't. |
|
|
|
And here is the information that I get from Block.io when retrieving private keys for address 3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke :
* Address: 3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke
* Address Type: P2WSH-over-P2SH
Ohhhhh... it's a SegWit address... OK, all bets are off. I honestly have no idea what you need to do at this point... but that probably explains the "witness program does not match script hash" error... As far as I can tell, I *think* that there are inputs used in your original transaction that are no longer available (ie. they've been spent in different transactions)... so I don't think your original transaction will ever confirm. It would appear that someone (your wallet? block.io? the receiving wallet? some other 3rd party?) is trying to rebroadcast that original transaction. Give it a day or so... and it should all settle down and the transaction should be completely dropped from the mempool and your wallet should show you the coins etc. Ok, but it's 4 days already. Only yesterday early morning I had a chance to send another transaction with a high priority from my Block.io wallet, but I missed that chance as I didn't expect the transaction to rebroadcast again. Anyway, so how can I access my Block.io wallet funds using the Private Keys? I still didn't find a way. There must be a solution to this and I hope that someone can help me. And by the way, there is still no answer from Block.io support.  Look, you have created a very complex transaction and it has been pointed out that at least one part has an error. Do this. Send a smaller amount of coin - pick the amount so that you get maybe 30 inputs to it. Or 60, whatever. Get that done. Then do another one. In other words, break the problem into pieces, and handle each piece one by one. At the end you may only be left with one problematic input. |
|
|
|
Who else is losing faith in BTC? I use to believe that BTC would change the world. What I just witnessed last night with BCH attempting to take over just shook my entire belief in BTC and crypto currency in general......
A tempest in a teapot. It will amount to nothing. |
|
|
|
That is not anywhere near correct. I did one yesterday with a $4USD fee and it was confirmed within an hour or two. |
|
|
|
Possibilities:
- Copied and pasted address from Internet myself viewing bitcoingold coins...
- Clipboard hack, or any other hack. (Tried to reproduce the bug but It works normally no address change showing)
- Jaxx bug hack, it showed me some errors that I had ignored and re-installed
Sorry but I "cleaned and changed" everything.
I am sooooo lucky that today transactions goes very slow, thank you to everybody.
lol man you won on that one, for sure. One thing I will mention in closing. Always get the wallet software from original source, such as Github. Always verify with the file signature. If it is suspected to be a virus, check all your flash drives and removable media for infection. |
|
|
|
May seem crazy, it would be interesting to try another transaction, to see if it also is hijacked. Of course, a small one. (I would play with this in a virtual machine. But a real machine with a possible infection, that's a very different matter. The machine and contents needs to be isolated.) Can you verify the presence or absence of a virus on your computer at this point? Remember that not uncommonly, a virus will be deleted and it will "re emerge" after a power off power on cycle or some other system event. Another possibility is wallet software that has been rewritten. Regardless, one must take the point of view that that computer, and it's contents, are unsafe for financial transactions. |
|
|
|
I believe there were some issues previously with the methods used for implementing the BIP38 encryption, which meant that sometimes you could run into difficulty when trying to decrypt them. There was one particularly nasty episode of this when it required a specific browser version on a specific operating system!
If you're worried about it, what I would suggest doing is create a throwaway wallet using the original method, and then attempt to decrypt it using various methods (bitaddress.org, blockchain.info etc)... that should at least prove that the systems you are using are compatible.
OK Ill do that thank you There were some issues. You should be downloading the javascript and running it locally, not typing these private keys into any online website. And the local computer should be off the internet when this is done. That's not really great, better is a linux OS on a flash drive so the computer stores and knows nothing. Anyway, here is what you should do. After moving the coins, simply print out a copy of the code (that's the downloaded and locally ran copy of the, whichever, for example bitaddress.org) that you are using to do the bip38 encryption. Store that program code with the paper wallet. Include notes as to your OS version and whatever else you think might help someone off in the future. IF you did this with a copy of bootable linux on a flash drive, and the files mentioned above were on the flash drive, then you could store this flash drive with the paper wallets. You are then saving with the wallets, a known good computing environment for their deciphering. |
|
|
|
It's probably a change address used by the wallet. Change addresses are what allows you to not only spend large chunks of Bitcoin at once. Unless your balance has decreased more than you expected it, you should be fine.
I should have received 0.27298966 BTC which is 0.27459522 BTC being sent minus the miner's fee, but there are 0.26861186 BTC in my balance on Bittrex. Should I contact them? 0.27298966 - 0.26861186 = 0.0043778 The blockchain link you provided shows the net of the transaction was 0.0043778. I suggest you look at the transactions in electrum, look for a receive address matching that displayed by blockchain. There is an address is Electrum and it's matching that is displayed by blockchain, but idk what is that address and why that amount was sent to it Sounds like you've got all your coins, just a matter of which buckets they are in. Make some test transactions and track what happens using the blockchain.info. What's a real bummer is that test transactions today cost several USD each....they used to be pennies... |
|
|
|
Suddenly, I cannot unlock my Bitcoin Core encrypted wallet. I was sending and receiving transactions only a few days ago. I am certain that I am using the correct password because I had backups of the password, and it is correct. My bitcoin remain in the wallet, but I cannot move them. I moved the wallet.dat file to another computer, but I get the same error on using the password. Is it possible that the recent upgrade to v0.15.0.1 affected the password?
get a hex editor app and plug the characters of the password in, and then cut and paste into the Core password field. You don't need to trust keyboards for this (and obscure means of entering special characters through keyboards). |
|
|
|
According to Mike Belshe's announcement, they expect the size of the block to be increased later, once there is greater agreement from interested parties. So it's not a definitive cancellation, how long is it going to take? we do not know yet, what is known is that the bitcoin community is not yet ready for this hardfork
This was never about the technical matter of block size. It was about control. There has always been differing goals and mindsets between bitcoin "industry" and "users." But if a minority can announce a fork and intentionally wreak havoc, and get away with it, that would appear to show a weakness in the overall functional of the algorithm in our admittedly imperfect society. This "agreement" came from New York. New York is the banking capital of the world. Wouldn't the bankers like to control crypto? It would of course be a very different thing then. That would be opposite from the goals of Satoshi Nakamoto. On the matter of block size and it's importance. Any traditional database expert would and is really laughing over a bunch of crypto nerds being conning on a pitch that a 2x block size in a database is going to solve their problems. Really when a system upgrade is made for increased performance, the thinking has to be in terms of orders of magnitude improvement. |
|
|
|
It's probably a change address used by the wallet. Change addresses are what allows you to not only spend large chunks of Bitcoin at once. Unless your balance has decreased more than you expected it, you should be fine.
I should have received 0.27298966 BTC which is 0.27459522 BTC being sent minus the miner's fee, but there are 0.26861186 BTC in my balance on Bittrex. Should I contact them? 0.27298966 - 0.26861186 = 0.0043778 The blockchain link you provided shows the net of the transaction was 0.0043778. I suggest you look at the transactions in electrum, look for a receive address matching that displayed by blockchain. |
|
|
|
Why is Bitcoin the predominant one among different forks, such as Bitcoin Cash, Bitcoin Gold, Bitcoin SegWit2X?
Is it because Bitcoin is the most original one? ....
Because there are hundreds or thousands of Elvis impersonators. But there's only ONE Elvis Presley. |
|
|
|
so i want to create a fake transaction 1 that will go trough but will not get confiremd because its not real how can i do that?
Define fake. |
|
|
|
Going with the "bc1***" on there own was a serious mistake.
There is enough confusion already, without developers placing burdens on the entire software community to support their latest style of encoding of the same data.
I disagree. P2WPKH and P2PWSH are incompatible with earlier wallets anyway and required their own addresses. BIP142 proposed cramming them into base58 format and the result was ugly. P2PWPKH started with letter "p" and P2PWSH with number "7". The latter were longer than usual base58 addresses. Base58 has a lot of limitations (mixed case is one of them; try to spell it via telephone or type on a mobile keyboard). Bech32 is much superior and now there is a clear upgrade path. Legacy addresses are base58, pure segwit is bech32. It is good that they look completely different because you can clearly see which is which. I agree with everything you have said. I like bech32 much better, it is practically no different than typing hex. But that wasn't my point. I said that for electrum to "go with bc1***" on their own was a serious mistake. Think of it as a business mistake, not a technical one. Better would have been at some get together, for a half dozen of the major players to announce support for bech32 "within a year." |
|
|
|
|
Show Posts
