The software to use is either bfgminer (https://bitcointalk.org/?topic=877081) or cgminer (https://bitcointalk.org/index.php?topic=28402.0). Those will work with any ASIC that you get, and if you compile it yourself, will also mine using your laptop's GPU and CPU. Neither support CPU mining by default (needs to be enabled in compilation), but bfgminer does support GPU mining whilst cgminer does not by default.

I do not think that quantum computers have/will have a significant advantage over classical computers when it comes to hashing. There are limits to what they are better at. Quantum Computers are not faster at everything, contrary to popular belief.

It looks like you need to enter your address in order to play and guess. The guess is only valid if they see that address in a transaction which spends to their address. Or that's what it seems like

What do you mean by evaluated backwards?

From what I understand, if I mine a block with 200 transactions and I submit a guess for 200 transactions and the transaction that goes with the guess is one of the transactions in the block I mined, then I win. But if the transaction isn't in my block of 200 transactions and instead it goes into someone else's block with 300 transactions, then I lose. Yes? If that is the case, then miners can cheat.

You will, Armory uses Bitcoin Core's bitcoind, which itself needs to download the whole blockchain. Armory cannot function without Bitcoin Core since it does not do any network stuff, instead it does that through Bitcoin Core.

I'm pretty sure it is just bad counting. I think it fills the keypool until the specified index (number you entered) has a key. The problem is that it starts counting from 0, so when you get to say index 10000, the size is actually 10001.

I have to say, the device seems pretty pointless. It seems like it is for developers and that the mining is to provide said developers with some Bitcoin to test stuff out on. It looks like it is a dedicated full node with mining capability so that the developers will have some coins to work with for testing. Honestly though, I really don't see the point of it. Testing can be done with the testnet.

As for the OP's question, I think that all of the devices are connected to the same 21 inc pool. Any blocks that pool mines will be attributed to 21 inc, and the resulting payout goes to the developers who are running the device, as normal pools do.

Use a wallet that does not send dust. Most wallets will give you a warning if you attempt to send a dust output. It is up to you to heed that warning and not send a dust output. Fees don't matter if there is a dust output.

The chances are very low. The dust output is considered dust under the new defaults (2730 satoshis) and under the old defaults (546 satoshis) so I am surprised that you even received it. Most new nodes would not relay a transaction with such a small output. I highly doubt that it will every get confirmed.

Not charged back, but the transaction will be dropped from the network, as long as no one is broadcasting it. Then it essentially becomes able to do a double spend since virtually no one will have that transactions

Your wallet will continue to broadcast the transaction while it is open, thus making it impossible for the transaction to drop. Since you are actually the receiver, you need to tell the sender to do that and then resend it.

As the receiver of the transaction, there is absolutely nothing you can do. You must wait for it to be confirmed, or wait for the sender to do a double spend and send the transactions but without the dust output.

It looks like you were victim to the transaction malleability attack. Someone malleated your transaction and it looks like one of the two transactions (original or malleated) was confirmed, so your coins are where you sent them, nothing except the txid changed. The problem is that Armory saw both transactions, and the one that is unconfirmed will never be confirmed (it is considered a double spend). To clear it, go to Help > Clear All Unconfirmed. That will also removed the other unconfirmed transaction you have.

Ok.

Can you guys at least put out an update for lowS signatures so that armory will work with bitcoin core 0.11.1?

The transaction shouldn't be affecting anything. You might just have a slow sync. If you routinely check and you see that number increasing, then you are still syncing and nothing has frozen. If it is stuck, try restarting electrum and maybe the computer.

Is that for you or the server? Whichever it is, it isn't synced since the block height is 380000+

Would you guys be able to republish it so that we can make aaacommunity developed version based on what has already been written?

Project development or digital goods

So it's no longer on github?

When will this resume and what exactly stopped its development in the first place?

Where can I get it?

What do you mean by

The answer is probably not (although that could change if you clarify). Miners would a) not want to waste time and electricity not mining and b) ASIC miners are highly specialized and can only do SHA256d (d for double) hashes, which means that they can't do normal sha256 hashes.

Hard to say. The github hasn't been updated in several months but the other developers of armory have been active on this forum recently.

Theoretically, yes. They would need custom software on their mobile device that would allow them to spend the same inputs again and with a different fee.