Thanks for your explanation and advice.
All my addresses in Electrum start with a "1", and there is a [standard] at the end of the title.
So it must be a "legacy" (aka. NON SegWit) standard wallet. right?
Based on the information you have provided... yes, it would appear you have a Non SegWit standard Electrum wallet. |
|
|
|
Right now I am trying to explain the situation.
What I do wrong?
OK, I've gone. Help yourself.
Didn't mean to offend mate... Just some friendly banter... Hence the "  " And also why I pointed out what you said was very true... The transaction doesn't (and can never) exist... Despite what b.info says :  Sometimes bc.i change their engine fixing one and breaking another. Isn't it obvious?
Quoted for truth... Honestly b.info is terrible sometimes... Their wallet is even worse  |
|
|
|
|
And that is a MultiBit classic .key file?
Does the script generate a "parsed_wallet.txt" file? Does that file have some "encryption" information at the end like the salt and iterations and encryption type?
|
|
|
|
If I store bitcoin in electrum wallet, can I claim future bitcoin forks?
The golden rule has always been... You need to have access to the private keys to ensure access to fork coins... Electrum gives you access to private keys... So the short answer is "yes, with a couple of conditions". Those conditions would be that Electrum MultiSig and/or 2FA wallets have historically been problematic when it comes to accessing fork coins. SegWit wallets are likely to be just as problematic. My advice, if you're planning on holding coins in Electrum for the purposes of getting access to fork coins is to use a "legacy" (aka. NON SegWit) standard wallet (Generated addresses should start with a "1") to reduce the chances of issues when claiming. |
|
|
|
Huh?? What transaction are you looking at?  OP said his transaction was this one: https://blockchain.info/tx/56b59662a847e10000e5793affe34d2198ca0c7d8aedae941fa18ba6a0aba1a2Fee per byte 10.858 sat/B (or 0.00010858 BTC per kB)... which is above the 10sats/byte (or 0.0001 btc/KB) minimum specified by ViaBTC. To the OP, recovery of your wallet without a backup file (and/or the seed) is pretty much impossible unless you can somehow make an image of the phones memory and try doing low level data recovery... not exactly a trivial exercise!  I've also accelerated your transaction using AntPool and ViaBTC... hopefully it'll confirm in the next few hours. Also, due to the low fee, the transaction is likely to sit for a while given current network conditions (70,000+ unconfirmed transactions, recommended fees about 15-20x what you paid)... If you need to rebroadcast the transaction because it gets dropped, here is the raw hex... copy paste it to one of the transaction broadcast tools ( https://en.bitcoin.it/wiki/Transaction_broadcasting) 010000000cb354edcdedc96f7f286bdc5166ea7e68d3e91f6a3c4355059ba7b75eca233b54020000006a47304402206134e5abf9914971bb4260d55d0ac0c31beafdb4f5ce184186489863fb63b6a802201b61426573bf514a722dbbf0ce06dfa5eae63c6d6e8203158f0ff5243cf009580121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffff76c227f24a4a49987dfcf0c5c924735f0f0043137ffcdad0a85f13c0da7be935080000006a47304402207cd63639c52549bab4947a75789831d5b8952004120973231d423ad48e14ee0d02203abd6d80114929c57d15a9f27607358277d3c1f71fc1ef44c34fb92c0280e0fb0121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffffa8550e3e99eded27922f42c5f4d7c854146e5eef8264a1c33ba8a4778c20cc29060000006a47304402205759e9282760dcd2f36eb31d05de1704716c7af39e094667c7415d9f4a157e3502204a6a9002d3b637f9875983b09165a2f1a86f262327810f74b1e723ef2e5c45620121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffffe91bc3bff543193d9b390980edc6fba7f95ee90ed49f73eb18b3e62bdc39689d160000006a473044022064f6e38d22752b5cb147af47cda74f383d8a3a7306a5ef1c022ad6daad6b395c02200ac605d4af99b0ae781487202b77198c7dbeb41431052ebf24970cbadfa868f20121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffff0ff5d8d59d9d4a3310d87d48918cb0ebb971424026e46f093152ccd6a04286eb030000006b48304502210082f6701ee96bf5a9b964d457bf8ea411f4b9e411c565c04bdbe3c28df775c47b02204c31491650644c0676583d0c77c390f64b34bb8320a96f614546174ac08804210121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffff6e82c90438f3ed785bd50f44d2ac72a0a5081bf10bab6e193781e1a52a29f5bf0e0000006a47304402200eea9f9839617bb7d8e8f4b277d71fbed38234ed5c649a8d2e1858a78642ca6f02202bac2d606109f0d0fa43ba357b2c2023012f06964c309c78c23d3ee1340749100121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffff1744b89b0819bf756dd79e4c55373cbdf42858a3cd16a5150b4d7ba551804a680c0000006b483045022100a7950223fda6c7ad4fbcb787f94845e0366670de8dc3db99ee79c6fad440121202204213afd3d425e9b4060cde661ec3a9bd5f89d58f1bbac70df212db1c9d8505860121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffff0a2cc44e785bb2364a75341246aeaed7acc0708cf33e58f25c6b3709934ba8700a0000006a47304402204178ed900fa7dead62b7f765e8a5197e729278aa8cec9ca41e09b6e4d1e81dbd02203fdbc9f8d4b7457b4491de7b05f64e2721ec05857da9b6de49e7f36729baf3710121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffff365b5e97e8ffb21daf5fe7fb20828df608a862fbb490234a837ef49dd5222fbd0c0000006a4730440220023b2ce74180a308db6fd72e6bc84527acdee38b8b19061088cd9a1fb50e92ab02207de74acfa2b95b86e37e5e1e6080df1bc89afc8a972fd0d52d2508722c43519f0121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffffb0c6a76ad9147ff1c1042da035a75e0896d078aee9d9b8580cc348a9e53f6da20f0000006a47304402207a2178481317b92390092ebba35429462b5783d0400966475977ccf139cde7cd022052d767a5e5e9c24e44d3456053282bf9c77848284d2eb315f8fa7329008297b10121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffff213cb886a3d817f3ac1935d56fb9e92c33d6d14618fcde98f878d45e99119e8a0c0000006a473044022030dca1fe0c8424df31af1dfa823c803c48c51e58109ab6e7fe858f524f07644402207bf29a7a42b771487440a72d31e98cdfa91796575bf1d2f8f8d23f50c43c04020121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffff973b1320081ec3ae0ef68e82c77b31a44b0dbbb90b6f7e5253315807234854870e0000006a47304402205ab04236bfe1fa2368799389113841d575ab669e311d3ceff7f3750dbe1a757d02203dacbbdf9036ea2fa596a5c92de0cd18f441589673e32c7d270b25954d69334a0121025f5775a6757274630659e149d0c47904d4065bd49f9d0543761262fd5c8f5ebbffffffff028870f6470000000017a914afa02c050adfe2c7eacf0f44517b6df9b421138e87a4020000000000001976a914f5bacaef771e6ad46ee61dbbaca8f0ecbcfe08af88ac00000000
|
|
|
|
Can I test the password somehow, instead of actually sending Bitcoins anywhere?
In the debug console... (Help -> Debug window -> console)... you can use the command: walletpassphrase YOURPASSPHRASE 0 This will "unlock" your wallet for 0 seconds  (that is to say, it won't actually leave the wallet "unlocked"... but it lets you test the passphrase) If the result you get is "null"... the passphrase is correct, otherwise you'll get an error message How do I put a small amount on a paper wallet?
1. Create paper wallet 2. send small amount of btc to the paper wallet address |
|
|
|
I had a dormant bitcoin account when the August and November forks. I have initialized the Nano S, but i am trepidatious about doing anything withoiut better understanding of
the consequences.
Can you please clarify if you want to have the SAME bitcoin wallet on Electrum and on your Nano S? Or are you just asking about having an Electrum wallet and having a separate Nano S wallet? If you want the same wallet on both, your best bet is to simply initialise the Nano S, then create a new wallet in Electrum with the "Use Hardware Device" option and connect your Nano S. That will extract JUST the xpub from the Nano S and create a "watching-only" wallet, so you can see all your transactions/coins etc inside Electrum, but the seed/private keys are still securely contained on the Nano S ONLY. Having the same seed in Electrum as your Nano S is a MAJOR security flaw... Electrum, while relatively secure if used properly, is nowhere near as secure as the Nano S and has a much larger attack surface for hackers/thieves to get access to your wallet and coins. The only time you should be doing something like this, is in an emergency recovery situation where you need access to the coins but the Nano S has been lost/stolen etc. Electrum (watching only) + Nano S = A very powerful and secure combo |
|
|
|
However i cannot spend it (still) and when i try to sweep the private key using bitcoin core (14 weeks behind) using dumpprivkey *priv key here* it says 'address does not refer to a key (code -3)
I think you're getting a bit confused with how the commands in Bitcoin Core work... dumpprivkey is used for getting private keys OUT of Core... not importing them! The command you want is: importprivkey "Priv key here" That will then put the private key into your wallet.dat and rescan the blockchain looking for transactions associated with that private key/address. Your transactions and coins related to that private key/address should then show up (assuming your Bitcoin Code is synced up until the point in time the transactions were confirmed)... If it is 14 weeks behind still... it won't be able to show transactions from 3 days ago |
|
|
|
|
Theoretically, if the transaction fails to get a confirmation for an extended period of time AND the transaction is not rebroadcast by any node, nodes will start dropping it from their individual mempools and the transaction will slowly disappear from the network.
The period of time this takes to happen is not "fixed"... older nodes defaulted to 3 days (72 hours)... newer nodes can be as much as 14 days. But it is dependent on how the node owner has configured their node.
Anyway, once the transaction has been dropped from all the nodes, it is as if the transaction never existed. You should be able to recreate another transaction spending those same coins, without it be labelled a double spend.
As mentioned, it requires that the original transaction is NOT rebroadcast. Note that some wallets will rebroadcast unconfirmed transactions periodically...
|
|
|
|
I dont understand the addresses system on mycelium app. Every time you send funds to mycelium your address is different? First you send funds to one address and then when you cash out the dust stays in mycelium app but when you check in blockchain explorer the amount iz zero on that address but in the app you can see like 0.00002 btc. Where is that stored? And why there cant be all the time the same address?
A legendary account that doesn't know about deterministic wallets... or how bitcoin change works? You might like to read here: https://en.bitcoin.it/wiki/Deterministic_walletand here: https://en.bitcoin.it/wiki/Changeany maybe do some research into bitcoin change addresses... find the "change address" from the transaction that generates the dust and put that into blockchain explorer, you'll see it. Mycelium (and most other deterministic wallets "hide" these addresses from the user) You can continue to use old addresses if you want, the coins will still appear in your wallet... HD wallets just like to generate new addresses for each transaction to prevent address re-use to help increase privacy: https://en.bitcoin.it/wiki/Address_reuse |
|
|
|
Yes... the "sweep" just sets up a "send" transaction that will take ALL the inputs it can find for the keys you've pasted... and send the total value of all those inputs (minus transaction fee of course) to the specified address. If you don't broadcast it... how is the network and more importantly, the miners, supposed to know about the transaction? If the miners can't see it, they can't mine it! |
|
|
|
You forgot a-z, there's a total of 3844 possible combinations.
No... there isn't... Base58 encoding excludes several letters. "A set of 58 alphanumeric symbols consisting of easily distinguished uppercase and lowercase letters (0OIl are not used)" Chart of Valid characters here: https://en.bitcoin.it/wiki/Base58Check_encoding#Base58_symbol_chartYou're also assuming that the OP knows the exact position of the missing characters. Ignoring the first character (as it can only be 1 of 3 options "5", "L" or "K", so it would be fairly obvious if it was incorrect) a WIF is usually around 51 characters long... leaving you with 50 character positions that could be "missing"... and it's 2 characters... The number of possible combinations is "quite large" Although, I would guess the number of "valid" combinations is quite a bit smaller. |
|
|
|
|
Your best option is to contact blockchain.info support and ask them for assistance. If you are getting an error like that, it sounds like you have the email address wrong, or b.info's system is broken. They are the only ones who can figure out which and help you sort this issue.
|
|
|
|
|
Don't sweep the private keys if you are just going to send them to an exchange etc... Sweeping is basically creating a "send" transaction and requires you pay a transaction fee and broadcast the transaction for the BCH to move where you want... so if you sweep into your wallet, then send to exchange, you'll pay two lots of fees.
Only sweep if you a planning on hodling your BCH for a while.
If you're going to dump the BCH, I'd recommend that you just import them into a new ElectronCash wallet... "File -> New\Restore -> Standard Wallet -> Use public or private keys -> Paste in your private keys"... your BCH balance will then show up and you can then have access to the "proper" 'Send' tab etc to send the BCH where you want.
|
|
|
|
Another question is, is there any tutorial on claim BCH with ElectronCash, it looks very similar to Electrum. I want do it at the same time, then no need to worry about any further risk on the old key(can discard it)  You basically do everything that same... but use ElectronCash instead of Electrum... ElectronCash was a "fork" of the Electrum codebase, so it is isn't identical, but works with BitcoinCash instead of Bitcoin. Simply import the private keys into ElectronCash they way you import them into Electrum (I'd do it at the same time)... then you have BTC in Electrum and BCH in ElectronCash... I'd recommend moving both your BTC and BCH to new wallets after importing. |
|
|
|
Yes that the address in my wallet, in the other hand I change the server, but always say synchroinizing, ¿is it means that i´m not conect to the net?
Shut down Electrum, then find the "blockchain_headers" file on your computer (C:\Users\YOURUSERNAME\AppData\Roaming\Electrum on Windows, ~/.electrum on Linux (and OSX I think)... and delete that file... Then restart Electrum. If it still isn't working, make sure you are using at least v2.9.3 or v3.0.2 of Electrum. Anything older might run into syncing issues. |
|
|
|
|
If you used the xpub from your b.info wallet as you stated, then the balance is correct... "I didn't have any BTC in my Blockchain wallet before the fork (they were in my paper wallet)"... so of course trying to import the xpub for that b.info wallet into another wallet is going to yield the same result... 0 BTC and 0 BCH.
You need to import your paper wallet into ElectronCash... that is where your BTC was before the fork, so that is where your BCH will be now.
|
|
|
|
|
Show Posts
