Bitcoin Core 0.14.2 is the latest version of Bitcoin Core.

There is no such thing as "the official wallet" of Bitcoin. No wallet is "the official wallet".

That's a file that is generated by SWIG when you compile the C++ code.

No such ads have been added to Bitcointalk. You probably have adware on your computer. You should run a malware scan and make sure that you don't have any malware on your computer.

You should try to not make any transactions around August 1st. That means both make and receive as you can easily be tricked into thinking you have money when you don't or your transactions may not be confirmed when you think it has been. If you have miners, then read up on what all of the proposals are and point your hashrate towards a pool that mines the proposal that you support.

The platform doesn't matter. The Armory version might make a difference, but none of the wallet code as been changed in any of the latest versions.

Armory doesn't use .dat files. If you are seeing .dat files that are supposedly for armory, those aren't Armory files.

How would you know they aren't corrupted? Do you happen to know the Armory binary file format? Armory uses a binary file format that you wouldn't know whether it was corrupted unless you examine it byte by byte.

Have you tried the Armory wallet recovery tool? It's in the software itself.

That's for wallet.dat files which are for Bitcoin Core only, not Armory.

Of all the log files you could choose to upload, you have chosen literally the most useless file as armorycpplog.txt is no longer even used. Can you instead post BOTH armorylog.txt and dbLog.txt.

You should also try using the 0.96.1 Testing Build #3: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.3-testing

The banscore is incremented for each piece of data that is received that an honest node wouldn't be sending. For example, receiving an invalid block from a node increments the banscore by 100, resulting in an instant disconnect and ban for that node for 24 hours. There are a variety of other things that can increase the ban score and its all littered throughout the message processing and validation code.

If your wallet files are corrupted and you don't have any backups, there is nothing that anyone can do.

Try using Armory's recover wallet tool and see if it can recover anything.

The wallet files are not text files, and actually contain basically zero readable text except for descriptions and labels. You won't get any information out of the files by opening them in a text editor.

Those are actually macros, not functions. They are defined here: https://github.com/bitcoin/bitcoin/blob/master/src/sync.h

The banning system in Bitcoin Core is supposed to help prevent DoS attacks, not just DDoS specifically. It does work, but it really is only used for disconnecting and temporarily banning nodes that are misbehaving and sending mangled data, not necessarily attacking you. If you were under a DoS or DDoS attack, the ban system may not be all that effective although it may help a bit.

Some wallets will choose to forget that a transaction happened or allow you to respend the coins after a certain amount of time or after you tell it to do so. This allows you to create another transaction which spends those coins, but that does not necessarily mean that the second transaction will be confirmed or will be the one that confirms. If nodes still remember your first transaction, then the second one will be rejected as a double spend, because that's what it is. The first transaction can still confirm too. Once one of the two transactions confirms, the other one instantly becomes invalid and will be dropped by all nodes on the network.

If your wallet does not support such features, then it may seem like your coins are "locked" or "lost" or unspendable, but they actually aren't. It just means that your wallet does not provide enough advanced functionality for you to make these double spends (and rightfully so). There is nothing in the network rules that prevent you from creating multiple double spends, just that only one of those double spending transaction will confirm.

Contrary to popular belief, transactions are not actually canceled. There is no mechanism which can "cancel" a transaction and make it no longer "active". What happens is that your wallet chose to forget about the transaction after a while. However that does not necessarily mean that other people's nodes did too or that they don't have a copy of your transaction. If someone has a copy of it and decides to rebroadcast the transaction, then the transaction will be on the network again and can still confirm. Even if it isn't rebroadcast, it can still be confirmed.

All paying a low transaction fee will do is make your transaction take longer to confirm. Once the transaction has been broadcast, the transaction has potential to be confirmed regardless of how many nodes have "forgotten" it. All it takes is one person to rebroadcast your transaction and the whole network will "remember" it again.

Yes there is, the transaction that you highlighted is that transaction. 1EE... is a change address of yours; the other output in that transaction corresponds to who you actually sent the Bitcoin to as indicated by the transaction list.

---

Did pywallet work? Your private keys will be 51 or 52 characters long and begin with a 5, K, or L. If you see any strings like that, then you have private keys which you can try to import into another wallet.

No, you don't. A watch-only wallet means that there are no private keys whatsoever in that wallet. Your password is useless here as no private keys are generated from your password. Your password is only used to encrypt the private keys, not anything else with them.

---

Do any of these three files exist: C:\Users\Admin\AppData\Roaming\Armory\armory_26BzNYf9H_.wallet, C:\Users\Admin\AppData\Roaming\Armory\armory_2gJKi3aoH_.wallet, C:\Users\Admin\AppData\Roaming\Armory\armory_2AYDvuXW7_.wallet? If they do, are you able to import them? If you can, what do you see when you do import them?

---

Sidenote: please stop spamming other threads about your issue. You already have this thread for it and people are helping you. By constantly asking for help in other threads you are breaking the forum rules.

BIPs 70-72 didn't exist until July 2013, and BIP 73 did not exist until August 2013. The thread I linked to was from 2011, and IP transactions were actually being removed before then. The removal of IP transactions was completely non-contentious even without the existence of BIP 70 or anything like it.

Armory 0.93.3 won't work with Bitcoin Core 0.13.1+ after segwit activates. However if you use an older version, the older versions of Armory should work fine after segwit. You just won't be able to use any of the functionality provided by segwit.

What makes you think it was a contentious change? Here's the thread discussing this change: https://bitcointalk.org/index.php?topic=9334.0. It is very non-contentious. Pretty much everyone agrees with the removal.

First of all, this is not "Core's decision". Bech32 was not created by "Core" and has not yet been adopted and implemented by the other developers of Core. It is the proposal of a few people who work on Core but they are not and do not represent Core.

This is all explained in the BIP here: https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki#rationale

Yes. If someone has a quantum computer that can get private keys from public keys, then if that person gets just your Master Public Key, you're screwed anyways as they can then get your Master Private Key.

Yes. This only applies to non-hardened derivation, which is what most wallets use (including Electrum) as that is what allows for watching only wallets. Hardened derivation prevents this but also means that you can't have a watching-only wallet as easily (it requires going back to the offline machine to generate a bunch more addresses instead of generating from the master public key).