Invalid Fee bug, Endless block header retrieval, and Potential Compromised Node Server #477
Comments
|
we aren't going to be supporting the non-tor electrum wallet anymore after this week (we will release one more binary) |
|
but try restoring your wallet in the electrum tor wallet using your seedphrase |
|
Thanks Justin |
|
Electrum wallet is still the main wallet on the website. If you want to limit its support, you should mention it on the web or pull it from the web. Now the web is misleading and pushing people to the electrum wallet. |
|
yeah we will this week. @Nori-MD what is the compromised thing you're talking about? that the site is flagged? definitely a false positive lol |
|
"Potentially compromised thing", meaning the popup window by Malwarebytes. Was thinking of false positive but since it popped up only for the electrum-xvg.stream address/server (please look at screenshot above in my opening post) and not the others, I became concerned and wanted to ask about it here and see if anybody else had seen similar. Something like that makes one suspect that specific box got hacked - network security professionals would agree. Unfortunately, Malwarebytes did not give any more info for me to pass to you here. Public confidence about the currency being secure will make or break the project. Nobody wants to be "that guy" that got scammed with the hardware Ledger Nano S last week. |
|
Ok here's my report on your recommendations on using the Tor variant of Electrum XVG:
So I'm still stuck. This time there were Python error entries in the log that may or may not help (I've removed the redundant traceback errors): Traceback (most recent call last): Traceback (most recent call last): Traceback (most recent call last): I hope that helps. Thanks again Justin. |
|
Forgot to include screenshot of "invalid line" screen when I tried using a stealth address generated by QT:
|
|
Justin - I've done a little digging around for us all on the issue of the security alert by Malwarebytes (MWB). Unless the machine at electrum-xvg.stream is truly hacked with malware sniffing all the traffic packets (worst case scenario, but low probability), things are ok. It appears that server was flagged purely due its TLD (*.stream). According to MWB at: **_"These gTLDs are blocked because the ratio of bad to good domains may be higher than average, indicating that the registry could do a better job of enforcing policies and shunning abusers.). Currently we are blocking the following gTLDs - .accountant (The wang one is funny) We don't know how many people have already seen similar warnings and stopped supporting XVG after deeming it unsafe. Damage control can be nipped in the bud by something like this in an easily found part of the FAQ file: "A couple new node servers were brought online in the lattter part of 2017 due to overwhelming, unprecedented numbers of network connections causing intermittent connection dropouts between the wallet client and servers. The top level domain (TLD) of "stream" was picked because of its low cost, but later found to be blacklisted by various network security software such as Malwarebytes, thereby causing security alerts and pop-ups. The server at electrum-xvg.stream is to the best of our knowledge, secured and safe." So that takes care of one of three issues, and the block header issue was solved by your suggestion of using the TOR variant of the electrum-xvg wallet client. |
|
@justinvforvendetta That leaves the 3rd of 3 issues, which is being able to transfer coins between Electrum-XVG (TOR or no TOR) and elsewhere such as QT. I still can't do that. Any ideas what I could do based on my post, 2 posts back (the one with logfile and findings)? |
|
electrum servers on our end are updating. hopefully community members who run electrum servers are doing the same. |
|
Hi @justinvforvendetta, one of my boxes is an Ubuntu box that I can compile the server and run, if you'd think it'd help. Disk space, RAM, CPU power, network bandwith won't be an issue. I didn't mean this update to be this lengthy but wanted to be thorough (yet concise with each point), anticipating follow-up questions from you. Update: I'm still trying to figure out how to migrate my coins on the soon-to-be-unsupported Electrum-XVG wallet, over to VERGE-qt. Still no luck - still get "Invalid Fee". I'm pretty sure I'm not the only person with this problem. I'm including four screenshots with a bit of commentary for each, hopefully giving you ideas on what is going on: First, this is a screenshot of overall history. It's composed of quite a bit of little mining deposits. I've since learned that the Electrum wallet (in general, not just the Verge fork - this isn't a problem created by Verge) isn't the best for mining deposits, which is another reason to migrate away from it.
Second screenshot. There's basically four receiving addresses that have been used. If I try to send a smaller amount, whether just 10 XVG or 50, I still get "Invalid Fee". Question: should I be able to do a single transfer of the wallet's contents, or does it need to be done by each of the four receiving addresses using the "send from" function - i.e. 1000 XVG for the topmost addresses, then ~500 for the next one, and so forth?
Third screenshot. Just for review - basically same as above. The "Invalid Fee" bug. When I switch to manual fee setting, when I enter a fee, it's colored blue (but not the number for transfer amount). I don't get the "Invalid Fee" bug when attempting to send XVG coins to the VERGE-qt wallet, but simply, nothing happens. No popup asking for password, etc.
Four and last screenshot. The network window, to show you which servers are being used. The servers by community people aren't there yet, I'm guessing they will start showing up in a few days if not sooner. However, the intermittent connection dropouts are much, much less now. Question: Does the endless "Getting block headers from X nodes" have anything to do with "Invalid Fee"? I'd think the block headers file should be completely synced before any attempts at transferring (just like if we were syncing with a full blockchain), but wanted to ask to make sure in case I'm wrong. Then again, Electrum gives no indication whether it's finished downloading the block headers and simply standing by for new headers, so I never know if it's finished with the block headers or not.
Overall, what do you suspect could be going on? I suspect the "many" transactions from mining could be a possible cause of the "Invalid Fee" bug from what I've been searching (again, just with the Electrum wallet, not the VERGE-qt wallet). I've been finding so many different posts by people who appear to have solved the issue, whether by sweeping private keys, or sending messages to be verified, that it's confusing what to do now. Occam's Razor would say that we simply need more working servers but you're in a better position to guess/suggest what's the next possible step. I'm sure I'm not the only person with XVG coins stuck in the Electrum wallet. I hope those with the same problem but less technically inclined have stayed strong and not given up on XVG! Thanks again Justin! |
|
should be fine now. |
I've been having issues with the Electrum-XVG wallet now for 7 days. Been trying to move coins from that wallet to the verge-qt 4.0.1 wallet. There are three issues pertaining to the "Invalid Fee" bug, endlessly stuck at "retrieving block headers", and potential malware. Can't I please get some help here?
This is for Electrum-XVG 2.4.1 of Win 10 64 bit. This is a bug report, and I will cover these three issues.
(1) The "invalid fee" bug. Again, I am trying to move XVG coins from the Electrum-XVG wallet to the new Verge-QT 4.0.1 wallet. I type in the addressee, the amount to be transferred, click send, then this popup shows up. Somebody earlier a few months ago apparently found a way around that bug but the description wasn't clear.
(2) Also, the wallet is constantly stuck at "Getting block headers from X nodes" (X ranges from 1 to 5). It's been stuck like this for a week now, with computer on 24/7. I'm assuming the block headers need to be fully downloaded before I'm able to make any transactions, yes? Or no?
(3) Lastly, Malwarebytes is flagging server electrum-xvg.stream as malicious. I don't know if this is a false positive but we're talking about digital coins where security is of utmost importance. I've blocked that site, assuming the others are mirrors of each other. What concerns me is that I get the pop-up ONLY for that specific address, electrum-xvg.stream, and not with the others. What is going on here?
Mainly, I need help transferring coins out of Electrum-XVG and into the new verge-qt 4.0.1. This has been very frustrating and time-consuming.
As someone else said, these are "confidence-killers" in the coin, and there are competitors to the coin (Monero, Zcash partnered up with JP Morgan). If we want this coin to succeed over the others, these issues need to be addressed ASAP because competition moves fast. No frustrations, no fears of compromised node servers, etc.
The file log.txt is empty and so I am not attaching it.
The text was updated successfully, but these errors were encountered: