That means that the transaction could be replaced in the future and thus be dropped from the mempool and never confirmed. This means that it either opts into RBF or it is part of a chain of unconfirmed transactions.

You can no longer use the bitcoind command to send RPC commands to the RPC server. Instead you must use

The developers are not very good designers and only make the GUI in such a way that can be used, but may not provide the best user experience. If you can make it better or add themes, then please do and submit a pull request.

Not likely. The old wallets compatible with the wallet will still be available. Also, new versions of Armory will continue to support the old wallet format for a while.

No. Armory's HD wallet, as of now, does not use a standard HD wallet. Thus there are no apps that are compatible with Armory's wallet. However, that may change in the future when Armory changes to use BIP32/44 HD wallets which are standard and have apps that can watch such wallets.

That is four people out of 17 primary contributors, not to mention that there are hundreds of other people who occasionally contribute. However, only one of those 4 has commit access, and none of those 4 are project maintainers. Since those 4 are not part of the project leadership (not maintainers), they cannot be considered to "basically represent core", they can't decide the direction that Core goes in and they can't force any changes to Core that other contributors are against.

Unfortunately, no, there is no way.

Are you being serious or joking? The core developers have done everything they can to keep Bitcoin from running directly into the ground. They are constantly trying to improve Bitcoin and think of new ways to improve Bitcoin.

Pretty sure that it is the first. Segwit has been tested in multiple testnets though and in a completely separate Elements Sidechain.

You're on a Mac, yes? If so, open up the Terminal app. Then type:

Once Bitcoin Core starts from this command, you should see that all of your unconfirmed transactions will be gone. The same behavior with those four transactions never happening should still happen.

Says who? I don't see it in any part of the agreement that segwit and a hard fork will come packaged together. If you are referencing antpool, then they are breaking the agreement as the agreement does not say that segwit and the hard fork will be activated at the same time.

There isn't really an logic to it. It may simply be that the miner's node is set to a point where many of those unconfirmed transactions are rejected. Additionally, there are many many empty blocks that are mined. IIRC if all blocks had the same number of transactions, there would be no backlog and no blocks would ever be full. One of the easiest ways to increase capacity is to have miners not produce empty blocks.

Blockstream does not "basically represent core". That is a common misunderstanding spread by r/btc FUDers.

The Hong Kong agreement explicitly states that the hard fork code would be ready within 3 months of Segwit's release, something that has not happened yet. The miners agreed that they would run Segwit in production in the meantime. IT DOES NOT SAY THAT BOTH A HARD FORK AND SEGWIT WOULD BE DELIVERED AT THE SAME TIME.

Yes, that is what I meant.

If you feel comfortable with invalidating these three transactions: https://blockchain.info/tx/c76068178d3e0cec7660cfea13b0326516707d7b2410e4987441026eb6662588, https://blockchain.info/tx/5506dd186fc7ef3f5b3cd24677927d77773b103397c8b747f94fad8a9255bf32, and https://blockchain.info/tx/4c6a6058ba14bff85323d50844ca52d4a25ffa72464555184568888f8480c7e2, then you can remove the one I linked to earlier from your wallet and be able to resend the Bitcoin from that transaction. If any of the above three transactions are also yours, then the coins sent by them will also reappear in your wallet.

The following will essentially revert your wallet to whatever it was like before any of the linked to transactions existed. Just go to Help > Debug Window and then the Console tab. In the box at the bottom, type

This command will remove that transaction and the above three from your wallet, thus allowing you to resend the Bitcoin locked up in those transactions. It will be as if those four transaction had never even happened in the first place.

As was mentioned in the other thread, your transaction is dependent on this transaction: https://blockchain.info/tx/152a65239eec41036614612be23f124f9ef861b30b521c57c9ff12c8c773b792 confirming. Is this transaction sent by you? If so, then there are solutions, otherwise, there is really nothing you can do.

That error means that the fee was too low or the transaction was unconfirmed for too long that blockchain.info decided to remove the transaction from their database. This does not mean that it was dropped from the network. Also, it appears that the transaction you mentioned in the other thread is still on the network.

What you need to do are actually 2 commands.

The first is to unlock your wallet with
where <passphrase> is your passphrase. The 120 indicates how long your wallet will remain unlocked, in this case 120 seconds (2 minutes). You have 2 minutes to do the next command.

This will sign the transaction.

After months of testing, coding, and work, Segregated Witness has finally been merged into Bitcoin Core: https://github.com/bitcoin/bitcoin/pull/8149.

Now that it has been merged, there are a few things that need to be done before release, and many things that will come after Segwit that builds upon it: https://bitcoincore.org/en/2016/06/24/segwit-next-steps/.

What was the command that you did?

If you know the M-of-N of the lockbox, then you can spend from it. Armory uses standard multisig for lockboxes, so any wallet that supports multisig can be used.