For the record... Coinbase wallet asks if you want to create a backup when you set up a new account "Take 2 minutes to back up your wallet, and never risk losing your money."  Tapping backup takes you to the "Recovery Phrase" window... with a (!) Not backed up warning at the top... your 12 words and the text: These 12 words are the keys to your wallet. Back it up on the cloud or back it up manually. Do not share this with anyone And then provides 2 options: - Back up on Google Drive (I assume because this is Android version, not iOS) - Back up manually I can't take screenshots, because the app doesn't allow screenshots on the recovery phrase windows for security reasons  If you don't complete the process by either backing up to the cloud, or backing up manually (which requires that you re-enter all the words in the correct order), it shows the following in the settings menu:  You get the (!) warning symbol next to the "Recovery Phrase" option... Tapping that options takes you to back to the Recovery Phrase window as above. I should point out that if you click "later" (or the 'x') to close the backup popup... then close and re-open the app, you get the "Don't risk your money" pop-up again. What do people think?  - not enough? Should the app just go straight to the "Recovery Phrase" window and refuse to let the user use the app without completing the backup process at least once? - Just right? It offers the backup option at startup, but also gives the "Later" option if you're willing to accept the risk of not having a backup and reminds you to backup later if you haven't. - Too much? nagging popups are annoying and unnecessary! |
|
|
|
Message signed with Electrum -----BEGIN BITCOIN SIGNED MESSAGE-----
I am Kavallo and today is February 15 2021,
I am here proving ownership of my Bitcoin address: 1gS4AfugyMSx6FESNad1R6gaHnsFU6A56
-----BEGIN SIGNATURE-----
1gS4AfugyMSx6FESNad1R6gaHnsFU6A56
HzV5+lvzauw1NV16Xo2xzTzEtJVDU2qGeAJml8UUUCgiKDW8t/ZAip+LwgLAIEo6NPFIvZCfF0m0QIQh1P+e3Qw=
-----END BITCOIN SIGNED MESSAGE----- Quoted and verified |
|
|
|
What if I’m completely technologically illiterate (and a complete idiot) who acquired some BTC on a dinosaur smart phone in 2008 or 2009 as a novelty item, at the time (think Coke points or Marlboro rewards 😆) AND I don’t have access to the old (Yahoo) email address, the phone is gone and I don’t remember the wallet (because it was all practically worthless then) and I abandoned that email and last name? Screwed??? Dude, I had like 23 of them. I’m dead! Anyone have suggestions or should I just shoot myself now?
Yes... screwed... You need at least one of the following: - A wallet file (and any associated password) - The private keys - A seed phrase/recovery phrase (aka 12/24 word seed mnemonic) It sounds like you don't have any of those things... or any way to recover any of those things. So, yes... screwed.  |
|
|
|
And here I made very big mistake. I opened wallet.dat file instead of masternode.con (don't know how).
Simply opening the file in a text editor should not cause any modifications to the file... it should have been OK if you simply closed the file again. If you changed anything and then pressed "save", then it would have corrupted the wallet file. What exactly did you do after accidentally opening the wallet.dat file? |
|
|
|
Definitely, there is a problem with Trezor Bridge version 2.0.30. at least in my case. Now I had removed this version, install 2.0.27 and voila! Firmware successfully updated after all.
Updated firmware through Trezor suite.
Yeah, I suspect that 2.0.30 had some "extra" (or deprecated? ) features that were implemented for the beta wallet... and causing it to not play nicely with the "non beta" versions... glad you managed to get it sorted!  |
|
|
|
I have a trezor currently with my bulk of btc on which I access via vpn. But I'm still paranoid that the trezor wallet might one day ask for KYC before allowing me to spend funds etc. That would be pretty much impossible. For a start, you should have a 24 word, BIP39 seed. That is compatible with a whole host of other wallets, which means that you could just import into another wallet and then spend your coins (but would effectively compromise your Trezor seed). Additionally, there are other wallets with direct support for interfacing with the Trezor, like Electrum, Sparrow etc... you could just connect with them and spend away regardless of what SatoshiLabs might try to do and it won't compromise your seed! Finally, I don't see SatoshiLabs ever going down the KYC path (like Shapeshift attempted to do with the KeepKey)... but, to be fair, it's not "impossible" (how improbable it might be). At worst, they would require KYC to be able to use their software... but the main point here is that you don't actually need to use their software! Also, the Trezor is arguably as secure as having Bitcoin Core and (air-gapped) Armory... and offers much more convenience. For one, you don't need Bitcoin Core (although that will sacrifice some privacy)... and you don't have to faff about with moving unsigned/signed transactions back and forwards between 2 machines to make a transaction. |
|
|
|
Any attempts to perform a test transaction to move a fraction of that amount show the same "0/unconfirmed, not in memory pool" message that I reported earlier in this thread, with the earlier wallet.dat file.
So with a fully synced Bitcoin Core... and a fully rescanned wallet, it shows a balance but then says "0/unconfirmed, not in memory pool" if you try and send a transaction? Or are you getting that if you just open the wallet.dat file and try to send coins? If the latter, then it's likely because the wallet itself isn't "synced"... so you're attempting to send coins which no longer exist... the transaction will be rejected and you'll end up with the "not in memory pool" type error. I've run -dumpwallet and swept the keys into a new Electrum wallet, per the process mentioned earlier in this thread, which yielded nothing - just ~140 lines resulting in "no inputs found" in Electrum. (From reading further forum posts around that Electrum message just now, I have not yet tried the -listunspent command in that wallet, so I'll try it once that wallet finished rescanning.)
That would tend to indicate that the wallet is actually empty... and the balances you're seeing when you first open were accurate when the wallet was last used, but the coins have since been spent and therefore, the wallet balance is actually zero. although one file (created in late 2015) is showing a message when I try to load it which ends: "...wallet is corrupt. Try using the wallet tool bitcoin-wallet to salvage or restoring a backup."
Generally, that doesn't end well PyWallet might be able to recover something The old salvagewallet option has been removed from the "core" Bitcoin Core app... so you can't use the -salvagewallet commandline argument with bitcoind or bitcoin-qt anymore... instead, it looks like there is a "bitcoin-wallet" (or "bitcoin-wallet.exe") that is now bundled with Bitcoin Core that you can use and the command is now salvage: Bitcoin Core bitcoin-wallet version v0.21.0
bitcoin-wallet is an offline tool for creating and interacting with Bitcoin Core wallet files.
By default bitcoin-wallet will act on wallets in the default mainnet wallet directory in the datadir.
To change the target wallet, use the -datadir, -wallet and -testnet/-regtest arguments.
Usage:
bitcoin-wallet [options] <command>
Options:
-?
Print this help message and exit
-datadir=<dir>
Specify data directory
-wallet=<wallet-name>
Specify wallet name
Debugging/Testing options:
-debug=<category>
Output debugging information (default: 0).
-printtoconsole
Send trace/debug info to console (default: 1 when no -debug is true, 0
otherwise).
Chain selection options:
-chain=<chain>
Use the chain <chain> (default: main). Allowed values: main, test,
signet, regtest
-signet
Use the signet chain. Equivalent to -chain=signet. Note that the network
is defined by the -signetchallenge parameter
-signetchallenge
Blocks must satisfy the given script to be considered valid (only for
signet networks; defaults to the global default signet test
network challenge)
-signetseednode
Specify a seed node for the signet network, in the hostname[:port]
format, e.g. sig.net:1234 (may be used multiple times to specify
multiple seed nodes; defaults to the global default signet test
network seed node(s))
-testnet
Use the test chain. Equivalent to -chain=test.
Commands:
create
Create new wallet file
info
Get wallet info
salvage
Attempt to recover private keys from a corrupt wallet. Warning:
'salvage' is experimental.
|
|
|
|
man, it feels really good to know my bitcoin is safe and useable.
I take it that this means your transaction history showed up without issue and the wallet.dat has the balance you expected then? |
|
|
|
Yeah... try "downgrading" to 2.0.27 and see what happens... It's a bit of a "guess" really, as I am fairly certain that the Trezor Suite software doesn't even use the bridge to communicate with the device, as the bridge is for the browser. But maybe if you have 2.0.27 you will be able to use the browser wallet to update the firmware? Still, it's very odd that the Suite is not recognising your device in bootloader mode... If downgrading the bridge still doesn't help, then I'd say you're going to need to contact Trezor support and ask them for assistance. |
|
|
|
Do you know if it would also work for my old laptop running on Windows XP?
I never attempted to update from XP -> 10 direct... and I don't think it is actually possible. Everything I did was Windows 7 -> 10, and my understanding is that you need Windows 7 as a minimum starting point. So, I believe the trick was to go WinXP -> Win7 (or Win8 etc) -> Win10 ( https://www.zdnet.com/article/how-to-migrate-from-windows-xp-to-windows-10-in-8-reboots-or-less/)... noting that you need a "spare" Windows 7 or Windows 8 license to do this. Also, if it's an older laptop with WinXP, there is a good chance that it might not meet the minimum system requirements for Windows 10... check those and make sure your laptop is capable. |
|
|
|
Just downloaded latest Suite version. I haven't even used that app so far, it's first time installed on my computer. Clear cache, restart PC, but still, nothing happened when connecting Trezor on bootloader mode. The same thing happened when trying to update the firmware through a web browser. (I am not doing this for the first time) after this nothing happens https://i.ibb.co/4SCFZCJ/image.pngnote. I can regularly using the wallet and have access to all assets on there. Possibly an issue with "Trezor Bridge"? What version do you have installed? I know I had issues with the "beta" version (2.0.30) that I was using with the web-based beta wallet... and it seems that the latest version for download is actually only 2.0.27!!?!   Bridge Download: https://wallet.trezor.io/#/bridgeVersion list: https://github.com/trezor/trezord-go/blob/master/CHANGELOG.mdAlso, what OS and browser are you using? |
|
|
|
So basicly what this does is extract the keys i need to transfer the funds to a new wallet in a different program?
That is correct... the tools should read (and hopefully decrypt!) the existing wallet file and output the private keys so that you can then import them into another Bitcoin wallet. I have now tried the first tool. I followed the installation guide, and tried the command for exporting keys. As i do not know what I am doing, its kinda hard to tell whats wrong, but during installation i think it threw a lot of errors. took screenshots of it. Do I need python installed to run this? install https://postimg.cc/563K7fyKCuriously... yes... it would appear that you do actually need Python installed to make this work. Basically this is just telling you that (due to the errors you got above), "mbexport" is not installed... ie. it can't find it. Now, the "bad news"™ is that I just tried this program (I've not used it before as I use my Python tools ) on a known good wallet and password combination (ie. I can open the wallet file in multibit 0.5.19 and test/export the private keys)... and mbexport is crashing during export. As far as I can tell, there is likely a required library missing... unfortunately, when I tried to install that library (bcoin), the installer just spat out a huge number of compilation errors  Given that the "mbexport" tool hasn't been updated since 2017, I suspect that it is just "broken" and probably should not be used. If you try my Python scripts, note that they need Python 2: https://www.python.org/downloads/release/python-2718/ |
|
|
|
All the transaction history etc is stored on the blockchain... unless the blockchain disappears or you lose access to your private keys, then your coins are going to be just fine As far as the private keys are concerned, as long as you have your 12 word Electrum seed (or a copy of the wallet file and the wallet password), you'll be able to recover those. It might be a bit of a hassle, but have you considered upgrading to Windows 10? While the offer "officially" expired... I am fairly certain you can still get the upgrade for free. (note that the story was revised in Jan 2021!) |
|
|
|
whether you have successfully updated new firmware on Trezor?
Everything usually works for me, I have the option both through the web client and also through Trezor suite to update the firmware. But after reconnect in boot loader mode, nothing happened.
...
No issues with the update for me... got an email from Trezor, downloaded the new version of Trezor Suite (21.2.2), installed it... connected Trezor ONE... it notified of firmware update, clicked OK... disconnected Trezor, reconnected while holding down both buttons to get in bootloader mode, and then followed the instructions on screen and on device to update the firmware. Didn't wipe the device, (didn't need to re-enter seed etc)... and was able to sync all my accounts without issue. NOTE: There was a note on the blog about the fact they released a "new" version of Trezor Suite pretty much immediately to correct an error with devices not being recognised: Please note that an update has been released for Trezor Suite since the time of posting. Version 21.2.2 is the latest and will fix issues where a computer does not recognize your hardware wallet. So make sure you're using 21.2.2! |
|
|
|
Ouch. It was painful to read that... Sadly, a not uncommon occurrence... users skipping through setups, eager to play with their bitcoins (perhaps a little too eager?)... not reading everything perhaps as well as they should... perhaps not taking the time to understand exactly what it is they're doing... or how the wallet/app works Roll forward a little bit and some unforeseen event occurs (hardware failure, OS update, lost phone etc)... and suddenly, they're looking for information that they skipped over Being your own bank affords some great freedoms... but also demands some great responsibilties... Crypto can be really unforgiving of "minor" mistakes. |
|
|
|
|
Check the wallet addresses:
In Armory, Click on "Wallet Properties"... you should see:
"Used Addresses"
"Change Addresses"
"Unused Addresses"
Drill down into those categories and see if you can find the address in question.
|
|
|
|
Ok... so at this point I would probably do something like the following:
...snip...
I thought I recognised some of the idiosyncrasies in that text... https://bitcointalk.org/index.php?topic=2019233.msg20161692#msg20161692 I'm not entirely sure all of that convoluted stuff is necessary if you simply want to get your coins from an old Bitcoin Core wallet into your Hardware Wallet. At the very least, you simply need to create a transaction that sends the entire balance from Bitcoin Core to a receiving address from your Trezor. Reading it now, it looks terribly complicated for what should be a simple operation. Is there a reason you don't want to just sync Bitcoin Core, open (a copy of) your wallet.dat in the synced Bitcoin Core, let Bitcoin Core "rescan" the wallet, then send the balance to Trezor T? Is the wallet.dat not password protected or something? |
|
|
|
... and you need to add one or more older address formats starting with 1 and 3 because they are separated. As far as I can tell, Trezor Suite should automatically find all the "accounts" that have transaction history as part of the "discovery" process it does when you connect your device. Mine shows up Native SegWit, Nested SegWit and Legacy. So, if OP had a Nested SegWit account, prior to using Trezor Suit, it should should automatically be added and shown. |
|
|
|
OOPS... I had accidentally left in the "to_seed()" call... which takes the mnemonic and generates the actual seed... including the computationally expensive code: stretched = hashlib.pbkdf2_hmac(
"sha512", mnemonic_bytes, passphrase_bytes, PBKDF2_ROUNDS
)
If I comment that part out... it runs "a little bit" faster  Start: 2021-02-11 21:13:07.520000
10000 Seeds 2021-02-11 21:13:10.346000
621 Valid Seeds 2021-02-11 21:13:10.346000
20000 Seeds 2021-02-11 21:13:13.092000
1204 Valid Seeds 2021-02-11 21:13:13.092000
30000 Seeds 2021-02-11 21:13:15.903000
1832 Valid Seeds 2021-02-11 21:13:15.903000
40000 Seeds 2021-02-11 21:13:18.769000
2442 Valid Seeds 2021-02-11 21:13:18.769000
50000 Seeds 2021-02-11 21:13:21.671000
3041 Valid Seeds 2021-02-11 21:13:21.671000
...
~3secs for 10,000... or ~200,000/minute... just goes to show how "expensive" the "ENT to seed" process can be! |
|
|
|
To your other point: the wallet is showing an available balance of zero in the background, while resyncing.
And is it showing any transaction history? If you can see all the "ins" and "outs", you might be able to figure out where all the BTC went... and when. |
|
|
|
|
Show Posts
