Could seed words generated in trezor work with software wallets such as Blue wallet?
Seed words from Trezor will work in Electrum or other wallets that support BIP39 seed. What ranochigo said is for 'Electrum seed' to Trezor, but it'll work vice versa ( Trezor seed to Electrum) using the BIP39 option when importing seed phrase to Electrum. |
|
|
|
-snip-But i can't pay actually. But i can share my wallet with helpful people  AFAIK, Dave will only take 20% of the balance as the payment and wont take 'down payments'. Their pricing: https://www.walletrecoveryservices.com/pricing/So basically, zero for the first ( few) failed attempts. Do not share your wallet.dat file to random " helpers", that's the very first thing you should be aware of. If you really want to, send it to people with positive ratings ( click "Trust" in their profile page) and ask others if they can trust that person. |
|
|
|
Try to contact walletrecoveryservices, aka Dave ( bitcointalk profile). You should at least have a 'guess' on your possible passwords or it will be impossible, even for him. Beware that there's no other " Dave" and some scammers with same name may try to PM you or reply to this thread ( the usual). You can check the user's " Trust Ratings" first to be sure. |
|
|
|
I search a bit and I think you are using Linux or maybe tails. -snip-
According to his other thread, he's using " Parrot OS 4.11"; link to the other thread: Problems installing the upateHe's having problem installing the update yet based from the link above, yet, he's upgraded the wallet file to v41. It seems like he got both old and new Electrum versions installed. |
|
|
|
|
Yes, as long as it's not a "fragmented backup".
v0.96.5 has the option to select the version of the wallet backup to be restored: from 1.35, 1.35a and 1.35c.
The "wallet version" should be on your paper backup.
|
|
|
|
-snip-
'This version of Electrum is too old to open this wallet.\n(highest supported storage version: 33, version of this file: 41)')
My guess is you've successfully installed 4.1.5, launched it at least once because the wallet file is upgraded to 'version 41'. But you still have the previous version installed and used it in that instance where you got the " Electrum too old" error. |
|
|
|
are there any plans of allowing public lightning channels on Electrum?, -snip-
As far as I can see in the repository, there's no discussion about enabling public channels in 'Issues' and 'Pull Requests'. Filtered with " lightning" tag: You can ask the developers themselves or post a " pull-request wanted" topic in the 'Issues' tab. |
|
|
|
It is not pointed out in the documentation as the ThomasV's signature is. I can see it being present on old pages in electrum.org, but when I try to access them, even using the Google Cached option, it is gone.
-snip-
It's still available in the latest version of the website, under " About" section: https://electrum.org/#aboutBut it's better if you can confirm it somewhere else ( like the reply above) other than the same site where the signature and binaries are downloaded from. |
|
|
|
Here is the strange part, after I load the unsigned transaction, I sign it offline, then I see a QR code, I can take that QR code, decode it, convert to hex, and I can load that signed raw transaction into a block explorer and it shows me all the inputs, outputs, fee, etc so I can double check before I broadcast it.
So it seems the unsigned raw transaction is buggy but the signed raw transaction isn't. I hope you can understand what I am trying to say because its difficult to describe without showing.
That's expected. The unsigned RAW transaction is " PSBT", not a " Raw Transaction" as I explained above, you can read BIP-174 for more info: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki#specificationIt can't be decoded by blockexplorers because it's not an actual bitcoin transaction, just a " Partially Signed Bitcoin Transaction" which is different than a raw txn ( check link above). But after it's fully signed, Electrum will construct a valid signed raw transaction that can be broadcast to the network. It's now in the proper format so blockexplorers or other transaction decoders can now decode it. |
|
|
|
-snip-
As you may know, the seed phrases are just a more convinent way to represent your Private Key, meaning that behind these carefully placed seed words is a private key, which is the "master" key of your wallet and that it will be used to generate all your addresses. If we use a tool that allows us to see the private key "behind" those seed phrases - such as TP's Brainwallet[2] - we get the following private key (based on the previous seed phrases): -snip-
Nice " Brainwallet" explanation but the seed phrase works entirely different. Brainwallet basically hashes the seed phrase ( Brainwallet calls it passphrase) to get a 256bit result which will be used as the private key. In BIP39, wrong arrangement will result with invalid seed phrase due to a wrong checksum. In Electrum, wrong arrangement will invalidate the result because it will produce an invalid seed " version number". |
|
|
|
I checked this transaction and there are many addresses on recipients so how did you know that it does not match from the copied address on Electrum? Not all in recipient address is yours you should check all the recipient by loading it more just scroll down to load the whole recipients and use "find" button from your browser to look on that address. This looks like a simple link of the transaction in question to me. In Moonpay plugin, you'll see the address where the purchased bitcoins was sent in the " Sending to" field under the " Order ID". Or " Destination wallet address" in the transaction receipt, there's no need to use a blockexplorer. |
|
|
|
-snip-
I see that you're using Electrum based from your other posts, And there's one niche case where you could expose that you're using Electrum, and opened a lightning channel. It's too specific but you might need the info: Only possible if you're using the setting " Create recoverable channels" then opened a channel ( setting only available for newly created/restored wallets). Someone who's monitoring you could tell that it's from Electrum and it's an " Open Channel Transaction", based from the OP_RETURN data Electrum included in the " funding transaction". That's if he already know that the spent input is yours. Release Notes | 4.1.0 - Recoverable channels (option): /spesmilo/electrum/blob/master/RELEASE-NOTES#L82-L101For other use-cases, same as the posts above. |
|
|
|
That's because of the new method of Electrum for exporting transactions that follows Bitcoin Core's format. It's now using " PSBT" ( Partially Signed Bitcoin Transaction), thus the QR Code for the unsigned txn as well. In Cold Storage setup, your offline Electrum should be at least version 4.0.1 to be able to recognize PSBT. What I did with Electrum 2.x-3.x was I displayed the QR code on the online computer, took a photo with a digital camera and put in that QR photo into my offline computer, decoded the QR code, then that base 43 I converted into hex, and was able to Load the transaction as a text and was able to sign it.
It's much simpler if you just directly export the PSBT ( text) and put in in your offline computer for signing. You can export it using the " Advanced Preview", after clicking " Finalize", use " Export->Copy to Clipboard". |
|
|
|
-snip-
There is something wrong and it is not my fault, for I am doing it with an informatics manager with long experience.
Thanks. What do you mean by " Informatics Manager"? If it's someone who've contacted you randomly after posting the first thread ( guess there was, because of the title), please do not hand over your 24-word phrase or private keys to him or anyone and just follow the first and second reply in this thread. |
|
|
|
-snip- Is there anyway to manually pick which UTXO you want to spend from like in Electrum 3.x ?
It's still available in 4.x versions. Just enable the 'Coins' tab ( View->Show Coins), open it, then multi-click ( holding CTRL or SHIFT) the coins you want to spend, right-click then select " Spend". The only difference with 3.x is you'll have to manually go to 'Send' tab and there'll be a green highlighted message below saying " Coin control active: .....". Alternatively, right click on the coin that you don't want to spend and select, " Freeze Coin" so it will be excluded from the coin selection. |
|
|
|
I'd like to see how this works in Windows and how to check the integrity of files, -snip-
There's Windows " PowerShell" and you can use the " Get-FileHash" utility: Instructions/SourceExample: Let's get the SHA256 hash of Bitcoin Core v22.0 installer in my " Backup & Installers" folder; open Windows PowerShell then type: get-filehash "E:\Backup & Installers\bitcoin-22.0-win64-setup.exe" -algorithm SHA256 | format-list Enclose the path with quotes ( like I did) if it has spaces or other illegal characters. Results will be: Algorithm : SHA256
Hash : 9169989D649937C0F9EBCCD3AB088501328AA319FE9E91FC7EA8E8CF0FCCCEDE
Path : E:\Backup & Installers\bitcoin-22.0-win64-setup.exe Which matched with the hash of 64-bit Win setup file in SHA256SUMS file from https://bitcoincore.org/bin/bitcoin-core-22.0/: 9169989d649937c0f9ebccd3ab088501328aa319fe9e91fc7ea8e8cf0fcccede bitcoin-22.0-win64-setup.exe |
|
|
|
|
Bitcoin Home Directory setting works in the GUI at my end.
But I'm puzzled how did that fixed the issue since it's he mentioned both work, while it's just a "not talking" or connection error where it's usually an RPC connection issue.
Can't tell without his reply.
|
|
|
|
... Let's go back to now, I don't remember that I made a password in the first place, but when I run the wallet it asks me for the password.
When exactly is it asking for a password?  Not to mention ( but I'll mention it anyways), he also got a seed phrase. If he's a " Bitcoin = Bitcoin Core" coin name old propaganda victim, he must be talking about a different wallet. If not, it's a made up story.@ Jan Drapper " Bitcoin Core" is the name of the 'reference client' not the coin, if you're talking about a " Bitcoin" in general, call it " Bitcoin" not Bitcoin Core. |
|
|
|
|
Show Posts
