Yes the good news is that I have my seed password everything I have saved well.It is just that when I study how to restore the thing I can not find good information.I found a article about restoring from Multibit wallet but visiting that site they say they are out of business.I see that they have the wallet for download but I dont now want to restore with something that is discontinued or maybe now is not secure.
I am going to try to change the cable that it uses to connect by the usb connection on the computer maybe that is the problem because someone online was complaining about that.
You still haven't adequately explained what the issue with the Trezor actually is... is it not being detected when you connect it to the computer? does it not power on? did you lose your PIN? In any case... have you tried looking at the very extensive Trezor documentation? Recovery: https://doc.satoshilabs.com/trezor-user/recovery.html#Troubleshooting: https://doc.satoshilabs.com/trezor-user/troubleshooting.html# |
|
|
|
|
blockchain.info? Most likely a web wallet... The blockchain.info wallet apps for Android and iOS are effectively just a front end for their web wallet service anyway.
If she/you have access to his email accounts, you might be able to find the walletID and other info relating to the account that might let you regain access to them via the website.
|
|
|
|
Redownload the installer... it seems that the copy you have downloaded is incomplete or corrupted. For reference, the "bitcoin-0.15.1-win64-setup.exe" I downloaded from bitcoin.org ( https://bitcoin.org/bin/bitcoin-core-0.15.1/bitcoin-0.15.1-win64-setup.exe) is 14,325,736 bytes Right-click the .exe and select "Properties" and see what the size is... if it is less than that, your download was incomplete/corrupted. |
|
|
|
No... you didn't understand incorrectly... Spendulus did  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.
This process is EXACTLY "transferring the bitcoin to a temporary safe address"... although it doesn't need to be temporary... your "new" wallet.dat should be fine to continue using for the future. By renaming your "old" wallet.dat to wallet.old and then starting Bitcoin Core, you will create a completely new BTC wallet.dat... So, your idea to take an address from the "NEW" wallet.dat, shutdown Core... then rename "new" wallet.dat to wallet.new... rename wallet.old back to wallet.dat... then start Core, and then send ALL your BTC from "old" wallet.dat to the address you just wrote down from "new" wallet.dat then your BTC will be "safe"... it is now on a completely new address, in a new wallet with all new seed/addresses/private keys. You can then safely import copies of the "old" wallet.dat into BCH Core (and probably BTG Core) to get those coins as all the BTC will be gone... or you can dump the private keys from your "old" wallet.dat and import the old keys into compatible ilghtweight SPV wallets if you don't want to download 3 copies of the blockchain   NOTE: If you're super paranoid (although BCH is fast becoming "worthless" again)... You could then repeat the exercise with BCH so that you create new BCH wallet.dat so when you import into BTG your BCH is "safe" #cryptoInception |
|
|
|
"Estimated BTC Transacted" is just blockchain.info's "Guess" at how much BTC was actually sent from the sender to the receiver... it really doesn't mean anything and is often wrong. For instance, the transaction you posted has one input of 4.32064555 BTC and it has two outputs: 0.06005236 BTC and 4.25866271 BTC Blockchain.info is GUESSING that the 4.25866271 BTC output is "change", so was not being sent to anyone... and that the sender was only sending 0.06005236 BTC to the receiver. So, they put "Estimated BTC Transacted 0.06005236 BTC" as their guess. You can read about what "change" is, and why it happens here: https://en.bitcoin.it/wiki/ChangeIf you don't understand why an input of 4.25+ BTC was used to send 0.06 BTC... read this: https://en.bitcoin.it/wiki/Coin_analogy |
|
|
|
I transfer to Bitcoin Segwit chain from Bitcoin Cash Split account on a Nano S.
I so used sen to a 3-adress.
Hi GBT_User: I'm having the same problem. Did you ever recover your BCH?
I'm in the same boat as VenderFee. I sent BCH to a Segwit BTC address that starts with a 3.
There is currently NO SOLUTION to retrieve BCH that has been sent to a SegWit BTC address (that starts with a "3") Refer here for detailed explanation and research: https://www.reddit.com/r/btc/comments/6z56x3/attention_benevolent_bch_miners_a_bch/NOTES: 1. not ALL "3" addresses are SegWit ("3" is a PayToScriptHash/P2SH address... SegWit is just one type of P2SH address, "Legacy" MultiSig's are also P2SH and can sometimes be recovered) 2. While it is not possible today, it *might* be possible at some point in the future if the miners put in the effort. For now, your BCH is locked away.  |
|
|
|
So you sent BCH to a Ledger Nano S SegWit BTC Address correct? If so, you chances are getting it back are pretty much zero at the moment. It *might* be possible one day, but for now, those coins are effectively locked away. BCH Network does not have SegWit, so you can not create that SegWit address on BCH or create a "SegWit" transaction to spend it... because "No SegWit". Refer here for some really in-depth research and explanations of all the BCH->SegWit address issue: https://www.reddit.com/r/btc/comments/6z56x3/attention_benevolent_bch_miners_a_bch/ |
|
|
|
|
I'll repeat my question... have you checked the addresses (that Armory has generated from your paper backup) on a block explorer? Do they actually contain any BTC?
|
|
|
|
Do we include the private key in message? If yes, is it not problem?
And where to post the signed message to proof my bitcointalk? So if get hack i can use it to proof.
NO!You should NEVER put your private key anywhere! Did you read the very first post in this thread? There are clear instructions there on how to sign messages... The only data that should be posted when you're signing a message is: - The Message - The Address you "signed" the Message with - The encrypted "signature" that was created when you signed the message There is also a thread for "staking" addresses... https://bitcointalk.org/index.php?topic=996318.new#new |
|
|
|
Thanks for the explanation... What seems odd to me, is that using the MultiBit HD seed straight into Electrum and/or ElectronCash *should* work, ("Standard wallet" -> "I already have seed" -> Enter seed words, click options, select "BIP39 seed" -> set derivation path of m/0')... I've tested it multiple times with different seeds and have had no issues.  It is certainly a lot less hassle than using the BIP39 tool and copy/pasting keys. |
|
|
|
I also had trouble with this shit - Electron Cash. As user HCP had adviced I disabled 2FA in new Electrum wallet (2.9.3) and opened it in Electron (2.9.3). After many "server doesn't response" errors it sent test transactions to "bitcoin.com" and Bittrex wallets.
I've noticed that first try to send BCC just after opening Electron is more likely to be successfull. So I tried opening and sending it many times. Some of them were broadcasted, most didn't. But those who did appeared in "bitcoin.com" and Bitterx wallets.
Hope my experience will help you.
Your problem is that BCH recently had a HardFork... and you need to be using v2.9.4 of ElectronCash... I think a lot of the servers won't play nice with ElectronCash v2.9.3... so make sure you update to v2.9.4 for ElectronCash Newest versions of Electrum seem to have a few little "bugs"... so if you're messing around trying to disable 2FA etc on Electrum, I would suggest v2.9.3 |
|
|
|
Do I need the last step for recovering corrupt wallet files and if so what is it for?. What is the next step as I understand that I don't need all packages for what I need. Thanks.
The last step is to open up the browser to see the web interface for PyWallet... this is as simple as it gets. You can load up a copy of your corrupted wallet file and attempt to "dump" it out... or you can attempt to "dump" just the private keys... If that doesn't work, you'll be down to the very last resort... which is the process that this guy used: https://bitcointalk.org/index.php?topic=1404609.msg14257235#msg14257235It involves getting a small USB stick (preferably 1GB)... wipe it clean (delete everything off it, format it etc) and putting just your "corrupted" wallet.dat on it. Then you have to manually run the pywallet command from the commandline to get it to scan your corrupted wallet.dat and try and recover private keys. Assuming you had a 1GB USB stick and it was showing on windows as D: and you "extracted" PyWallet to "C:\PyWallet" (when running the PWI_0.0.3.exe): Step 1. you would put (a copy) of your corrupted wallet.dat on the USB stick Step 2. Start -> Run, Type cmd and press enter Step 3. cd \PyWalletStep 4. pywallet.py --recover --recov_device=D: --recov_size=1Gio --recov_outputdir=C:\PyWalletIf your USB stick is larger, change 1Gio to what Gigabytes it is... 8GB = 8Gio, 16GB = 16Gio... if you use a stick larger than 1GB, be prepared to wait a LONG time while pywallet scans it. After that finishes, it should have created a "recovered_wallet_DATESTAMP.dat" that you can attempt to load in Bitcoin Core... or use PyWallet to dump the keys |
|
|
|
|
Can you please clarify exactly what you did for the sake of anyone else who reads this...
You managed to get it working by entering your MBHD seed into ElectronCash and using the path of m/0'?
Or you used the BIP39 tool (and m/0'/0 and m/0'/1) to get private keys and imported private keys into ElectronCash?
|
|
|
|
|
In all likelihood... Bitsler have probably changed something on their end... ie. updated the API either without giving Seuntjie a headsup, or the opportunity to update the bot... or they did, and Seuntjie hasn't updated due to being super busy...
If the bot is working on other sites, and it is just Bitsler that isn't working, then you'll have to hold tight until Seuntjie has a chance to investigate and/or talk to the Bitsler Devs.
|
|
|
|
In latest version of Electrum (v3.0.2)... Right click on the address tab ("View - Show Addresses" if you can't see the Addresses tab)... select "Details" You'll see the address, public keys... and the "redeem script"... Copy/Paste that Redeem script into coinb.in "verify": https://coinb.in/#verifyIt will decode it and show you the addresses that match the public keys.... you will then need to use the original wallets to get the private keys for the addresses. |
|
|
|
Do I understand correctly that in your opinion it was not the software that I used, but that someone monitored and copied my private key and initiated the stealing transaction outside from my computer? Would the details of the transfer on Blockchain help to diagnose what actually happened? Correct. Electron Cash has been in use for months now... I'm not aware of ANY instances where people have had coins stolen due to something that a "legit" version of ElectronCash has done. Any loss is from users having either installed a "fake" version... or having had malware/keyloggers or whatever on their computer... and their private keys/seeds were compromised. Maybe try doing a Google search for the address that your coins were sent to... see it it pops up in any other threads regarding stolen coins. |
|
|
|
This is probably stistill fees. Can you post your address here (or PM me your master private key from the wallet dropdown menu).
Alternatively, go as if you're sending the transaction, and click preview. This won't spend anything until you click sign. Post a screenshot of this here?
I really hope you meant Master PUBLIC key... and not private!  |
|
|
|
Ahhh ok... I see what the problem is... this:  is NOT showing you the Firmware version of the actual Ledger... it is showing you the version of the Bitcoin App that you have installed on your Ledger... the most recent version of the Bitcoin App is 1.1.10. As I said, goto Ledger Manager... click the trashcan next to the Bitcoin App... (this does NOT wipe your coins or anything)... you may need to authorise the removal on your Ledger device. Then click the download arrow... again you may need to confirm the installation on your device:  After this, the bitcoin App on the device should be updated to 1.1.10 and you won't see the "Confirm Output#2" when sending transactions. NOTE: to see the actual device firmware... use the "Settings" App on your Ledger device... scroll down and select "Device", then select "firmware"... it should say "Secure Element, 1.31" and "MCU, 1.0" |
|
|
|
The short answer is that you can't. Once a transaction is broadcast, there is no way to reverse or cancel the payment. Even if it is unconfirmed. You could attempt what is known as a "double spend" where you try to broadcast a transaction using the same inputs (but different outputs ie. Send back to your own address and a much larger fee) in the hope that it gets confirmed first... But it is very technical, complicated and difficult to do and there is no guarantee it will work... Even if the double spend is accepted by a node (most will reject it or refuse to relay it) All that does is let you bump the fee... You can't "reverse" the transaction using RBF... It'll still go to the same address if confirmed: But there are some strict policies like the same sending and recipient address for new payment. Scammers have no way to do the tricks to double spend the money to new address |
|
|
|
|
Show Posts
