So what should I use if I have a paper wallet that I want to spend ?
It's the 'Cold Storage' option. However it's not the safest option since exposing the private key to the internet to spend it isn't really 'cold storage'. ( read the warnings in the reply above). Are you limited to mobile devices that's why you're inclined to use Mycelium? Do you have access to a PC? |
|
|
|
-snip-
@nc50lc archive has no file.
Seems like they've deleted the files from their archive as well, every timestamp has " no file" after starting the download. Try to use @HCP's BIP39 tool, it's a slight variant of iancoleman's but supports Electrum seed: https://github.com/HardCorePawn/electrumBIP39Of course, select the correct coin, then use BIP32 derivation path m/0 for receiving addresses and m/1 for 'change addresses'. |
|
|
|
I can not open the Dash electrum. But I have the 12 words seed.
But can you install it? If so, just reinstall Dash Electrum and restore your 12-word seed there, then do the steps I've given. Just go with the blockexplorer method since you cannot sync it to see which addresses have coins. |
|
|
|
If dash Electrum wallet is the same as Electrum, do this: - Go to "Addresses" tab (View->Show Addresses) and check which address(es) contains balance from your last sync.
If you think that the coins have moved, check each address with a blockexplorer. - After finding which addresses have coins, get their private keys by right-clicking on an address and select "Private key".
- Copy the key and use it to import your funds to another wallet (of course, select an import method that accepts private keys).
|
|
|
|
1. What is the difference between the "Add Account --> Single Address Account" and the "Cold Storage" options?
In Mycelium, The former creates a random private key and use it to derive all three address types. The private key remains in the device and the " SA account" will be saved in your account list. While " Menu->Cold Storage" is temporary, you'll only use an existing private key or seed phrase in that session to send its funds. After that session, the key will be deleted from the device. |
|
|
|
Thanks. what do you mean by the last part - that i need to create at least one new wallet in order for the wallets folder to be created, before I copy the old wallets over?
It's just because the data directory doesn't exist if Electrum haven't run at least once, it's same for the wallets folder inside it. If there's no wallet created yet, the " wallets" folder wont exist. The best route to export the wallet file to the new PC is: Run Electrum for the first time - close it without creating a wallet ( skip this line if you already did). Go to the newly created data directory, create " wallets" folder inside the data directory if it's not present, then paste the wallet file there. |
|
|
|
they start with U2Fs have some funds in there from way back not a lot but a few bits when I try to sweep them would not allow me to do so as the button is grayed out i have the key file as I have extracted it
Those are encrypted. Do you still have access to your Multibit wallet? If you do, make a new unencrypted private key export file by not ticking " password protect export file" when exporting the keys. If you do not have access to the wallet, you have to use other tools to decrypt it. Example: BTCRecover has an export-script that accepts MultiBit's private key export file, but I haven't tested it. Link: extract-multibit-privkey.py - from: github.com/3rdIteration/btcrecover/tree/master/extract-scriptsHCP also has a post with steps to decrypt encrypted PrvKeys export file: /index.php?topic=5304446.msg55964982#msg55964982 |
|
|
|
daymm thanks but it went over my head!.
You can try to create a " Feature Request" issue in Bitcoin's GitHub repository, here: https://github.com/bitcoin/bitcoin/issuesIf the developers will find it useful, they may consider implementing a " gross balance" feature. |
|
|
|
-snip-
How should I set the path? I don't understand the computer. Can you give me a detailed suggestion
Start by giving details like the command that you've used and the directory where you're looking for wallet.dat files. Since you got that error, then findwallet must be working correctly now but the given directory followed by " -i " is incorrect. example: findwallet -i "E:/appdata/bitcoin" |
|
|
|
How old of an electrum can you still use without it having problems? For example i mention the electrum version that i have on my windows pc that i installed and verified not that long ago. But how often does electrum have an update? Once every... how many months?
Not depending on months, it depend if there's a major bug in the version that you're using or if there's a new feature that you need from the latest release. You can refer to the release notes in my previous post to check what's changed. Now, it's safe to assume that your currently installed v4.1.5 can work without issues. Also when did people actually starting verifying electrum.
I can only guess based from the archived page of electrum.org. Ever since the start, they've added a simple checksum ( MD5 Hash) to check if the downloaded binary is the same as the release. But that's not the verification we're doing now. If archive.org's dates are accurate, they've started including signatures in 2013. electrum.org/download: March 2013 - MD5 checksum and signature electrum.org/download: January 2013 - just MD5 checksum |
|
|
|
-snip- But is that the same with electrum or you need to verify the hash each and everytime with electrum?
Electrum is different, It's in-app notification will only prompt you to download the latest version from the official website linked in the " update check". It wont be downloaded and installed by the app itself. It's basically the same as downloading a new binary that's not linked to your previously verified file. So it's still recommended to verify the new binary every time there's a new update. Now, do i need to update electrum again if i plan to use it?
It's up to you if you want the new version's features or need the bug fixes. ( release notes) |
|
|
|
-snip- Seems the recommended method is to use seed phrase to set up the wallets on the new computer, but how safe is it to do this if the computer is temporarily disconnected from the internet?
Regarding the third post's suggestion to use the actual wallet file, you can get it from " wallets" folder inside Electrum's data directory. Location: https://electrum.readthedocs.io/en/latest/faq.html#where-is-the-electrum-datadir-locatedIt's better than seed method since the labels and contacts wont be restored by the seed phrase alone. Reminder when copying the file: Make sure that Electrum isn't running while copying the file. Also, in your new PC, Electrum should be at least run once for it to create its data directory, then have one wallet to have the wallets folder or manually create one. |
|
|
|
Try to post it in your local language for better support. There may be some mistranslations if everything has to be machine-translated. See if your language is in this list: http://bitcointalk.org/index.php#5 ( local boards) |
|
|
|
Each wallet.dat file shows the btc amount but is there any way the bitcoin core shows gross btc of all the wallets that have been connected?
Just to be clear, since you're using BWT plugin in, are the " connected wallets" from Electrum? If so, then it's doable using this workaround: Create a " blank descriptor wallet" that will hold all of the wallet's master public keys. Importing each xpub key via " descriptor" can be time consuming but after setting it up, that specific wallet.dat will be able see all of the imported master keys' transactions and total their balances. These are the steps: - In Electrum, get the "Master Public Key" of the wallet that you want to import in "Wallet->Information".
- For Native SegWit and P2SH-SegWit wallets, you'll have to convert the zpub or ypub into xpub to be compatible with Bitcoin core
using the console command ("View->Show Console" to enable console tab):convert_xkey(xkey="zpub6YBr.....XXZ3DysZgsPX",xtype="standard") - With the xpub, create a parent descriptor by following this format:
For P2WPKH (receiving): "wpkh([00000000/0]xpub....YOUR_XPUB_KEY......./0/*)"
For P2WPKH (change): "wpkh([00000000/0]xpub....YOUR_XPUB_KEY......./1/*)"
For P2PKH (receiving): "pkh([00000000/0]xpub....YOUR_XPUB_KEY......./0/*)"
For P2PKH (change): "pkh([00000000/0]xpub....YOUR_XPUB_KEY......./1/*)"
For P2SH-P2WPKH (receiving): "sh(wpkh([00000000/0]xpub....YOUR_XPUB_KEY......./0/*))"
For P2SH-P2WPKH (change): "sh(wpkh([00000000/0]xpub....YOUR_XPUB_KEY......./1/*))" If your Electrum wallet is Native SegWit (P2WPKH), create P2WPKH receiving and change address descriptors.
- Get its checksum by using Bitcoin Core's console, use the command getdescriptorinfo
For example: getdescriptorinfo "wpkh([00000000/0]xpub....YOUR_XPUB_KEY......./0/*)"
Take note of the "checksum" among the results.
- Now, it's ready to be imported to Bitcoin Core.
Create a new blank wallet in Bitcoin Core by ticking the boxes: "Disable Private Keys", "Make Blank Wallet" and "Descriptor Wallet".
- After creating the wallet, go to Bitcoin Core's Console (Window->Console), select the newly created wallet from the drop-down menu above.
- Then import the descriptor by using this command:
For receiving addresses:
importdescriptors "[{\"desc\": \"wpkh([00000000/0]xpub....YOUR_XPUB_KEY......./0/*)#2r29ev5v\",\"timestamp\": \"now\",\"watching-only\": true,\"internal\": false,\"range\": [0,999]}]"
For change addresses:
importdescriptors "[{\"desc\": \"wpkh([00000000/0]xpub....YOUR_XPUB_KEY......./1/*)#mh0yyey5\",\"timestamp\": \"now\",\"watching-only\": true,\"internal\": true,\"range\": [0,999]}]" The example checksum are "2r29ev5v" and "mh0yyey5" that are next to the descriptors; the only difference is "internal" flag, it's set to 'true' for change address; and lastly you might need to increase the end range depending on the wallet's usage.
- Just repeat the steps to each of the connected Electrum's master public key, except the "create a new wallet" step.
Import the other descriptors to that same wallet.
-edited the title for search engines- |
|
|
|
-snip-
We're in a forum where conversations are written not spoken, So words like " wrong" or " no" will sound harsh most of the time even though the poster meant it to be read calmly. As long as there's no words like " Id**t", " S***id" or similar, I'd not consider a reply unpolite. Overall, it's entirely based from the reader's perspective. Example: " No, You're wrong" can be perceived by the reader as " No! You're wrong!" even without punctuation. A boy will one day grow up to b a man.
Exactly. |
|
|
|
-snip- Just wondering if it no longer works in windows?
I have a Windows10 PC ( 1903) and jackjack's pywallet works with Python 2.7. Here's a screenshot ( open in new tab to view full size):  |
|
|
|
-snip- I mean, if I understood correctly, all you have to do is run the hash function with the desired outcome, in this case, with the leading 17-19 zeros.
You can't do that because all Bitcoin nodes will check if your " winning" block header's hash is valid by checking if that block's SHA256(SHA256(Block_Header)) hash matches. Since you've used a different hashing algorithm, they will come up with a different result. |
|
|
|
-snip-
What's beyond my knowledge is why I change the bitcoin blockchain dir to my external drive at e:\ but the log file still shows the original. It's like the GUI changes are registering.
Any other suggestions?
Maybe you've created the file as " armoryqt.conf.txt" instead of " armoryqt.conf" that's why it's not recognized by Armory. Windows hides the file extension by default, check if it's ticked in File Explorer's setting: Go to the directory where 'armoryqt.conf' is, click " view" and tick " file name extensions", after that, extensions like " .txt" will show up; if your config file has that extension, rename it so it will be " .conf". |
|
|
|
Is it possible to receive a LN payment on Electrum if im only online on a watch only wallet on my phone?
I asked few ppl on other forums and nobody knew/answered this, lol...
It works on the PC version so it might work on the Android version. The steps (for the Desktop version) are: - In your watching-only wallet copy of a 'Native SegWit' "bc1" Electrum wallet, go to "Wallet->Information" and enable lightning.
- Restart Electrum, then go to "Channels" tab, click "Open Channel" and fill-up the fields.
- After the last step, Electrum will prompt you to sign the PSBT (unsigned txn) using the main wallet just like what you're doing with the usual transaction.
- After broadcasting it, the channel should be established after 3 confirmations.
The steps (for Android version) should be similar [last steps untested]: - In your 'Native SegWit' "bc1" watching-only wallet, tap the wallet name above to view its information.
- In the wallet info, tap "Not enabled" next to 'Lightning:', then read and accept the warnings, after that, Lightning is enabled.
- Go to "Menu->Channels" and open a channel (the rest of the steps are similar to the desktop version).
Note: The funds in your channel is separate from your on-chain funds so it's not protected by your cold-storage set-up. Also, you cannot immediately be able to receive through lightning since you need to gain " inbound capacity" to do so; one way to gain it is to use " reverse swap" which is available in the desktop version by clicking the switch " ⇄" button in " swap", try tapping values/names in the Android version. Swap/Reverse-swap costs on-chain transaction fee and the back-end's service fee though. |
|
|
|
|
Show Posts
