If you just want a lightweight wallet that doesn't require you to have Bitcoin Core installed and running... but is also relatively secure if used properly, I'd suggest Electrum ( https://electrum.org/#download). It is easy to use, actively maintained and can also be used in an Offline/Online two computer setup if you want... Hardware wallets are good, if you don't mind the cost of purchasing one.  |
|
|
|
I took the liberty of hacking up a small python script that will take a text file of HEX privkeys and convert it into a text file with WIF privkeys... It will convert the hex to both "uncompressed" and "compressed" WIF keys, so you shouldn't miss any addresses. So you can simply run the script and then copy/paste the WIF keys into Electrum  import bitcoin
with open("hex_keys.txt","r") as f:
content = f.readlines()
# you may also want to remove whitespace characters like `\n` at the end of each line
content = [x.strip() for x in content]
f.close()
outfile = open("wif_conv.txt","w")
for x in content:
outfile.write(bitcoin.encode_privkey(x,'wif')+"\n")
outfile.write(bitcoin.encode_privkey(x,'wif_compressed')+"\n")
outfile.close()
NOTES: - You need the "bitcoin" library... ie. pip install bitcoin - hex_keys.txt should be a text file that has one hex key per line... like this: 1c2448d1a829c3f0c363f5e1d77a72cbd85ed1e9b4405eb5c160945db3a21ba001
f9d606ff0d9474483bde36a711f1c41896122056cc7e7a23b05b3e68438165da01
a5f2143180073849ec38a4936aceecde398e031b57a17aad20194b6132d0612101
64c85fc1473a8ea297e3c65a68b9fc2a1ac64c966111f8c7d0f5abfe8b574ad501
93917a448caecfe50e0850880edea56e1e5202bfdd6a68e32e049ab535ca000f01
Script will output "wif_conv.txt" which will contain both the "WIF uncompressed" and "WIF compressed" representations of those hex keys: 5J2gRZtwPeMHgjakdLL839Xn5pLBdNTKDBeB5uHDJTcwYaL5Tvb
KxAR1SCF4wrYeNwyZNKQ4UeqzFufuXh9Nmy5WdkZJ4VdjsSM3GRv
5KiKJpBHXnRARET7KvQtYvSspTGjazcV1y4yxkbrXkSdCQL8DCR
L5bModEPxsTeZxNEvWkSXtuDJSxSy3HcfGUaR5Sqcik6kroMm4pQ
5K5NSTHgcdiizKawaczdXm7nnyWPk2seZcMpsqfGkW3peZ2rtbX
L2nHdM2drH5AL12ouPsNEmiy7vQjNwGYnw4vKPmvX1DTJKS6HVUX
5JafwWRx3dUUpX4ZFQv93DHrkKFkkyYWSWSWdRV4oZmqF3sxM6a
Kzbcsau7xbzHnjghLcZYUmFQaBa896a4wawbmm4snXesvaSMjW5e
5JwH1pa4KBjJr2zu2zCHkHQafShkQbf7kv2k3xJu2T7hTbbM9rQ
L2AZgcxudGMjmRpYfmSpv3R5agSrb9yEpq4h237zdQGZa4bvBM6t
|
|
|
|
really i don't want to use old seed, you're right. I want to create a new seed from ledger/trezor and make a transaction from my electrum wallet.
But i want to do this for each electrum wallet i have.
What you could do with the Trezor/Ledger is use different passphrases to generate a different BTC wallet for each Electrum wallet you have. The passphrase effectively acts like a "25th word" for your seed... and allows you to generate completely different wallets based off the same seed. some references: https://ledger.zendesk.com/hc/en-us/articles/115005214529-Advanced-Passphrase-optionshttps://blog.trezor.io/hide-your-trezor-wallets-with-multiple-passphrases-f2e0834026ebAlternatively, you can setup multiple "Accounts" within your Trezor/Ledger wallets... and each account could act like your separate Electrum wallets. Each account has separate addresses/coins etc... but are all able to be recovered from the one seed. |
|
|
|
Thanks,
Is it correct that downloading and installing the node Bitcoin core takes days? Is there another way?
regards,
Paul
In a word, NO. Armory absolutely MUST have a fully synced Bitcoin Core to be able to function properly. If you have sent coins to an address in your Armory wallet, the only way you can get them back out is to either install Bitcoin Core and let it sync up fully... OR you will have to manually export the private keys from Armory and then import them into a different wallet. |
|
|
|
Did you happen to setup Bitcoin Core to use a "non default" datadir? If you look at "Help -> Debug window -> Information" in Bitcoin Core, what is the datadir listed as? is it "C:\Users\Me\AppData\Roaming\Bitcoin" or is it something else? -INFO - 03:47:57.579: (..\DatabaseBuilder.cpp:134) scanning new blocks from #35335 to #35334
It seems that Armory can only find 35335 blocks... so either Bitcoin Core ISN'T fully synced up properly... or Armory is looking in the wrong directory for the Bitcoin Core blocks. |
|
|
|
if it is a .zip.aes, then that is an encrypted zip file backup... according to the multiBit HD documentation: https://multibit.org/help/hd0.4/backups.htmlThe zip file backups are encrypted using a key generated from the wallet words... so if you don't have your wallet words, there is no way to actually decrypt those backup files  Pretty much ANY of the .aes files you can find will require either the wallet words (backup zips) or your wallet password (xxxx.wallet.aes wallet files) |
|
|
|
|
Is it possible that you've opened an "old" wallet and not the new one you thought you were creating?
What happens if you go "File -> Open"... do you see multiple wallet files listed? (NOTE: by default this will NOT have a .dat or .wallet extension, they'll just be called "default_wallet" or "wallet_1" etc)
|
|
|
|
Most likely just an issue with Jaxx... it seems to have a lot of bugs/issues. You can try and contact Jaxx support and ask them why their wallet shows two different balances (I suspect their answer will be, reset your cache  )... |
|
|
|
Here's the command I'm using in cmd, followed by the return I'm getting:
C:\Users\jackg>C:\Users\jackg\Downloads\pywallet-master\pywallet-master\pywallet.py --datadir=K:\Bitcoin --recover --recov_size=2000000 --recov_device=K:\Bitcoin --recov_outputdir=C:\Users\jackg\Desktop
Starting recovery.
Can't open K:\Bitcoin, check the path or try as root
Error: (13, 'Permission denied')
recov_device paramter sould be a device. in linux /dev/sda or something, in windows maybe "K:"
It is most likely this... pywallet doesn't let you scan a directory or file... you need to give it a device identifier and it scan the device... my suggestion is to get a smallish usb stick (prefer 1 GB or less), to minimise the "scanning time".... wipe/format it and then put ONLY your wallet.dat on the usb stick. Let's pretend that Windows has mounted your 1GB usb stick as the drive letter "X"... (replace "X" with whatever drive letter your system uses for the usb stick)... your command should be: C:\Users\jackg\Downloads\pywallet-master\pywallet-master\pywallet.py --recover --recov_size=1Gio --recov_device=X: --recov_outputdir=C:\Users\jackg\Desktop
NOTE: --recov_size should equal the size of the usb stick... 8GB stick = 8Gio, 4GB stick = 4Gio... I have no idea why the pywallet author choose this format?!??  |
|
|
|
Ah sorry I used the Bip39 mnemonic program recommended by coinomi. I used it for bitcoin cash and there were about 20 keys so I scanned them all, lots had nothing in, a couple had a small amount and one had the majority. Nothing like this though.
Did you try changing the "external/internal" value from 0 to 1 to generate your change addresses as well? Try that and scan through a few of those addresses... ps. the BIP39 mnemonic tool will generate an infinite number of addresses (at least, until your PC runs out of memory) Unless you have made thousands of transactions, I doubt your coins in receive or "change" addresses are likely to be further down the list than 100 or so |
|
|
|
|
-zapwallettxes removes ALL transactions from your wallet history (not just unconfirmed ones)... it then usually forces a -rescan on restart to rescan the blockchain for your "confirmed" transactions, however you stopped it, so it may not do that now.
So, you should try and start Bitcoin Core with the -rescan option to force a rescan of all your transactions. Assuming your Bitcoin Core is fully synced, then it should show your correct balance once it is completed.
|
|
|
|
No No
So regular bet is for example martingale 1sat 49.5 and 100% increase on loose
i there will be 2 over 99% in the row i wish to bet 10% of the balance opposite direction on 99%chance as there is low chance of getting the third one.
So the script should monitor for >99 and <1 and act if there is 2 in the row.
than it should count how many of this hi or low strikes was and let say after 5 it should bet only if there is the row of 3
Ahhhh ok, yeah... that makes way more sense! You're looking for clusters of <1 or >99 rolls... and then wager 10% of current balance on the opposite, hoping you don't get 3x "<1" or ">99" rolls in a row. But you're also wanting to count these clusters... so after 5 clusters, change so you only bet 10% if there were 3x "<1" or ">99" rolls.. well almost
it looks like it waits one bet before the correct bet i do not know why?
anyone knows why after 2 bets i am looking it does 3rd bet on 49.5% and then it does the 99% bet instead o directly after?
It's because the check for highCount >= 2 is effectively being done BEFORE the checking of the previous roll... so, what is happening is that the script is checking if highCount >= 2... then it actually checks the previous roll and increments the count... it should be the other way around and increment first and then check... like this: basebet=0.00000001
nextbet=basebet
chance=49.5
highCount=0
lowCount=0
previousbetBackup=basebet
function dobet()
if lastBet.Roll > 99 then
highCount = highCount+1
else
highCount = 0
end
if lastBet.Roll < 1 then
lowCount = lowCount+1
else
lowCount = 0
end
if highCount >= 2 then
bethigh = false
nextbet = balance * 0.1
chance=99.0
else if lowCount >= 2 then
bethigh = true
nextbet = balance * 0.1
chance=99.0
else
chance=49.5
if win then
nextbet = basebet
else
nextbet = previousbetBackup*2
end
previousbetBackup = nextbet
end
end
|
|
|
|
I think 99% bets are not even allowed on most sites right?
I think you got it back to front... and they're wanting to wager 10% if there are 2 rolls in a row under 1 or above 99... then wager on the 1% chance bets... not on the 99% chance bets ie. Roll 1 = 0.74 Roll 2 = 0.87 Roll 3 = wager 10% of balance on chance = 1, bethigh = false (ie. bet low) or Roll 1 = 99.4 Roll 2 = 99.87 Roll 3 = wager 10% of balance on change = 1, bethigh = true (ie. bet high) |
|
|
|
|
I think that Pywallet also works with the Litecoin wallets... so theoretically you can just do the same thing for the litecoin wallet files... then just load the recovered wallet.dat into Litecoin Core instead of Bitcoin Core... But don't quote me on that...
|
|
|
|
|
Which version of Electrum are you using?
If it is v3.x you need to use a slightly different menu selection... it is NOT "File -> New\Restore -> standard wallet -> Use Public or private keys". This requires a "Master Private Key" (aka "xprv") to generate an HD wallet.
Instead, you should use "File -> New\Restore -> Import bitcoin addresses or private keys"... this allows you to import private keys in WIF format.
|
|
|
|
print("Privkey: " + bitcoin.encode_privkey(privkey, 'wif_compressed'))
hmmm... I'm wondering if this is the issue... My script is assuming that the wallet has "compressed" keys... it's possible your wallet might have "uncompressed" keys? Seems that the private key checksum is failing when the script is converting the binary private key into WIF format... |
|
|
|
|
Any update?
Did you manage to get the recovered wallet loaded into Bitcoin Core?
|
|
|
|
thanks both for your answers, but i don't understand why this choice.
I understand that the hwwallet can't use the same seed on my "old" electrum wallet, but why don't create a two different seed if i import two different wallet?
i think it's more safe (from malware attack) have your coin splitted in two wallet
It's a design limitation of current hardware wallets. They only allow for one seed per device. All wallets for each currency are derived from the same seed. You simply can't have two different seeds at the same time. In any case, importing a seed generated somewhere else into a hardware can actually render the security of the hardware wallet useless as there is a possibility the seed has been compromised before it even gets on the hardware wallet. The safest solution is to let the device securely generate its own seed, so that it is NEVER on any device other than the hardware wallet. Theoretically, a seed generated completely offline using dice etc could probably be just as secure, but a seed generated by a software wallet on a computer that is online should never been used long-term as a hardware wallet seed. |
|
|
|
^^ Yes it was electrum - But when It never showed up in electrum so i exported the key and imported it to BC.I and now its like disappeared lol.
"exported" keys are not removed or deleted by Electrum. They are still kept in the Electrum wallet. Exporting simply displays the private key on the screen and/or allows you to save it to a file if required. Find the Electrum wallet that contains this address and you will be able to export the private key again. |
|
|
|
|
Show Posts
