Did you delete the "databases" folder or you just updated Armory and didn't delete that folder?
As mentioned by nc50lc above, you can also rebuild and rescan databases.

If you did so but it didn't work, post the logs, so we can know what's causing the problem. You can find the logs in "armorylog" text file.

Walletexplorer can't be helpful here.
Walletexplorer put different addresses in a same wallet if they are co-spent in a transaction. For example, if you make a transaction and use addresses A and B as inputs of that, then both addresses go to a same wallet. This is all they do and there is no way they can know which of addresses is the change address.

To mine a block, miners must solve a proof of work problem.
As the proof of work problem is solved through brute-force method, there is no way to know when exactly it will be solved. Given the difficulty of the proof-work problem, we only know that blocks are mined (roughly) every 10 minutes on average.
If the fee you pay for your transaction is high enough, your transaction will be included in the next block. But the time it takes for the next block to be found does't depend on the fee you paid at all. In the case it takes 1 hour for miners to find the solution, you have to wait 1 hour even if you have paid a very high fee.

Take note that even if you delete the files, they are not permanently gone and they may be still recoverable using some recovery tools.
When you delete a file, it means that you no longer need that file and your OS hides that file. The file exists until it's overwritten by some new data.  

You are wrong too.
The block time isn't exactly 10 minutes. Blocks are mined (roughly) every 10 minutes on average.
A block may be confirmed a few seconds after the previous one. It's also possible that it takes more than an hour.

I would move the wallet file to the default location too. But note that you don't have to move the backup file to the default location. You can move the backup file to any location you want.


There is no difference. Both can work as a backup.
When you click on "Save backup", electrum actually create a copy of your wallet file.

First of all note that there is no miner in a POS cryptocurrency. Instead, people need to stake their coins.
In a POS cryptocurrency, people with more coins can have more power and since a significant percentage of the coins are usually owned by a few number of people, they can have full control over the network and make the coin centralized.

It's true that trustwallet is closed source and it shouldn't be used. But it allows you to adjust the the transaction fee.
To do so, you should tap on "Setting" button at top right corner the screen before confirming transaction details. After that, you will see a new window in which you can enter the fee rate.

No. You get 1 Free golden ticket for every 0.005 BTC you wager and it doesn't matter whether you set the multiplier to 1.1 or 50.
Below is the information displayed on "Multiply BTC" page.

If all outputs of a transaction have been spent, (in theory) it's possible that a new transaction with the same ID is included in the blockchain. In practice, that's very very unlikely.
If there's a non-spent output in a transaction, even in theory it's impossible that a new transaction with the same ID is included in the blockchain. According to BIP30, a block can't include a transaction with the same ID as a not-fully-spent transaction.


Yes. By default the mempool size is 300 MB. (A node can have a different setting.)
If the mempool reaches that capacity, the node has to remove the transactions paying low fee, so transactions paying higher fee can enter the mempool.


In every new block, some transactions are included in the blockchain. Other transactions stay in the mempool and wait for next blocks.

Yes.

---

The thing I don't understand is how the attacker can manage to do this and that's why I said it's very very unlikely.
For being successful, it's needed that majority of nodes see transaction_2 first and the honest party (the one who does CPFP) sees transaction_1 first.

The coinjoin transaction is using UTXO A and is non-RBF. UTXO A doesn't have any unconfirmed parent and there is no problem here.
There's another transaction made using UTXO A. In this transaction, there's another input which is UTXO B. This transaction is also non-RBF.

The two above transactions have been made at the same time. So, some nodes (including the other party of the coinjoin transaction) see the coinjoin transaction first and some nodes see the other one first.

The transaction that has created UTXO B is still unconfirmed. This transaction has been flagged as RBF. As this transaction is RBF-enabled, the sender can easily double-spend that.
With doing this, the transaction spending UTXO A and UTXO B is invalidated and now the coinjoin transaction is the only transaction that uses UTXO A. Now, the coinjoin transaction can be propagated and confirmed without any problem.

Note that the attacker isn't trying to invalidate the coinjoin transaction at all.
The attacker is only trying to force the other party to pay more fee for the coinjoin transaction. (The other party doesn't know what's causing the issue and think that the problem is with the low fee.)

Again, this is what I understood from o_e_l_e_o's post and I think it's very very unlikely that the attacker can succeed.


From my understanding, this is not the case here.

The UTXO used in the coinjoin transaction doesn't have any unconfirmed parent at all.
That UTXO was combined with another UTXO in a different transaction at the same time as the coinjoin transaction. This is the transaction which was invalided with doubling-spending its parent.
As both transactions have been made at the same time, it's possible that the client see the coinjoin transaction before the other one and doesn't understand what's causing the issue.
This is my understanding from o_e_l_e_o's post and I really don't know how likely this is.

Me too.


No.

Even if some nodes don't enable full RBF, there won't be any new chain and we won't have any hard fork.
It's possible that a transaction exists in a mempool while it doesn't exist in another mempool, but all nodes will still have the same blockchain.

Odusko, it seems that you have shared a wrong link. It's about stock market and has nothing to do with your topic.
Anyone who is interested in this topic can visit the link below for more information.

Binance.US Launches Zero-Fee Bitcoin Trading

The problem here is that you can't create the watch-only wallet which you need for making the unsigned transaction.
Electrum doesn't support importing public keys and if you import the address instead of that, it won't show P2PK transactions.

Trustwallet gives you a 12-word BIP39 seed phrase and that's compatible with electrum.
From my understating, OP had two different wallets and now he/she has no access to the seed phrase of the one holding 17 BTC.
 

I feel he/she is referring to transaction ID of the deposit made to the wallet.

If I have got o_e_l_e_o correctly:
The non-RBF transaction is invalidated with double-spending its unconfirmed parent (which is RBF-enabled).
With invalidating the parent, the child (which was spending the same UTXO as the coinjoin transaction) is removed from the mempool and the coinjoin transaction can be propagated and confirmed.

The tool can brute-force your seed phrase if you have missed some words.
Since you don't know any of the words, that's not possible.


No, there is no way to recover the wallet if you don't have the seed phrase.
You can only recover the wallet you have its seed phrase.

Your feeling is right. It's not secure to keep your coins on an exchange.


You can also use electrum. It's open-source and give you full control over your fund.
(Download electrum only from its official website and do not forget to verify your download.)

Note that electrum only supports bitcoin and if don't create your wallet on an air-gapped device, it wouldn't be as secure as a hardware wallet.
For 100% security, you should use electrum on an air-gapped device or as already said, use a hardware wallet.


Then you will have to a make transaction and move your coins to an exchange.