|
If you don't have Google Authenticator setup, and you didn't write the seed down (both of which were required when you first created the 2FA wallet) then you will be unable to move the coins...
If Google Auth is not working properly... Try and resync it from within the Google Auth app. There is an option in the Google Auth settings menu to resync with the servers.
|
|
|
|
They're just made up variables.... You can call them wherever you want... In this case, they're what is known as a Boolean or True/False "flag" used to indicate a specific state... Are we "betting high"? Yes or No? Etc With regards to the if/elseif/else question: www.tutorialspoint.com/lua/if_else_statement_in_lua.htmThey're useful for identifying a specific condition when you have multiple options... Ie. (If) Is it blue? (elseif) Or red? (elseif) Or green? (elseif) Or yellow? (else) Or none of those colours If the terms aren't familiar to you, then I suggest you read some basic programming tutorials and the ones that Seuntjie wrote, specific to the bot: https://bot.seuntjie.com/ProgrammerMode.aspx There is nothing called elseif.
Yes, there is...  |
|
|
|
Do you know how you got hacked? This is very serious since electrum seems to be the preferred wallet for most etc.
As the OP stated... He downloaded malware... It wasn't a security flaw in Electrum How do electrum wallets get hacked?
Through poor security practices by wallet owners... For instance, downloading infected software that installs viruses/trojans/malware... Insecure/non-updated operating systems that have unpatched bugs that allow hackers access... Once the malware is on the machine, there are various ways they can leak the info to the hacker, some detect certain programs and send screenshots, so they can see when your seed/private key is displayed... Some scan for wallet files... and then log keystrokes so they can detect passwords etc Some just trick you into sending coins to the wrong address but replacing addresses detected on the clipboard with their own |
|
|
|
Okay so i have a few btc addresses where i used those addresses a lot to send and receive. I also have btc addresses where there shows btc amount there but i never used those addresses even once.
They're probably change addresses... If you don't spend the full amount of a UTXO, you get "change" which Electrum puts back into a new address. These new addresses are effectively linked to the original address you sent from... As they'll show on the blockchain. Example: https://blockchain.info/tx/fa65a6c0fc053d1ff861023dfc2f9a5eb6ef88095d9ff9b85ae56904613d26f3Here the person had 2.86789873 BTC in address 18doD24d3UpKVcVcQyUMwoxtum2JcqgEUS, they sent 2.85963189 BTC to 1Q6hc4irsnqcnq68XZE3t7JVJBkVBeseFN, which left a change amount of 0.00691084 BTC, which was placed into address 1JpvUJ7FXziVNZ4CT7WRSimnS72oHVYhw9. So the 1Jpv "change" address is now linked to the original 18do address... (Note, it's also possible that the person actually only sent the 0.00691084 amount and the 2.85963189 amount was the change... Further analysis would be required to determine which was which, but you should get the idea of how people can see the links etc) Okay but let say starting from now, i want i request btc from a site and give them a brand new btc address i never used. Then when i receive that btc, i would send that btc to another site for example. So wouldn't that mean you cant really just use a btc address once? Thus its really twice since you have to receive btc first to that address? Then the next time you receive btc, you have them send it to a completely different btc address? Yes, by use an address once, people really mean 1 receive, 1 spend... Also one other thing. So when i send btc to a site or someone, if there is not enough btc on addressa, it would take some from b. But when the site or other person receives the btc, IT ONLY SHOWS ONE BTC ADDRESS RIGHT? No. It will show all the addresses that coins have been used from. Check this transaction: https://blockchain.info/tx/78cb7aa7d8780860928cf009887d75628995420f352d09d7f158674fa68533e4You can see how it has combined UTXOs from around 30 different addresses into one payment... All those addresses are now effectively "linked" as belonging to the same person. |
|
|
|
Instead of giving out your full wallet file, I suggest that you use btcrecover to generate a partial extract of the wallet file... That way you can just give the people helping the extract and they'll be able to test password guesses, but not have access to your coins when they find the password. Have a read here: https://github.com/gurnec/btcrecover/blob/master/docs/Extract_Scripts.md |
|
|
|
If seed is greyed out and the wallet is asking for authenticator codes, you're running a 2FA wallet... The is no way to find the seed from this wallet... It is not stored in the wallet file. If you no longer have the 12 word seed phrase, then you have no way to recover or restore the wallet... If resyncing the time in your Google authenticator app does not work, then you chances of recovering the coins aren't great  |
|
|
|
It's very possible... do a Google search for "accidentally sent LTC to SegWit address" There is a reason they put all the warnings on deposit address screens on the exchanges... There are a number of coins that use similar address algorithms and you can end up creating a so-called "cross chain" transaction... Which, essentially just means that you sent funds to a valid, but unintended address. Sometimes you can recover the funds, sometimes you cannot. It depends on the currencies involved, the algorithms for converting private key to public address and who "controls" the private key. In this case, I believe the OP is out of luck as, while it was a BCH to BTC address situation... He doesn't have the private keys as it was an exchange based deposit address and they seem to have a "we don't help for incorrect deposits" policy Note: We will not refund an incorrect withdrawal/ Deposit. This deposit address is for BitCoin (BTC) only. |
|
|
|
I have found out the reason for this issue.
The code from Github is not integrated and you need to download dependent packages.
Thanks!
Which packages exactly?? I thought the build scripts picked up the required packages... I'd be keen to know the specifics as I'm wanting to play with v3 on Windows... But my builds don't start |
|
|
|
|
The only way for those BTC addresses to get linked would be if several of them were included in the same transaction... This generally occurs when you need to send an amount that is larger than one address holds, so Electrum has to combine multiple UTXOs to make up the required amount...
For instance:
AddressA 0.1 BTC
AddressB 0.2 BTC
AddressC 0.2 BTC
And you want to send 0.5 BTC... It would need to combine all those 3 inputs... And then they'd all be "linked" as coming from the same source.
However, by right clicking and saying, send from this address, I believe that Electrum will only let you send up to the amount contained solely in that address.
So if you right clicked AddressB and selected "send from this address", it would only let you spend 0.2 BTC max, but it would mean that you never accidentally "linked" your addresses.
|
|
|
|
|
Electrum (as at v2.9.3) does not yet support SegWit addresses...
With the latest Trezor firmware v1.5.2, the default Trezor wallet is generating SegWit addresses... And as you've discovered, these will not show in Electrum, only the Trezor "Legacy" wallet addresses will show.
Thomas has been working on SegWit support for Electrum v3.0 which is due out "soon"... Until then, you'll only be able to use your legacy Trezor addresses with Electrum.
|
|
|
|
I've exported the key as csv from Wallet > Private Keys > Export
Pretty straighforward.
Which will become outdated and effectively useless after you use more than 20 receive addresses or 5 change addresses... And it starts generating more keys in the key pool which aren't in your backup. You don't need to mess around with private keys when you have an HD wallet like Electrum... Just make sure you have safe and secure backups of your 12 word seed phrase. That will enable full recovery of your wallet, regardless of how many addresses you have used. My next step now is to deposit some BCH into my wallet. I'll use Bitstamp for that.
Wait... What? BCH??!?  Are you using Electrum or ElectronCash?? Electrum is BTC only! ElectronCash is BCH. Be careful about what currency you're sending and to what wallet address! |
|
|
|
|
Did your Google authenticator ever work with Electrum 2FA? As in, did it just stop working? Or has it never worked?
Perhaps try contacting TrustedCoin support and see if they can help... They're usually fairly responsive... And the 2FA wallet is using their system to process the Google authenticator codes
|
|
|
|
Would some of the wallets/websites involved have the private keys if they could agree to help?
What wallet has the address that you used? Was it a desktop wallet like Electrum or BitcoinCore or was it a web wallet? In either case, if that wallet allows you to export private keys (or has a 12 word backup phrase)... Chances are good that YOU have the private key and can simply import that key into a BCH wallet and get access to your misplaced BCH  |
|
|
|
[/ quote] What do you mean? This is the official website and it's working: https://wallet.mycelium.com/[/ quote] Edit 2: It looks like i dont know how to properly quote single line... Sorry  Remove the first "/"... The quote tags are used as follows: [quote]the quoted message goes here![/quote] |
|
|
|
So... You have 2 different 12 word seed phrases? One from Android and one from your desktop right? If so, you just restore the original one you had from Android with the 1+ BTC and you'll have access to the coins again. If there is no "restore" option on Jaxx, you might need to clear the app data on Android so that Jaxx reverts to "newly installed" mode and should have a "pair/restore" option when you first run it. Knowing the addresses doesn't help... But having the backup phrases certainly does!! However, if you only have one backup phrase... Then you're probably out of luck, as it would appear you only have the backup phrase with the small amount... And not the backup phrase with the 1+ BTC |
|
|
|
|
It depends on the type of address and the currencies involved...
Theoretically, whomever owns the address that the coins were sent to, should have the keys... But it's possible, given that you've stated that an incorrect currency address was used, that no one currently has the private keys for it...
The reason the currencies involved is important, is that if they're "similar" like BTC and BCH, the private keys from BTC will generate the same address on BCH and vice versa...
However, in the situation where coins are not "similar", it is possible that due to differences in the algorithms for how private keys are converted to public keys/addresses... That no one (or some random party) is in control of the private keys that the coins are now associated with...
What currencies were involved in this incident?
|
|
|
|
|
Saw your post in the Armory forum... Where the app didn't have permission to create the log file... That would seem to confirm my suspicions that it might be a permissions issue.
Right click to Electrum icon and select "Run as Administrator"... See if that solves the problem.
|
|
|
|
Safety issue? No... Not unless someone figures out a way to reverse the sha256 and ripemd160 "one way" hashes! Privacy issue... Maybe. Posting your addresses is effectively linkng your BTC address to your username at the least... And potentially let's others see how many coins you have and possibly what you've been doing with them. "We" = potentially everyone on the internet... But most probably just the people who read these forums Personally, I wonder if you didn't actually have 2 different seeds running on your devices... So the Android device had different addresses (hence different balances)... And syncing had effectively overwritten the wallet on the Android device with the seed from the PC. |
|
|
|
"Don't use a bootstrap.dat. That's way slower than just resyncing the whole blockchain from scratch."
This statement proves you don't know what your talking about
Plus the debug.log will never say anything about a fragmented hard disk...which is what the problem was....the chain kept syncing on top of fragmented disk space so the drive kept thinking it was already full when it was over half way fragmented and I had to run diagnostics and de-fragment it numerous times because it kept saying there was still 1% fragmented...
0% fragments and full disk optimization was the fix....had nothing to do with debug.log file
works faster than ever now...
That's complete rubbish.  File fragmentation does not cause the system to think a disk is full, regardless of how fragmented it is... All fragmentation does is impact on read and write speeds as the drive head has to constantly readjust to read the scattered fragments or find the empty sectors that it can write too. And it has been a well known fact for several versions that bootstrap.dat IS slower than resyncing from scratch... https://github.com/bitcoin-dot-org/bitcoin.org/issues/846https://bitcoin.org/en/release/v0.10.0#faster-synchronization"It's better to remain quiet and be thought a fool, than to open your mouth and remove all doubt" |
|
|
|
OK, so a Segwit address is what a Nano is? And I would need to put my BTC back on my computer to participate in the airdrop.
A Nano only uses SegWit addresses if you set it up that way... And generally only of you're using the Ledger Chrome wallet... You can fairly easily set it up to use the "Legacy" addresses... But you will need to transfer your coins to those addresses of you want to use the Nano and participate in the drop... You probably see something like this:  When you start it up, it should ask if you want to use "BTC" or "BCH" and then ask if you want "Legacy" or "SegWit". If it didn't, click on the "Settings" at the top...  Then select Blockchains:  Select BTC:  Select Legacy:  And then you should be in the "Legacy" wallet with "Legacy" Bitcoin addresses:  |
|
|
|
|
Show Posts
