ROFL... Thanks for correcting that, l will just go and ninja edit my post  knew I'd probably screw it up... that's what you get for doing stuff after a 12hr shift with 1.5hrs sleep  |
|
|
|
|
You can restore from seed... make sure you restore a "2FA" ("File -> New/Restore -> Wallet with two-factor authentication -> I already have a seed")... It will ask if you want to "Keep" or "Discard" the 2FA features... If you select "Discard", it will restore your wallet with 2 of the 3 private keys on your PC, so it is effectively no longer a 2FA wallet.
Alternatively, you can just setup a new wallet with a new seed and move your coins across. Personally, I'd recommend setting up a new "standard" wallet and moving the coins to help minimise the chances of any issues later on.
|
|
|
|
Pretty much a common issue with MultiBit HD... there are at least 5 or 6 threads in here with the same issue  Additionally, KeepKey have effectively stopped all support and development of MBHD ( https://multibit.org/blog/2017/07/26/multibit-shutdown.html) If you had the seed words, you could recover your coins really easily... but you say you don't have it... So I would suggest you attempt to use: https://github.com/gurnec/decrypt_bitcoinj_seedThat python utility will help you extract the seed words from your wallet file... Once you have the seed words, I would suggest downloading the latest version of Electrum 2.9.0 and follow the videos on the multiBit blog post ( https://youtu.be/E-KcY6KUVnY) that shows how to import your MBHD seed into an Electrum wallet. Also, why would you move coins from a hardware wallet like a Ledger Nano S to a software wallet like MBHD?  You shouldn't need to do that to use a hardware wallet! |
|
|
|
setSatoshiDir: directory does not exist: C:\Users\brandon\AppData\Roaming\Bitcoin\
Armory is not able to find where your Bitcoin Core is storing the blockchain data... so it is unable to sync up and find all your transactions. Where did you install Bitcoin Core to? and what is the "Datadir" that it is using? (in Bitcoin Core: "Help -> Debug Window", check the Datadir value) |
|
|
|
So this is a sort of prevention of double spending or loss of coins as a result of sending any of the btc to the wrong node ?
No, it isn't related to "double spending". "Double spending" is an attempt to spend the same coins on the same network twice (usually, but not always, as a means of committing fraud). It also isn't related to "sending btc to the wrong node"... this doesn't actually make any sense. You don't send btc to a node. You transfer control of BTC from one address to another address (Technially, it is actually transferring control from a private key to another private key, but for the sake of keeping things simple, we'll say "address")... As BTC and BCC share a common history and (mostly) common technology... without replay protection, it would be simple for a person to take a transaction from BCC network and rebroadcast it on BTC network... or vice versa. So, theoretically, if one currency isn't worth as much as the other (ie. 1 BTC = 10 BCC) someone could be like... "Hey, I see you have 10 BCC... I'll buy it off your for 5 BTC"... you send them the BCC, thinking you got a good deal (5x!!?! wooooo!  )... they then broadcast this exact same transaction on the BTC network... and you suddenly find your 10 BTC has been sent to that person!  (Two-way) Replay protection, which is what has been implemented by the BCC devs, makes it so that a BTC transaction is NOT valid on the BCC network... and a BCC transaction is NOT valid on the BTC network. The result being that you don't have to worry about someone being able to take the coins from you unless you specifically create a transaction on that particular network. |
|
|
|
Also, the speed of your Internet connection is a big factor. If you have ISP enforced limits on your downloads, or data caps, then that is a factor beyond your control and you will have to live with it (or get a different ISP).
It is actually more CPU bound than network bound... (You'll most likely find your network is hardly being used, while your CPU is being hammered). Crypto hashing when verifying the blocks downloaded is generally the bottleneck, so the speed of your internet connection is largely irrelevant (assuming you're not on dialup )... If you don't want the ENTIRE Bitcoin blockchain, I've heard that you can also download just part of it with the -prune=nnn command.
When running with pruning switched on, you still have to download the entire blockchain... that is to say, you will still need to download the 130+ gigs to get it "synced". However, it doesn't store all 130+gigs on your disk, so the "available" storage requirements are a lot lower. |
|
|
|
Could someone please tell me what to do
Im have a bitcoin balance on my blockchain wallet worth 0.005 i would like to transfer it to my another wallet.but it show i can only transfer 0.00014 of bitcoin.,due to insuffiecient funds
Do i need to add more bitcoin on my wallet to cover the fee?
Let me guess... you have received a whole lot of tiny little "dust" sized inputs from faucets and/or cloud mining and/or <insert micro earning service here>... is that correct? That would probably explain why it says you can only send 0.00014 BTC... Your transaction probably has like 20+ inputs and the fee being calculated is HUGE. If you're using blockchain.info webwallet, click the "Customize Fee" link in the "Send" dialog and set a custom fee of "10 sat/b":  That should help minimise the fee and let you send more of your 0.005 BTC and still let you use the ViaBTC TX Accelerator to get your transaction confirmed. |
|
|
|
That method is for exporting "MultiBit HD" generated wallets ONLY... NOT a wallet from your hardware wallet device. If your wallet was created by the Hardware Wallet... and is already on your hardware wallet... you want to use: "File -> New\Restore -> Standard Wallet -> Use a hardware device"... then connect the hardware wallet (if it isn't already) Restoring the seed into Electrum effectively removes ALL the safeguards of the hardware wallet and exposes your seed/keys to your computer!! However, if you create it as a hardware wallet within Electrum, it will only expose the Master Public Key... which will generate what is effectively a "watching only" wallet... You'll be able to see all your addresses/coins/transactions etc... but to spend, you will still need to use the hardware wallet and your private keys are never exposed to the computer.  |
|
|
|
Updating to latest version is required during hardfork or current version 2.8.3 is enough ?
Depends on whether or not you care about Bitcoin Cash... As per Theymos' post: https://bitcointalk.org/index.php?topic=2012799.0 (Read the "What should I do to secure my bitcoins?" section) If you have no interest in it... and believe it will "die" and BTC will continue as the longest chain with max hashing power... you pretty much don't need to do anything... 2.8.3 should continue to operate as normal... If you would like to fork your coins, you can do it with 2.8.3 (it requires some work)... or you can download 2.9.0 and try the nifty features that ThomasV added in to allow you to specify what blockchain you want to use in the Network settings window. If you want to use Bitcoin Cash instead of BTC... you may need to manually configure Electrum to connect to BCC servers if any exist... or go use another BCC specific wallet. |
|
|
|
Yeah... Excel is the quick and dirty way to do this... In the simplest form, you want to have 5 columns... and 2 "fixed" cells: Columns: BetNumber, BetAmount, SumWagered, WinAmount, Profit Fixed Cells: Multiplier, Payout First Row formulas: BetNumber=1 BetAmount=0.00000001 SumWagered=BetAmount WinAmount=BetAmount*Payout Profit=WinAmount-SumWagered 2nd (and further rows): BetNumber=PreviousBetNumber+1 BetAmount=PreviousBetAmount*Multiplier SumWagered=PreviousSumWagered+BetAmount WinAmount=BetAmount*Payout Profit=WinAmount-SumWagered To determine the "max" number of rounds you can survive... I plug in a "guess" for the first BetAmount value... then look down to the row where SumWagered > Balance... the BetNumber BEFORE that row is the max number of losses before you can no longer wager. Make first BetAmount smaller to make max Rounds bigger... and vice versa I'm not sure of an easier way to explain it I could upload a basic spreadsheet somewhere if you let me know what format you need... |
|
|
|
When I start BTC Core through the shortcut(with that special target) it goes through veryfing blocks but it won't open the BTC Core because it says not responding and the only thing I can do is to close it. The last time it was up and running the procces was at 75% or so if that helps.
BTC Core can be quite CPU intensive... and it can do the "not responding" thing occasionally if it is really busy hashing stuff while calculating checksums etc... any chance you can post the debug.log When I start my first BTC Core without that shortcut, it opens normal and is fully synced but that doesn't help me since my Armory balance doesn't change with that one.
In that case, with your first BTC Core open (and fully synced)... can you goto: "Help -> Debug Window" and see what the "Datadir" path is... if that is NOT "D:\Bitcoin" then you can try and set the path in Armory to be whatever it says there... |
|
|
|
Ahhhh... looks like that transaction has "Pay To Many"... like MANY addresses... hahah. So the ACTUAL output of your address got drowned out in the noise... Updated the script (same URL as before): https://pastebin.com/bB6qS4ViThis oneshould not dump out all the "not found" messages and only so addresses that match... Also, just FYI, ThomasV released 2.9.0 of Electrum, that should now import MultiBit HD seeds. During wallet creation, select "Standard Wallet -> I have a seed -> Click options and select BIP39 seed -> Input seed -> Next -> and use m/0' as derivation path. All your addresses should be generated and transaction history loaded!  ps. sorry about the delay in responding... |
|
|
|
|
Yeah, localbitcoins "can" be good... Depends on where you live and who is available etc... Usual precautions apply.
As for mixer's... BitMixer closed recently... ChipMixer is a recent addition to the marketplace, but is pretty reliable in my experience. I've heard good things about BitBlender, but never used it...
ChipMixer works slightly differently to "traditional" mixer's... They just give you private keys rather than forwarding to an address... The keys are preloaded with value so it can mix almost instantly. They currently work on a donation system.
Traditional mixer's like BitBlender generally ask for a forwarding address, and allow you to specify a fee in a range (to help "randomise" the fee and make it harder to identify it as being a mixer transaction)... And allow you to set a timer for when the forwarding transaction is done... Again, to make it more difficult to track.
One thing to be wary of is "clone" sites that look exactly like the original with a similar URL but are scams...
|
|
|
|
If you have MultiBit Classic then it is very easy to export your private keys... Just use "Tools -> Export Private Keys":  Don't encrypt it, otherwise you won't be able to open the output file in a text editor and copy/paste the keys But do be careful... If someone gets access to that file, they can take all your coins... So I'd suggest doing it while disconnected... Import to Electrum... Delete export file... And then reconnect. |
|
|
|
Release Notes:
# Release 2.9 - Independence (July 27th, 2017)
* Multibit support: If the user enters a BIP39 seed (or uses a
hardware wallet), the full derivation path is configurable in the
install wizard.
THAT is easily the best thing you've done with this release... that is going to save a LOT of people a LOT of frustration... I've been helping a lot of people recently with the dreaded "Password did not unlock the wallet" error with MultiBit HD... Until now, the only compatible wallets were "Breadwallet" and "Simple Bitcoin Wallet" (both wallets for mobile phones!!)... However, this feature is going to make it stupidly easy for them to regain access to their coins (and get introduced to the awesomeness that is Electrum) in one easy step!  |
|
|
|
A wallet file with no password has seed and "Master Private Key" (aka xprv) in plaintext:  Setting a password will encrypt the seed and xprv inside the wallet file that is stored on your computer... But the wallet file itself will still be in "plaintext" (Note how the seed is "random letters" and xprv doesn't start with "xprv"):  Ticking the "encrypt wallet file" checkbox when you set a password will then encrypt the entire wallet file as well:  Note: the data stored in the "keystore" section in Electrum will depend on the wallet type and how it was created (For instance, it doesn't store imported BIP39 seeds, only the xprv... and if you create a wallet based on imported private keys instead of a seed... all the private keys are stored... but the same rules apply... No Password = Everything plaintext, password = import stuff encrypted in plaintext wallet... password + encrypt file = EVERYTHING encrypted ) |
|
|
|
|
Depends what you're really wanting to achieve... but in general, sweeping is probably "safer" than importing.
While both methods require you to "expose" your private keys... sweeping moves all the coins to new (and hopefully unexposed) private keys. Importing leaves the coins on the old keys which have effectively been exposed.
|
|
|
|
It works fine with Electrum... you can test this message on coinig.com: 148csPChWs998WStfvLgZ9awkKMx13jVWb This is a message from 28th July 2017 by HCP H84BhBQJR0Jl4Mv7YewJzNUiRNJomzSic1ugmiZqJFFzRBpSFH3IOUBU02P2kgZiniyLlpHGQT6UfRYRnsLtOsU= be VERY careful when you copy and paste that it isn't adding extra spaces and/or line breaks etc... especially in the "message", as even just one extra "space" character at the end of the message will break the signature. |
|
|
|
It doesn't show on ViaBTC because it has an unconfirmed parent: 7d149d0dfda8903554b88d70c74db1ef39b28c055d28fcc9a47e24e619762a9eYou should try accelerating that transaction with ViaBTC first... once it confirms, your transaction should confirm "normally".. especially with a fee that big! In fact, with current network load... it might just work as a "Child Pays For parent!"
EDIT: For whatever reason, it seems like the unconfirmed parent had dropped from the mempool? So I rebroadcast it... and then rebroadcast your transaction as well... seems like they're both showing on multiple block explorers again |
|
|
|
|
Show Posts
