Someone with more information should kindly assist.
No one has more information than YOU... as you have not provided any of the following basic information that will assist people who are trying to help you  1. The Transaction ID and/or the addresses involved 2. The version of Electrum you are using 3. The Operating System you are using 4. Did you double check the LBC wallet address is the one you actually sent to? Finally, have you actually tried contacting LocalBitcoins? It sounds like the issue lies with your wallet on their system... the send from Electrum seems to have worked perfectly, as you say the transaction has confirmed. ps. Please don't write in ALL UPPERCASE... it is annoyingly hard to read. And don't start pointless polls when you create a thread (click "New topic", not "Post new poll" ) |
|
|
|
migrate to Electrum ca be done without any fee???
and second question, why not green address? is it a good choice too?
1. Yes, you're just effectively importing the private keys (for MBC) or the seed (for MBHD)... That effectively just replicates your MultiBit wallet, so you're not sending any transactions, so you don't need to pay any fees (Fees will only be required when you send the coins from Electrum) 2. No idea about Green Address... I've not used it. The main reason for suggesting Electrum is that: a. I know it works (personally tested it) b. there are the n00b friendly video tutorials (that mean I don't have to explain how to do it!  ) c. In the case of MultiBit HD, Electrum is one of the few wallets that works with the Derivation Path m/0' (most wallets don't use this and/or don't allow you to specify it) |
|
|
|
hash160 to btc address
for p2pkh only
how to make it work with p2sh ?
why p2sh 's hash160 gives p2pkh address upon conversion through hash160 to bitcoin address and not the p2sh addresss ?
Because, as Danny already told you, you don't hash a public key to get to get a P2SH address... it is a "Pay to SCRIPT hash"... you need to hash a "redeem script", not a public key. Read my answer in your other thread: https://bitcointalk.org/index.php?topic=2380374.msg24318230#msg24318230PS. don't create multiple threads for the same question, it'll fragment/split the answers and make things more confusing. Suggest you pick one thread and lock the other. |
|
|
|
You have totally missed the point regarding "P2SH" aka "Pay to Script Hash" addresses and how they work. These addresses are effectively built from hashes of a "redeem script". They are NOT hashes of a public key (generated from the private key). To spend UTXOs controlled by a P2SH, you need to be able to provide the full redeem script, and any signatures, such that when the script is executed, it does not return false. You might want to read here: https://bitcoin.org/en/developer-guide#p2sh-scriptsespecially this part: When Bob wants to spend the output, he provides his signature along with the full (serialized) redeem script in the signature script. The peer-to-peer network ensures the full redeem script hashes to the same value as the script hash Alice put in her output; it then processes the redeem script exactly as it would if it were the primary pubkey script, letting Bob spend the output if the redeem script does not return false.
Also, you should probably note this warning in the developer examples: Warning: You must not lose the redeem script, especially if you don’t have a record of which public keys you used to create the P2SH multisig address. You need the redeem script to spend any bitcoins sent to the P2SH address. If you lose the redeem script, you can recreate it by running the same command above, with the public keys listed in the same order. However, if you lose both the redeem script and even one of the public keys, you will never be able to spend satoshis sent to that P2SH address.
Effectively, if you lose the redeem script, you will have NO WAY to spend any coins sent to a P2SH address unless you have some method to recreate it (in the case of a MultiSig Address, if you have all the public keys, you could recreate the redeem script)... you would of course still need any private keys associated with the P2SH address to be able to sign the transaction (if required). |
|
|
|
help, please. I want to claim my bitcoin gold. I have some bitcoin in my android electrum wallet, which was set up with a 12 word seed. But the android version of electrum is very different from the windows version (so all the online directions don't work), and i can't work out how to get the private keys, to claim my bitcoin gold. So, 2 questions:
1. does anyone know how to get the private keys?
2. is there any way of claiming bitcoin gold using my electrum wallet seed only, and not the private key?
anyway to do this with an iphone? The short answer is, unfortunately, No. There is no iOS version of Electrum. The longer answer is, possibly... assuming there are HTML/Text editors available for iPhone that will allow you to work on a downloaded copy of the BIP39 tool, make the edits I listed above and then open that edited HTML file in your phone's webbrowser so you can run the edited code... If someone wants to send me an iPhone I'll give it a try! |
|
|
|
thanks hcp, i'll read ian coleman's website.
Re. point 2, i used electroncash wallet to claim my BCH, but it won't work for claiming bitcoin gold, will it? Isn't my only option to read up on how to get my private key from the seed by modifying the bip39 code convertor?
It's a pretty simple mod... basically I downloaded a copy, and then modified the "BIP39 Mnemonic" validation... so it just always returns "True"... Hint: look for this function, and just change the last statement so that it always returns true: self.check = function(mnemonic) {
var mnemonic = self.splitWords(mnemonic);
if (mnemonic.length == 0 || mnemonic.length % 3 > 0) {
return false
}
... SNIP bunch of code ...
return true; // h == nh;
}
and then changed where it calculates the "passphrase", so instead of using the string "mnemonic" + entered passphrase, it uses the string "electrum" + entered passphrase. Hint: look for this code and change the highlighted line: self.toSeed = function(mnemonic, passphrase) {
passphrase = passphrase || '';
mnemonic = self.joinWords(self.splitWords(mnemonic)); // removes duplicate blanks
var mnemonicNormalized = self.normalizeString(mnemonic);
passphrase = self.normalizeString(passphrase)
passphrase = "mnemonic" + passphrase;
var mnemonicBits = sjcl.codec.utf8String.toBits(mnemonicNormalized);
var passphraseBits = sjcl.codec.utf8String.toBits(passphrase);
var result = sjcl.misc.pbkdf2(mnemonicBits, passphraseBits, PBKDF2_ROUNDS, 512, hmacSHA512);
var hashHex = sjcl.codec.hex.fromBits(result);
return hashHex;
}
After that, you simply put in your seed, Click BIP32 tab, use a "custom derivation path of m/0 and m/1 and you'll see all your receive and change addresses and associated private keys I really don't recommend using the android version of electrum. It's a completely different set-up from the mac and widows versions, and when reading any guides, they refer to the other versions, which is very confusing (and exasperating)
The Android version is not meant to be a 1:1 copy of the desktop version... that is expecting a bit much. It is more of a "companion" app... in that it will give you quick and easy access to your wallet "on the go" for basics like sending and receiving. Is there any particular reason why you can't just use a desktop computer, restore your seed into desktop version of Electrum and then extract the private keys from there? You're probably going to need one to modify the BIP39 Mnemonic Code Convertor anyway... the downloaded HTML file is HUGE, nearly 45,000 lines of code... and it runs pretty slow on a mobile device! |
|
|
|
it just arrived while i strat the thread.. omg..
is it because, 0.10 is little ? this is why it is late?
No, it has nothing to do with the size of your transaction. Both of your transfer amounts were in the exact same bitcoin transaction, so they both confirmed at the same time. The issue is with the receiving Exchange system. It is quite possible that their system uses "one time" deposit addresses... so after one deposit is received, the deposit address for your account will change. Likely, the system detected the 0.303 amount, credited that to your account and then changed your deposit address. Then it found the 0.1 amount but did not know where to credit this as the deposit address for your account is now something else. No doubt that this likely occurs a LOT, so I would guess that what has happened, is that they probably have a team that go through "unassigned" deposits... get the address and then find the account that matches this "old" deposit address and then credit that account with the funds. This would be a slow and manual job, which would explain why it took so long... It also wouldn't surprise me that after telling you they didn't get the funds, the receiving exchange actually went looking for it and found it and credited your account |
|
|
|
I imported to my Electrum wallet my 2 Private Keys of the Bitcoin address (3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke) from which the transaction was sent, but it gave me 2 empty addresses with zero transactions....that's so strange.  That's because block.io is using P2SH (Pay to Script Hash) addresses... possibly a MultiSig (hence the multiple private keys). So, you'd need to create a MultiSig wallet using the two private keys they gave you... not even sure that is possible to create a single address MultiSig with Electrum, or if you have to use xpubs/xprv's... fairly sure it ONLY accepts xpubs and xprvs You'd probably need to use something like Coinb.in to recreate the MultiSig, create your raw transaction, sign it and broadcast from there. Obviously, I would recommend downloading a copy of Coinb.in and running it on an offline machine to reduce exposure of your private keys Also, it would appear that there is a reason the transaction was pretty much rejected by the entire network: Error validating transaction: Transaction f89b79d5222a2016d0d2e0059d8834a61da817fd9ad31b3d58e0770cba4ddd87 orphaned, missing reference 53fdc0657ccf15529cbce4dc129633dc4f815e4a06e28dde3dacf6701baaeef1.
It seems (at least) one of the inputs is from a "bad transaction"... I tried to repush the "53fdc" transaction via BlockCypher, and it says: Error sending transaction: Error running script for input 0 referencing 1498c6c02aa91d7c95a7ad7b1dd0e5b0f9741998c357117fa5575c7344050b84 at 0: witness program does not match script hash.
Something seriously screwed up with all of that...  |
|
|
|
Most likely, it'll be a bug in B.info wallet... honestly, it is one of the most poorly coded systems (both web and mobile)... I don't know why it is so popular??!? It is probably caused because the wallet doesn't know how to properly reconcile the fact that it sent 0.00792085 BTC TO 1FYyHeSHy47NTiEBBYs3HAwsss8b3oYK3N and then received 0.00792085 FROM 1FYyHeSHy47NTiEBBYs3HAwsss8b3oYK3N... and the values cancel each other out. You have the actual blockchain as proof you returned the coins, he will need to sort it out with B.info (probably delete the app data for his wallet app... and restore the wallet from seed or repair it or whatever system b.info use ) |
|
|
|
How should i inform myself? Where is it written that export won't work?
Guess you missed this warning when setting up your wallet to use P2SH-P2PK addresses:  It says pretty clearly that "Only Armory 0.96+ can spend from" those addresses... attempting to claim fork coins from "P2SH" addresses like MultiSigs, Electrum 2FA and other "script"-type addresses has never been a straightforward "one click" solution. |
|
|
|
Yeah, I do have a private key and am able to access it. No they don't have the seed for the wallet. Terrible service is what I think of because they are in from past 2 years and recently i did few transxn recently it was smooth but from last night this issues( may be coz of no segwit news, as they were giving free 2x coins) their ratings are average and sometimes good too but yeah reliability and customer support is pathetic.
Yeah that absolutely sounds correct, balance should be 0.98 only.
Ok, in that case, I would suggest your import your private key into another wallet like Electrum (when you create a new wallet select: Standard wallet -> Use public or private keys)... and double check that it generates the same address and has the correct balance. I certainly wouldn't be happy about not being able to see my coins because their server is down for maintenance!!  |
|
|
|
I am just thinking, i sent a payment from my electrum wallet yesterday but i had to input my password before it would finalize. i am not sure that this is a standard feature but if so the transaction would need your password, thatt should not be easy to get. there has to be a compromise in your security That would only be the case if the thief only had the OPs password protected wallet file... if the wallet file was not password protected, the private keys/seed/xprv are stored in plaintext. Also, if the thief managed to get their hands on the seed or actual private keys, they wouldn't even need the original wallet file or it's password. They could just create a new wallet with whatever password they wanted. |
|
|
|
1) so I signed up with Electrum and i put a 2fa so i just wanted to know does everyone have a mining fee and a additional fee?
Yes... with an Electrum 2FA wallet there are additional "fees" that need to paid to the 2FA service provider "TrustedCoin". They used to allow both "pre-paid" and "pay per transaction" options... but have now moved to "pre-paid" only. You need to have "credits" to be able to send transactions... and these are now pre-paid in either groups of 20 or 100 credits. If you have no credits a fee to purchase credits is automatically added to your transaction. refer: https://api.trustedcoin.com/#/electrum-help2) question what if since i use 2fa and it uses google authenticator what if i lose my phone for example or get a new phone whatever but i forgot to transfer my app to the new phone not sure if it helped but i wrote down the google authenticator code down not sure what it does but does it help?
The answer to this question is also on the TrustedCoin Electrum 2FA FAQ Page: https://api.trustedcoin.com/#/electrum-helpBasically, you restore from seed and either disable 2FA altogether, or you can enable the Google Authenticator on a new device. 3) If i can't access electrum anymore can i see the seed on blockchain.info for example or whatever exchange if electrum isn't support which is 99.9% probably not going to happen.
No, Electrum seeds are not compatible with any other wallets as far as I know, as they are NOT BIP39 compatible. Additionally, Electrum 2FA seeds will definitely not be able to be imported into other applications, as they generate a special MultiSig wallet using TrustedCoin. |
|
|
|
Does the Seed(Master key) can use in any bitcoin wallet software? such as Bitcoin core.
The seed mnemonic (aka 12 words) generated by Electrum when you create your wallet, does not conform to the BIP39 standard. As such, it can only be used with Electrum (I'm not currently aware of any other wallets able to import Electrum seeds) I saw some threads that said that the private keys will be changed after transactions, is it true? or I misunderstanding?
Are you talking about addresses changing after each transaction? Private keys don't "change"... they will always remain the same. Some wallets will automatically give you a new "address" after each transaction to help prevent "address re-use" to help with privacy and, to a lesser extent, security. This new address will have a new private key... but all the previous addresses and private keys will still be stored in your wallet. Fairly sure that bitaddress.org is only generating "private keys"... They will start with a "5", "L" or "K". A "master private key" is usually generated by "Hierarchical Deterministic" or HD wallets and will start with "xprv" |
|
|
|
|
For the time being... ignore what Electrum is telling you with regards to the number of transactions and amounts. It's possible the servers have got a bit "confused" with the multiple send attempts/connection issues etc... and it's possible your failed transactions may be "stuck" in your wallet causing issues.
Instead, instead of relying on Electrum... go and check to see what the blockchain says about it all... Goto your favourite block explorer and input the addresses and/or the transaction IDs that you can see in Electrum. That will tell you what has ACTUALLY happened according to the blockchain.
Alternatively, you can post your Transaction ID(s) and/or addresses here (if you don't mind giving up some privacy) and we can investigate for you.
|
|
|
|
|
Even if it is offline, you should be able to export the private keys...
Wallet Properties -> Backup this Wallet -> See Other Backup options -> Export Keys List -> click "Export keys list"
Then make sure the following are ticked:
- Address String
- Private Key (plain Base58)
- Include Unused (Address Pool)
- Omit spaces in key data
Addresses+Private keys will be displayed in the text box, copy/paste and/or save to a text file... you'll be able to then copy the private keys and import/sweep them into the wallet of your choice.
|
|
|
|
|
Can you click "preview" instead of send... and tell us what the reported "transaction size" is (in bytes) and how many inputs are being used... also, how much BTC are you attempting to transfer?
It's possible, that if you have received a number of small "dust" sized inputs, when you are attempting to transfer your funds, the data size of the transaction has been made so big due to a large number of inputs, that the dynamically calculated fee is bigger than your total available balance.
It's also possible that you're attempting to spend "unconfirmed" inputs... and your Electrum is not configured to allow this (Tools -> Preferences -> Transactions -> "Spend only confirmed coins")
|
|
|
|
|
The most important question is: do you have access to the private key for this address (17fb1G7nF3N6K6zSpR1D8Y1tQbhRNzPRWU)? or do you have the "seed" for the wallet?
If the answer is NO... then this Bitcoin-India either has TERRIBLE service or coding or both... OR it is a scam... over 90 confirmations on the blockchain, there is absolutely no valid reason for that amount to not be reflected in your wallet balance.
The address: 17fb1G7nF3N6K6zSpR1D8Y1tQbhRNzPRWU has received over 1.5 BTC since 21st October... and the current balance is 0.98451 BTC... does that sound correct?
|
|
|
|
|
Show Posts
