That is not how Bitcoin works. The network has no concept of a "wallet". The network does not know nor does it care about what addresses are in your wallet. There is no such thing as a "wallet ID" to the network (or one that is consistent across multiple wallet implementations).

This is being worked on for the next version of Core (after 0.15.0). It will likely be a minor release.

Yes. That is the human readable part of bech32 and will be the same for all bech32 addresses. Bech32 addresses are different from the legacy addresses (1.. and 3..) since it uses a different encoding.

Bech32 uses a different encoding scheme which is case insensitive unlike the legacy address scheme which is case sensitive. Legacy addresses are encoded with base 58. However bech32 encodes things with base 32 which does not include any casing.

The address should be invalid. It is case sensitive, so that would be wrong.

Since segwit has already activated, such a fork would result in you losing any and all money that is in a segwit output, both nested and native. This is because such a fork without segwit would regard all of those outputs as anyone-can-spend outputs and the miners who initiated that fork would steal all coins in segwit outputs and send them to themselves.

To actually spend those, for native outputs, you would just have an empty scriptSig and it would work. For P2SH nested ones, you would just put the redeemscript in the scriptSig and it would work. There would be no place for signatures to go.

Go to the Armory data directory (it should be C:\Users\Palazzeschi\AppData\Roaming\Armory) and delete the databases folder. Then start Armory. This will force it to build new databases and that should fix your problem.

That's not true. It still has to download part of the blockchain and there is still a lot of info that you cannot get from it without downloading the entire blockchain. For example, you cannot use bitcoinj to find an arbitrary transaction in the blockchain since it does not have that data and it can't ask for that from a node.

That does not look natural. That is almost certainly because of problems that blockchain.info has. It doesn't match what other mempool chart sites like https://jochen-hoenicke.de/queue/#2d show.

Have you tried using Bitcoin Core's -salvagewallet option yet? Although -salvagewallet has a few issues, it should help if your wallet is corrupted. But before you do that, always make sure that you have a backup of your wallet somewhere.

First of all, don't hijack someone else's thread with your own problems.

Secondly, please post your log files.

Only if you want to have it confirm faster.

If you are sending the Bitcoin to yourself to an address in the same wallet, some wallets will say that because the Bitcoin is leaving your wallet (besides the transaction fee).

Please actually read the OP before responding and look at the picture that he linked to. That picture contains enough details.

Your transaction should confirm eventually, but it may take several days. You will probably need to rebroadcast the transaction every day or so to keep the network reminded that the transaction exists.

That is quite strange since I am able to connect to one of the IPs in your log that had a connection timeout. Are you sure that you don't have a firewall that is blocking connections to and from Bitcoin Core? You can try disabling UPnP, but I don't think that is a problem here.

That's from Bitcoin Core allocating space for blk00000.dat and inserting the genesis block into it.

That normally happens when you start a browser. It tends to connect to many things on the internet.

Have you tried doing a full resync? You can see if that will do anything before actually resyncing by renaming the datadir to something else and letting it make a new one. If it is able to establish connections, this means that something is corrupted in your block files, the block index, or the chainstate that is making it unable to connect, although I don't see anything in the log that indicates that that is happening.

I don't think that matters.

Is TOR running? If so, what happens if you stop it and then run Core?

This topic has been moved to Trashcan.

Duplicate

Start with the -debug option and post the full debug.log from that (it may be very large).

The forum does not moderate scams or scam accusations. Topics will not be deleted or moved to the trashcan for being misleading, being a scam, or anything else. The only reasons for a thread's removal is for violating any forum rules which do not have anything pertaining to scams or scam accusations. They only pertain to posting behavior (i.e. spamming, off topicness, duplicate threads, etc.), and those are the only things which will be moderated.

You can click on the Fee in the send dialog and a new dialog should appear that allows you to set the transaction fee.

No, ECDSA keys are not like RSA keys. You can't do that to ECDSA keys.

This topic has been moved to Trashcan.

Duplicate

As many as you want.

Native segwit addresses (bech32) make native segwit outputs which are smaller than the P2SH nested ones (3.. addresses). This saves you 22 bytes when you go to spend the output.