... ledger live has no way of generating legacy addresses anymore (lame)..
Ledger Live, on the whole, is relatively lame...  However, you can still use Electrum to generate Legacy addresses if required. As a bonus, if you do that and create some "transaction history" on your Legacy account (ie. you receive at least one transaction to one of your Legacy addresses), then Ledger Live will be able to find your Legacy Account when you use the "Add Account" feature in Ledger Live (and it will then let you send/receive from it)... It just won't let you create a Legacy account with "nil" history (and it may not find the history properly if you did "weird" things in the Chrome app like selecting addresses manually from the dropdown list instead of using the "receive" functionality as there is a possibility the addresses you used are outside the "gap limit")  |
|
|
|
Think I have the seed, but have a few of them and am not 100% sure which is which or if I even have the right one for it anymore..   I'd say that not knowing whether you have the correct seed mnemonic backup is probably your biggest issue at this point... regardless of any device/wallet/firmware issues. At the end of the day, that seed mnemonic backup is your safety net... without it, you're asking for trouble, even if you were running the latest firmware, up to date wallet software and using your device every day! Personally, I would make it my #1 priority to either figure out which seed mnemonic is the correct one, or determining that I don't actually have the correct backup and then taking steps to mitigate that risk (ie. create temp wallet, send all funds, reset device, create new wallet on device, send all funds from temp wallet to new hardware wallet) |
|
|
|
To be honest... It's more art than science. There are so many variables involved that it is pretty much impossible to say with complete certainty what a "good" fee is... do you need block confirmation? can you wait a day (or more)?  Is the network busy or are there only a few hundred unconfirmed transactions? Is it about to take 2 hrs to find the next block? Is BitMEX about to dump it's daily transactions onto the network? Is <insert "random" event here> about to happen that pumps/dumps the price and causes a flurry of activity on the network? Is today a day ending in the letter "y"?  Attempting to code a "catch all" fee estimation tool is going to be pretty difficult... like PrimeNumber7 says, you can either shoot "low" but end up with the potential to miss your time/block target... or aim "high" to try and meet your time/block target more often than not, but will likely end up "overpaying"... I have personally been caught out a number of times by "cheaping out" on fees... trying to be clever and hit the sweet spot of "minimal fee with reasonable confirmation time"... a block isn't found for an hour or 2... the transaction backlog builds up, fees go up... transaction gets "stuck" for 12-24 hrs... You get what you pay for, I guess  |
|
|
|
I'm searching for a bitcoin wallet supporting old version of android (4.3). Samurai and electrum don't. Is there any other open source wallets that do support it?
Is this the only and/or main device that you have/use? Or is it just a "spare" device that you were wanting to use for stashing some bitcoin? |
|
|
|
Afaik you can have any multiple of 3 greater than 0 and less than or equal to 24...
No. You can't have whatever you want if you want to strictly comply with BIP39.The BIP states: The mnemonic must encode entropy in a multiple of 32 bits. With more entropy security is improved but the sentence length increases. We refer to the initial entropy length as ENT. The allowed size of ENT is 128-256 bits.
Therefore only mnemonics with 12,15,18,21 or 24 words are "strictly" BIP39 compatible as they are they only seed lengths that comply with the ENT restrictions. Anything with ENT outside of that range does not technically adhere to BIP39. |
|
|
|
That is correct... for unecrypted MultiBit classic wallets... the private keys (in hex) are the 32 bytes after the byte sequence "1A4E08011220" However, if you can't find that byte sequence in the file and see some text towards the end of the file like: "org.multibit.walletProtect.2" then your wallet file is encrypted and you'll have to hope that the overwriting/corruption hasn't broken the file so that it can't be decrypted.  You can try using my "decrypt_multibit_classic_walletkeys.py" script from here: https://github.com/HardCorePawn/multibit_recovery (Requires Python 2.7 and a couple of dependencies installed, install instructions here). If the wallet file is unencrypted, it should just output addresses/keys... if it is encrypted, it should prompt for the wallet password and once the correct password is entered, will output the addresses/keys. If you get some sort of parsing error, chances are the file is corrupted. You might still be able to extract some keys if the wallet file was unencrypted, but if it was encrypted, then you're likely going to be S.O.L. |
|
|
|
It occurs to me that the wallet would be encrypted, I still have the paper where i wrote the password down. Is it possible I need to decrypt these 32byte strings and then check? Or does it not work like that.
As far as I'm aware, if the wallet file was encrypted, then the search for hex "3081D30201010420" (or 2001010420) likely won't work... that was only valid for unencrypted wallet.dat files. As far as PyWallet is concerned, I've had various success attempting to recover keys from "deleted" wallet files... sometimes it works, sometimes it doesn't I haven't been able to figure out the exact requirements for recovery, but if the wallet.dat was encrypted, it you don't have the correct passphrase, it won't be able to recover anything at all and you'll end up with an empty "recovered" wallet, even if it can "see" the deleted file. Have you tried using any recovery software on the disks to see if they can recover the wallet.dat files? If you can recover the file itself, pywallet might be able to dump the info from it. |
|
|
|
Yes, but addresses which contains BTC doesn't show up there, i checked one by one but those addresses were 0 BTC.
Then, as bob123 has already said, your wallet file simply does not have the appropriate private key to be able to spend those coins. Either they are on a "watching-only" address (ie. an address was imported into Bitcoin Core using the importaddress command... which means the transactions and balance for that address would show, but would not be spendable... or the file has been manipulated in some way, so that it contains the public key/address that has the BTC, but the private key does not match. If the wallet file is actually your old file, then it's most likely the importaddress scenario, if you bought or downloaded this wallet.dat online, then it is most likely the 2nd scenario and the wallet file is fake. |
|
|
|
The Website asked for a refund address(D) in which I gave them in case anything goes wrong! The refund has been sent to the address I gave them!
How did you provide this refund address? Did you send it on email or via an Instant Messenger like Telegram, Whatsapp, Skype etc? Or did you enter it directly into the website your ordered from? Do you have any record of the address that you sent them? I ask, because you need to confirm that the address you sent the vendor, is in fact the address they supposedly sent to the refund to. It doesn't necessarily mean you sent them the correct address, but it at least will rule out any shenanigans on the part of the vendor! If you can confirm that the address you sent, is the same address that is shown in the "blockcypher" link, then the vendor is most likely not at fault, and it's something at your end that has not gone right. In which case, you need to try and remember where you generated that address... did you do it from your blockchain wallet or from your Electrum wallet? |
|
|
|
Is it possible to have authentication codes of the same site across two or more 2FA apps at the same time? Yes, it is... I have Google Authenticator, Authenticator Plus and Aegis installed and running... I have the codes for several sites in either 2 or all three of the apps without any issues. NOTE: I mainly use Aegis these days... the other 2 are "leftovers" I stopped using Authenticator Plus because it stopped getting updates (last update Dec 2018). |
|
|
|
Yes im same person in stackexchange thread... but no helpful there at all
@nc50lc, well spotted!
Seems the wallet.dat is either: 1. Corrupted 2. Contains "fake data" 3. or it has one or more "watching-only" addresses imported into it (ie. no private key for the addresses of the UTXOs being spent) Would advise that you make some copies of the wallet.dat (if you haven't already) to prevent any further corruption of the wallet file... and only work with the copies, not the original file. Have you tried using dumpwallet from Bitcoin Core to dump the keys from the wallet.dat? If it doesn't show the private key for the address in question, then either it's a watching-only address or the wallet.dat is corrupt/tampered with. Alternatively, you can also try using PyWallet to dump all the keys from the wallet.dat file I would recommend trying dumpwallet command in Bitcoin Core first. |
|
|
|
So will a new private key and a new address get added to my wallet.dat automatically?
If yes then this is not good, I like to label my addresses in a pattern.
I believe that you can specify the label for any address in your wallet by using the setlabel command. So, you can just retroactively label the change address after it has been created. Also, technically, the private key and address are probably already generated and stored in your wallet.dat before you even request a "new" receiving address or "create" a change address with a transaction. Bitcoin Core HD wallets have a keypool size of 1000 by default, so they already hold 1000 pre-generated keys in the wallet.dat. When you "create" a new address, the application just defaults to using the first one (in order) that it has in the keypool. I still need to learn how to generate txid. Any simple explanation as to how to generate that?
You don't generate the TXID... it's returned to you automatically once a transaction is created and then signed. Only at this stage will the transaction be considered "finalised" and the TXID able to be generated (it's the hash of certain transaction data). |
|
|
|
I'm trying to use the GitHub and Python program, but I'm struggling, I'll try everything this weekend and I'll let you know, for the moment thank you very much.
In this wallet there are 29 BTC, I have to try them all before giving up ..
If you need any further help, just ask here... It's been quite a while since I did any work with MultiBit Classic wallets... but they were relatively "simple" protobuf format wallet files that were based on "BitcoinJ". If they're not too badly damaged, it might be possible to use the Python scripts (might need some minor modifications? ) to at least dump out the raw wallet file in "plaintext". Do you know if the original wallet file had a password/was encrypted? If it was, that might complicate things a little bit... especially if the file is corrupted/partially overwritten. Also, what is the exact filename(s) of the multibit file(s) that you have recovered? There were .wallet files, .key files and possibly .wallet.cipher files... |
|
|
|
Purchased Bitcoin through BTCMarkets and moved to Electrum Wallet on Mac
Which version of Mac OSX are you running? Which version of Electrum are you trying to run? |
|
|
|
Have you checked the Bitcoin Code debug.log file to see if there is a more detailed error message than simply "signed transaction failed"? You can find the debug.log in your Bitcoin Core "datadir" (same directory as your wallet.dat file) which should be listed in "Windows -> Information" menu of the Bitcoin Core GUI.... it's a plain text file, so you can just open it with a standard texteditor. Try recreating the transaction, wait for the error message, then open/refresh the debug.log in your text editor to see what the detailed error message is. |
|
|
|
....
So I downloaded Electrum and tried to recover the seed through there and used my recovery phase to set up a bip39 legacy wallet which just shows 0. I chose standard wallet > i already have a seed (checked the bip39 box) > enter seed > choose legacy (p2pkh) m/44'/0'/0' > created a password > then it just shows 0 balence
I would be fairly confident that this is one of those "chose an address from the dropdown menu in old Ledger Chrome App"-type scenarios... Where the address is at a "high" index or was in fact a "change" address, even though it was displayed at the top of the dropdown menu. The result being that the Legacy address that your coins are attached to is out beyond the "gap limit" of both Ledger Live and Electrum. Possible fixes: - Increase gap limit in Ledger Live: https://support.ledger.com/hc/en-us/articles/360010892360-Address-gap-limit- Increase gap limit in Electrumm type the following on the Electrum console: wallet.change_gap_limit(50)
Then restart Electrum. If 50 doesn't work, try 100 - If the coins are on a change address, you can generate extra change addresses in Electrum, by typing the following on the console to generate the next 20 change addresses: for i in range(0, 20): wallet.create_new_address(True)
NOTE: Ledger Live still does support "Legacy" accounts, but only when it can find transactions/history on the Legacy addresses within the initial gap limit... I reset my Ledger Live and Ledger Nano S a few weeks ago when testing things for another user and it still "found" my old Legacy account:  |
|
|
|
I believe that is likely to be the same encryption method, just it's private keys instead of the "protobuf" formatted wallet file. Have you tried using a more recent version of the wallet application (ie. Bitcoin Wallet for Android) and importing the "bitcoin-wallet-keys-YYYY-MM-DD" file? If that doesn't work, you might be able to decrypt the file using the openssl command with your bitcoin-wallet-keys-YYYY-MM-DD file: openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-keys-YYYY-MM-DD -out bitcoin-wallet-keys-YYYY-MM-DD-decrypted
Assuming that works without error, if you open the "decrypted" file in a text editor... do you see the keys listed? |
|
|
|
Google Authenticator now allows users to create and download a backup of their codes. Were you able to import this backup into Aegis or did you add the 2FA codes manually?
That's not quite correct... GA now allows you to create a single "QR Code" on screen that you're supposed to scan with Google Authenticator on a "new" device and it will import all your codes for you... but there is no option to "save" that QR code and screenshot is disabled within the app. As far as I can tell, the idea is that you go directly from GA on Device 1 to "authenticator app" on Device 2 etc... Aegis does seem to be able to read and import this single QR Code tho. Also, can Aegis be used all over the place same as Google Authenticator or does it come with some limitations? I am considering using Aegis myself, so it might be good to know.
I have not found any GA code that is not compatible with Aegis... again, the only issue I've had is the occasional "time sync" error, where it won't accept the code, but doing the sync in GA seems to fix that issue. |
|
|
|
This apparently is a "multicurrency" wallet that uses a local version of electrum to work the "btc" functionality: https://github.com/jesobreira/multiwalletYou can see it just uses the Electrum JSONRPC API to communicate with Electrum from within node.js: https://github.com/jesobreira/multiwallet/blob/master/lib/currencies/btc.js#L122You can read more about the Electrum JSONRPC here: https://electrum.readthedocs.io/en/latest/jsonrpc.htmlNote, I believe that the full list of available commands is the same as you get when you use help() in the Electrum console: >>> help()
[
"add_lightning_request",
"add_peer",
"add_request",
"addtransaction",
"broadcast",
"changegaplimit",
"clear_invoices",
"clear_ln_blacklist",
"clear_requests",
"close_channel",
"close_wallet",
"commands",
"convert_xkey",
"create",
"createmultisig",
"createnewaddress",
"decode_invoice",
"decrypt",
"deserialize",
"dumpgraph",
"dumpprivkeys",
"enable_htlc_settle",
"encrypt",
"export_channel_backup",
"freeze",
"get",
"get_channel_ctx",
"get_ssl_domain",
"get_tx_status",
"get_watchtower_ctn",
"getaddressbalance",
"getaddresshistory",
"getaddressunspent",
"getalias",
"getbalance",
"getconfig",
"getfeerate",
"getinfo",
"getmasterprivate",
"getmerkle",
"getminacceptablegap",
"getmpk",
"getprivatekeyforpath",
"getprivatekeys",
"getpubkeys",
"getrequest",
"getseed",
"getservers",
"gettransaction",
"getunusedaddress",
"help",
"import_channel_backup",
"importprivkey",
"init_lightning",
"inject_fees",
"is_synchronized",
"ismine",
"lightning_history",
"list_channels",
"list_invoices",
"list_peers",
"list_requests",
"list_wallets",
"listaddresses",
"listcontacts",
"listunspent",
"lnpay",
"load_wallet",
"make_seed",
"nodeid",
"normal_swap",
"notify",
"onchain_history",
"open_channel",
"password",
"payto",
"paytomany",
"remove_lightning",
"removelocaltx",
"restore",
"reverse_swap",
"rmrequest",
"searchcontacts",
"serialize",
"setconfig",
"setlabel",
"signmessage",
"signrequest",
"signtransaction",
"stop",
"sweep",
"unfreeze",
"validateaddress",
"verifymessage",
"version"
]
The documentation for each one isn't great... but reading the python code here should help: https://github.com/spesmilo/electrum/blob/master/electrum/commands.py |
|
|
|
|
Show Posts
