You can't 'brute force' a wifi just because it has WPS enabled.

There are SOME router which have a vulnerability. This vulnerability allows you to get access to the PSK (or more detailed: to surpass the need of the PSK).
But an updated router does NOT have any vulnerability with WPS enabled.

Especially since you almost always need to press a button on the router to enable WPS for a short amount of time (e.g. 60 seconds).




That's completely wrong. WPA2 can NOT be cracked.
Multiple implementations have a vulnerability because the protocol is a bit flawed.

This allows an attacker to lead the flow of the program to a point where the same encryption key is used twice. THIS can be then used to DECRYPT the traffic IN ONE DIRECTION.
The direction (e.g. client -> router OR router -> client) depends on the protocol implementation on each individual router.


But, decrypting the traffic DOES NOT MEAN that the PSK can be cracked or that one can gain access to your network. Those are 2 completely independent cases.

Adding a temporary user doesn't bring you any benefit. Neither does the VM.
With an infected host machine, your VM is compromised too.

The general approach to safely create a seed is:

• Download a wallet (e.g. electrum)
• Verify the signature to make sure you are not a victim of a MITM attack
• Boot your PC with a linux live system (without internet connection)
• Move electrum to your live system and generate your seed
• Back your seed up (offline, on paper)
• Export your xpub (to create a watch-only wallet on your online-pc)
• Delete everything (Or simply shutdown your live system; all traces get removed)

And afterwards you have to make sure to NOT import your seed into a wallet on your online-machine. This would destroy the whole purpose of creating the seed offline.
To sign transactions you either have to use an alway-offline-PC or boot into a live system (without internet connection) each time.

The easier way probably would be to use a dedicated offline machine or a hardware wallet.

I heavily disagree with that.

2FA's whole purpose is to be a second layer of security in case of the password getting leaked.

A user with security in mind and a password which does not composed of the name of a pet + 123, does not need 2FA at all.
If the password is secure AND one can somehow 'guarantee' that their system will stay safe, 2FA is no way necessary.


Regarding 2FA as mandatory is a wrong approach. 2FA won't help you if you are doing everything without security in mind.
I agree with 2FA as a second layer being more tough to hack into, but it is BY FAR not impossible.

Is there a reason you have created a second (almost identical) thread ?

