Try to copy a random xpub and paste it somewhere else, for example: xpub6DBNLPKQ6DMSjMaateX5TyzgwDgoDFyxNokKQa75EMp3KkEWHm2GkM4Madx5YZUrZ49onJUYW73PSo3zRDh4N5qVKvug6WCrhmz6dFzZKr1 Check every characters if something changed because there may be a variant of " clipboard hijacking virus" that changes 'extended public keys' instead of addresses. If not and you have no idea where you might have copied it, try to link both of your hardware wallets to Electrum, both Trezor ( latest firmware) and Ledger should have " native segwit" option when creating a new wallet using a hardware device. |
|
|
|
I'd suggest you to use the coin control as HCP suggested, You can use 'SHIFT+Left Click' to select multiple coins ( UTXO) at a time, you can make 2 transactions each using half of your available coins. I can live with the fact that I still pay 86 USD fees for all 1000+ inputs if I use 2 sat/byte. Maybe I consolidate them with 1 sat / byte then I "only" have to pay 43 USD ^^
Or pay 1.2sat/B, it's higher than 1sat/B but not as expensive as 2sat/B  It's possible by editing the 'absolute fee' above the fee slider next to the equal sign of the 'Target fee' and 'bytes' in the advanced preview. |
|
|
|
AFAIK, it contains a mini private key format. If so, this post from 'stack exchange' may be the one you're looking for if you are planning to sell the bitcoins in an Exchange: Re: How can one redeem a Casascius Physical Bitcoin?The linked reply has every information and the links you need. -typo- |
|
|
|
|
Is the other PC's Electrum connected after you restored the Seed phrase?
The connection icon below should be a green circle.
Because if it's newly installed, there may be a delay before it can display the wallet's balance.
Or if the version is too low, it will not connect to the network at all.
You can also check the address tab (View->Show Addresses) if your address is listed there.
|
|
|
|
|
Good, it says "ok", then the BIP39 seed is valid.
Next is to match the derivation path to your addresses, do they start with '3' or 'bc1'? After inputting the seed phrase, there'll be a "Script type and Derivation path" window.
On that screen, select "native segwit (p2wpkh)" if your addresses start with 'bc1', select 'p2sh-segwit (p2wpkh-p2sh)" if they start with '3'.
If it's legacy (starts with '1') and Electrum is connected (green connection icon), then the seed phrase is just from an empty wallet, could be from a wallet with unique derivation path or other issues.
|
|
|
|
|
Try clicking the option under the box where you input the seed phrase, then tick "BIP39 seed".
After pressing 'ok', if it says "BIP39 (checksum: ok)", your seed is a valid BIP39 mnemonic phrase and you may continue.
If "BIP39 (checksum: failed)", there's something wrong with the seed phrase and you'll likely need to provide some info like the Electrum version when it was created and other non-private stuffs.
|
|
|
|
satoshi supposedly sent the first bitcoin to Hal Finney so it has to be in the first block! Blocks are still valid even without any transactions in it aside from the coinbase transaction. Look, the genesis block nor the next block doesn't contain any additional transactions: btc/block/0 and btc/block/1Here's the block where the transaction that you're talking about is: btc/block/170Im just wondering if there is a list of all wallets which are Satoshi Nakamoto related? ... Perhaps from block 0 to 32688 ?....
Would help for a project im doing, ... havent been able to find any list so figured i would ask here ....
No one can tell which is which exactly that's why there is no reliable list. Some of the old block's reward could be an early adapter's bitcoins not Satoshi's. |
|
|
|
Maybe we can back up the discussion a little bit and you guys could help me understand the different formats we are dealing with.
Using 4.0.9 I can choose to "export", and "copy to clipboard". This gives the transaction encoded in base64? And if I choose to "export to file" that is same base64 converted to ASCII?
No for the second part; if you open the .psbt file using a text editor, it will just assume that the contents are any of the text character encodings and will display non-readable data. I guess that it's a binary encoding: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki#EncodingBut the encoded data is the same whatever option you've used to export the partial raw transaction. |
|
|
|
Can anyone tell me anything more about how the latest release handles saving unsigned transactions to a file? I like to manually verify all the outputs in the unsigned transaction file before I allow the file to be copied to a blank thumb drive. (And then loaded on the offline wallet to be signed.) Is there anyway to validate the contents of this file using something external to Electrum before signing the transaction? I tried to open the file but it looks like encrypted contents now. The documentation does not appear to be updated since this was changed.
It's Base64 encoded... and the data is in "Partially Signed Bitcoin Transaction" aka PSBT format... You can read about the PSBT format here: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawikiIf he use " Copy to clipboard", it will result with a Base64 string; IDK for the " Export to file" but it looks like a 'binary version' like he said. @ 77Network Either (1) use the " copy to clipboard" and paste it on a text file then you can use Bitcoin Core ( even offline) to decode it using the command: decodepsbt. Or (2) Sign it first ( then the exported file/text back to the online machine will be in HEX) and before you broadcast, you can decode it using your usual tools. Of course, all of this are after the upgrade. |
|
|
|
So I installed this 1st on the 28th of Nov https:raw.githubusercontent.com/specnimo/specnilon/main/electrum-4.0.5-setup.exe
This is the correct Github repository of Electrum: https://github.com/spesmilo/electrumSorry to say that you're funds were hacked and bitcoin transactions are irreversible. |
|
|
|
For those who've posted late and planning to post: the issue is already solved. The OP said it in this reply: Thank you for all the suggestions...
The problem has been resolved by contacting the support from Indodax ...
|
|
|
|
-snip-
No. It is not working. But it will be not working the last time. Next time I get it to work I am done and move the coins to another client. I am stuck at scanning transaction history forever. I mean, this few times Armory worked after spin up, I can count on one hand. This wallet is a joke, potentially dangerous. I have enough. O...kay.. If it worked just recently then I assume that your wallets have saved the latest transactions. So just do " HCP's export tutorial" link in my post and import the WIF ( base58) private keys of addresses with balance to Bitcoin Core ( if the "standard client" is what you mean by "regular client"). You can also share the armorylog.txt from the datadir so the developer could see the actual issue. |
|
|
|
Is Armory working ( just acting up)? Then the best solution is to simply send the funds to Bitcoin Core through a transaction. Next option is to Import the private keys to Bitcoin core through core's console/command line using importprivkey ( how to use). You can get the address' private keys in Armory's " Wallet Properties->Backup This Wallet->See other Backup Options". Here's an 'export from Armory' guide with pictures by HCP: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691 |
|
|
|
-snip-
8. When trying now to login to wallet B I get the verification mail, but when I press the link in it I get an error - cannot decrypt wallet
9. I've tried to use the recovery phrase - I've had some issues with that too, because I have 17 word phrase, not 12.
10. After another mail to the company, they replied that my wallet is a legacy wallet and sent me a link for legacy recovery, that accepts 17 words.
11. My recovered password is the same as the one I have, but I still can't log in. -snip-
What's the actual error? Because if the password is incorrect, it would be: Error decrypting wallet. Wrong password If you're sure that the password you've been typing is correct, then the issue must be their server's encrypted copy. Try to use a different browser, PC or clear your browser's cache; if it didn't work, Blockchain.com is the only one who can help you with this. FYI, a user will be prompted to enter 2FA code ( if enabled and email verification if necessary) even though the password is incorrect, the error will appear after. |
|
|
|
As these addresses / private keys are generated there is always a probability that another address was already generated at a certain time in the past, as a matter a fact, I searched for one address I generated via bitaddress.org and I could find 2 of them on blockchain.com transactions explorer
FYI, the two results on blockchain.com explorer are for two different blockchains that support the same legacy address format, namely, Bitcoin (BTC) and Bitcoin Cash (BCH). Plus most block explorers will show an address whether it's used or not; it just means that it has a valid checksum if there's a search result, the address is invalid if there's no search result. It does not indicate that the address was already generated by someone. |
|
|
|
Here's the information that you need including other FAQs: https://electrum.readthedocs.io/en/latest/faq.html#where-is-the-electrum-datadir-locatedBTW, Electrum will display the name of the last wallet that you opened if the " config" file inside the data directory is intact. If you have links to tutorials to help me understand how all this works. I would appreciate it because I understand NOT MUCH...... except that I need to keep the seed safe. I would feel safer storing my BTC on an online service but everyone says it's a bad idea... Right?
It's for you to decide and it seem like you're already aware of the risks. If you decided to do that, make sure that the file is encrypted and if you like, disguise it as another type of file ( like .jpg) since you can freely add an extension. And couple it with a bunch of .jpg images, and you have a hidden wallet. Example ( testnet) - with '.mp4' extension:    |
|
|
|
I was using a new app to purchase BTC I hadn't before Binance and somehow I ended up purchasing ETH and sending it to my Coinbase BTC address
There is an upvoted post in reddit about a Fake Binance app ( posted 1day ago), check if that's the one you've downloaded. Link to the thread: linkYou post alone suggests that you were scammed by a fake app. Ethereum address and the Bitcoin address' formats are too different to be mixed up by an app, let alone from a big company like Binance. |
|
|
|
Looks like the issue was solved, figured due to the address' blockexplorer history. But, anyone love to see some details? Here's some: It appears that he had replaced this 1.182sat/vB fee rate transaction: 27b60a104906256079236fafb7d62fb37208a26458ebd2258abcffc77a3d6453with 5a624e5bcee5161217cf2d4dbe922c66b61d82d8fbc3820e2cfd4134f09d3afa that sent back the coins to his wallet, using the same address as the inputs. Then somehow the same inputs were used the first time he tried to send to bc1qk0fdr6cq8lt7qdlyl045nvjqmalkkzvfqs72n0. I suspect that the fee rate is just suggested by Bitcoin core's estimation. "inputs": [
{
"addresses": [
"17mMVesSaC6kL4F8g5bA13u5iEvWc4ytND"
],
"age": 601104,
"output_index": 0,
"output_value": 472021,
"prev_hash": "f43cbaccdf447369a4d9dd231dc087ca02b0526e00d91f0561a9544f4c90cc99",
"script": "473044022077154e42f100048dac1273bf624ed5d51abc696002fa440792eb59a9 -snip-",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
},
{
"addresses": [
"17mMVesSaC6kL4F8g5bA13u5iEvWc4ytND"
],
"age": 590503,
"output_index": 1,
"output_value": 678529,
"prev_hash": "b4e218497a2500b99f1f849c744143af46fe7fd61ed381d195fd4213a2e714c3",
"script": "47304402206d34e2d861ddce65adb9e676db7375fddf734f2eaa76 -snip-",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
},
{
"addresses": [
"17mMVesSaC6kL4F8g5bA13u5iEvWc4ytND"
],
"age": 585899,
"output_index": 0,
"output_value": 560621,
"prev_hash": "40736fe05bd2389d0a2a726a8acd747cd2c7ce84a3d98d497f247dff42dfa69d",
"script": "473044022018827c1ea7924ddc1405732d5163ac75c293ef9b1db881927f7a247916be6a -snip-",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
},
{
"addresses": [
"17mMVesSaC6kL4F8g5bA13u5iEvWc4ytND"
],
"age": 628291,
"output_index": 0,
"output_value": 5894754,
"prev_hash": "5148f6c2205a63c7ad768a50a32c12ef4828020fdbb6af7157947c1bcec23012",
"script": "47304402204ecb7886d6f97e8524ddeb12a318bef5eb40228beb78ac867d5d0e9df8fab8d8022 -snip-",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
},
{
"addresses": [
"17mMVesSaC6kL4F8g5bA13u5iEvWc4ytND"
],
"age": 601120,
"output_index": 1,
"output_value": 472544,
"prev_hash": "f945edc32db2121b857483cd8c44a10056ca7c9cb6d34dfa1d0cc51507d8afdf",
"script": "4730440220670f430fd7ac269731d3750e888b7b3736bc9ac66c613f7fb2bd79abf2cb2abe02201fb8dc3 -snip-",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
},
{
"addresses": [
"17mMVesSaC6kL4F8g5bA13u5iEvWc4ytND"
],
"age": 601104,
"output_index": 0,
"output_value": 431559,
"prev_hash": "cc1eb9247649a6663b3053781da61c671580f14748d070bbcbb084549d00ac91",
"script": "47304402201f9c65a8052bba8930ec5ee22d26f1e34c98228b958fd17f5cd4d008ba037130022015f2 -snip-",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
},
{
"addresses": [
"17mMVesSaC6kL4F8g5bA13u5iEvWc4ytND"
],
"age": 577958,
"output_index": 0,
"output_value": 2355860,
"prev_hash": "2b81fb9e1647d8b3621b82512f8fc6f66c0ea85e2e2603e7f2a315c4f36a238e",
"script": "47304402205a39f17302c16faf40acf82054655649fbd8e7d9432cf943e14486d6b19aadbb0220361a80 -snip-",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
}
],
"lock_time": 662285,
"opt_in_rbf": true,
"outputs": [
{
"addresses": [
"bc1qk0fdr6cq8lt7qdlyl045nvjqmalkkzvfqs72n0"
],
"script": "0014b3d2d1eb003fd7e037e4fbeb49b240df7f6b0989",
"script_type": "pay-to-witness-pubkey-hash",
"value": 10864580
} But the next attempt used the consolidated output of the previous transaction instead, that solved the issue as seen here: 17mMVesSaC6kL4F8g5bA13u5iEvWc4ytND |
|
|
|
-snip-
All I can say is, there's no other way to increase the fee since it's not marked as "replaceable" (RBF)
and the change is too small to do a reasonable CPFP unless you have other available coins (UTXO) to spend.
Thanks for your effort sir, but in the end what do u think, waiting long time, infinite time? Not really, it usually clears within a week but this time, the " low-mempool-season" only took a few from 1sat/B transactions probably because of the bull run plus the strangely slow block rate this past few days. If you're lucky it could be mined by Saturday or Sunday. As I mentioned above, if you have another UTXO in your Electrum, open 'coins' tab ( View->Show Coins) aside from that transaction's change, you can do a manual CPFP by using coin control. CTRL+Left Click to multi-select the coin(s) you want to use then right click and select " spend" ( don't forget to add the stuck txn's change as well), there'll be an info below about the coins you've selected; finally create a transaction using the send tab with your own address as the recipient. Set the fee considerably high because the parent's size is too high, at best, that could set the total fee rate of the parent+child higher than 2sat/B. But I'd suggest you to just wait it out. Lastly, read the posts above about bitcoins denomination. |
|
|
|
I have many bitcoin core wallets from years ago (encrypted). How do I check their balance from command line? Loading each one in bitcoin core GUI is a painfully slow process that will take weeks/months.
The command line will be as slow as the GUI when it comes with scanning a wallet file once you've loaded it, so querying for the balance using Bitcoin-cli will have the same pace as Bitcoin-qt. At the very least, how can I extract addresses so I can check them online for their balance?
If they were previously scanned with balance and history, then there should be readable addresses after the string: name" when you open them with a text editor. But that won't show you the correct balance of the wallet, just a hint that it may be hodling some bitcoins. If the wallet has clear history ( eg. when previously used -zapwallettxes), all you'll see are 'jumbled' strings. |
|
|
|
|
Show Posts
