Thank you for ongoing advice. Yeah, i must be misremembering. Now it seems clear that i had to have deleted the transaction on the "Receive" tab. It was certainly an actual implemented transaction, and not just a request to receive BTC. BUT there were of course no confirmations. I just have this inexplicable memory blank about who the actual sender was.
-snip-
For the record, the delete option in the receive tab is labeled "delete", while the one in the history ( only for local transactions) is labeled "Remove". So since you've mentioned that you clicked " delete" in the OP, it's the receive tab which is only an invoice. That also explains the " blank memory" of the sender because there wont be a sender if you haven't sent the invoice to anyone. |
|
|
|
|
Yes, Bitcoin Core is a hard requirement of Armory.
Without it, there's no way for Armory to acquire the data from the Bitcoin blockchain.
Take note that you should disable the "prune blockchain" settings in Bitcoin Core before downloading the blockchain or it will not work with Armory.
|
|
|
|
BTW, your images: "Coin Control" and the alleged turned watch-only wallet "Electrum 2" doesn't fit the story because of the huge difference in the number of available (unspent) outputs and "TX" count in the history.
Yes its true because I have 8 wallets and I didn't have an image for that particular combination so I posted a picture I took with my Phone. -snip-Okay... I see the situation strange based from the available info and at this point, I have no idea what's happening in your client since none of it should happen under normal circumstances. ( 'Imported' into 'imported watch-only' | Imported the same prvKey to other wallets and derived different address) Sorry I can't help more. |
|
|
|
-snip-
I know what you told me to start over and so on but if there are anybody reading this post that had a similar problem where it seems the address of the private key is different and that had a solution, please help.
It will be much appreciated.
I think the information you need is about the nature of private keys and addresses. It's not some sort of a backup that'll fetch an address from a server; just think of it as a " pair". The Private key is actually a big number which a public key can be computed from, and the address is derived from that public key. Better ELI5 explanation: https://learnmeabitcoin.com/beginners/keys_addressesThere can't be a network/server-side error which could lead to wrong address recovered from a private key, all is computed by the client/wallet, if there's an issue, it's the client. With that, if Blockchain.com and Exodus both derive the same address ( and test other clients), then there's something wrong with your Electrum or you've imported the wrong private key. You said that you've verified its signature and it checks out? BTW, your images: " Coin Control" and the alleged turned watch-only wallet " Electrum 2" doesn't fit the story because of the huge difference in the number of available ( unspent) outputs and " TX" count in the history. |
|
|
|
-snip-
Something that also surprised me is that Electrum doesn't operate with BIP39 seeds, it seems, so if I create a seed in Electrum I can't use the seed directly on another wallet, would that be the case? I'd need to grab the xprvs for this.
I searched for a way of converting seeds but don't know if that's possible. Needless to say, it's great that Electrum itself accepts BIP39 seeds.
Yes. BTW, what's the reason why you need to use another wallet? As another cosigner? If so, that client should have a " PSBT" feature ( Partially Signed Bitcoin Transaction), without it, it wont be able to sign the exported unsigned/partially-signed transactions from Electrum and vice versa. |
|
|
|
They never replied to me. Do you have the BTC derivation path of Coinbase? 200 $ for you if yours work.
We already tried with many derivation paths.
I'm shocked that you still haven't received your bitcoins, at least if I were you, I would, in these two years, force coinbase tech support to tell me to fuck off (give me back the coins). Problem is " Coinbase" isn't " Coinbase Wallet"; although both are products by the same company, those aren't the same. OP's wallet is the latter which isn't custodial, so Coinbase doesn't have anything give him since they don't have the funds. BTW, if you've read the previous replies, you'll see that in various users' attempts, they can restore their address in Electrum, but for some reason, OP can't ( and it's for you to judge what went wrong). |
|
|
|
maybe i changed the first 3 letters of the private key, it has it has 44 letters and numbers including uppercase and lowercase letters.
-snip-
Maybe you didn't, maybe it's a private key in " BASE64" format like mentioned above. You can use the tool below to convert it into " BASE58check" ( WIF) to be able to be compatible with most Bitcoin wallets. Here: https://brainwalletx.github.io/#converter | Use it on an offline machine: " Download ZIP", extract, copy to the offline PC then run using your browser. To convert, Go to " Converter" tab, paste the 44 characters private key, select " Base64" for the 'Source Encoding' and " B58Check" for the 'Convert to'. If the base64 in the Source Encoding isn't selectable, then it's not a BASE64 prvKey; otherwise, the result should be a 51-character string that starts with '5' which is the WIF ( Wallet Import Format) private key. |
|
|
|
I'll follow the steps described and report back when the UTXO is free again 🙏🏼🍻
Take note: the steps I've provided is only for recovering the 1000 satoshi that you've already sent to the wallet, it's not the right way to create a MultiSig wallet. And you shouldn't use the recovered wallet(s) after sending the funds out, create a new MultiSig wallet the right way: https://bitcoinelectrum.com/creating-a-multisig-wallet/ |
|
|
|
-snip-
I have only dat file
How to recover my wallet with only dat file?
Is it a " wallet.dat" file or " electrum.dat" file? If it's wallet.dat, post a new thread in Bitcoin Technical Support board and follow the sticky thread " Tech Support Help Request Format". Otherwise, post it here in Electrum board. For starters, if it's electrum.dat, you can just load a copy of it using the latest version of Electrum and it will open without issues. For further concerns, please add it to the thread that you'll create. |
|
|
|
-snip- Since there is nothing in this particular private key let me post it here with screen shots. Coming up
I'd never do that if I were you. Even if it's empty in your tests, there may still be unclaimed be " fork coins" in there or specially if the issue turns out to be the software's fault. Anyways, you can test if the Electrum you're using is indeed deriving the correct address from the given private key by importing a random private key ( e.g: from paper wallet generators) and see it the correct address will be imported; if it does, then it's what they've said. |
|
|
|
No there was only one adress i used, never created one more, i didnt need it to and never send any btc to anyone. I only get paid in that adress, what i tell u if i say i get paid less than 7 seconds when the job is done after write down my btc adress in their payment option. Believe that?  Okay, if you're certain on that, then 5 is good. Now, open electrum.dat as a text file and you should find 5 uncompressed WIF private keys as plain text. e.g. ( from ETF's electrum.dat): 5JTvMqQhEeBQwcGBjPGsBod2XTsAQB7TWGgCMEpAdfsjVBcAze3 and 5K5rq6DKJ95VxjLnkf26uF2NBMdMh1fkrZupm5rCKNcqCNj9ivA(The array of 51-character strings that start with "5")Then in the latest version of Electrum, create a new wallet but during wallet creation, select the option " Import bitcoin addresses or private keys" instead. Paste the private keys one line each ( no need to prepend anything since those are uncompressed WIF). Finish the wallet and see if it comes up with a balance ( if it's the first time Electrum launched, you must wait for a few minutes). If it's empty, try the same procedures again with the private keys from old Electrum version 0.32 or v0.33. When you enter your seed in the latest version of Electrum, what is the "seed type" displayed as? I've tried with the test seed created by ETFbitcoin when he ran the 0.3.0 version... it shows as "Old":
It must be " old" since he's able to restore it to 0.30 since that old Electrum do not support the new seed version. |
|
|
|
-snip-
It's easy to recover with the console command: convert_xkey: - First, open the console tab ("View->Show Console" to enable the tab) of the two cosigners which you'd want to get the "master private key" from.
- Type getmasterprivate() on each console to get each wallet's master private key (you'll get 'zprv' since it's p2wpkh based from the screenshot).
- Type convert_xkey("zprv.......................","standard") to convert it into an "xprv" key, then copy the converted keys of the two cosigners.
- Lastly, create a new multisig wallet(s) using those two xprv and one xpub, just make sure that the xpub that you'll use isn't the xpub of the already-given xprv.
- Or Alternatively, create two cosigners using 1 xprv and 2 xpubs.
Notes from my test ( testnet: vprv=zprv | tprv=xprv): 2-of-2_Multisig_from_StandardSegwit_to_MultisigLegacy
-----------------------------------------------------------------------------------------------------------------------
SEED1: dwarf mixture waste width duck survey custom need dash erosion grit gap
vprv1: vprv9FvME8ocMUz3qdq2sF5tPUMJyT3cVKhuWMZpb7jtf68vhkVYMMz7ydixsdQtc9huXq1gtgNKypodofi9hYf4phck6CGT6bgqqeFfNJD5qBG
vpub1: vpub5UuhdeLWBrYM47uVyGctkcJ3XUt6tnRksaVRPW9WDRfuaYpgtuJNXS3SiwgNKiCqYa5RX6LS1VHjADm43jiy7ySFjTDu5rtQNwbH2qPTExX
tpub1: tpubD8wrmDW2CVam2WUb6BBENhpRCYGemQupFS8AJqzRKMBZS37rUSUav12Z1PgKr2Tv9kqwdd3RTupscyUnszQEbtFkXjN3wDBcWMJya4ExRWA
convert_xkey("vprv9FvME8ocMUz3qdq2sF5tPUMJyT3cVKhuWMZpb7jtf68vhkVYMMz7ydixsdQtc9huXq1gtgNKypodofi9hYf4phck6CGT6bgqqeFfNJD5qBG","standard")
tprv1: tprv8cFpcoTn47u693SoCXWdyJAJdWkic5iug8XP2Kx7u5PAbYs5r3ezjWQgqDVicLQ4iYn5PjBD4W6Y36V2G9q3EEFYMWsbvn3sJC8NbBS61jA
-----------------------------------------------------------------------------------------------------------------------
SEED2: effort pipe ask skate father decline desk deal fuel frown shoe shine
vprv2: vprv9GUMt1Grqo1in3GbqXJMn4c7YX7tZM2Bdch4xL5EjE6F7NAXTYWnbMqMn4dAwZJXRtyASBGx5Pi7aN6zetpiHw9HZXaXxfYcNqGT1rHGEz6
vpub2: vpub5VTiHWokgAa1zXM4wYqN9CYr6YxNxok2zqcfkiUrHZdDzAVg15q39A9qdKuPoqga3KDbz321gXxMTySZqNfBz9ppHSMSnYYay2UgQpvttyz
tpub2: tpubD9VsR5yGgocRxuvA4TPhmJ5DmcLvqSE6NhFQg4KmPV8sqenqad1FXj8wumuML9weeVz86Zj18xVVvjAJfdLTU4eK5iVbdtqo6SCNwx31qVD
convert_xkey("vprv9GUMt1Grqo1in3GbqXJMn4c7YX7tZM2Bdch4xL5EjE6F7NAXTYWnbMqMn4dAwZJXRtyASBGx5Pi7aN6zetpiHw9HZXaXxfYcNqGT1rHGEz6","standard")
tprv2: tprv8coqGfw2YRvm5StNAoj7MtR7Capzg73BoPedPYHTyDLV1AY4xEBfMEX5jehzwjzgccjYwE5qA511onssDVzghTn5prBgnqudqP9AEcPNEgF
-----------------------------------------------------------------------------------------------------------------------
1st address: 2N3sdmPzgVzY2P6ZpDN3tWcrC8wu2APFbax
----------------------------------------------------------------------------------------------------------------------- |
|
|
|
Whats the point of generating more and more receive adresses? 20 or 40?
Because the unencrypted ( no password) electrum.dat file will display 20 private keys if you generated 20 addresses in the receive tab. There's no " export private key" option in v0.30 but you can exploit that to dump the wallet's private keys. The point is to make sure that you will export enough private keys in case you've made as much transactions at that time. Exporting a few prvKeys may not be enough in case if you previously used 20 addresses before, right? |
|
|
|
-snip-
What is interesting is that it didn't generate the same addresses:
That's what I'm talking about in the previous replies, as stated in the release notes of v0.32+: /index.php?topic=5379817.msg58904925#msg58904925The key derivation was changed twice since v0.31 ( v0.31 and v0.34), thus, those old wallets' private keys can't be restored using the latest version. He'll have to get the private keys from the restored wallet in v0.30 and import them to the latest ( if still didn't worked, get the keys from v0.32~0.33). But it seems OP is having trouble following the guides so I'd to stop responding to his already-answered questions ( answered by the previous posts). |
|
|
|
-snip- Should I provide the blockchain network link that was given to me by Genesis Mining
That will certainly reduce the number of possible cause of the issue but will reduce your privacy a bit since everyone will be able to link the transaction to your bitcointalk account. If privacy isn't a concern, you can share the TXID here. If you don't want to, at least tell which " blockchain network" are you talking about since there are couple of " bitcoins" out there that don't belong to the Bitcoin network. In other words, in the " blockchain network", is it showing Bitcoin, Bitcoin Cash or other Bitcoin " insert-name-here"? if it's not " Bitcoin", then Electrum won't be able to access the funds since it's a Bitcoin-only wallet. If it's blockchain.com, it's not the "network" of anything, it's just a 'blockchain explorer' which has a database fetched from various cryptocurrencies' blockchains. |
|
|
|
anyways the wallet has only 0.00000275BTC (not even sure if it covers the price of a coffee cup at McDonalds at today bitcoin price value). But it's the learning and trying that is fun  If it's just for experience and test, I'd recommend you to use a wallet with known weak password instead so that you can easily confirm that your commands work without waiting for hours in each try. Just create a new wallet file in Bitcoin Core, set a weak password and get its wallet.dat file from the folder with the same wallet name in the wallets folder in bitcoin data directory. Then in BTCRecover, just assume that you don't know some of the characters in the password and try to bruteforce it using the available methods. |
|
|
|
-snip-
Guess what i'm looking for is a kind of limiter on a wildcard.
You can use --min-tokens 5 --max-tokens 6 plus PawGo's suggestion above to limit the tokens to 5 to 6 and since each characters are tokens, it wont reuse them. But it will still try ABCDE, ABCDEF.... UVWXYZ; besides that's what bruteforcing using random charcters is all about if you have no idea about the possible characters. Otherwise, exclude the character(s) from the token list. Token Counts: github.com/3rdIteration/btcrecover/blob/master/docs/tokenlist_file |
|
|
|
It is showing 2 weeks and it has taken a whole week to get where it is. -snip-
Based from your other thread, it seems like your node is already synced, right? Then the " 2 weeks" that you've seen was most likely 2-weeks-worth of blocks and not the estimated time. |
|
|
|
OK, finally Armory has noticed Bitcoin qt. It started syncing, which took forever. After it downloaded ~270 GB of blockchain to my HDD, I ran out of space. So I started deleting the oldest part of it and did it a few times to keep it going until the end. No I got 229 GB of blockchain on my 270 GB HDD.
-snip-
A 270GB HDD wont do, Armory requires the whole blockchain in your disk which will require about 400GB of data. Even if Bitcoin Core is fully synced with pruned blockchain, Armory won't be able to build its database from the pruned blocks. |
|
|
|
-snip-
Thank you for your suggestion, I didn't know this was possible. I have been using the -datadir option to point my secondary drive that would be large enough to hold all of this, but I did not realize you could "open wallet" that way.
The menu " File->Open wallet" is just for loading wallet.dat files from the wallet directory, not a replacement for -datadir start parameter. The main use of it is for opening multiple wallets or loading an existing/backup wallet. |
|
|
|
|
Show Posts
