Yeah, you'd be better off creating a small live Linux bootable distro on the pendrive... install Electrum on it (do NOT create the wallet yet) and then configure it so that all the networking features are disabled at boot time.
Once you've got it configured to be offline... boot off the pendrive, and setup your wallet in Electrum... noting the public address(es) as required. Backup the generated seed to paper and put it somewhere safe and secure. Shut down, remove the pendrive.
Then on an online computer, install Electrum, create a "watching only" wallet using the public addresses that you noted down.
This should effectively create a system that is effectively "air gapped".
If you want to send coins, create an unsigned transaction from the watching only wallet, put it on a 2nd usb stick. Then boot your distro from the bootable pendrive, sign the transaction on the 2nd usb stick. Shutdown, reboot into your online OS and broadcast the transaction.
A little convoluted and time consuming, but the increase in security is quite significant. Your private keys effectively never go near an online machine.
|
|
|
This is PERFECT!!!! I have only only question: Where, or at what point would I indicate that I already have a seed???
This is specified during wallet file creation (or after you select File -> New/Restore). You simply select the "I already have a seed" when prompted by the wizard: Just be sure aware that the seed only covers the private keys it generated itself. If you imported keys into your wallet those are not backed up by the seed!
You shouldn't need to worry about having any private keys that aren't covered as Electrum does not let you import private keys to an HD (aka seed based) wallet in the first place. They can only imported into an old style keystore wallet which needs to be manually backed up.
|
|
|
Now I want to proceed with a payment but it asks for a password that I don't remember, anymore. What happens in that case? If you have your seed then just go "file -> New/restore" Select "Standard Wallet" and "I already have a seed".. follow the process and put in your seed and (optional but recommended) add in a password and encrypt the wallet file. After it is all successfully resynced, you should be able to send using the new password you just reset. Having your 12 word seed safe is the ultimate recovery and "password reset" option!
|
|
|
where is this = to the %appdata%/MultiBit directory= to copy and paste to?
Thank You for all your Help!!
It is the main MultiBit folder that contains the untitled-data folder (that contains the key-backup and wallet-unenc-backup dirs etc)... it should also contain some other files like "wallet.spvchain"
|
|
|
pretty much just a standard low fee issue.... for the record, this is your first transaction: a356f6733b359725dcee4aab2ba6aa312d5713c953f51af230c34fb3701e6aa0Also, as your 2nd transaction is spending an unconfirmed output from the first, it won't be able to confirm until after the first one does... so work on getting the a356f6 transaction accelerated first... you just have to submit in the first few seconds of a new hour. If you're going to continue using b.info wallet (not recommend! you should get a proper desktop wallet)... at least start using the new "custom fee" option on the send dialog and make sure you fee is matching up with: https://bitcoinfees.21.co/
|
|
|
20% of your balance to recover the password? That's highway robbery... I wonder if the 2nd password is actually just a one-way hashed value stored in a DB or if your wallet info is actually encrypted using the password? If it is the former there should be no problem for them to remove it... if the latter then without that password your balance is stuck. So you remember the start of the password? and its just a few characters on the end? how long was it in total?
|
|
|
Just sent $50 worth of Bitcoin using Mycelium and was charged a fee of over $8!! Something's definitely wrong with their fee schedule!
Total fee is irrelevant... What was the fee rate is satoshis per byte (or BTC/kB)? That is the only way to determine if fee is appropriate or not... current fees are like 250-300+ sats/byte for quick confirmation... https://bitcoinfees.21.co/https://btc.com/stats/unconfirmed-tx
|
|
|
I can log in to my wallet normally. Bitcoin is still there but not used ! The reason is: I lost the backup paperwork of 12 recovery phrases and forget password 2 of Blockchain (Blockchain.info)
Sadly, it would appear that you may be out of luck: Beware that there is no password reset functionality. Depending on how you generally set your passwords (length + character types), you might be able to crack it... but have you tried contacting b.info support and asking if there is anyway you can get the 2nd Password removed? Personally, I think it is just crazy that there is no password reset option available.
|
|
|
To be honest, most of these issues are due to MultiBit HD basically being abandoned by the devs. The wallet has become more and more unstable. Just look at the number of threads regarding "Password did not unlock the wallet" or "transactions changing to unconfirmed". The issues have been ongoing for weeks/months and the last commit on github was in March!!?! Even the MB Devs recommend you use something else: And for the record, I don't recommend MBHD, either. Move your keys to electrum. No need to pay fees.
|
|
|
No. Your understanding of activity is incorrect. Read this: https://bitcointalk.org/index.php?topic=237597.msg2513302#msg2513302Don't go spamming the boards trying to jump up levels... it doesn't work. As stated in that thread, posting once a day will have same affect on activity as posting 30 times a day. Posting more than once per day on average is useless for increasing activity. The maximum number of activity points you can get is 1 per day, but your activity score only updates every two weeks.
|
|
|
Regarding sweep private keys in Electrum,total amount of coins will be send to one Electrum address,this means not send through blockchain,is that correct?After that I can still use my old address/private keys(need some of them) in other wallets and then send coins to Electrum wallet?
No, sweeping creates a transaction on the blockchain. This is the only way to get coins from one address/key to another. You can continue to use those private keys/addresses if you want/need, but it isn't advised as they have now been "exposed"... especially if you entered them into a copy of Electrum on an online computer. If you created the sweep transaction on an offline PC and offline Electrum then it isn't as likely they will have been compromised, but still not advisable to continue using those addresses.
|
|
|
After you get "acceleration succeeded" message, you have to wait for ViaBTC to mine a block... They usually mine 5-10 a day (average 1 about every 4 or 5 hours... sometimes more , sonetimes less)... but you should get confirmation within 12 hours at most. Can confirm that ViaBTC TX accelerator works well... it is just busy these days and you have to time it right! But at least it is free! EDIT: I just went to test to see if it would accept your transaction... and it said Acceleration succeeded! So next time they mine a block it should hopefully confirm It has been around 3 hrs since they mined a block, so hopefully they get lucky and find one soon EDIT2: And now you have 8 confirmations you're welcome... Included In Blocks 471321 ( 2017-06-15 02:45:02 + 932 minutes ) Relayed By ViaBTC
|
|
|
If I needed to transfer 2000 BTC I would use a higher than necessary fee, something like 0.005 BTC. It would confirm very quickly and still have cost only 0,00025% of the sum. Not even 15 bucks to transfer more than 5 millions USD !
Not necessarily... the total fee amount is generally irrelevant to confirmation time... it is the sats/byte (or BTC/kB) value of the fee that determines the likelihood of your transaction being confirmed by a miner... while 0.005 BTC seems like a lot... if your 2000 BTC transaction has 100 inputs and the transaction size is ~14,800 bytes... your effective fee is 500,000 / 14,800 = 33.78 sats/byte... which is going to get stuck for days. I could send a 0.1 BTC transaction with only 1 input with a 0.0007 fee and get it confirmed faster. People need to stop looking at total fee and be more aware of sats/byte fee rate...
|
|
|
Only thing I will try is to install new copy of MB and then import my private keys,just to check is wallet.dat file causes this problem,but if your explanation is correct then MultiBit is no longer for use-some say it has been so for long time.
Yep... MBC is basically "abandoned"... they claim it is in "maintenance mode", but given they haven't even fixed their "current" version (MBHD), I very much doubt that MBC will be updated ever. MultiBit Classic MultiBit Classic is:
free and open source under the MIT licence designed to work directly with any Bitcoin full node (no servers) not related to the Bitcoin Classic full node project a legacy product so you should upgrade to MultiBit HD It is now considered to be a legacy product and is in maintenance mode. This means that only essential security and network compatibility updates will be made to the codebase.
The security model of MultiBit Classic is weaker than MultiBit HD so we only recommend using it if you have private keys that cannot be migrated.
Note that release numbers are not continuous but are based on distributions made available through the main website
|
|
|
I answered in the other thread that you started: https://bitcointalk.org/index.php?topic=1966443.msg19554614#msg19554614tldr; Nothing malicious... it is "Change Addresses". When you got your private keys you only generated private keys for "receive" addresses... you need to generate the private keys for your "change" addresses and import those to your other wallet!
|
|
|
No "malicious acts"... what you're seeing is "change addresses" in action. To break it down... in this transaction: https://blockchain.info/tx/e6cfaf4858af0d105973382588d31700dc11a97efde576c2b6d11a1311c07d84You spent an "Unspent Transaction Output", also known as a UTXO, worth 0.01 BTC... from address: 1FYnsK8Zqt89bvTVhXVvvfi9pVFE2LQhrL Of that 0.01 BTC: - you gave 0.001 BTC to address: 1E37CUCsdibNpieqS6uKoeNEnjksDbwDZb - you used 0.0005 BTC as the miners fee - you had 0.0985 BTC leftover (0.01 - 0.001 - 0.0005), which got sent to YOUR "change address": 1JY13j7kpNDzHtk3koVHayUmkFqwbFYG3U So your coins are still in your "wallet", just in a change address, as opposed to a receiving address. The big issue you have now is accessing it. If you have your 12 word seed (and I really hope you do!) you can find your change addresses really easily: Option #1:Simply restore your seed using "Breadwallet" (on iOS/Android Devices) or "Simple Bitcoin Wallet" (Android only)... this will enable quick access to the coins stuck in your broken MultiBitHD wallet, but I don't recommend long term use of these apps. I would suggest you restore and then send ALL your coins from Breadwallet/SBW to another wallet. NOTE: Breadwallet/SBW are the only wallets I know of that are compatible with MBHD seed/derivation path. Option #2:1. create an offline copy of: https://iancoleman.github.io/bip39/ (instructions at the bottom of the page) 2. put your seed at the top where it says "Mnemonic seed" 3. In the "Derivation Path" section, Click the "BIP32" 4. For "client", select MultiBitHD (the "Bip32 Derivation Path) should say: m/0'/0 5. Copy all the "Receive" addresses/private key pairs from the bottom of page (you may need to click "show more" a few times to find ALL you "Receive" addresses used) 6. Now, chance the "client" to "custom"... and set the "BIP32 Derivation Path" to: m/0'/1 7. Now all the addresses/private keys listed at the bottom will be your "change addresses"Specifically you want to get the private keys for the two addresses in the transactions you've linked above: 1JY13j7kpNDzHtk3koVHayUmkFqwbFYG3U 1JkCceVDSXcWtkmmwrcv8w22Y3tfFZbBXY And possibly any other change addresses from transactions that you've made. Option #3:Slightly more technical... but if are comfortable with installing Python and running Python scripts... I have written some scripts that can find all the address/keys with coins from your MultiBit HD wallet file Good luck!
|
|
|
I'm assuming you were using an online web wallet of some description? As you said you were sending to your daughter... but that transaction has 5 outputs! Anyway, if my assumption is correct, the online wallet service screwed all the recipients with a very low 70 satoshi/byte fee The current recommended fees are anywhere from 220 to 390 sats/byte. You can check here: https://bitcoinfees.21.co/https://btc.com/stats/unconfirmed-txNote: recommended fees are continually flucuating, so it is usually better to pay slightly higher to avoid an big upswing and end up with a low fee. You can try submitting to the ViaBTC TX Accelerator in like the first 30 seconds of a new hour and you might get lucky and nab one of the 100 free hourly slots... At almost all other times you'll just get "Submissions beyond limit"
|
|
|
Just put in a counter to count your losses... reset it when you win (or hit 3 losses)... check it on a loss and if it equals 3 then multiply ... losscount = 0 ... function dobet() ... if win then losscount = 0 ... else losscount = losscount + 1 if losscount == 3 then nextbet = previousbet * multiplier losscount = 0 end ... end
end
|
|
|
If you have problems with these Exchanges – check your wallets on the Blockchain. There seems to be a pattern to this back-door fraud that the Blockchain will reveal: even though the Exchange tells you that you have coins in your wallet – the Blockchain will reveal that soon after you deposited Coins into your wallet – they vanished into another wallet: without U being informed.
That is actually pretty 'normal' behaviour for most "online" services, like exchanges, where you don't control the private keys and just have an "account balance". The service controls the address, you deposit coins into 'your' unique deposit address... the service then credits the matching amount of coins to your account... effectively like a bank account really. They are then free to use these coins for whatever they want (like fulfilling other peoples withdrawls)... much like when you deposit $100 into your local bank, they don't put THAT specific $100 note aside for just you... Then when you want to withdraw your coins, they just send you the matching amount using coins from any of the addresses they control. Using a system like this actually offers the company some good benefits... in that it becomes possible to minimise transaction inputs, by having more flexibility to match a withdrawl request with an appropriately sized deposit amounts... AND (despite the obvious security risks of letting "RandomCompany" Ltd. look after your coins) you get the added benefit of coin mixing!
|
|
|
It is not, I have read the above quote, I agree with it someone did a really great search. Can you post the link to it? Sometimes, We have very large transaction size, even the transaction has only one input and one output, So, how can you explain that?
Then you are misunderstanding either the terms, or what is counted as an input or an output. An input is NOT an address... so if you see something like this: Which looks like 1 input... but has a MASSIVE transaction size... click the "Show scripts & coinbase" link... then you'll see the ACTUAL inputs to the transaction... like this: Check this transaction for an example: https://blockchain.info/tx/271f6489c2d5562046be3965dd2d1a2f7bf6f200d967c0c70dfef6cfb987eb12Every single one of those inputs adds at least 148 bytes to the transaction. This is why you shouldn't collect dust inputs to your wallet... if you're collecting faucets or doing captcha's or cloud mining or whatever... set your MINIMUM payout to at least 0.001 if not 0.01... otherwise you are generating dust inputs which end up costing you a lot to include in a transaction... each input = 148 bytes... recommended fees of 300+ sats/byte = 148 * 300 = 44,400 sats to include an input in a transaction... if your input was only 100,000 sats to start with, you need to spend 44% of it just to put it in the transaction!!?!
|
|
|
|