I have answered your question in your first thread. This post (https://bitcointalk.org/index.php?topic=5029186.msg45711317#msg45711317) contains all necessary information you need.


You obviously have only imported an address. That's the problem.
Instead of creating a second thread, start explaining HOW you got that wallet.

Because, either you have done something terribly wrong, or you got scammed. This fully depends on the procedure how you created your wallet.


Again: You can NOT send funds without the private key. There is no work-around or 'hack' or whatever.

Usually (with each PROPER wallet), nothing except for bruteforcing the private key (which does only work if you had a very very weak password or you can remember the majority of your password).

But.. since you are using jaxx you might have another chance.
Jaxx has quite a few vulnerabilities which allow to extract the private keys. You might want to search for one and get/create an exploit to extract the seed / private keys.

And in the future, make sure to have a backup of your mnemonic seed. And please do NOT further use jaxx.

ANYONE can steal your coins if you are using jaxx using simple malware.
In this case, this is helpful for you. But generally this is a worst case scenario.

This snippet is useless.

The best would be to post the complete log. And please use https://pastebin.com/ and provide us the link.
Images are a pain in the ass to look for errors inside a log.

IMO this is the least probable event.
The problem started to appear yesterday (directly after upgrading electrum).

I am not aware of electrum server not working in russia SINCE YESTERDAY. So unless OP didn't use electrum for a pretty long time, it most probably just is a dead server or bad network configuration.

OP, when did you use electrum the last time ? Did you ever had such problems ?
Did you change anything inside of your network (firewall, topology, ... ) ?

I agree with this.


If you have entered the seed AND are seeing transactions and a balance, the chance is almost 0 that there are funds sitting on another derivation path.

The whole messing around with derivation path is often needed because people use their seed and get a wallet with 0 balance and different addresses than they had.
In this case, changing the derivation path helps finding the correct private-/public- keypairs.

But if you are able to access a wallet with the plain seed (how it is intended to be), you have access to your wallet. Changing derivation paths most probably won't get you 'another wallet' with more funds.

---

Transactions do consist of inputs and outputs.
The inputs (which you need the private key for) are used to create new outputs.

All you need to do to check the balance/history is to check the history tab in electrum, receiving vs. outgoing transactions.

This most probably is due to the node having some bad configuration.
A lot of people who try to run a node of a BTC fork (e.g. bcash) start their node with wrong configurations.

These nodes are regarded as bad nodes since they do not follow the correct rules / format. This happens more frequently than one would think.


As long as your node is connected to several other nodes, those log entries are nothing to worry about.

Making a hard drive unformattable per se is not possible. Especially not on a software level.
With root access on a machine, you have full control over the hardware. Formatting is always a possibility.

But malware could theoretically flash the firmware of a hard drive to make it unusable.
This damage can still be repaired by a person with enough understanding, but most probably this would result in replacing the hard drive because of failure.
Especially since such a damage would be non-standard and probably more costly to let it fix by IT repair services, than to simply buy a new one.

Why don't you simply create a transaction and send your funds over ?

What are you referring to with 'single use account' ?
Did you import an address (as a watch-only wallet) into mycelium ? Because if you did, you need to get the private key of the address (remember where you got that address from, where did you import it from) to access the funds.

What happens if you try to 'Send' from your address ? Do you get a message saying "This is a watch-only account ... " ?
If so, you have just imported an address. And the private key is NOT known to mycelium (which is needed to create a transaction).


If you have created a 'Single Address Account', you can simply click on it, and then choose 'create backup' at the upper right.
This will give you the private key to import into another wallet.

But since you seem to be unable to send your funds using mycelium, i guess you have only imported an address.

This warning can be safely ignored.




What (exact) command are you trying to execute ?
Also, did you make sure to have a few backups of your wallet files available ? Pywallet can mess up those files pretty heavily, making them unreadable.

This may be just connection dropping from bad nodes.
If core is running as it should (and has outgoing connections), there is no need to worry about it.

Or doesn't core connect at all suddenly ?

You might want to create a new thread with all the necessary information.

What problem do you exactly have ? You can't open armory on your mac ?
Is/was it installed ? Did you change anything with your system configuration?

A lot of information are necessary to fix your problem. Start off with the basics (OS, program versions, description of what happened, etc.. ).

The nano s AND trezor BOTH had security vulnerabilities in the past.
But all of them required physical access to the device.

Calling one of them not safe, is the wrong way. Vulnerabilities do ALWAYS exist. In each kind of software.
It is just a question on whether / when they are found and how fast / efficient they are going to be fixed.

Yet, no vulnerability has lead to a loss of a trezor or nano s (at least there is no case publicly spoken about).


Both can be assumed to be secure. They are not 100% secured, but you can never achieve full security.

The thing is.. the support can't do anything in this case.
They have no control and/or overview over OP's wallet / case.

The bad design of exodus itself has probably lead to this situation. There are multiple reasons to advise NOT to use this wallet.

While OP might of course (and probably should) try contacting the support, it most probably won't lead to any success..

Pywallet does not run on python3. You need python 2.x to run pywallet.




What are you trying to achieve with pywallet ?
If you want to use it regularly as a wallet (not advised) you do need core + blockchain synced.

But if you only want to dump your private keys, it is not required.

How (with what flags) are you starting pywallet ?

Pip is by default included since python 2.7.9+.
On earlier versions you have to install it with apt-get install python-pip in linux and through running get-pip.py on windows.

Regarding your problem installing pip:
You also need OpenSSL installed on your system. Download and install it and check the OpenSSL version used by python via:

inside the python interpreter. What is the output ?

The 'puzzle in it' is that the private keys associated to the outputs have been generated in a specific way (e.g. a specific formula).
If you look at the transaction more detailed, you'll see that the outputs are 'ordered'. Beginning with the smallest .. to the highest.

Until (including) address 17aPYR1m6pVAacXg1PTDDU7XafvK1dxvhi (0.056 BTC) the UTXO's have been claimed (puzzle solved) already.
But from address 15c9mPGLku1HuW9LRtBf4jcHVpBUt8txKz (containing 0.057 BTC) up to address 1FMcotmnqqE5M2x9DDX3VfPAPuBWArGisa (0.256 BTC) the outputs havn't been claimed yet.

If you find out how to generate the private keys (based on the earlier ones, it may be some kind of increasing difficulty / search space), you can claim those BTC. And that's the 'puzzle'.

Yes, you need to enable it in case of it being disabled.
You'll have to look into the settings. Are you running an android or windows tablet ? Which tablet are you using ?

The best probably would be to check it using a standard USB port on a computer. Don't you have any computer accessible ?