|
Just install the BCH "app" on your Ledger Nano S using the Ledger wallet manager Chrome app.
Then unlock the Nano S and open the BCH app.
Now, when you open the "Ledger Wallet Bitcoin" Chrome app, if it doesn't prompt you to select BTC or BCH, click on settings -> Blockchains and then select BCH.
You'll see your BCH wallet, generated from your Ledger Nano S seed... And you can get a BCH address from that
|
|
|
|
The only option is to attempt to crack it using brute force... The wallet files for MultiBit are encrypted using AES256 encryption. Your best option for brute force attack is probably using gurnec's BTCRecover tool... It requires that you can use Python and the command line... And you'll also need a fairly good idea of what your password might have been... Or you need to have used fairly simple password. If you have absolutely no idea what your password was and/or you used a relatively long and/or complex password, chances of successful recovery are pretty much zero Refer: https://github.com/gurnec/btcrecover |
|
|
|
I can't seem to find any wallets that will let you recreate using xpubs... The nearest I could find was coinb.in website ( https://coinb.in/#newMultiSig), but that only lets you use individual hex public keys, NOT xpubs... So you'd have to put the xpub into something like the BIP39 mnemonic tool ( https://iancoleman.io/bip39/) first... just paste the xpub into the "BIP32 root key" box at the top. Then, get the first 2 or 3 hex public keys, put the 2nd xpub in, get 2 or 3 hex pubkeys, 3rd xpub... 4th xpub etc... Once you have your hex public keys, you can then then use coinb.in to generate the MultiSig addresses using the hex pubkeys (note that the hex pubkeys need to be entered in alphanumeric order, so 021xx before 02Axx before 031xx etc). Click "submit" and make sure it's the same as what Electrum has created. I've tested this process and it works... The trick is to click the BIP32 tab on the BIP39 tool and set a "custom derivation path" of: m/0 otherwise the BIP39 tool won't generate the same hex pubkeys as used by Electrum It's a bit tedious and requires a bit of manual work, but both the BIP39 tool and coinb.in can be downloaded and run offline! If that's too much work... maybe do a dummy run using a throwaway set of xpubs/multisig wallet and an online computer with Armory to satisfy yourself that it will generate the same addresses? |
|
|
|
Hi who can save me with this transaction i have all the day waiting is from yobit
Please
And you'll probably be waiting for another day...  YoBit "cheaped out" on fees... 120 sats/byte when recommended are over 300 sats/byte ( https://bitcoinfees.earn.com) due to the 60,000+ unconfirmed transactions ( https://blockchain.info/charts/mempool-count) So, I accelerated your transaction using both ViaBTC and AntPool... Unfortunately, the transaction is 521 bytes so would be $4 on confirmtx.com  Hopefully one of those 2 miner's finds a block soon... I'd expect it should hopefully confirm in the next couple of hours.  |
|
|
|
hello i have this sequences but what should change that i want multipler basebet *3 if loss ? can u help me ?
I assume you mean you want to multiply the basebet if all 4 bets in the sequence lose? What should happen if you win 1 of the four bets but lose the other 3? And 2 wins/2 losses? And 3 wins/1 loss?  The code below only multiplied by 3 if four losses... Otherwise it'll stick with 0.0000001 as start of sequence In any case, you need to create a way to track the number of wins... A counter and the use of "if (win) then" would probably do it... And then just use something like: -- NOTE: INCOMPLETE CODE -- DO NOT COPY PASTE!
chance=49.75
minbet=0.00000001
seqnum=0
winCount = 0
basebet = minbet
function dobet()
if win then
winCount = winCount + 1
end
if seqnum>3 then
seqnum=0
if winCount == 0 then
-- lost all 4bets, multiply by 3
basebet = minbet * 3
elseif winCount == 1 then
-- stuff
basebet = minbet
elseif winCount == 2 then
-- other stuff
basebet = minbet
elseif winCount == 3 then
-- more stuff
basebet = minbet
elseif winCount == 4 then
-- yay we won lots!
basebet = minbet
end
winCount = 0 -- reset count
end
if seqnum==0 then betchoice=math.random(1,3) end
if betchoice==1 and seqnum==0 then
bethigh=false
nextbet=basebet
end
if betchoice==1 and seqnum==1 then
bethigh=false
nextbet=previousbet * 2
end
if betchoice==1 and seqnum==2 then
bethigh=true
nextbet=previousbet * 2
end
if betchoice==1 and seqnum==3 then
bethigh=true
nextbet=previousbet * 2
end
....
Do the same for the other sections with nextbet = basebet for seqnum==0 and previousbet * 2 for the other seqnum
...
|
|
|
|
In all likelihood, those funds are lost.  BTC-e is dead, so your only hope is to contact the Wex.nz support and see if they can assist. Chances are pretty slim that they'll be able to recover the funds, and their support seems fairly overloaded and slow to respond. I don't think Wex.nz has direct access to the old BTC-e deposit addresses... It seems like they only have access to a limited number of cold storage addresses... As they were only offering something like 50% recovery of funds last time I looked? (And that was by way of a "token" not actual BTC) |
|
|
|
You could always just try logging into the blockchain.info wallet via the website... It seems like you have the WalletID in that email, you'd just need the password that you used when you originally set up the wallet back in 2014. If that walletID isn't valid, use the "having some trouble? View options" link on the login screen and input the email address you used to register with blockchain.info to get the walletID emailed to you. You can also try the blockchain.info wallet import utility: https://blockchain.info/wallet/import-walletAgain, you'll need the password used to encrypt it... ie. The wallet password you used back in 2014. |
|
|
|
You don't even need to send any funds... Just note down the addresses that have been generated... Then re-initialise the device (wrong PIN 3 times), select the "X" symbol when asked if you want to configure as a new device... Enter your seed (NOTE: This takes a LONG time)... After that's done, double check that the addresses being generated are the same... If so, you have it all correct. |
|
|
|
And is twice the price To be honest, the "added shiny" isn't really enough to tempt me to get the Trezor T. I'm a big fan of the K.I.S.S. principal... But good on Trezor, I'm sure it'll appeal to the "ZOMG colour touchscreen!!?!" crowd What does concern me... will Trezor run the "only add new coin support to the new device" play? ie. Stop development on the older device? |
|
|
|
HCP - Yes I did download from https://electrum.org/#download From that page I downloaded the Windows Standalone Executable and immediately installed it. I had at first copied the seed only to a Word document. I would estimate that after an hour or so I wrote it down on a piece of paper and put it in a safe place. I also then deleted the word document. Well, it's possible that by storing your seed in digital form on your PC that it has been compromised. Seeds and private keys should never be stored digitally unless they are encrypted and even then only if proper precautions are put in place to ensure no 3rd party access is possible. It is possible to recover deleted files... But that's some serious hacking effort for 0.0165 BTC... Even with the huge increase in BTC value... That's only ~$120. The address the coins were sent to has collected some 1.57+ BTC so far... But the address doesn't seem to show up in any other "my coins have been stolen" threads that I can see... In any case, the only way for that outgoing transaction to have occurred (if you didn't send it), is that someone has access to the private key for the 113E address. Do you have TeamViewer or any other remote access software installed? |
|
|
|
|
If you password protect the export file... It will be encrypted with AES256 encryption and you won't be able to open it with a text editor to copy/paste your keys into Electrum... In fact, nothing will be able to read that export file except a decryption app like OpenSSL.
You certainly won't be able to import the encrypted file into any known crypto wallet.
Exporting your private keys is not entirely without risk. It would be advisable to disconnect all networks and do what you can to make sure your PC is free from viruses/Trojans/malware etc. before exporting...
Maybe even consider using a Linux Live CD and the Linux version of MBC with your MBC wallet to lower the odds of the keys being stolen, if your main OS might be compromised?
Personally, I'd also recommend that you "sweep" the keys rather than import... Yes, it'll cost a transaction fee, but it'll put your coins into a new wallet with unexposed private keys and with the added backup protection of the 12 word seed!
|
|
|
|
Is it MultiBit Classic or MultiBit HD? Either way, I'd suggest migrating your wallet to Electrum first (importing the keys in the case of MBC, importing the seed in the case of MBHD)... And then using Electrum to send to your hardware wallet. Trying to send from either MBC or MBHD may result in a relatively low fee transaction as the fee calculations in MBC and MBHD are very outdated. Also, MBC and MBHD may have some issues syncing properly and/or opening wallets due to unfixed bugs. MBC to Electrum: https://youtu.be/LaijbTcxsv8MBHD to Electrum: https://youtu.be/E-KcY6KUVnY |
|
|
|
... because what I heard/read online was that BTG was the only fork that doesn't have replay protection...
As i have read too that BTG has no replay protection unlike to BCH which is may be dangerous to those HODLER out there if they transfer their funds on BTG...
You both heard/read wrong or possibly outdated information. Bitcoin Gold (aka BTG) has implemented full 2way replay protection: https://bitcoingold.org/replay-protection-development/ |
|
|
|
Just recently, a certain user seems to be running through one particular board and just replying to EVERY thread they see regardless of when the threads were last posted to... There was one example of a thread where the previous "last posted" date was from 2014!!?! It's fairly obvious the guy is just spamming semi-coherent "Google Translate Output" in an attempt to raise "activity"... I'm thinking future SigSpammer or Account Seller. I can't find any reference in the rules to "necro-posting"... What are the rules on this? Is it worth reporting to the board moderators? Maybe as spamming? |
|
|
|
I think you'll find the OP has posted the incorrect Electrum address (1MREVrSRXyFbnbt4c6X5YdqDHQnFJHnW7Q) and the incorrect Cryptopay address (3EL14BoZCDXBmV65uCGAawXAZZxvnvZwN7)... Probably because they've gone to the "receive" tabs in both apps and been given new "unused" addresses. For the record, as previously stated, the TransactionID for the outgoing transaction from OPs Electrum wallet was: 029f70aaeb6d99cd4b9cd3d53f28667e77b2cc109b84a70bcea037b428cce9c2This transaction, shows the 0.0165 going from OPs address 113Eab3eyWW4wfdpeZ3rNgD2gLWtDU84Gr to 13y2Ct6ee6E7s6y7qK9z798oktVfb1jJ1R (thief's address?) The original 0.0165 came from: 36TEeqDrHnMFz9izKjgJipquvooJ7iTDa7 in transaction: 7d13233cfbc4aaeb56c3b3eed1b46a970acea00750fbeb2b93e9b731c10acc5cAs for how this happened, the OPs computer is most probably compromised... Either the wallet+password got stolen or the seed and/or private key was exposed (exported and/or stored digitally?)... Perhaps the OP downloaded one of the fake Electrums? Did you download from https://electrum.org/#download ? |
|
|
|
|
It has nothing to do with 32bit or 64bit... -daemon basically attempts to launch bitcoind as a background daemon task in Linux (and possibly OSX given its Unix-like nature)...
This functionality is NOT available in Windows. I believe it would require that the Windows port of bitcoind was specifically coded to be able to be run as a "service" within Windows.
The error you are seeing is telling you exactly what the issue is... The -daemon option is unavailable on your OS (ie. Windows). It is an OS limitation.
Either don't use that option, or go and Google "run application as a windows service" if you want to run bitcoind completely in the background without the command prompt window open.
|
|
|
|
* 12 word passphrase(i tried using electrum on my phone to retrieve my wallet but somehow its another walletaddress? Does this depend on what wallet the 12 passphrase code was used or? I doubt it but it might also be from another address where no bitcoins where on but i really doubt that, also the 12 word passphrase was made on a mac not my android phone)
Just a note, Electrum on mobile devices does not allow for recovering non-Electrum 12 word passphrases. If this passphrase was NOT from Electrum, you'll need to use a desktop version of Electrum (available for Windows, Linux and Mac here: https://electrum.org/#download) When you create the new wallet, select "standard wallet -> I already have a seed", then make sure you click the "Options" button and select "BIP39 seed". After you enter the seed and click next, you'll be prompted for the "Derivation Path". I would suggest trying the following common ones to see if you can recreate the wallet: m/44'/0'/0' - default, used by a lot of Hardware wallets m/0' - used by MultiBit HD m/0'/0' m/0 If none of those work, you can also try using an offline copy of Ian Coleman's BIP39 tool ( https://iancoleman.io/bip39/) and see if you can find the right derivation path by experimenting (click the BIP32 tab and select "custom derivation path" from the drop down), buy the chances of it being anything else are relatively slim |
|
|
|
Just installed in on Windows 10 64bit (finally) and its not stop synchronizing..
Try shutting down Electrum, deleting the "blockchain_headers" and "recent_servers" files from your "%AppData%/Electrum" folder and then restart Electrum. NOTE: DO NOT just delete the Electrum folder, you'll lose your wallet files!If that doesn't help, try going to "Tools -> Network"... Untick the "select server automatically" and manually change to a new server. |
|
|
|
waiting for distribution.
Hope it is a smooth process. I can tell both of you (and everyone else who hasn't participated before)... It is a smooth but SLOW process. Your airdropped Bytes will not "instantly" appear at "November 4 05:23 UTC". Instead, as per Byteball.org, "The balances will be snapshotted at the time of the first Bitcoin block after this date". Once the snapshots (of BTC blockchain and Byteball DAG) are done, the system sorts through all the linked addresses and calculates the payments... Largest are done first, so if your expected payout is relatively low, it could take several hours (sometimes up to a day or 2) for your payout to occur. Once all the bytes are distributed, then the BlackBytes are distributed. Again, this is a SLOW process with largest payouts first and, again, can take several days for all payouts to occur. When ALL the Byte payouts are completed, Tony will announce it in this thread. Same with BlackByte payouts. So, with that in mind, please don't come here 5 minutes after the full moon yelling that you haven't received your bytes and that the airdrop is a scam! |
|
|
|
|
Did you also download and fully sync Bitcoin Core?
Armory absolutely REQUIRES Bitcoin Core and it's blockchain (all 150+ gigs worth) to be able to create the Armory database.
Without a fully synced blockchain, Armory will never be able to show your Bitcoins. If you can't (or don't want to) download the full blockchain with Core, what you could do is export your private keys from Armory and import them into another wallet (preferably a lightweight wallet like Electrum).
Note: exporting your private keys does run the risk of potentially exposing them to any malware or trojan on your PC and possible loss of Bitcoins. It should NOT be done lightly... Make sure you are fully aware of the security implications and take appropriate precautions before doing so!
|
|
|
|
|
Show Posts
