Both you and the poster above have said to check her PC for seed words? Does anyone actually invalidate the use of their hardware wallets by having their seed words on their machines? Like what the hell?
Sadly, yes... there have been numerous instances of people who did stupid things like email themselves their wallet seed mnemonics as a backup... or write the phrase in a text document... or take pictures on their phones of seed phrases displayed onscreen etc. A lot of people just don't seem to comprehend how easy it is to "lose" crypto...  I would certainly look for the recovery card or a list of 24 words in papers/notebooks etc... but I would definitely be searching through the laptop as well. |
|
|
|
Hello,
The late versions of electrum reload the lists in timeframes of some seconds. This is really uncomfortable since when editing a label you suddenly are thrown out and even your sorting is gone. So at the end you sort fast and write fast and maybe even save the first part of the label first before it reloads again.
Can this be changed? I just want the list to stay the way I sorted it and of course it should let me write without reloading.
I think the "refresh" might be related to having the "fiat" value displayed... screen refreshes when fiat value is updated etc. When the displayed fiat value is set to "NONE" it doesn't seem to refresh (as often):  After changing this setting, you might need to restart Electrum to get it to stop refreshing... Also, since some time all the addresses are in one huge list again. Might be that is to bring users to create a new wallet from time to time but it's still troublesome. Can we setup somehow to not show used and empty addresses?
You need to turn filtering on using "Wallet -> Addresses -> Filter":  This will then allow you to use the "all/receiving/change" and "all/used/unused/funded" filters:   |
|
|
|
First, if you just hit random pin code tries as some people suggested, you will be locked out from the Ledger as it has built in security, after a few wrong tries the time for you to be allowed to enter the pin again with increase exponentially.
Trezor has the exponential time delay, not Ledger. With a Ledger, after 3 incorrect PIN attempts, the device actually wipes itself. To recover coins from the Ledger Nano S, you need either: 1. The device AND the PIN number. Having the physical device without knowledge of the PIN is effectively useless. or 2. The 24 word seed mnemonic My advice would be to search the laptop and all of the Aunts physical papers/documents for the 24 word seed mnemonic. Hopefully she used the official recovery card that looks like this:  That will make it easier to recognise. Otherwise, she might stored them in a document stored on the laptop. |
|
|
|
Hope my experience may help someone as I've just lost 0.63284516 BTC by using a scam site.
Do you mean you have lost your fund for using chipmixer, has it not gave you withdraw option or you just lost on betting on the site chipmixer? If you loss on betting then it is not scam it is loss on betting. Did you read any of the last page? Or did you just need to make your posts for the week as you made 15 posts in 30 minutes today?  Not only did he say he lost his BTC to a scam site in the post that you quoted, but 3 posts above that, he is asking if chipmixer.info is a scam site... which clearly it is... as the ONLY legit URLs are https://chipmixer.com/ and http://chipmixerwzxtzbw.onion/ |
|
|
|
Or the mods could decide to permaban someone (based on the quality (or the lack of quality) of his/her posts), or to give a second chance (sig.ban).
It's alway better to have a year sig ban, if you have an established account, because you would miss only one bull run, but you don't have to start you account from scratch...
You do understand that "permaban" means "permanent ban" right?  The " person" is banned... so their original account is banned, any alts are banned and they are banned from making new accounts. There is NO "starting account from scratch" when you are permabanned. |
|
|
|
You might want to redo your message WITHOUT the "----BEGIN BITCOIN SIGNED MESSAGE----" part!  Yes thanks, i am actually did by accident Please verify again, -----BEGIN BITCOIN SIGNED MESSAGE----- I'am Krislaw from bitcointalk.org, Today May 18, 2019. MyETH: 0xE4a86E4B26dCA832e6424d66B472b33a0B0Eeb86 MyTelegram: @Krislaw -----BEGIN SIGNATURE----- 3NuuM9HTbhFAh97zXfxAu2DT1JkppJfVaC IAzdZqblAj8QaO85F92AytqxMDEtVMWu2b9Ul/wm2yJObVZNo0/yvA2GpELvNcBXsnRN5aIr0/xRjH1CkFMVtAw= -----END BITCOIN SIGNED MESSAGE----- There we go... Quoted and Verified using Electrum:  |
|
|
|
The message is only displayed when directly viewing the profile and is not under every message they post.
This ---^ It basically invalidates the entire argument of this thread. It isn't like the user has this posted under every single one of their posts... ... because you are carrying that sign which can be used by people to attack you instead of addressing the post (typical in discussions in which someone doesn't agree with you and just use something else that isn't part of the point, like a grammar mistake or physical defect etc...).
As for the whole "they'll be taunted in arguments intellectual debates" thing... oh, puhleeeeezzzz... "you got sigbanned so your argument is invalid" is about as effective as "you're a sigspammer so your argument is invalid" If someone has to stoop to that level... it's going to be fairly obvious to anyone with half a brain who is actually winning that debate  Just to be clear, I'm claiming that 100% of people that plagiarize did so to boost their post count intentionally with the intention of escaping detection. That means that they did not value their post enough to read a topic, come up with a somewhat insightful response, and reply. Rather they found a relevant post somewhere else and responded with no thought put in to furthering a discussion.
I think you're giving too much credit to some of these users... insofar that I doubt that they believed or knew that they needed to escape detection of anything. Most of them haven't read the rules until they got banned and linked to the rules in their " I didn't break any rules Ban Appeal" threads. |
|
|
|
The Android Electrum wallet has it's own builtin keyboard that prevents you entering "non" BIP39 wordlist words... Once you type in the first character of a word, ONLY characters contained in BIP39 wordlist words are available to type and you have to select a word from the presented list:  However, it is possible that the OP has simply got one of the BIP39 words incorrect... there are very similar words in the list... things like kit/kite, kid/kind, keep/keen etc |
|
|
|
|
I don't think you can "boot" VirtualBox... it still needs to be run inside an OS of some description. No harm in trying VirtualBox and see if it works. You're not going to damage or break the Nano S. At worst the Ledger just won't be able to connect and you'll just waste a bit of time. If that doesn't work, then you can give the Live distro (with persistence) a go.
Likewise, there is no harm in trying Windows 7 in "safe mode" before you attempt any of this as it is probably the easiest/quickest solution to try first.
Given the choice, personally I'd just upgrade the box to Windows 10
|
|
|
|
Lets assume the mempool doesn't empty and for some reason my transaction fee is not enough, will my transactions be dropped and returned to their original addresses I sent from eventually? If that make sense.
The default "expiry" time for a transaction, that is the time at which an individual node will "drop" a transaction from it's mempool, is set to 14 days for Bitcoin Core nodes. Note that this is just a default setting, and is customisable... Node owners can set whatever they like, so there is no guarantee that any given node will even drop the transaction after this time. Now, let's assume ALL nodes use 14 days. If your transaction was "stuck" for 14 days and was then dropped by every single node... then it would be like the transaction never happened, there would be no record of it and you could simply create a new transaction spending those UTXOs and it wouldn't be rejected as being a double spend attempt as there would be no record of the original transaction. However, it's possible that your original transaction could be rebroadcast... either by your wallet or by another node... so that it is never dropped by any nodes and remains in node mempools forever. Attempting to then send a new transaction spending those same coins would likely be rejected as a "double spend" attempt (unless using Replace-By-Fee aka "RBF" to increase the fee). There are also situations between those two extremes where some nodes will drop it... and some won't... In this case, it's possible to attempt to create a new transaction to replace the old. The nodes that dropped your original will accept it, the ones that still have your original will not. Either one of your 2 transactions could get confirmed at this point... most likely decided by which one has the higher fee, but not guaranteed. As a user, there is nothing you can do to influence whether any given node drops your transaction or not... there is no "cancel transaction" option with Bitcoin. |
|
|
|
Firstly... you didn't "double spend" in Trezor. Simply spending an unconfirmed UTXO(s) in a new transaction is NOT "double spending". Also, spending UTXOs from unconfirmed transactions is not prohibited... it just means that the 2nd transaction cannot be confirmed until the first one is confirmed. Note that this could actually occur in the same block. For the record, I've seen "chains" of unconfirmed transactions 25 transactions long!  As for what is likely to happen to your transactions... eventually the network congestion will ease as the price has dropped a little and stabilised, so there won't be quite the number of transactions taking place as during the big pump. You can see the visualisation of the memory pool here: https://jochen-hoenicke.de/queue/#0,24hSee how the unconfirmed transactions has dropped from 70,000+ to under 20,000? Likewise, the fee levels have dropped back down to the point where a "1 sat/vbyte" fee is enough to get into a block... so I would expect your transactions to both confirm sometime in the next 6-12 hours (if they haven't already). |
|
|
|
This loss streak calculator says you have a 2% chance of encountering a 150 loss streak at 1,500,000 rolls with a 10% chance (aka 90% chance of loss). Not exactly a "big" chance of this happening... but it is certainly not insignificant. If the percentage had been something like 0.00002% then sure, that would be harsh... but think of it like this, if you set your win rate to 2% and then hit a win before 1,500,000 rolls you'd be effectively achieving the same sort of odds. Just to make you feel better, I hit a loss streak of 147 once at 10% (on a completely different and very legit site)... so your streak seems reasonable to me.
|
|
|
|
I only see these labels on outgoing transactions, but not on inbound ones. Not sure why they aren't available for inbound transactions.
"Capital Gains" are only realised when you "sell" an item... at that point in time, the difference in price between what you paid for it and what you received for "selling" it is your capital gain. |
|
|
|
|
Please note that VirtualBox isn't likely to be as reliable as running a Live USB distro in terms of USB communication... the reason being that virtualbox still needs to communicate with USB devices via your Main OS, which can often cause issues.
|
|
|
|
Yeah... I've tried helping a few people with MultiBit issues since they shutdown... and have conducted a bit of experimenting and there is definitely something a bit broken with the way they implemented the encryption. I'm not sure if it was a library they used, or a specific version of MultiBit that caused the issue, or if maybe OpenSSL is broken? But I've had instances where I can create an encrypted file from MultiBit... which supposedly should be able to be unencrypted using OpenSSL... however, it won't decrypt properly. It'll either claim the key is wrong or just decrypt garbage. Yet the same key would reliably decrypt the file using MultiBit!!?! Then there are the instances of people being able to decrypt the files... but getting private keys with like 90 characters in them etc. So, it is quite possible that you have a "corrupted" file |
|
|
|
|
A possible solution (assuming it is an HD wallet) would be to revert to a backup of the wallet.dat before you imported the address...
|
|
|
|
It was a mistake, I forgot to do it, but did I make another mistake? If I do something like this, do I deserve this [Permanent] reward?
Yes, those were the rules. Apparently you didn't read them: 33. Posting plagiarized content is not allowed.[e]
33. This includes both copying parts or the entirety of other users' posts or threads and copying content from external sources (e.g. other websites) and passing it as your own.
There are still many other people who make mistakes worse. That doesn't change the fact that YOU broke the rules now does it? Ask you to make a wise decision, I am a user and I want to continue to actively participate. Before you state such things... you do realise, that on the (very) small chance that one of the mods decides to reduce your punishment to a "temp + sig ban", that you will not be able to have a signature for probably a minimum of 1 year. Are you still going to "actively participate" without the financial reward of sig campaign participation? |
|
|
|
That's correct... if you are getting a "different" (and empty) address from the imported private key... then the private key you have is (obviously) NOT the private key matching the address (with BTC) that you have. So, it would indeed appear that the backup you have is for a different wallet. As for getting into the tablet, You might want to head over to: XDA Developers and see if you can find the section relating to your make/model of device. Otherwise, perhaps a local data recovery service might be able to assist? The downside being that these services are generally quite expensive. |
|
|
|
If neither of those versions of MultiBit are able to import your .key file... then chances are the password you are using is incorrect. What is the error you get when you attempt to import the key file? |
|
|
|
|
Show Posts
